RobAmy wrote:
Dave you need to log in to your account and then the upgrade is $79.00 vs full price. If not logged in and you hit upgrade it is not discounted.
Thank you Rob!
Nice of them to let you know this, especially when you're asked if you want to upgrade when you open the program.
docusync wrote:
Are you on MacOS or Windows? Drag and drop of a bunch files works fine on Windows 10. This is a part of my workflow. I can do a video screen capture for you when I get back home on Monday I have no idea about MacOS or Windows 11 though...
stanj wrote:
Mac all the way.
docusync wrote:
Apparently they screwed something up for Mac
Actually it works on the Mac as you'd expect, as long as you drag _only_ raw files. God forbid you also include an XMP file or some other garbage file that may be alphabetically sorted within your images. It just silently refuses, unlike just about any other application that will simply ignore the unwanted files.
I agree that in terms of NR, ON1 may be slightly better, but the way they handle color profiles (or rather, don't) is a no-no for me. The color is baked in, WB sliders in LR are relative like as if you're editing a JPG, not a raw file. You get the dynamic range, but the color adjustments are severely impacted. I provided this feedback and passed.
Well... I just tried running 8 images through DXO2 and the first 4 DNG files are pure black frames and the last 4 seem to have been processed correctly.
Not happy with the black frames on 50% of the images but boy am I loving the new UI. All the images simply started popping back into LR and even pulled in my previous edit work and image ratings. This is what it should have always been like! Such a relief from the previous BS I noted earlier.
Edit: Just noticed the correctly processed images did not pull in the correct Profile and defaulted to Adobe Color rather than Camera Standard that I have the raws et to.
Another strange thing happened during the DXO processing.
About halfway through the 8 images I noticed a Pop-up appear very briefly in the lower right of my screen. It said something about my graphics card blocking access from unknown program or something like that. I immediately clicked on this pop-up to try to get it to open so I could read what it was saying but it never opened so I have no idea what that was all about.
It seemed to have been processing faster until this pop-up appeared then seemed to slow down.
Running Windows 10 Pro with a GeForce RTX 2060 GPU
lighthound wrote:
Edit: Just noticed the correctly processed images did not pull in the correct Profile and defaulted to Adobe Color rather than Camera Standard that I have the raws et to.
This is a known issue: if your original raw image had an explicitly set profile (as in, you changed it from default), it will be correctly preserved - at least that's the case with R5 files. However, if you just imported the R5 files and the default profile is set for an image (whatever it is - even if you changed your default say to Color Fidelity), then the DXO DNG file will have the Adobe default profile set. It's weird, but it's part of my routine to batch apply the profile again before I do any work.
stanj wrote:
This is a known issue: if your original raw image had an explicitly set profile (as in, you changed it from default), it will be correctly preserved - at least that's the case with R5 files. However, if you just imported the R5 files and the default profile is set for an image (whatever it is - even if you changed your default say to Color Fidelity), then the DXO DNG file will have the Adobe default profile set. It's weird, but it's part of my routine to batch apply the profile again before I do any work.
Ah, ok. I have a custom import made so the Profile is set to Camera Standard on import, so what you are saying is that DXO will only pull in your profile if you change it once the image is already imported into LR.
I can live with this glitch I suppose until they can get it corrected. What is driving me crazy is this black frame result that I keep getting on those first 4 images. I've tried running them through DXO individually now several times and they just come back as black frames. I recall having this same issue when I first got DXO last year. I contacted their support group but never received a definitive answer for the issue. After the first or second update last year that problem went away. Hopefully they'll fix it soon on this release.
lighthound wrote:
Ah, ok. I have a custom import made so the Profile is set to Camera Standard on import, so what you are saying is that DXO will only pull in your profile if you change it once the image is already imported into LR.
... AND actually changed by hand (or by explicitly applying a preset). My default profile is "CF Neutral V5", and every R5 CR3 imported into LR gets it without any interaction. If I just process the image in PR, the DNG will be whatever Adobe default. You have to manually change the CR3 profile to say "CF Landscape V5" in LR and then process the CR3 in PR for it to "stick". I actually think this is more of a bug in LR than in PR, but we're just splitting hair anyway.
stanj wrote:
It depends on the GPU. The M1 machines use the GPU basically fully, I am told Nvidia GPUs are also loaded, but other Macs don't use Nvidia hardware, and thus don't have CUDA, and thus... suck. My M1Max runs at the same speed as my MacPro, which is not because the GPU there is so bad, but because it doesn't do CUDA and DXO requires it for maximum performance.
It's lazy engineering but for a small company it's pretty standard. What miffs me more is what I would call blatantly false advertising, since I have an M1Pro and an M1Max machine and neither shows any performance gains whatsoever, so their claims are deceptive....Show more →
I don't know whether I had previously tested on a non-M1 optimized version but after your comments I went back to see again and indeed the GPU is ~90% during about 60-70% of the time on my M1 Max MBP. Previously I had seen very low <40% utilization.
stanj wrote:
Actually it works on the Mac as you'd expect, as long as you drag _only_ raw files. God forbid you also include an XMP file or some other garbage file that may be alphabetically sorted within your images. It just silently refuses, unlike just about any other application that will simply ignore the unwanted files.
I agree that in terms of NR, ON1 may be slightly better, but the way they handle color profiles (or rather, don't) is a no-no for me. The color is baked in, WB sliders in LR are relative like as if you're editing a JPG, not a raw file. You get the dynamic range, but the color adjustments are severely impacted. I provided this feedback and passed....Show more →
It's too bad ON1 does not have the same option as Topaz. "Disable RAW colour correction".
Jesse Evans wrote:
I don't know whether I had previously tested on a non-M1 optimized version but after your comments I went back to see again and indeed the GPU is ~90% during about 60-70% of the time on my M1 Max MBP. Previously I had seen very low <40% utilization.
As for PureRaw I tried both the Auto and M1 options on my M1 MacBook Air. Auto was much faster.
Zenon Char wrote:
It's too bad ON1 does not have the same option as Topaz. "Disable RAW colour correction".
I have a question. Are you finding this the colour issues with ON1 NN 2021 or 2022. I just got the version update the other day. Still checking it out.
That's too bad. I've been messing around with all 3, PureRaw, Topaz and NoNoise. In my opinion NN has the best fine detail but you have to use a RAW file. ON1 says it is working to obtain the same fine detail for DNG and Jpeg. Still a cumbersome process compared to PureRaw. Obviously NN is tuned for Raw Photo. Hopefully some day they look into better integration with LrC like DXO did.
Just ran a fresh new set of 11 images through DXO2 and yet again the first 4 images came back as black frames just like it did the first time the other day.
I have to exit/close LR then go back into LR and select those 4 black frame and delete them, then select the first 4 images that were messed up and run it through DXO2 again. Only then do they come back as processed images.
stanj wrote:
Nope, then I still don't get to choose my color profile in LR, and WB is in relative terms, not in Kelvin.
I contacted NN support hinting they may obtain more customers if the DNG sent back to LR from allowed access to Adobe or Canon profiles like DXO does. Below was the reply. Not sure we will ever see this. Since I'm a hobbyist slight colour shift does not bother me but it is a disappointment after waiting for a year for Adobe to add camera profiles back to the CR3 files.
When NoNoise creates a DNG from being launched out of Lightroom, we apply our color settings to the file. You won't be able to select any specific color profile (that you can for an original RAW), as this has already been baked in to the DNG file. There will be differences in color between the original RAW file and the DNG returned back to Lightroom. (You'll need to use the standalone app if you want closer color matching) Also, by default we apply lens profile corrections to the DNG when opened into NoNoise.(You can turn this off in the NoNoise preferences if you do not want this to occur) However, Lightroom applies lens profiles in different ways for different manufacturers.The DNG created by NoNoise will not have any Lens Profile automatically applied in Develop. However you can manually enable this to override and apply a profile.This is how the DNGs will be handled when used as a plugin from Lightroom.
@RobAmy DxO quietly updated PR (1 & 2) to support the RF400/2.8 with and without TCs, I can only imagine that some other big whites are now also supported. Just FYI.
stanj wrote:
@RobAmy@ DxO quietly updated PR (1 & 2) to support the RF400/2.8 with and without TCs, I can only imagine that some other big whites are now also supported. Just FYI.
Nice I did not know that, thanks Stan. The RF 600mm is there also
lighthound wrote:
Just ran a fresh new set of 11 images through DXO2 and yet again the first 4 images came back as black frames just like it did the first time the other day.
I have to exit/close LR then go back into LR and select those 4 black frame and delete them, then select the first 4 images that were messed up and run it through DXO2 again. Only then do they come back as processed images.
Anyone else having this issue?
I had the same problem with DXO PR1 and my R5 when I was processing more than 5 files at a time. It happened all the time. Then, one day, it was fine. I think DXO fixed it with an update. Since buying my R3 and upgrading to PR2, I haven’t had the issue yet. Fingers crossed I don’t.
RKnecht wrote:
I had the same problem with DXO PR1 and my R5 when I was processing more than 5 files at a time. It happened all the time. Then, one day, it was fine. I think DXO fixed it with an update. Since buying my R3 and upgrading to PR2, I haven’t had the issue yet. Fingers crossed I don’t.
Yep, same here. The black frames seem to be a thing of the past now. I haven't had any issues in some time now.
I have no idea about MacOS or Windows 11 though...