Interacting with photos within a meta library?

[rubin110]

So I'm guessing this is one of those cases where that thing I got extremely used to in Lightroom just doesn't exist here, but I thought I would ask as it's bugging the hell out of me.

I see two tabs, Library and File System. I thought the differences where that you import the notion of where photos exist in the file system to the library. From the Library tab I can go through and move photos around between different directories, create new ones, group them up as I please, while the actually photos never physically move around in the file system. The File System tab lets me directly manipulate the location of photos on the file system wile still maintaining that meta reference in the library.

I seem to be wrong and both tabs pretty much do the same thing, move files around physically in the file system. Is this functionality I think should be existing here something that does and I just haven't figured out how to turn it on, or is it something that AfterShot Pro doesn't do at all?

Thanks.

[ogrizzo]

Bibble 5 used to be like that, when importing by reference to file, but the option was removed in ASP: now the library mirrors the file system.

The point of the latter view is that, as opposed to LR, you don't need to import pictures in the catalogue in order to edit them.

[rubin110]

Yeah I don't particularly like that being a feature. When I here nondestructive photo editing, I tend to think that the file never gets touched when I'm playing with it in the Library view. Additionally I would want to import everything so I can actually search for it when I want to.

I would really like a way for the Library tab to have it's own directory/folder hierarchy that isn't correlated to the file system. File System is how I want things to look when I'm thinking about shoots archived, Libraries should be completed sets or groupings of hand picked processed photos from shoots.

[afx]

I would really like a way for the Library tab to have it's own directory/folder hierarchy that isn't correlated to the file system. File System is how I want things to look when I'm thinking about shoots archived, Libraries should be completed sets or groupings of hand picked processed photos from shoots.

Nope.
The library should always mimic the file system which is hopefully decently organized.

But, what is needed is virtual views on the library that allow you browse the library according to organizational aspects without having to click together loads of silly stuff.
This is what iMatchs hierarchical categories are quite useful for. If AS had its hierarchical keywords separate from the regular keywords that would be useful as well for this.

cheers
afx

[ogrizzo]

Yeah I don't particularly like that being a feature. When I hear nondestructive photo editing, I tend to think that the file never gets touched when I'm playing with it in the Library view.

The file never gets touched by ASP: all editing is written out to the sidecar file.

[rubin110]

The file never gets touched by ASP: all editing is written out to the sidecar file.

No actually that's incorrect. If I move the file to a different folder in the Library tab, the file does get moved to that directory in the physical file system. In my opinion that's touching the file.

[afx]

No actually that's incorrect. If I move the file to a different folder in the Library tab, the file does get moved to that directory in the physical file system. In my opinion that's touching the file.

Might be incorrect for you, but that does not mean the rest of the word agrees withing the context of non-destructive editing.

cheers
afx

[ogrizzo]

The file never gets touched by ASP: all editing is written out to the sidecar file.

No actually that's incorrect. If I move the file to a different folder in the Library tab, the file does get moved to that directory in the physical file system. In my opinion that's touching the file.

Not really: when you move a file, it's just the address of its first sector in the thing that defines directories that is changed: the file stays exactly where it was on the file system.

[afx]

Not really: when you move a file, it's just the address of its first sector in the thing that defines directories that is changed: the file stays exactly where it was on the file system.

pedantic nitpick: That is only true if you have a system that implements the move properly and when source and destination are on the same file system ;-]

cheers
afx

[d-light]

I don't think it is really helpful for the OP to discuss what touching of files means in detail. rubin10 has outlined his objective rather clearly.

Comparing the different approaches in the various pieces of software it seems to me that there is no right or wrong but more a matter of taste how a library should work.

...
I would really like a way for the Library tab to have it's own directory/folder hierarchy that isn't correlated to the file system. File System is how I want things to look when I'm thinking about shoots archived, Libraries should be completed sets or groupings of hand picked processed photos from shoots.

and

...
Nope.
The library should always mimic the file system which is hopefully decently organized.

are just two completely different interpretations.

Obviously not even ASP and B5 (having the same roots) follow the same philosophy.

Just my two cents
d-light