Would be nice to be able to create a stack from selected images so that they can be grouoped together to make editing easier. e.g. images that are part of a focus bracket or exposure bracket could be grouoped together to make things better organised and easier to see.
And why donât you use the âalbumâ function within PLâs library part? As itâs sorted (only?) alphabetically, you could create albums like â__stack 1â, â__stack 2â and so on, drag the RAW files into for as long as youâre working on them and then empty it to make space for the next project.
Or do you need permanent stacks of images?
That would be too messy - I use albums for other stuff and these might be a smaller part of an exisitng album. Permanent stacks makes things a lot tidier - just grouping bracketed shots together.
I unterstand. I use the source images for focus-stack only until the stack is ready and then include the result into the âmother albumâ, after that I delete the single images. I also used to keep the source images for âthe time some better technique is inventedâ. I donât do this anymore, it just clutters the hard drives. And except a stack has some scientific or historic relevance, I donât see the raw-material as untouchable.
Of course, some stacks are rather complicated, especially with shiny/glossy materials or metal, as the out-of-focus-parts pollute with their highlight bokeh the in-focus-parts. In Affinity Photo I can do some retouching, but as soon as I close the resulting image, that possibility is gone and if I missed a repair, I have to re-initiate the whole process.
Sure - I guess we all have processes that work for us but I learned very early on never to delete the original raw files - we differ in that respect.
I learnt so, too, but modified that dogma for stacks. Usually my cameras are set to a custom mode âFocusstackâ. Here they produce JPG and RAW and an even number of images (like 20) as that makes it easier to group them afterwards by using the labels of Mac OS.
If Iâm happy with the first JPG stack ooc, the RAWs have to go. If not, itâs time for the JPGs to say goodbye and being replaced by new ones from edited RAWs. Stacking is a lengthy process, often not suitable for moving subjects, and also difficult to pre-visualize in sufficient time.
And if I need more than 1:1, it becomes a gear battle with focus slider, remote control, certain flashes as the Laowa 2:1 or 5:1 lenses are only manual focusing. There are no shots I didnât have to do a second time, partly also because setting up the rig is more time-consuming than the shooting itself.
But in the backyard such a rig is not mobile enough, and a little bit of wind inmidst of stacking will literally blow the result.
Are we confusing eac h other with terminology - I am talking about stacking images in the library to make things easier to find and to keep the whole thing tidier. I think you are talking about focus bracketing and or exposure bracketing - I know focus stacking and focus bracketing are used for the same thing - I am talking about stacking the images after the bracketing to keep the images grouped together.
if you donât like to use projects
- copy / move them to a new (sub)folder
- give them a color label and if necessary sort them accordingly
(which is then sorted in the same way in other folders) - rename them like this
- combine any method âŚ
I do like to use projects - for projects! Stacks are not projects. I am sure there are many ways to do this but selecting the files and then adding them to a stack would be far quicker and tidier. two keystrokes and one thumbnail - presto.
What youâre asking for sounds useful. I wonder if it would require a redesign of PhotoLabâs image library. Except for virtual copies, PhotoLabâs library is just a file browser, not a collection built up from other collections throughout your filesystem. You can tag images, rename them, group them into folders, etc. - but you canât use logical relationships to group them together into stacks or other virtual structures.
Personally, Iâm content with file management. When organizing my images, I donât want to rely on a database that can become corrupted or can be difficult to preserve over time.
However, I will vote for this, as I suspect it could be implemented without ditching correspondence with the filesystem.
Stacking and versioning are classic management in DAMs and although PL do have a simpler DAM functionality - itâs not a DAM per se.
If DxO wish to move closer to a more complete DAM feature set, stacking and versioning would be two great features.
No, I donât think weâre confusing each other, I was just carried away. I know images stacks since the time I used Aperture to develop my RAWs.
As you can see, Apple dedicated âstacksâ an own menu with plenty of shortcuts (to learn and remember). And I never found it very useful. You call it âtidierâ, I call it âhard to keep an overviewâ. It very much depends on how the stack is recognizable for you.
This is a filmstrip with two stacks, one expanded (5 images), one compressed (7 images). With only a hint of a little darker grey background. If the whole filmstrip contains stacked images I cannot see âIâm inside a stack nowâ. Usability? Not the best one. Sometimes itâs hard to decide wether I want the user not to get distracted or get him/her visible clear information.
If I double-click the compressed one, I only see the first image of the stack in full view. No indicator is showing me âhey JoJu, now youâre working on a stackâ. Using the cursor key left, the last one of the 5 images expanded stack is shown. Using the right cursor key, the next image outside the stack appears. The 6 âinvisibleâ images within the compressed stack never appeared. And Aperture is not made for two screen view, I believe. As also DxO PL is not very well made for two screens, but usable for sure.
Do you seriously believe PL programmers who have already failed to achieve a reasonable DAM could do better? Look around in this forum, whenever it comes to the subject DAM, a wave of workarounds and second apps to do the DAM part is popping up. I say (and see myself confirmed over and over) PL users are in general highly allergic to any database, they love digging in their file system.
A stack option is only possible within a well made DAM and this is the first stepping stone DxO refuses to jump over.
And another word to explain why I delete RAWs belonging to a focus stack: I use them to work on, then export JPGs (rarely TIFs) to hand the images over to the stacker app. As far as I remember I never tried to get a better result with another app (except for comparison purposes). 12 years ago I used helicon, today itâs Affinity Photo or FocusStacker by Alexander Boltnev, Olga Kacher, an app from 2017. There are more and better apps around.
But I canât see a historic value of 40-160 single images, especially since the stacker app doesnât tell, which images it uses. Yes, hard drives are cheap, but they donât get faster the more files I pack on them.
But remembering myself 12 years ago I also was eager to keep the single images. Now Iâm certain I donât need them anymore and will delete them, but in the beginning I didnât feel so certain about. So I understand your wish, I just don 't see it happen in the future of PL.
Makes sense