Output of Redcine gets stuck on a frame

[Thom Steinhoff]

I finally started shooting today and am processing the shots in RedCine on a Macbook pro. Everything is working just fine: color adjust, bouncing back and forth between clips, copy paste, zooming--even in high res 4k: everything.

It is really working quite well until I get to the output. It seems to render about 500-600 frames then duplicates the last frame for the rest of the project. If I have it so it splits it into files with the same name, it looks like its working fine, then when you open the first clip--it is frozen after a certain frame. Then if I open all of the subsequent files--each of those files shows a clip the length of the clip in that sequence but the image is a freeze frame of the frozen frame from the first clip in the sequence.

Anyone else experience this? What am I doing wrong?

[Antoine Fabi]

Oooops...

Worst here...I get a fixed image (the first frame) for all the exported movie.

I use A Mac Octo 3,2 Leopard QT 7.4.1


EDIT:
Exported to Apple Int codec and working fine.

[Kevin Stanley]

Oooops...

Worst here...I get a fixed image (the first frame) for all the exported movie.

I use A Mac Octo 3,2 Leopard QT 7.4.1


EDIT:
Exported to Apple Int codec and working fine.

Leopard is not fully supported at this point and QT 7.4 and 7.4.1 have known bugs that could cause this. I would definitely suggest reverting to QT 7.3.

Kevin

[Kevin Stanley]

I finally started shooting today and am processing the shots in RedCine on a Macbook pro. Everything is working just fine: color adjust, bouncing back and forth between clips, copy paste, zooming--even in high res 4k: everything.

It is really working quite well until I get to the output. It seems to render about 500-600 frames then duplicates the last frame for the rest of the project. If I have it so it splits it into files with the same name, it looks like its working fine, then when you open the first clip--it is frozen after a certain frame. Then if I open all of the subsequent files--each of those files shows a clip the length of the clip in that sequence but the image is a freeze frame of the frozen frame from the first clip in the sequence.

Anyone else experience this? What am I doing wrong?

I have been testing and working to resolve this. Are you mixing footage formats in the timeline (ie. 2K and 4K)? How many shots are you trying to process?

Thanks,

Kevin

[Thom Steinhoff]

Thanks Kevin,

I have 18 4K 24fps clips in the project, I am running a reverted 7.3 on leopard. Today I will try various combinations (reorganizing the clips and different codecs)

I tried Prores 1080, 720 so far with the identical result.

Also, if I have the clips go to one file it freezes at exactly the same point as if I leave the clips separate.

Thanks for your help!

Best Regards,

Thom

[Craig Bowman]

This is also a problem when asking for Quicktime output using a variety of codecs on the PC platform. You get the first frame repeating over and over. I just output to a frame sequence format like DPX and then convert to the desired file format and codec in another app. Takes a bit longer but I end up with what I need all the time and its predictable.

I'm sure eventually the bugs will be sorted out. I've stayed with QT 7.3

[Kevin Stanley]

Can you guys please provide me with some additional info:

A more detailed list of the shots you are using when this happens:
ie. 4K 16x9 24fps or
4K 2:1 23.98fps mixed with 2K 16x9 23.98fps

and..

a detailed list of the format settings you are exporting to:
ie. QT, Prores 422, Maximum Quality, Full Debayer, Linear Scale Filter, 1080P

and... last but not least

