After running a few hundred images through the new version, a few observations:
Image quality has improved somewhat. Sharpening artifacts were something to beware of always whichever sharpening was used, basic or wavelet, especially in downsized images or if noise reduction was used. Same goes for NN or plugin. I have experimented with higher settings than I would normally use and a definite improvement. For my D90 a push in dim lighting to 1600 ISO is possible without much loss of resolution. For D7000 I don't see any loss of resolution when completely getting rid of noise at 1600.
I don't see color shifts like I sometimes did in exposure changes, especially in mid and lowmid tones. They were subtle but there, especially in red region.
Edit changes are still instantaneous for me so no slow downs there. I bought a D800 last week which had me dreading the p ossible slow downs as files seem to be much larger than advertised. Raw files average, so far, 60-100 MB. Still way faster than other editors in this regard.
That being said, some obvious problems with plugin incorporation and open cl. I usually use the straighten tool, if needed, as one of the first changes. However after Bibble 5 came out have had no problem using it at anytime in the process. Yesterday I realized at the end of editing an image it was slightly off axis. I moved the straighten tool one key stroke and the image went blank and ASP crashed. Shades of Bibble 4. I restarted several times and same thing. I created a new image, unedited and no problem. i could straighten as much and as fast as I wanted. Edited image and tried again and it crashed. I haven't bothered to see what is causing it as I can straighten before editing and it will work.
Open cl is a joke and obviouisly was not ready for incorporation into a release version. Output on the new version is way slower, even with it disabled. I will say that it handles my D800 jpeg output (25-50 MB) just as fast per MB as my D90 (3-5MB) or D7000 (4-15) average at 96% of full size uncropped. My fastest setting is on high, but really not a lot of difference between any of the settings. So far size of image of number of images ( I use a maximum setting of 5 at one time) don't seem to effect output time. it's just plain slow, slow, slow. They have messed up one of the stellar aspects of Bibble's main attractions.
I hope somebody is working on this but am still checking out other editing options.
I realize some Linux users are having problems with installs but how about you guys and gals who are using it? Have you noticed any editing changes?
Some observations on 1.1.0.30
-
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
-
Denis de Gannes
- Posts: 52
- Joined: Fri Jan 13, 2012 4:57 am
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Gigabyte- G31MX-S2
- processor: Intel Core Quad CPU Q6700 2.66 GHz
- ram: 4GB
- Video Card: On Motherboard
- sound_card: nk000
- Hard_Drive_Capacity: 1820 GB
- Monitor/Display Make & Model: AOC 2216Sw
Re: Some observations on 1.1.0.30
For what its worth, Adobe Photoshop Lightroom does not have Open CL support and indications are it requires major change to the existing structure and will not be available in the near future.
Denis
Camera: Oly E300 & E510; ZD & OM Lenses; Panasonic G3
Software: PSP x4; Corel Video Studio Pro X3; PS CS6; SilkyPix 4; ASP 1; LR 5.4; Capture One Ex 7; Qimage Ultimate; VueScan.
Camera: Oly E300 & E510; ZD & OM Lenses; Panasonic G3
Software: PSP x4; Corel Video Studio Pro X3; PS CS6; SilkyPix 4; ASP 1; LR 5.4; Capture One Ex 7; Qimage Ultimate; VueScan.
-
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: Some observations on 1.1.0.30
Sounds a bit high.ormdig wrote: I bought a D800 last week which had me dreading the p ossible slow downs as files seem to be much larger than advertised. Raw files average, so far, 60-100 MB.
Switch on lossless compression.
I bet an interaction with a plugin that performs spatial changes.I haven't bothered to see what is causing it as I can straighten before editing and it will work.
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
-
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: Some observations on 1.1.0.30
Spatial changes makes sense. I had cropped it. Images are 14 bit uncompressed as I am still testing the camera. Will adjust to what I am shooting and the desired outcome when I am ready to use for shoots. Memory may be "cheap" but it ain't that cheap. Purchased 24-70 and 70-200f2.8 with it. Haven't even tried my primes yet but am slack jawed at resolution. The hype is well earned.afx wrote:Sounds a bit high.ormdig wrote: I bought a D800 last week which had me dreading the p ossible slow downs as files seem to be much larger than advertised. Raw files average, so far, 60-100 MB.
Switch on lossless compression.
I bet an interaction with a plugin that performs spatial changes.I haven't bothered to see what is causing it as I can straighten before editing and it will work.
cheers
afx
-
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: Some observations on 1.1.0.30
Apart from slightly different processing times saving and loading the images, the lossless compression has no impact at all (in contrast to the older lossy compression, but even there, the impact was mostly irrelevant on the older cams, that might be different today).ormdig wrote:Images are 14 bit uncompressed as I am still testing the camera.
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
-
tundraquad
- Posts: 97
- Joined: Tue Jan 17, 2012 4:25 pm
- System_Drive: N/A
- 32bit or 64bit: 64 Bit
- Location: Canada
Re: Some observations on 1.1.0.30
The only consideration would be if you shoot wildlife with actions, where fast continuous shooting is required.
So long.
So long.
-
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: Some observations on 1.1.0.30
Out of curiousity, how much time does the compression add to write speeds (using 1000x/150MB/s compact flash card) and does this transfer into noticeable slow down? D800 isn't exactly a barnburner anyway so I'm thinking I wouldn't notice any slowdown. I did go to lossless compression which resulted in a reduction in file size to 45-50MB on average. I can live with that.tundraquad wrote:The only consideration would be if you shoot wildlife with actions, where fast continuous shooting is required.
So long.
On a related note, since my images haven't needed much if any processing so far I have been using just basic tools and the conversion speeds with open cl, high, if NO plugins are used are phenomenal. .75-1 sec per image on 15-45MB jpegs. I haven't done any tiffs so far, I am still evaluating the camera/lenses. If I use ANY plugin the speeds drop through the floor. I updated all my plugins, installed the plugin manager, it doesn't make any difference, slow, slow slow. I have gone through every plugin I have, using the same image, one at a time and it is the same with every plugin. Drastic increases in conversion time. It doesn't really hurt my workflow in actual use but does indicate a problem that needs to be addressed by the developers unless it is something that is peculiar to my system/program. Any ideas of what to check? Anybody have similar situation? Thank you.
Pete
-
tundraquad
- Posts: 97
- Joined: Tue Jan 17, 2012 4:25 pm
- System_Drive: N/A
- 32bit or 64bit: 64 Bit
- Location: Canada
Re: Some observations on 1.1.0.30
I can't give any exact speed number to you. I'm using D700 bodies & my cards are still x300 that I will replace in the future by the Delkin CombatFlash which are still slow cards. Also, I never compress the NEF's in winter shooting, since battery saving is a real concern for me.
The ASP plugins I'm using are mostly zText & Wavelet. I didn't notice any difference of speed w/ them. I never installed the PluginManager.
As a result I cannot really help you since the tools that we are using are different.
Good luck anyway!
The ASP plugins I'm using are mostly zText & Wavelet. I didn't notice any difference of speed w/ them. I never installed the PluginManager.
As a result I cannot really help you since the tools that we are using are different.
Good luck anyway!
