This was in a FCP library that had been moved to an archive drive and opened on a different computer. The way we got rid of it was to figure out where the invisible track would have been attached and delete that part of the clip, so the invisible audio was deleted, then drag the end of the clip to recreate the section which had been deleted.
I turned off all the audio I could see, and the invisible track still played.
I thought it was just the garbled music played at the event, but it turned out to be the same invisible audio track problem. A few days later, I had a client who said the audio of a video I'd given her was not synced properly. Another editor told me about having the problem. Here's a new example that came up today - an invisible audio track that plays but can't be seen. I do not believe these issues are specific to my computer, as I've encountered them on other computers I own, and the other editors I referenced have different computers and are encountering similar problems. I appreciate the computer suggestions, but I really posted this hoping that someone from Apple/FCP would see it.
However, I think this places a greater burden on the software manufacturer to be sure the new versions are adequately tested before giving them to everyone. In today's world, everyone is afraid of hacker attacks to vulnerabilities, so many more of us are using auto-update. In times past, software manufacturers used to announce new versions, and the more cautious customers had the option to wait until the bugs were worked out before adopting the new version. When I received it, all the level adjustments without keyframes were again lost. He finally finished his part of the edit and gave to me to do my part. Several times, FCP lost all the level adjustments for those clips without keyframes. It was a 2.5 hour recital with over 50 songs.
If one is trying to do a lot of complex edits, this eats up a lot of time, and sometimes still the marker is in the wrong place.Ħ) Another editor was editing audio by opening the two mono audio channels and adjusting the volume there, sometimes with keyframes and sometimes just dragging the levels indicator. It often jumps ahead (or sometimes even back to the start of the project) and we have to move back to the place where we want the marker. This means that we have to double-check everything thoroughly and often recreate a number of the credits when we have finished everything before sharing the final project.ĥ) When adding a keyframe in the Transform part of the Info panel, FCP often acts like it doesn't know where it is in the timeline. This is quite nerve-wracking when it happens, takes a lot of time, and often has to be repeated on the problem project every time FCP is restarted.Ĥ) We've been adding credits from Photoshop as PNG files, but when the project starts to have problems, a lot of the credits disappear or move to negative space before the beginning of the project. The easiest answer seems to be opening a library that is OK, then opening the problem library, then highlighting the problem project file and exporting as XML then reimporting. even though the folder name is different.ģ) In a complex project, FCP sometimes begins to have problems and crashes when moving around in the project, zooming, or even opening it. Zooming in or out makes them reappear, but this is a nuisance if one has to do this over & over & over.Ģ) FCP gets confused if a number of files have similar names, e.g., Photoshop files that begin with the same string or characters, or folders of audio files that all are named "1 Audio Track.aiff", etc.
(For additional background, I am using OS 10.12.5 on a late 2013 Mac Pro 3.5 GHz 6-Core Intel Xenon E5 with 16 GB 1866 MHz DDR3 and an AMD FirePro D500 3072 MG graphics card.)ġ) When moving forward or backward in an edited project, the clips disappear in the timeline. Usually several different editors work on each one, and this is where the program is driving us crazy. This is the season when we film and edit lots of multi camera dance recitals. Several other editors and I have been running into lots of problems with FCP 10.3.4 lately.