It seemed like a good idea at the time, but I just can't get anything done with ASP. 2 big issues that nobody has been able to adequately address:
1. When I use the external editor option (Gimp), Aftershot only sporadically updates with the edited version I did in Gimp. I've tried every variation on saving the files. 8 bit tif, 16 bit tif, jpg, blah blah blah.... and there is no consistency to the way AS either shows or doesn't show the files after I've edited them. This makes a professional workflow pretty much impossible.
2. Noise / demosaicing: I was willing to put up with slightly lower performance on this one, because of some of Aftershot's advantages... but Lightroom truly is superior to Aftershot in this department. My editor has been questioning me about the noise in my images and, in conjunction with issue #1... it looks like Aftershot has proven itself to be a half-baked nice idea, but totally unsuitable for a production environment.
If anyone knows of any fixes to either issue (particularly #1) let me know. Otherwise I'm going to be reinstalling Windows and bidding farewell to LInux.
Aftershot = coat hanger abortion
-
tintin
- Posts: 169
- Joined: Thu Jan 12, 2012 2:45 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- processor: Ryzen R5 3600X
Re: Aftershot = coat hanger abortion
to question 1)
in file system mode you can easily press "F5" to update your folder tree/files.
in catalogue mode i don't know
for question 2)
did you already try the "wavelet denoise" plugin?
br,
tintin
in file system mode you can easily press "F5" to update your folder tree/files.
in catalogue mode i don't know
for question 2)
did you already try the "wavelet denoise" plugin?
br,
tintin
-
ormdig
- Posts: 56
- Joined: Mon Jan 16, 2012 7:31 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Asus Sabertooth X58
- processor: Intel i7-950 3.72Gh
- ram: 24Gb
- Video Card: Nvidia GeForce 460
- sound_card: Realtek HD audio
- Hard_Drive_Capacity: 4.5 Tb
- Monitor/Display Make & Model: HP LP2475w, HP LP 2065
- Location: Arkansas
Re: Aftershot = coat hanger abortion
+1. When ASP is open and edits or additions are made in another program or file system, ASP's file system has to be refreshed to show the new entries. As to noise, I have yet to find any editing program that can handle significant noise of any type without losing resolution. ASP is still unmatched in speed, both in editing changes and batch conversion.tintin wrote:to question 1)
in file system mode you can easily press "F5" to update your folder tree/files.
in catalogue mode i don't know
-
jp_wieseth
- Posts: 6
- Joined: Wed Apr 11, 2012 8:29 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: ASRock 890GX Pro3
- processor: AMD X6 1100T
- ram: 16GB
- Video Card: ATI HD6670
- sound_card: onBoard
- Hard_Drive_Capacity: 2 TB
- Monitor/Display Make & Model: Samsung SyncMaster S27A850D 27"
Re: Aftershot = coat hanger abortion
to question 1)
ASP cannot view/open compressed TIF Files.
jpwieseth
ASP cannot view/open compressed TIF Files.
jpwieseth
Re: Aftershot = coat hanger abortion
Only Tiff with JPEG compression can't be read by ASP.jp_wieseth wrote:to question 1)
ASP cannot view/open compressed TIF Files.
LZW compression works fine.
Darktable 3. Bye bye aftershot.
Re: Aftershot = coat hanger abortion
in catalogue mode, Alt+P to rebuild thumbnails.tintin wrote:to question 1)
in file system mode you can easily press "F5" to update your folder tree/files.
in catalogue mode i don't know
Darktable 3. Bye bye aftershot.
Re: Aftershot = coat hanger abortion
I'm familiar with F5 command. It does not produce anything. Here's what's happening in a little more detail:
1. I'll right click on an image in ASP and open it in GIMP.
2. Image converts automatically to 8 bits, that's fine. As I'm doing that, on my other monitor I can see the in ASP, the new file being created. It shows up with the filename "DSC_1234_edit.tif" and the image placeholder is a white box with a big X in it. SO... it's totally clear that ASP is watching that directory and is "aware" of the file.
This is where things start behaving inconsistently:
3. For the sake of these experiments, I've just been using the brush tool and writing a letter on the background layer of the image, then exporting as a tif file. Gimp is asking me if I want to overwrite "DSC1234_edit.tif". I say "yes". I then go to close the file, and it asks me if I want to save. Since I already exported, I choose "close without saving".
I'll go back to ASP, and sometimes the edited file shows up in the directory, perfectly. Other times, as soon as Gimp is done exporting the file, the placeholder that showed up in ASP disappears. Pressing f5 doesn't bring it back. Rebuilding thumbnails doesn't bring it. Sometimes deleting the cache and restarting ASP will make it appear again, sometimes it won't.
If I happen to create any layers in the image in GIMP, I can be certain the image won't show up in ASP. (and yes, I"m flattening the image down all the way and exporting as a .tif file). The only way my edited image has a CHANCE of being recognized by ASP is if the edits happened on the background / base layer. As you know, this is a totally unrealisiic scenario. If you are going to be doing edits in gimp, some layers are going to be happening.
Are there any clues to this mystery that I may be overlooking? Thanks everyone. I really do love the speed and efficiency of ASP, but if I can't reliably access edited files, it's totally unsuitable for a professional workflow.
1. I'll right click on an image in ASP and open it in GIMP.
2. Image converts automatically to 8 bits, that's fine. As I'm doing that, on my other monitor I can see the in ASP, the new file being created. It shows up with the filename "DSC_1234_edit.tif" and the image placeholder is a white box with a big X in it. SO... it's totally clear that ASP is watching that directory and is "aware" of the file.
This is where things start behaving inconsistently:
3. For the sake of these experiments, I've just been using the brush tool and writing a letter on the background layer of the image, then exporting as a tif file. Gimp is asking me if I want to overwrite "DSC1234_edit.tif". I say "yes". I then go to close the file, and it asks me if I want to save. Since I already exported, I choose "close without saving".
I'll go back to ASP, and sometimes the edited file shows up in the directory, perfectly. Other times, as soon as Gimp is done exporting the file, the placeholder that showed up in ASP disappears. Pressing f5 doesn't bring it back. Rebuilding thumbnails doesn't bring it. Sometimes deleting the cache and restarting ASP will make it appear again, sometimes it won't.
If I happen to create any layers in the image in GIMP, I can be certain the image won't show up in ASP. (and yes, I"m flattening the image down all the way and exporting as a .tif file). The only way my edited image has a CHANCE of being recognized by ASP is if the edits happened on the background / base layer. As you know, this is a totally unrealisiic scenario. If you are going to be doing edits in gimp, some layers are going to be happening.
Are there any clues to this mystery that I may be overlooking? Thanks everyone. I really do love the speed and efficiency of ASP, but if I can't reliably access edited files, it's totally unsuitable for a professional workflow.
-
afx
- Posts: 1675
- Joined: Thu Jan 12, 2012 1:38 pm
- System_Drive: N/A
- 32bit or 64bit: 64 Bit
- Video Card: FirePro 4900
- Monitor/Display Make & Model: NEC PA301w, ColorMunki
- Location: München
- Contact:
Re: Aftershot = coat hanger abortion
Looks like the flatten step in Gimp is not alsways perfectly executed. Try analyzing the TIFFs with imagemagic and other tools.
cheers
afx
cheers
afx
Send bugs to the Monkey // AfterShot Kickstart Guide // sRGB clipping sucks and Adobe RGB is just as bad
Bibble since 2005 // W7 64 on quad Phenom // Ubuntu 14.4 on quad i7 and dualcore AMD // Images
Bibble since 2005 // W7 64 on quad Phenom // Ubuntu 14.4 on quad i7 and dualcore AMD // Images
