Relinked picture files not updating
Hi all,
To begin with, I am using final cut pro 10.0.8 on mountain lion 10.8.4.
The problem I'm having is that my media files are not updating in final cut pro x once they have been changed outside final cut pro. I'll explain what I'm doing:
1. I have imported some png files into my events and chose not to copy to my events folder. These picture files are used extensively in my project.
2. I have found that I need to make some changes to the png files. After making the changes in photoshop (the original file is psd and I save to png), final cut pro does not automatically update the new details even though when I click the event and choose reveal in finder, it takes me to the newly saved file that does have the changes. The file name and location did not change.
3. I then tried to manually relink the files, but it still does not update the new changes. What is interesting is that the info on the picture still refers back to the orginal details when the file was created. Again if I choose reveal in finder, it highlights the newly saved png.
4. I then decided to delete the original png file and empty the trash can. Final cut shows that the media is missing. I saved the png from photoshop again and final cut pro automatically relinked the file, but it is still the old image!
5. As a last resort, I trashed the original image again, resaved the png with a different name, relinked again. This time final cut updates the date it was created, but the image is still the old image!
No matter what I try to do, I can't get final cut pro to update the image. I dropped the png into the timeline and did and export hoping it was just displying the original image but would use the new image when it renders. Unfortunately, the movie it created had the old image still.
Obviously the image the event is pointing to is not the one it is using because I have double checked that the file saved has been updated outside of final cut. Is there something I am doing wrong? Or is there a bug with final cut pro? I'm suspecting it is using a chached file somewhere.
Thanks for your help,
Adrian
MacBook Pro (Retina, 15-inch, Early 2013), OS X Mountain Lion (10.8.4)