10.0.8 Bugs

For me 10.0.8 has mostly been a step backwards.

I'm seeing a lot of errors in the interface. The biggest complaint being that I simply can't move easily from event clips back to my project. Often I'm stuck in the event viewer no matter what I try.

I suspect it's dodgy code after giving us the event clip viewer.

Yes feedback has been left. If anyone has a solution to this I'd appreciate it.

Not the best answer in the world but it works for me. Hit Command 3 and then Command 2.

I too have sent feedback on the issue of not being able to get out of the event viewer along with what seems to be a "laggy" interface at times.

Just hitting Command 2 does not seem to work but Command 3/Command 2 always does.

I notice I get a LOT of "import failed" errors. If I try to capture via the card, it is faster, but I receive this errors very often. Sometimes it works as it should.

If I try to capture via an external HDD (firewire 800), it takes FOREVER to transcode and I still receives this error. Eventually it works.

I am trying to move on from FCP7, but I am having critical errors that does affect my job's deadline...

In FCP7, if I log and transfer, I can leave the mac and later on, I KNOW I will have what I want. In FCPX, I levae the mac and later on, I get this "import failed" error in 11% of the total proccess, for example. So I need to start all over again from the beggining. I am using ML and FCPX 10.0.8.

I have been hitting Command 2/command 1/command 2, and it gets the focus back.

Also keeping the event viewer open seems to help.

I edit in compound clips most of the time. Perhaps that is contributing to it.

I notice I get a LOT of "import failed" errors.

By chance is it avchd footage?

No, it's DLSR MOV files and Canon's MXF files.

Not seeing this. Cmd-2 switches to the project from the browser and playback is in the viewer. Cmd-1 switches back to the browser and playback is in the event viewer.

I get something similar. When in the event viewer and edit into the project, I click the project and play but the event is still in the viewer... My work around is to simply click the viewer then the project (timeline) and it switches the viewer source...

I hardly ever use compound clips and I get the "stuck in event" problem. But I've been having it since at least the previous version. Use the feedback form to Apple to tell. They are in fact responsive.

The problem may be that people are clicking in the event viewer to make it active. I never do that. Never have to. Make the browser active and whatever plays in the browser plays in the event viewer if it's open. You only ever have to switch between the browser and the timeline.

I upgraded from 10.0.5 to 10.0.8 and have found the new version to be a lot slower. I'm getting choppy playback and lag on footage I used to fly through.

Tom Wolsky wrote: Not seeing this. Cmd-2 switches to the project from the browser and playback is in the viewer. Cmd-1 switches back to the browser and playback is in the event viewer.

I wish I could replicate that. It's frustrating because you think you've switched to the project and you hit "Down" on the keyboard expecting to jump to the next edit and instead you select the next clip in the event. Very frustrating. The best fix I've found is to keep the Event viewer open at all times.

Funny because initially this is what I was crying out for, but now I have it I realize most of the time Apple was right. I don't need it.

Doh! If only I'd kept my mouth shut.

I absolutely cannot reproduce this. Cmd-2 never fails for me regardless of what is the active window.

Tom - the bug is an intermittent one where the focus suddenly shifts from the timeline to the event browser.

The command 1/2/3 stuff is just about how to try and resolve it.

Ahhhh.... So these are problems you guys are having as well. I noticed all of the above really. Especially the lag time in switching from event to edit screen. Also switching keyword collections as well. Seems to take a lot longer than before.

I never really wanted an event viewer...I was fine without it. I don't use it now...but I guess i have a reason to.

I have noticed some lag in overall performance but not the non-responsive viewer-event window issue. I am happy that the titles now work properly (sans the key framing of movement).