A log file after the issue occurs (Mac HD>Library>Redcine>Settings>Logs>the newest log is the one I'm looking for) (PC >All Users>Application Data>Redcine>Settings>Logs>newest log)

This would be a big help for me. Thanks for the input, much appreciated!

Kevin

[Thom Steinhoff]

Macbook Pro 2.1 ghz Rev 1.1
ATI Radeon X1600
2 Gig of Ram
200 Gig 7200 rpm Hitachi drive
Leopard
Quicktime 7.3 reverted with Pacifist from 7.4

All shots taken with a new camera as shot with default settings: 4K 2:1 24fps.

With mine it works for several hundred frames then freezes for the rest of the project (even if the files are split with #f.mov each new file has the same frozen image from the first file)

Tests:
Prores 422, Quality High, Filter Linear, Format HD 1080, Process Full
tried also 422 HQ, format 720, Quality:Maximum (I think), also splitting into files (#F.mov) and (#S.mov) with the same reaction.

Also, tried to rearrange the files, no effect (same results).

Now I have deleted the project, added the files back in, reset all of the settings and am trying it again.

When it is done I will post/pm the log.

[Thom Steinhoff]

UPDATE:!!!

It seems that wacking the project was the ticket. I deleted the project folder and rebuilt it (I am happy that my grades were with the clips so it was really just re-adding the files, setting project and output settings and hitting go)

And it worked!

I was able to have my grades create 1080p prores clips and it worked just fine.

It seems that the project files become corrupted somehow.

Hope that helps track down the issue!

Thom

[SF Geek]

Trust me Thom. That workaround sucks. Try deleting the project multiple times a day. Not to mention all of your color correction settings get deleted as well. It's high time for a new Red Cine. It's time to support Leopard. If you want another workaround try deleting all of the clips except for one and transcode that one. It's such a fun workaround. I just looove doing it!

Kevin,
I get the same problem.

All shots are redcode 36, 4k 2:1, 23.98

Project is scaled down to HD 1080
Output is Pro Res HQ, Maximum, Full, linear (although I tried lanczos today. I have no idea what the fucking difference is). It would be easier for Red support if they gave us some instruction on the program.

Running Leopard and quicktime 7.3 on Macbook pro dual 2.6gig with 4 gigs of ram.

[Chris Swinbanks]

linear (although I tried lanczos today. I have no idea what the fucking difference is). It would be easier for Red support if they gave us some instruction on the program.If it helps, I did some tests on Build 12 footage to 2k DPX log output that gave following results (IMHO), from sharpest to softest:
Cubic/Sync : Linear/Triangle : Gaussian/Lanczos : Box : Mitchell : Quadric : B-Spline
(note: no sharpening (doesn't seem to work), NR LOW, Detail HIGH, Quality FULL)

Chris

[SF Geek]

Thanks CWS. So you found that cubic gave you the sharpest image? Did the image have a lot of small detail? Does that make a difference?

Also, does it make a difference what format you're outputting in? Does DPX call for something different than say ProRes HQ?

[Chris Swinbanks]

Thanks CWS. So you found that cubic gave you the sharpest image?Cubic and Sync seemed to be a pretty similar result on sample frames (in each colour channel), didn't test any render time differences or screen long rendered clips... I probably should :whistling: but feel I've seen enough images to make a judgement call at the moment.


Did the image have a lot of small detail? Does that make a difference?Yes it did, high shot over mountain forest and lake, with rock walls etc etc... very scenic. I was looking for the cleanest conversion that would give optimum detail in a 2k workflow, without any "patterning" noise, particularly from blue channel.
Seems that using NR on low dissipates the patterning of the blue channel without having too much effect on red/'green, and I feel that a light sharpen after compositing/grade (before filmout) will make a beautiful image. Pretty much every clip I've looked at from several shoots has worked with this setup.
I'm looking forward to seeing some build 15 images.


Also, does it make a difference what format you're outputting in? Does DPX call for something different than say ProRes HQ?Haven't tested that, but I would assume it would follow the same path regardless of the output. We'll use ProresHQ for edit only, so not something I need to look into at the moment.

[jon erwin]

I just had the same issue. Have a mix of 4k 2:1 and 2k 2:1. Project set to 1080. Output to prores 1080. I can process one clip at a time but in a batch it gets stuck on a frame for the duration. I'm way behind now. Help!?

iMac 2.4ghz 2.5gb ram. red cine (90)

[CJ Roy]

The stuck frame issue happens in Tiger & Leopard for me. The only work around I have found is creating a new project, erasing the Library>RedCine files and only importing one mag/reel at a time. It sucks, but it works.

-CJ

[palelnan]

An old thread, but the problem lives on. I recently discovered an interesting thing: The very first clip I rendered from RedCine the first time i used the application was 584 frames (0–583) long.

After that, every export produces 584 frames of content, then gets stuck on the same frame. Even if I have several clips, it is frame number 584 counting from the first (leftmost) frame which persists through all the exported files. The same happens independent of different output settings.

So, I tried to delete files and folders associated with my RedCine installation and reinstall. In frame 584 of the export, the process speeds up, and gives me the same result.

I moved it to a Windows PC and it worked, even if the QT version was too new there too.

Mac Pro 2x2.66 GHz Dual-Core Intel Xeon, 4 GB 667 MHz DDR2 FB-DIMM
OS X 10.4.11
Final Cut Pro 6.0.4
Quicktime 7.5.5
REDCINE 3.1.2

[Russell Fogle]

I'm currently having this freeze frame problem... I've now had it in every build. In every instance it's always on files that split the .R3D files into multiple files... So basically any long take that was shot. Seems to have no problem rendering frames before the file splits to second .R3D file. These .R3D files seem to max out a 2GB and then create a new file... This seems like some old FAT file 2GB limitation stuff and the frame freezes when the footage goes to the second linked file... Resolution?... I have no idea.. That just seems to be the case with me. Files that are only one .R3D never produce a still frame for me...

If someone has a sensible solution... I'd love to know about it.

[palelnan]

The FAT limitation lives on, in every flash memory card. So I suppose the memory cards for the RED camera also use FAT.

But seriously, we need to get this fixed.

[SF Geek]

I'm on a macbook pro with 10.5 installed and I haven't had any freeze frame issues in months. Maybe you need to update your operating system.

[palelnan]

Thanks, SF Geek, I have a computer with 10.5, but thought that was completely incompatible. I'll try it this weekend.

[palelnan]

Well, I tried a completely new OS X 10.5 installation, same problem there. I am using an eSATA hard drive, could that be the problem?

[richard peterson]

me too, freeze frame that runs the total length of the movie.

2 x 2.8 GHz Quad-Core
osx 10.5.5
quicktme 7.5.5

[Ferdinand Weinrother]

Hello,
I have got the same problem. This problem has nothing to do with the system (OSx / Leopard usw) Someone tried to limit the number of used prozessors on multiprozessor systems?

I work with Windows Vista 32, QuadCore Q9550, ATI HD4780, Quicktime 7.5.5, RedCine 3.1.5

[Peter Savage]

have posted this in the report bugs for redcine too....
It seems Redcine 'remembers' the duration of a previously output file somewhere. I trashed just the Library/Redcine/Project/Sesion_1/Construct.reg file to wipe the slate clean... All my previous project settings were lost - I expected that. I loaded a new shot into Redcine. I did not set any in or out points, I changed settings in the colour panel and output to ProRes HQ. All worked perfectly. I removed the existing shot and and loaded a new, longer shot. The metadata, and the player showed the correct length for this shot. I made my colour adjustments and then output this shot.
It was fine for the exact same number of frames as the previous shot, then for the rest of the actual length of the shot it was a still frame of the last frame rendered. Any thoughts anyone?
I can output the files from Red Alert no problem... but...
I hope this points someone in the right direction to maybe resolve this issue as Red Alert does not seem to have the same degree of control as Redcine.

peter

Mac Pro 2 x 3GHz Quad Intel Xeon. OSX 10.5.5 QT 7.5.5

[Mark Pugh]

It seems Redcine 'remembers' the duration of a previously output file somewhere.

Well spotted, Peter!
I haven't heard of this being noticed before.

[Litzwire]

I have gone by the suggestions of uninstalling/reinstalling and all that; I still get the freeze frame problem in RedCine 3.15. At first I thought it was just on shots that are made up of more than one R3D file, but I'm finding that it occurs on shots that are made up of only one R3D. I max out at roughly 30 secs on any output I try. Is this just happening on QTs, or does it happen on sequences as well? I wish someone would fix this soon, it will be a month or two before I get my super-honkin' PC with CS4 and the plug-in, so RedCine is my only choice for output. Sucks.

[Peter Savage]

I'm working on a Mac... but I think if you delete the Redcine project folder (I don't know how you would find it on a PC) it should give you a clean start - you will lose any settings you may have already got but at least you should be able to output your new clip(s). see my post above for what seems to happen (on a Mac at least). It's laborious but it did allow me to output all of my Redcine 'new project'. Now that there is more support in Final Cut Pro I am mostly going that route and using Color to grade. Hope this helps... good luck.

p

[Litzwire]

Indeed, just deleting the Project folder is the ticket! It's a drag to reset everything everytime, but ya gotta do what ya gotta do. Thanks for the help!