I usually work directly with nikon raw file, I don’t convert to other formats before exporting, and when I press the nik collection button I would like to have a copy in the format I need to work in nik made immediately, automatically on request with changes already made or not.
And the second - my catalog is divided by days of shooting and it takes a very long time even this day is loaded into the program, because sometimes there are 2 - 3 thousand photos. I don’t want to make my catalog by hours)))))
I would like the program to calculate changes in the background, and display only those files that are visible in the window. That would speed up loading for sure. And work.
not that things constantly shouldn’t be improved, but there is a lot of wishful thinking in your post. I just cannot image you want 1000+ files converted to TIFF in the background to then notice, oh my storage is full / I don’t want all of them or sth else.
What is your workflow so far? What applications have you been using?
Good afternoon.
When I open the program, it takes a long time to load until the program reads all the photos in the catalog. And it is impossible to view them, because they jump with icons of circles and questions. I have all the photos on my hard drive and all this takes a lot of time, and if you consider that I have 5 hard drives and 600 000 photos, it’s a nightmare. Therefore, the proposal that what is visible in the program window, those photos were processed faster, and the rest, in the background. Specialists on the forum write that the program should check the changes. So let it check in the background. That was the first question, and
the second - I do not convert files from raw format when processing - but sometimes I need to apply processing in nik, there is a button, but it does not see raw files, I must first convert and then open in nik. Suggestion to make the file automatically converted when you press the nik button.
In principle, the developers should probably rather introduce a small cataloger into the program, with small previews stored in memory. This would strengthen it on the market. And with the possibility of downloading from a camera or flash memory.
Perhaps I’ve misunderstood the intent of what you are asking for with regard to using the Nik Collection from within PhotoLab . In the Nik Collection settings from within PhotoLab., you can set the export file type to Tiff or JPEG. Once that is done, when you edit a raw file in PhotoLab and use the Nik button It automatically exports the raw file to Tiff or JPEG and opens it for editing in the selected Nik module.
Yeah, but now it keeps making copies every time I click on a Nik.
and I would like NIK to ask whether to make a copy or work with this one pic.
I basically found a way - the first is export RAW to APP, and the second in the NIK no export.
But it is a way with many buttons. I would like it to be simpler.
Hi, thank you
If I select the RAW file, the nik does a tiff.
If I select the RAW file again, this screen saver appears… just like in your picture.
But if I select tiff, it immediately makes a second tiff… And I don’t need a second one… I need to process the first one into a nik once again… And I need a question from nick process this tiff or to do the second tiff.
Hi Alex,
when I asked about your workflow and the apps you use, I wanted to get an idea if you are still testing PL or have a license, if/which plugins you use, which Nik version, etc.
As @mwsilvers explained, the Nik Collection expects JPEG or TIFF files, meaning if you haven’t already, a raw developer (e.g. PL) will need to convert your file first.
If to avoid a 2nd exported file you can choose PL’s option to export the selected file(s) without processing
note
In Nik 7 you can add another tool without first returning to PL (to then export and apply again).
.
If you want to avoid conversion, you should check out FilmPack.
The FP standalone version has a browser to view the images in the opened folder (like PL, no need to import the images into a catalog) and you can apply one of the many presets (even in batch mode).
Then, if necessary, you manually adjust the available settings and can apply (but not adjust) some automatic functions (but only standard noise removal, unlike PR/PL).
The output of the standalone version is saved as JPEG or TIFF.
If you purchase a FP license, you can unlock the FP features already built into PL. The main difference is that in PL you continue to work non-destructively until you finally export your file(s) to JPEG or TIFF.
.
You may want to wait and see what awaits you this fall before making a decision.
Wolfgang
Hi, Wolfgang.
I have purchased versions of Affinity , Pixelmator Pro , Capture one , Dxo 7 and Nik collection 6 as well as the old LR 6 which oh my god still works on my Mac with Ventura 13
I upload photos to a directory on disk with LR, it sorts the files well and I am completely satisfied.
Even processing suits me and bad that Adobe is doing everything to overthrow my program from the computer, and it still works every time I change the operating system)))))
Capture one 23 I do not like it at all, it has a broken catalog inside and in principle do not like.
Affinity 1 requires strange file conversions to work. I don’t know about the second, but I don’t use the first.
So I often use Dxo but went to the forum and saw that there is a thread requesting functions.
So please i ask to him think about the catalog, or at least uploading with storage of previews. It would be very easy and speed up the work, in my opinion. Then coordination with their own product - Nik, so that by clicking on the button may asks whether or not to do the conversion, and if it is already there, then open this file with all the presets or make a clean new tiff.
I do not write about the fine-tuning of the Dxo program and different functions - a lot of things have already been written about it here. I more or less like everything.
I hope the thirst for profit will not lead to monthly payments for licensing. Because of which Lightroom and Capture Ones are no longer with me.
And yes , my photos are stored on external disks - 24 tb originals and 24 tb archive and broken down by years months and days of shooting . And some days from 1000 to 5000 photos. So the question of opening even one day in the catalog is acute)))))) To decide which photo to process, you have to wait for a long time when they stop jumping in the Dxo))))
As I have said several times, when Nikon Capture NX2 was made by Nik, there was a wonderful integration of Color Efex into it.
You could apply all the Color Efex filters and effects directly into Capture NX2, non destructively, and with no need to export a TIFF or a JPEG: they were simply applied on top of the RAW development settings, as an additional “layer”, in a completely transparent way and without leaving the Capture NX2 interface.
And that was… 15 years ago.
PL doesn’t have this powerful and very easy to use feature, and it probably never will: it would require a complete rewrite of PL, with full integration of the Nik suite (or at least Color Efex) into its code.
Well, as you’ve noticed, PL displays developed files that replace the embedded JPEGs that are only initially visible. To avoid lag, I changed PL’s cache to reside on a separate 1TB NVMe M.2 SSD “scratch” drive, which is also where all my LR 5.7 catalogs reside. And my pics (in use) are stored on a internal HD. But I don’t have that many pictures, nor do I keep everything.
As others have reported, PL does not react that quick with more than 1000 (new) pics in one folder. While PL has been improved, I think you will have to look for another application.
And btw, if you can’t wait for the raw-files to be converted you have to use ooc JPEGs.
@Joanna
But when I see all my station performance setting when dicovering image directories at less than 100% (understand generally less than 20%) : cpu usage, drive usage, gpu usage, it seems there’s a lot of room for improvments.
…
But it probably could run more instances at the same time since nothing run at full speed.
Am i wrong ?
And clean this old bug that makes image brower change displayed images (jump back to the beginning of the list) when discovering directories (maybe pc bug only).