Final Cut Studio ( Summer 2009 ) Bug Report thread.

R

RyanBellaCine

Well-known member
I could be wrong, but I thought it would be a good idea to host a bug thread for us to keep tabs on with the new release. I've already come across a couple.

These are "Bugs", not feature complaints or wish lists.
 
I'll start off with Compressor 3.5

- Frame Controls do not work, do not work properly. I couldn't get Compressor to de-interlace any footage with frame controls no matter how hard I tried. The workaround is to use the legacy deinterlacing filter. That seems to work fine. I've found others on Apple's Forums complaining their Frame Control settings don't work either, Or at least they look worse then the previous version. The huge difference in render times ( which usually add quite a bit of time for deinterlacing ) leads me to believe that they are just not workin at all. Renders finish way too quickly. And at about the same time, no matter how I set the controls.

- Virtual Clusters. Making a render cluster breaks the project up into sections to process at the same time, making use of all cores available. I've had a bunch of lingering sections that just don't want to render. All the other segments are finished, but this one random segment won't start. I seem to be able to jump start it by quickly pausing and unpausing the render. Do it too slow, nothing happens. Do it really fast ( like double clicking) and I've gotten it to jumpstart itself and finish the render.


Final Cut Pro 7

- My custom layout doesn't seem to want to hold. It keeps resetting itself back to default. Once the windows jumped around while I had FCP open, but in the background as I was working in another program. Hitting the saved layout does restore it back the way I want to however. A minor nuisance as of now. I don't think It was a user error that messed them up while the program was open... but I could be wrong. I'll keep an eye on that one.
 
No one else finding ANY bugs? Or I may just be the only one interested...

Anyway, here's another finding:

FCP 7
- The "background exporting" ( via "sharing" the file ) feature does work. But it's not anywhere near perfect. Despite having the option to send your export to a Virtual Cluster, Apple still has not fixed whatever causes the export to crash. I would assume that if you add the option to your software, it should work. But it doesn't. It will only work when sending the file to "This Computer" But even that has problems as I found with a clip i was "baking" for a Color sendoff. It's exporting, but the status bar gives no indication on how long this will take. You just get an infinite barbershop scroll. FCP is only using a horrid 100% of my CPU power. ( 600 - 1600% is desired on a Nehalem Mac Pro for full use of all cores ). As of this post, FCP 7 is definitely NOT 64 bit or multicore friendly. boo. Even still, FCP shudders when trying to work on the timeline. It might work better on more simpler timelines, this one I'm using is pretty complex with still images and multiclips galore. My "background render" is still going.... about 25min so far. It's only a 2 minute SD credit roll created in Motion with Jpgs overlayed & keyframed. I'm not sure what the holdup is....
 
Most of my bugs are around the Share functionality.

While convenient, it's not very stable. What appears to be happening
is that FCP spawns a compressor job in the back ground. If Share is
doing it's thing, bringing up Compressor (stand-alone) causes all sorts
of very odd behaviors.

If FCP crashes, it can leave a zombie Compressor process in the back-
ground. This zombie process may attemp to restart FCP and pick
up where it left off. Unfortunately, since the Share export dialog
does not re-appear, you can't tell what it's doing.

Another unfortunate bug is when you attempt to burn a CD while
Share is making a Blu-Ray. I was using Waveburner to make a CD
master while FCP was making a Blu-Ray .. I put the blank CD in ..
and instant crash.. this is easily reproducible.

In short... I think using the normal FCP->Compressor flow is
more stable than the convenience of the FIle->Share dialog ..

I like the idea though .. it's just not implemented well.

And while I'm harping on the topic... How in God's name are you
supposed to see what the disk menus and title look like in that
teeny tiny thumbnail? Get real... and why can't we have a looping
piece of audio on the title and chapter movies? ..

jeff
 
Color:

- The "Add Unrendered" button in the Render Queue room sometimes doesn't recognize grade changes you made. For example, I rendered a clip with a tracked vignette, then change the placement of the vignette, but Color doesn't recognize it as a change and the button doesn't re-add the clip to the queue.

- Send to Final Cut Pro still occasionally freezes up Final Cut Pro. I had this problem before as well. I use export to XML instead.

[another one I just noticed]

- Tracking info not kept after saving and restarting Color. Create a new tracker, track some object, then apply it to a vignette in the secondaries room. Save, restart Color and the tracking is no longer applied.
 
Last edited:
Still Store feature in Color shifts gamma of video being viewed so badly that the feature is basically unusable. The problem is documented on Creative Cow.
 
I have found a serious issue on 2 separate Mac Pros. One with 10.5.8 and the other with 10.5.7, so I think this is a FCS issue.

I keep getting a "general error" every time I try to export a NTSC DV timeline to any destination. Whats more is that I found QuickTime Player will not open a .mov encoded in DV/NTSC. I get a QT window with no video window. Something like if you were playing an audio file. When trying to open the file, the hard drive goes nuts as if it's attempting to cache the file or trying to read it.

And further, Compressor bogs down to all hell when I try to import a DV/NTSC movie into its batch window. The hard drive goes nuts like its attempting to read the file but some reason can't just like with QuickTime.

I think a currupt codec may be to blame... I've yet to try to replace it with a version from FCS2. I'll report back if any workaround works. Right now, my productivity has come to a halt.... Although anything exported in Pro-Res seems to work no problem. Too bad most of the stuff we do here is DV/NTSC!!

EDIT :

LOL. The problem with opening the file wasn't related to the General Error thing. A co-worker accidentally had the "Make Movie Self Contained" unchecked. It was MPEG Streamclip which tipped me off when it asked for a FCP render file while I was trying to open the movie.

Still have the General Error problem on export though.
 
Last edited:
You must log in or register to reply here.
Back
Top