Currently Being ModeratedJul 2, 2012 7:05 PM (in response to Matt Davis (UK))
I think what you may be seeing is the UNIX hard versus soft (symbolic) links.
I suspect that FCPX creates hard links to the original file, but when you create an alias in OSX, you create a soft link.
Or something like that, anyway.
Have a look at Wikipedia:
http://en.wikipedia.org/wiki/Alias_%28Mac_OS%29 <-- talks about OSX Aliases
http://en.wikipedia.org/wiki/Hard_link <-- talks about UNIX hard links
http://en.wikipedia.org/wiki/Soft_link <-- talks about UNIX Soft/Symbolic links
Currently Being ModeratedJul 3, 2012 4:02 AM (in response to CodeWench)
FCP X creates Symbolic links (a.k.a. "soft links"). These appear in the Finder with a little arrow, just like aliases. To an unsuspecting user, they are virtually indistinguishable from aliases, but they are not the same thing.
A symbolic link is like a little text file that basically contains the name of the real file to which it is "pointing".
I don't buy the notion that the symbolic links "decided" to point somewhere else. Anyway, you could probably sort that mess out by remaking the soft links. Here is how you create a soft link to a file with minimal typing:
1) Open Terminal
2) Type the following, without the quotes, but with the SPACE at the end:
"ln -s "
3) Drag the original file from the Finder to the Terminal
2) Drag the destination FOLDER from Finder to the Terminal
3) Type Enter
Currently Being ModeratedJul 3, 2012 4:31 AM (in response to Luis Sequeira1)
I'll give this a try, Luis.
I don't buy the notion that the symbolic links "decided" to point somewhere else.
To be honest, neither do I. Nevertheless, they changed due to some reason that is beyond my powers of reason.
There may be clues, if only to run it up the flag pole and see who licks it up...
- This mess was on a SparseImage volume
- The SparseImage volume was on a Solid State Disk (Crucial M4) via Thunderbolt
- Immediately before the problem...
- I had quit FCPX, Ejected the Sparse Image and copied the sparse image to an external FW800 drive
- Ejected the SSD and physically removed it from its Seagate SATA cradle, and replaced it with a standard spinning drive to copy additional rushes to the FW800 drive
- Ejected the spinning drive, physically swapped it out for the SSD
- Opened up the Sparse Image
- FCPX hangs on launch due to SymLink issues
So, whilst it's tempting to point the finger at the SSD, the alias mess happened before it was ejected, and probably happened at the FCPX quit. The backup of the SSD is identical (handy, as I'll use this to make copes and try to fix it). The edit had been going smoothly to that point, the app being quit and reopened regularly as new rushes became available.