QT freeze frame issue

[Sean Michael Johnston]

Has anyone figured out a workaround for the freeze frame issue in RedCine?
As long as I keep files shorter than 600 frames it will work fine. Which is workable for a 30sec spot, but for longer sequences it sucks. I saw some posts about going to dpx or tiff sequences, but then I lose my timecode and cannot easily resync in FCP. I've tried different codecs, but it seems that anything based on Quicktime has problems.

I've been looking around all the latest threads and seen nothing yet, except that Rob said they were going to be talking to Apple about it. Has anyone had any better results?

 

[Jay A. Kelley]

I'm afraid not... This is a pretty serious issue, but I do hear they are working on it.

Jay

 

[Deanan]

Clearing out the preferences directory and reinstalling usually fixes the problem. The path is in the readme file.

 

[Sean Michael Johnston]

I've tried trashing the RED folder in the library, but no luck. Is there another preference file I should be looking for?

 

[R Fogg]

My Redcine single frame solution

My Redcine single frame solution

Well it has been a couple of weeks, but after lots of fiddlin I am finaly able to export qt movies with more than a single frame! (please note this is a PC solution)

My solution:

1. Delete all folders and files located in C:\Documents and Settings\All Users\Application Data\REDCINE
2. Uninstall redcine
3. Uninstall qt 7.4
4. Install QT 7.31
5. Install Redcine
6. Export successfully
7. Tears of Joy

Hope this helps anyone else out there trying to fix this.

 

[R Fogg]

I guess I spoke too soon - I still get single frame output on the dragster(or is it a funnycar?) file jim shot. Other R3D files seem to work fine. - Will post shortly with test results

 

[R Fogg]

OKAY!

Redcine Rule #1: No mixing formats in the output of redcine - this causes the single frame issue for me.

Rule #2: The project format settings in Redcine must match the source shots you are trying to output.

No more frozen frames for me.

 

[Sean Michael Johnston]

I've tried deleting and reinstalling RedCine and the RED folder in the library on my Mac 8 core running OS 10.4.x and QT 7.3.x.

OKAY!

Redcine Rule #1: No mixing formats in the output of redcine - this causes the single frame issue for me.

Rule #2: The project format settings in Redcine must match the source shots you are trying to output.

No more frozen frames for me.

Not sure what you mean by mixing formats. I'm working with 4K 2:1 and sending out QT Prores 422 HQ at HD1080 size. Are you saying that sending out a QT in a 4k format might be the best solution for me?
I'll try that on Monday.

 

[R Fogg]

Sorry, by mixing formats I mean 4k & 2k, 25 fps & 24 fps - but this may be unique to the PC related freeze frame errors. Not sure about mac. It seems that each platform is having its own set of issues. What I did discover on the PC was that I cannot mix file formats in the output, I cannot out put from a source file that is different than the file format (2k, 4k, 25fps, 30fps) specified in the project format settings and Redcine also gets very unstable for me if I have different file formats in the library. On the PC if I am getting crashes from mixing formats I have to delete all the files in the C:\Documents and Settings\All Users\Application Data\REDCINE\Project\Session_1 folder in order to work in red cine again - for the mac the folder is located /Library/REDCINE/project (Note: I do not have a mac to test on - I gathered this from the redcine readme file).

As an experiment I suggest deleting the project files in the above mentioned folder, restarting redcine and making sure your project format settings are set to 4k 2:1 (with whatever framerate your source file is) and then try to output your 422hq at 1080.

 

[Sean Michael Johnston]

The frustrating thing about all this is that it's not really a bug in RedCine alone, but a Quicktime bug as well. RedCine is happily churning out its processed files and the final file sizes reflect this. There is no problem sending out file sequences of any type. It's only the QT wrapped files that have the issue. There must be a marker in the file that causes the QT player display the frozen frame even when all the processed frames there. I suppose that's why its going to take a little longer for the Red team to fix this, since they'll need full attention from from the Apple QT guys.