Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Crimson/Redcine Spanned R3D

simonpeterarnold

Well-known member
Joined
Jul 5, 2008
Messages
68
Reaction score
0
Points
0
Have come up with anothers snag in my workflow today. Just doing some test transfers that have been edited from spanned R3D files and when I import the Crimson XML into Redcine it is not editing to the correct in and outs. From what I can make out the information seems correct in Crimson. There is a frameslip of around 14980 frames and then it has a render in as +150 from that point and the render out seems to match the EDL. IN Redcine it is not doing the initial frameslip and the render point is +150 from the strart of the first spanned clip. Anyone have a solution to make it work with spanned clips or am I going to have to manually fix all the shots from spanned files.
 
Hmmm,

No I think the problem may be on my side. I mentioned this on the release notes, crazy frameslips have been creating problems so frame slip has been disable. While the engine is still calculating that number, it is not affecting anything, currently.

I don't however understand what you mean by spanned clips?
 
Hmmm,

No I think the problem may be on my side. I mentioned this on the release notes, crazy frameslips have been creating problems so frame slip has been disable. While the engine is still calculating that number, it is not affecting anything, currently.

I don't however understand what you mean by spanned clips?

Sorry probably bad terminology. I mean spanned takes. R3D files are limited to 2GB in size so takes of a certian length are spanned over several R3D files. In this case its spanned over 8. There is only 1 Quicktime proxie however for the whole take so I guess this is why it goes a bit odd. So I guess I will have to work around this by either exporting full takes or ammending each shot accorrdingly.
 
Sorry probably bad terminology. I mean spanned takes. R3D files are limited to 2GB in size so takes of a certian length are spanned over several R3D files. In this case its spanned over 8. There is only 1 Quicktime proxie however for the whole take so I guess this is why it goes a bit odd. So I guess I will have to work around this by either exporting full takes or ammending each shot accorrdingly.

Spanned takes aren't an issue affecting slip frames. In the eyes of all the RED software all the 2GB chunk should just read as a the same file as long as they remain together.

But timecode difference between your proxies and your R3D files can create problems. The ideal situation is that the proxie matches up frame for frame with the group of R3Ds. This is when Crimson operates best. So the question is what is causing your stuff to be so far off. Is it finding the right in point in Redcine?

Would you like to send your FCP and telecine XMLs to h e l p @ c r i m s o n w o r k f l o w . c o m.

Cheers,
IBloom
 
Spanned takes aren't an issue affecting slip frames. In the eyes of all the RED software all the 2GB chunk should just read as a the same file as long as they remain together.

But timecode difference between your proxies and your R3D files can create problems. The ideal situation is that the proxie matches up frame for frame with the group of R3Ds. This is when Crimson operates best. So the question is what is causing your stuff to be so far off. Is it finding the right in point in Redcine?

Would you like to send your FCP and telecine XMLs to h e l p @ c r i m s o n w o r k f l o w . c o m.


IBloom


Will do, funny thing is it all matches up if I manually trim the shot in Redcine to the same settings in Crimson. I know that the in and out points are correct its just that Redcine takes the in and out points from the first of the R3D files rather than the one the take is actually in.
Cheers,
 
Will do, funny thing is it all matches up if I manually trim the shot in Redcine to the same settings in Crimson. I know that the in and out points are correct its just that Redcine takes the in and out points from the first of the R3D files rather than the one the take is actually in.
Cheers,

I don't fully understand. Are you loading your telecine XML into Redcine?

IBloom
 
I seem to have a similar issue.

Did you find a solution simonpeterarnold?
 
I seem to have a similar issue.

Did you find a solution simonpeterarnold?

No, I have had to just convert full takes so far which is a pain as some are 15mins. I have not tried that new Monkey App that might work.
 
Back
Top