Photos: can't "Show Referenced File in Finder"

nolanpaulstanley wrote:

I'm not looking to copy the file, only access it in the finder.

Why do you need to access it in Finder? Like it says in the help topic, if you change it in any way you could corrupt the library.

There may be 8 or 9 replies but not for what I'm trying to do.

What are you trying to do that can't be accomplished using the Media Browser?

nolanpaulstanley wrote:

One workaround I found is that within FCP X, you can Command+Shift+R the file and it will reveal the location in the Photos library

🙂

So what workaround have you found for avoiding possible corruption of the Photos database when you make any changes to the video that are saved back to its library?

I appreciate your concern. I'm not altering the files. I just want to see if they were being duplicated (they were).

As far as creating possible corruption, nothing in FCP X alters the actual video file. I've been editing with Photos / iPhoto linked videos for a while now with no problems.

I understand the need to keep common users from f-ing up the database. I get it. I'm also an Avid editor and the database is king. However, when programs inadvertently start duplicating your data hungry files, the only people that benefit are hard drive manufacturers and now Apple with iCloud photo/ video storage.

I think i answered this in the other post, but simply trying to see if the file is being duplicated (without me wanting it to be duplicated)

nolanpaulstanley wrote:

I appreciate your concern. I'm not altering the files. I just want to see if they were being duplicated (they were).

How can looking inside the Photos Library where you already are storing the originals tell you if the copy you find there is a duplicate? A duplicate of what? It isn't a duplicate of whatever is in your iPhoto or Aperture Library files unless those libraries are not on the same drive as the Photos one.

See Photos saves disk space by sharing images with your iPhoto or Aperture libraries - Apple Support or this more detailed explanation before you jump to conclusions about what you think Finder is telling you.

I'm not jumping to conclusions. You neglected to mention FCP X. Clearly, that program doesn't share the Photo library material. I simply wanted to see if my FCP X file was being duplicated and not referencing the original Photo library. The only way to do this is to see if the file exists in both locations at the finder level.

Anyway, I don't think I like your acerbic tone. I'll take it from here, thanks.

I would think if it's particular corrupt image, it would keep crashing at the same spot.

Even that test would not be fully conclusive, nolanpaulstanley. Just look at the way Photos, iPhoto, or Aperture are sharing the original files by hard links. You cannot tell from the files you are seeing in the Masters folders inside the package in the Finder if the files are shared or not. The hard links look like the original files in the Finder. The only evidence of the link between the apparent duplicates is the identical inode number checked in the Terminal.

Have a look: Six Colors: The (hard) link between Photos and iPhoto

i don't think I was haviing a problem with crashing. Anyway, there are two same named files in my finder, both with identical sizeS. (One used by FCPX and the other one by Photos. Are you ssuing one of the files is just a link, like an alias?

tthanks!

Are you ssuing one of the files is just a link, like an alias?

I am saying, files of the same name, some size could be hard links. I don't know about Final Cut Pro X, because I never looked, but the original files in Photos are hard links to the original files in Aperture or iPhoto, but look perfectly identical:

The same original master file in the migrated Photos Library as in the original iPhoto Library:

You can tell that it is a hard link from the identical inode number in the Terminal using the "ls -i" command:

Last login: Sat May 23 07:46:46 on ttys000

Hermione:~ dreschle$ ls -i ~/Pictures/Aperture\ Library2015.migratedaplibrary/Masters/2015/05/23/20150523-185458/IMG_0107.jpg

37677881 ~/Pictures/Aperture Library2015.migratedaplibrary/Masters/2015/05/23/20150523-185458/IMG_0107.jpg

Hermione:~ dreschle$ ls -i ~/Pictures/Photos\ Library2015.photoslibrary/Masters/2015/05/23/20150523-185458/IMG_0107.jpg

37677881 ~/Pictures/Photos Library2015.photoslibrary/Masters/2015/05/23/20150523-185458/IMG_0107.jpg

Hermione:~ dreschle$

Removing the ability to access your files is more than just a loss of function (albeit a function hidden in a tertiary drop-down menu previously). It is a fundamental hijacking of our control over our personal belongings. Everyone here who is not a shill for Apple knows it.

To those that say that the reason it is necessary to block our access is that we risk corrupting the library by accessing our files: that statement is itself a condemnation of a library which cannot withstand being used in the most basic way a library is useful.

Apple's mobile media apps, and now "Photos", are part of its ongoing trend to create black boxes around our personal belongings and then charge for access to them - through absurdly bulky and opaque filing systems, through ad-laden social media apps, through mobile data plans, etc.

The bottom line is this: if you use this app as stand alone library, you lose access to your photos and videos, because Apple created a library which can reportedly only function if its contents do not change. Or something. If you believe that.

Loavenbruck wrote:

The bottom line is this: if you use this app as stand alone library, you lose access to your photos and videos, because Apple created a library which can reportedly only function if its contents do not change.

Nonsense. Apple provides multiple ways of accessing the items in the library, including but not limited to exporting original or edited versions & direct access from the open menu of other apps via the Media browser.

Shill.

It does not allow access to the files. Not by searching in its finder. Not by referencing them from the app.

It will "export" my file - i.e. take a photo of my photo and give that to me. How about just give me my photo?

It will reference other apps which will give me my photos. How about I just use those other apps then?

Photos is a library which will not give you access to your files, except indirectly, with workarounds and rigamarole. As a standalone, the way it is intended to be used by the huge majority of people, it is a black box with no way to get inside. The new standard at Apple.

Well TECHNICALLY you can still get to the photos directly, it's just a huge pain in the butt. You need to right-click the Photos library and choose "show package contents."

That'll let you surf through all the folders with the photos in them. Not ideal, and I want that darn reveal in finder feature back, but we're not completely cut off.

I do agree with you though, the solutions offered so far weren't what I needed and I've left Photos altogether as they do not work for my workflow as much as others insist that they should/could. 😕

I'm not ungrateful though, I always appreciate people double checking that I'm aware of all of my options. ^_^

Of course using your advice will cause many people to make errors and corrupt their libraries causing data and maybe photos loss - there are no user serviceable parts in the library and there never is any reason to go into it - doing so is very dangerous and is strongly not recommended - Your photos may not matter to you an you may choose to do improper things putting them at risk - but your early should not tell other people to put their photos at risk - especially with warning them of the dire potential consequences of following your ill placed advice

LN

"Your photos may not matter to you an you may choose to do improper things putting them at risk'

Wow. Larry, it's not as dire as all that. Chill man. ^_^

What can I say? It doesn't scare me in the slightest. I've been doing it ever since the feature was placed in iPhoto. That means I've been doing it for years. I've never made a slip up. I've had my hard drives die twice in that time. So my hard drive failure is frankly higher than this scenario of photo library corruption. And it's all backed up anyway.

Bottom line, I'm not coming back to this program until the feature is back. I'm not mad at anyone here, I'm just saying my peace that it'd be nice to be treated like a moderate power user that's been using Macs since 1996 and not have someone else assume my skill level.

It's fine, I'm using Adobe's offerings instead now. It was just a pain to switch over but it is what it is.