Bugs

Before this gets too far OFF topic:
I think my concern with syncing is certainly no bug in the way Tom asked for in the original post.
Perhaps I´ll open a separate topic but before I have to do more research to it. There has been so much written about it.

Regarding using multicam for synchronizing:
Yes it works nice, but a lot of clicks to do it and it adds a layer of complexity I try to avoid.
Actually for those basic functions as syncing audio and video, I try to stick with the way it´s ment to be done in the app.

@Carsten
Syncing normally means attaching a number of audio clips to a video clip. No mixing involved.
In feature/tv series/dcoumentary you will often have more than one audio file belonging to a video file. It could happen that your left and your right channel are separate audio files. You wouldn´t want those to be mixed together.
First step after actual production is always syncing - "Ton anlegen" we call it in german.
And it is possible in FCPX to achieve nicely synced clips - only the sync feature doesn´t get there in an easy way.

nils.dettmann wrote: … syncing - "Ton anlegen" we call it in german.….

… was ich persönlich mal wieder eine seltsame Eindeutschung finde, Begründung gleich: …

well, … as mentioned in my previous post, I'm a complete noob conc. audio - just argueing from a UI-pov:
I do see a difference btw. attaching tracks to a clip and synching (… 'ne atmo kann ich anlegen, Sprechtext muss ich synchen...)....

Due to the mantra of Magnetic Timeline, attaching doesn't ask for any additional action - ok, for cosmetics you can collapse the stuff into a 'container' aka compound; synching therfor is a special task of attaching, beyond magnetic. And perhaps in Apple-lingo meant equatable to 'mix down' ... (??)


.. again: highly academic from my side, I'm not Apple, nor expert in audio handling.....

Just my innocent point of view, and maybe a lingo prob .... (synch, mix down, attach)

A "Sync Clip" is a specialized Compound in which FCPX attempts to match up all included clips, automatically using audio. It is not a mix down (create a final stereo or mono file). Thus yes, inside it does have connected chips, but automatically created. Simply adding Connected Clips to a Timeline doesn't automatically "sync" anything. A Compound Clip doesn't automatically "sync" anything.

"Anlegen" (something like "to lay alongside" for the non german speaking) is probably coming from film times where the audio tape was layed alognside the movie film.

The Synchronize Clips command actually does a mix of audio tracks if you sync more than two files together.

For example:
If you synchronize one video including audio and two additional audio files, the resulting synchronized clip will only have two channels in the audio tab of the inspector. Camera audio on the main storyline and a mixdown of the two additional audio clips as a1 on the connected storyline. When you edit part of the synchronized clip into a project and expand audio components it will mirror this configuration.
Now, ungroup the clip and the original audio clips will be back and accessible.

I found several posts about people surprised by this in different forums.
I´ll write a feedback note asking them to at least include this behaviour in the documentation.

Which does not happen when you create a multi-cam, you have total control over every audio track, you can set each track to a specific thing, left, right, stereo, audio, surround.

The only problem is the video, only 1 video unless you cut/blade, then you change the focus of the video, seems multi-cam has so much potential, so a new type of "multi-channel", that takes the power of multi-cam to a sync clip, would that not be a solution??

Thanks everyone. Can we try to keep this thread on topic? You can start a thread at any time to discuss thoughts on the way FCP should work.

Doodle bugs, I like them, don't get rid of doodle bugs (rolly-pollies). Nor lady bugs, I like them, too. Roaches, get rid of them all, I hate them.

I get misplaced keyframes from time to time.
After clicking a keyframe icon in the inspector I sometimes find that the playhead has inexplicably jumped ahead and a keyframe has been added at some random point in the timeline other than where I originally parked it. I think this was meant to have been dealt with in the last maintenance update but I still see this behaviour from time to time. Apart from that, I don't have any real issues.

I used to have a bug where keyframes wouldn't always be placed where the playhead was, but It hasn't happened since the last update, I'll let everyone know if it pops up again.

Recurring bug that's very unpredictable, but happens quite often is the inability to relink media because the tracks don't match even when you are relinking exactly the same files that were imported into the library. For me this is perhaps the most serious and persistent bug going back many versions.

Tom Wolsky wrote: Recurring bug that's very unpredictable, but happens quite often is the inability to relink media because the tracks don't match even when you are relinking exactly the same files that were imported into the library. For me this is perhaps the most serious and persistent bug going back many versions.

+1

Dealing with this on a client project right now.

Even if there is some newly rendered copy of the same exact clip you're trying to link to, with extra empty audio channels or whatever, it could give a warning pop up that the audio tracks are different and that it will stop the space-time continuum if you continue, etc, etc...or something...and then let you relink anyways...IMO. :S

This bug has driven me and my coworker nuts ever since FCPX first CE out. I even ran into this today.
Sometimes transitions, titles, and generators skip. We have not found any concrete solution.
The best thing we can do is restart the computer and replace the transition, titles,and generators. This error will export too. It's not just a weird timeline anomoly that has no affect on export.
There's no rhyme or reason that this happens. I have a 2013 Mac Pro and he has one from like 2010. The clips have enough to extend out. I can't think of what the term for that is.

Does anyone have a solution?
It happens on stock and custom transitions, titles, and generators.

When you say "clips have enough to extend out" you are referring to the clip handles. You can open the precision editor to see and adjust these. As for transitions skipping, not sure what you mean by this. This implies that maybe the transition, effect or generator is not the right length for where and how it's placed into the timeline, but if you could post a short video of the problem it would be helpful to help diagnose the issue.

Yes, clip handles. It was right before bed...forgot the term.

If I run into this issue today, I'll add a YouTube link to this forum.
The weird thing is, sometimes when I reapply it, the thing works without skipping.

Nils,

Would it be possible to upload one of these files somewhere like Dropbox or WeTransfer. I don't have any material like this.

Thanks very much.

Hi Tom,

I think the easiest way is to send you a little self contained testlibrary. I will try to make one later.
I made the audio files I used in the example above specifically for testing.
The real world problem is a little more complex.
I dug a lot more into this and I think it´s independet of the file type.


And I have one more point about the relinking problem mentioned earlier.
It happened to me recently, when I was consolidating old libraries.
I have a library which was working fine. Only when I tried to relink the media to a different location it didn´t let me relink 2 of +100 files
In the relinking dialogue FCPX stated that it couldn´t relink because of non-matching timecode ranges in a project that wasn´t even present in the library anymore. Neither the project nor the event with the project, both had been deleted long time ago.
So I think one instance where the relinking "bug" happens is when a library gets corrupted but is still usable to edit.
A library integrity check would be nice (I already wished for that in "Waiting..." thread")

Thank you Nils.

This is a very interesting thread and I agree with Tom we should keep it as close to the subject as possible.

Bugs can only be solved "easily" when they are perfectly reproducible and not random. Whenever you talk with FCP X engineering (and they do listen much more than anyone can ever imagine), the first question you get is: how can we reproduce the issue you are describing. If they can reproduce the issue, they have debugging utilities that allow them to see where and when the problem occurs and they can find a way to stop it from occurring. Overly simplified, but that's how it basically works.

So please keep this thread focused on bugs that many of us know and that can easily be reproduced. Those are the ones that may get solved in a next release. If you have a particular issue that cannot be reproduced by everyone, you can start a new thread and we will try to help you find a solution.

Looking forward to all your responses.

- Ronny

I updated the OS a couple of days ago (to 10.11.5) and I've been noticing FCPX hanging and having to reboot a few times. I've deleted prefs with preference manager - which may have sorted the problem - but I'll keep an eye and see if it persists.

I have two long standing issues that have been there as long as I can remember:

1) MULTICAM: Garbled thumbnails in angle viewer multicam once a clip has been resized in the timeline. This happens in every project 100% of the time. And has happend all the way back as far as I can remember...

2) TITLES: Pretty much the only time FCPX crashes is when changing text in titles. This seems rather random and happens even when using the fonts that comes with the system etc. This too has been going on as long as I can remember through multiple versions... Seems a bit better as of late but still happens more often than I'd like...