[John Pale]

As nutty as it sounds….

Importing the OMF into ProTools and exporting from ProTools removes all references to group clips.

Other than that, I havent found anything else that works.

[John Pale]

[Lumiere] “Made sense to me but my latest test proves that it isn’t the case. Again, I only have one clip in the timeline and exporting only 5 sec is fine (no need to render when reimporting) where exporting the complete movie (44:50 min) isn’t (needs rendering when reimporting in the same timeline!).”

I guess this bug is even more random and weird than I thought!

I have not had it re-occur since it happened to me a month or two ago.

In my case, it was definitely not due to the length of the export. Once I took care of the problem clips the long exports went fine.

[John Pale]

You do not need to mix formats in the same timeline.

The Kona 3 can cleanly cross convert HD formats on capture. Pick whichever format you have the most footage (or whatever format you are required to deliver in)

[John Pale]

I dont think its really a bug. When you apply the composite mode (and render) you are now viewing the render movie instead of the original media. The render movie was generated without the anomaly that resulted in the long frame. It probably made some sort of adjustment to make every frame be the proper length (with some material this adjustment could be undetectable, with other material it might produce a visible jitter)

My guess is if you apply any filter and render you would get the same result.

Then again…. I am just making an educated guess.

[John Pale]

Try exporting sections of your sequence (gradually increasing the length) until you can narrow down what effect is causing the problem. Perhaps just re-rendering that effect (or as a last resort, removing it) will fix the export issue.

[John Pale]

I suppose you can break up your sequence into six 4 track sequences using copy and paste. Make separate EDL’s for each. Then combine them in the audio software.

EDL’s were created for dealing with linear tape based edit suites. At the time the standard was created there were no commonly used VTR’s that could record more than 4 channels of audio.
You are dealing with a 1970’s protocol.

[John Pale]

This is a bug in FCP 6 that is affecting a lot of people (but not everyone). Apple has a technote about it, but it looks like you are screwed. You are probably going to have to re-render.

One possible solution would be to uninstall FCP6, re-install 5.1.4, then open a copy of the project from the auto-save vault that was never opened in FCP6.

Sorry about your troubles. I have had some issues with missing renders, but it was stuff that could be re-rendered fairly quickly.

J

[John Pale]

A few things.

Make sure you are using the Easy Setups in FCP. Do not try to manually change all the settings. This trips a lot of people up.

Make sure everything is set correctly in the Kona Control Panel.

Still no luck?

Download the latest Kona driver kit from the AJA website. Not the CD that may have come with your card. Use the Kona Uninstaller. Then install the new drivers.

[John Pale]

I dont like daisy chaining FW drives….much prefer SATA raids. You might want to look at buying or building a RAID. It’s less expensive than you think.

Even though FCP 6 can work with mixed formats, that feature will not perform all that well with your older computers. If you can convert the HDV and other formats to DVCPRO HD, that would be much less taxing on your systems. With a Decklink or Kona Card you can capture everything to DVCPRO HD. I’ve seen a few used Kona 2 cards being sold cheap. Its worth looking into. The Kona handles the anamorphic scaling of DVCPRO HD in hardware, taking some of the load off your G5 processors.

Be warned though…. if you buy a capture card for your G5’s you will not be able to migrate it to a new MacPro system down the road, as they use PCIe slots instead of PCI-X.

Be very organized from the beginning and stick to it. Back everything up that you can along the way.

[John Pale]

No. I did try to shift the fields and it did not help.

Anyway, I know what a field shift looks like and this is different looking.
Unfortunately I cant think of an effective way to post a screen shot.