Please log in. To create a new account, enter the name and password you want to use.
If you supplied an email address when you signed up or added a email later, you can have your password reset.
This user name doesn't exist. If you want to create a new account, just verify your password and log in.
This user name exists. If you want to create a new account, please choose a different name.
Enter the current email address you have registered in your profile. You'll get an email containing your new password.
You have no email address in your profile, so you can't have your password reset.
Password reset. Check your email in a few minutes
That account does not exist.
The email address specified is not registered with this account.
Delivery to this email address has failed.
You can adjust memory allocation upwards in the "performance" options dialog. You may need to restart for this to fully take effect (not sure).
I'm not sure if 32-bit Photoshop will ever make more than 2gb available to a filter. (The field that exposes how much memory it has is signed...) Currently, a 7kx10k image will need almost 3gb to run, so I'm not sure that'll work anyway--we're coming up to hard 32-bit limits here (swap won't help).
Note that the greyc commandline defaults to tiling; to get the same type of filtering, you need to use -tile 0.
If you're hitting runtime errors, it's probably just out of memory; it wasn't handling OOM in a thread correctly. I've fixed this and I'll update it in a bit, as well as setting the PS hint that tells it how much memory it'll need (which may or may not matter; the documentation doesn't actually say exactly what this does).
I might try an overlapped tile version: work on tiles (horizontal slices, actually; simpler), but yank out much bigger pieces than are actually being processed to avoid tiling artifacts. This would be slower, though, as part of the work for each slice would be repeated twice.
petopeto
I'm not sure if 32-bit Photoshop will ever make more than 2gb available to a filter. (The field that exposes how much memory it has is signed...) Currently, a 7kx10k image will need almost 3gb to run, so I'm not sure that'll work anyway--we're coming up to hard 32-bit limits here (swap won't help).
Note that the greyc commandline defaults to tiling; to get the same type of filtering, you need to use -tile 0.
If you're hitting runtime errors, it's probably just out of memory; it wasn't handling OOM in a thread correctly. I've fixed this and I'll update it in a bit, as well as setting the PS hint that tells it how much memory it'll need (which may or may not matter; the documentation doesn't actually say exactly what this does).
I might try an overlapped tile version: work on tiles (horizontal slices, actually; simpler), but yank out much bigger pieces than are actually being processed to avoid tiling artifacts. This would be slower, though, as part of the work for each slice would be repeated twice.