Bugs

The multicam bug goes back many versions.

I see a lot of title problems reported, but I don't think I've ever had one myself. My first thought usually is that it's perhaps a font issue as they seem weirdly susceptible to corruption, or maybe there're just a bunch of badly made fonts floating around on the web.

Haven't slogged through the whole thread because of the sidetracks. This may or may to have e been mentioned.
When I have control-v active, show animation keyframes, and I click on any parameter in the inspector to create a keyframe, the playhead often jumps to a random place in the timeline. Could be forward or backward. It's annoying as heck because the keyframes are persistent and they are invisible. They have been placed at some trimmed part of the clip that is not visible or active.

Think it was mentioned somewhere, but yes, that's definitely a reproducible one for me too.

bogiesan wrote: Haven't slogged through the whole thread because of the sidetracks. This may or may to have e been mentioned.
When I have control-v active, show animation keyframes, and I click on any parameter in the inspector to create a keyframe, the playhead often jumps to a random place in the timeline. Could be forward or backward. It's annoying as heck because the keyframes are persistent and they are invisible. They have been placed at some trimmed part of the clip that is not visible or active.

If you add a keyframe with the video skimmer off (S), that strange behaviour is greatly reduced. Still a bug to me, but hard to reproduce since it is random.

Tom,

did you get the PM with the Dropbox link?

No. I'll look for it.

Got it. Thank you very much. Really appreciate you doing this for me.

Since v1 FCPX consistently leaves various small parts of the timeline unrendered. The orange bar continues to show over handfuls of clips in probably 30% of my projects. This orange bar stays no matter how many times I try and force that section to render. Thankfully, if I export the timeline, those sections do in fact render on output, just not for playback in FCPX.Sometimes I can force a render by positioning the playhead over the clip and/or disabling any clips that are "below" it. That's hit or miss though. This has happened on all our machines, all versions of FCPX or OS. The consistent cause has something to do with having "layers" of connected clips and when effects are used.

The other render related bug (at least to me it's a bug) is the fact that whenever I open a project that has been rendered in the timeline, more often than not it wants to re-render it. Maddening! This has also happened since day one of FCPX for me, across all versions of app and OS.

I confess I don't render much and switch off background rendering. I've seen problem reported quite a few times, but have never been able to reproduce it. I tested it extensively yesterday on 33 different projects with different media of different lengths with stabilization and optical flow and speed changes and different effects and titles, but I couldn't make it happen. No idea if it's media specific, system specific, or something else, but on a few year old rMBP with different drives I could not make it happen.

Try this one ...

Place some audio at say frame 10 in your timeline. Now, place the playhead at the very beginning of the timeline and then press the right arrow to advance frame by frame. Hear the audio even through you shouldn't be?

Annoying as hell bug.

That one was mentioned in the first message I think.

What happens when you actually put the playhead over a part where there is are 3 mono clips? You've got the playhead parked over a stereo and mono clip. Perhaps it gets it's data from the first frame too.

mindbend wrote: Since v1 FCPX consistently leaves various small parts of the timeline unrendered. The orange bar continues to show over handfuls of clips in probably 30% of my projects. This orange bar stays no matter how many times I try and force that section to render. Thankfully, if I export the timeline, those sections do in fact render on output, just not for playback in FCPX.Sometimes I can force a render by positioning the playhead over the clip and/or disabling any clips that are "below" it. That's hit or miss though. This has happened on all our machines, all versions of FCPX or OS. The consistent cause has something to do with having "layers" of connected clips and when effects are used.

The other render related bug (at least to me it's a bug) is the fact that whenever I open a project that has been rendered in the timeline, more often than not it wants to re-render it. Maddening! This has also happened since day one of FCPX for me, across all versions of app and OS.

In my case there are times FCPX never stops rendering some parts of the timelline or it loses some render files when reopening a library. This happens using some third party plugin like Neat video (i have V3) and Lock'N'Load. So, to me, is a bug introduced by some third party effects. When I'm using just the built-in effects everything is fine.

The "audio skim" bug is really annoying and i experienced it a lot of times (always with audio clips at the beginning of the timeline)

This is an interesting observation. When you post a "bug" you also should check if the issue is related directly to FCP X or if it only occurs when you use specific types of third-party software or hardware. In those cases it's a problem that has to be reported to the third party.

- Ronny

ronny courtens wrote: This is an interesting observation. When you post a "bug" you also should check if the issue is related directly to FCP X or if it only occurs when you use specific types of third-party software or hardware. In those cases it's a problem that has to be reported to the third party.

- Ronny

I didn't report to the respective developers because:
- My Neat video is the V3. Maybe the last release solved this problem.
- I'm using Lock'n'Load in a particular way: since it doesn't support RED raw, I apply the effect on the proxy clips and then render the original. In this case lot of times FCPX goes in "perpetual rendering". I don't use optimised media since i will lose the benefits of the raw native clips.

Anyway I don't expect a solution from the Apple FCPX team

This was just a general observation based on your experience. I agree there are render bugs with some third party plugins over which the FCP X team has no control at all. And I'm happy to hear that you don't expect them to solve these. But in general it's always good to report such bugs to the developers of the third-party plugins so they can see if there's a way they can solve these.

- Ronny

jcmcnamee wrote: Audio waveforms aren't correct in clip browser (towards the end they are never correct).

I second this. Visual display of the waveform doesn't match the sound at the end of clips. Irritating.

Found this out yesterday.
Park playhead on timeline, go to browser and create a freeze frame (for a connected clip) the playhead jumps to the beginning of project after creating ff.
No like, want playhead to stay at point for freeze frame in timeline.
Is this a bug?
Can't figure out a reason it should jump to beginning.

Greg

VidGreg wrote: Found this out yesterday.
Park playhead on timeline, go to browser and create a freeze frame (for a connected clip) the playhead jumps to the beginning of project after creating ff.
No like, want playhead to stay at point for freeze frame in timeline.
Is this a bug?
Can't figure out a reason it should jump to beginning.

Greg

I can't reproduce this one. For me the freeze frame connects and the playhead stays at the end of the freeze frame.

Can't reproduce it here, even when connecting between different libraries.