Welcome to our community

Be a part of something great, join today!

Log in
  • 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 :)

AVID says timecode is too long??? Epic M

Steffen Vala

Steffen Vala

Well-known member
Joined
Mar 24, 2009
Messages
163
Reaction score
0
Points
0
Age
49
Location
Gainesville, Florida
Website
www.svala.cc
Hey all, the avid editor faces an issue w dnxhd 185 10bit files I transcoded out last night from RCX-487.
He said there was some avid error that read something like the timecode is too long.
Has anyone heard of this? How do we fix it?
We start shooting day 2 in under an hour and I need to get this solved ASAP of course.
Any guidance from the red thread heads would be super appreciated.
 
Steffen,

I would try to get the exact Media Composer message, along w/ how the how editor is trying to bring the files into MC and exactly what version of MC he's using, and on what OS.

But to more generally answer your ?, no I have not heard of this issue/error before. Good luck.


P.S. Also, are you using HDRX? And I'm assuming you shot 25P since DNxHD 185 is 25P and you're in Europe.
 
Hi I'm the one with the problem:

when importing via media tools my master clips has no duration (00:00) and when I try to playback it say "Exception: The sequence or one of the source elements is too long to be played". The timecode jumps around like crazy when I try to look through the clip. I tried exporting a ALE from RCX and relink but it only relinks to the original R3D files which doesn't work.

We have used Redcine-X 454, to make MXF files but another weird thing is RCX doesn't export any AAF or ALE along the MXF files even though the audio was recorded into the camera.

It is shoot in 25p.

My AMC version is 5.0.3

MacPro 10.6.8


2x3.2 GHz Quad-Core intel Xeon

16 GB 800 MHz DDR2 FB-DIMM


EDIT: just tried using RCX 487 only thing different is that I can can hear sound in RCX, still no AAF exported.
 
I don't see why you would. I think DNxHD out of RedCine-X takes care of the fact that MC can't currently read 5K .R3D's. MC has for about a year now been able to link to 4K .R3D's via AMA. One issue that I wonder about is if HDRX is somehow messing things up, since an HDRX DNxHD file would be different from one w/o HDRX.

I think you should take heart that Avid says that using RedCine-X, you can indeed work w/ Epic files. So there should be an answer for you *fingers crossed*.

http://community.avid.com/forums/p/94932/571955.aspx#571955


P.S. If you haven't, you also might want to try using RCX w/ Red One .R3D's. If you're having the same problem, then it's not an Epic issue. But again, I hope someone w/ more experience will respond.
 
So far it seems like it's not only Epic R3D but also Red One files. So either it's RCX vs Avid compatible or else I'm doing something completely wrong. I'm pretty confused at the moment...

Btw it's shot without HDRX.
 
We are looking into 1080p25 issues with REDCINE X. REDCINE uses Avid's Media Toolkit (AMT) to export the MXF and AAF. Reports from the folks at RED seem to indicate that this issue is in the Mac version and not Windows of REDCINE. I need to verify that to be sure. Are you on Mac or Windows?

Michael
 
MichaelP said:
We are looking into 1080p25 issues with REDCINE X. REDCINE uses Avid's Media Toolkit (AMT) to export the MXF and AAF. Reports from the folks at RED seem to indicate that this issue is in the Mac version and not Windows of REDCINE. I need to verify that to be sure. Are you on Mac or Windows?

Michael
Click to expand...

I'm on a Mac Pro.

I think we now know what the problem is. It seem like some mistake in the transcoding and maybe in the camera options. I have a guy looking at it at the moment and will return hopefully with a full explanation.

Btw thanks for the help Peter Moretti. Always nice with someone trying to help


EDIT: it seems like the problem is in Red Cine-X. In the export settings you have to remember to click the "Sub-folder per clip" ON, otherwise you won't get any AAF which means the whole import process doesn't work.

I think it's something you should at least get warned about in future RCX releases.

Hopefully this will help some people in the same situation.
 
Daniel Persson said:
Hi I'm the one with the problem:

when importing via media tools my master clips has no duration (00:00) and when I try to playback it say "Exception: The sequence or one of the source elements is too long to be played". The timecode jumps around like crazy when I try to look through the clip. I tried exporting a ALE from RCX and relink but it only relinks to the original R3D files which doesn't work.

We have used Redcine-X 454, to make MXF files but another weird thing is RCX doesn't export any AAF or ALE along the MXF files even though the audio was recorded into the camera.

It is shoot in 25p.

My AMC version is 5.0.3

MacPro 10.6.8


2x3.2 GHz Quad-Core intel Xeon

16 GB 800 MHz DDR2 FB-DIMM


EDIT: just tried using RCX 487 only thing different is that I can can hear sound in RCX, still no AAF exported.
Click to expand...

Definitely use the latest RCX (487 at this moment). I can tell you that RCX 487 will make perfect MXF/AAF files for Avid for 23.976, using HDRx as well as simple R3Ds. I just processed a terabyte of footage to Avid through that path.

You should read the RCX and Epic build notes, and perhaps contact a Red Bomb Squad rep to see if there are any known issues with the path in 25 fps. I think I remember a note about that in one of the Epic builds (but not being in 25fps territory, I don't remember the details).
 
This problem exists only in 25p. The workaround we do right now is to transcode to MXF with all sound disabled in Redcine X and doing the sound sync in Avid.

For the transcodes disable the Audio in the RCX setup and then the MXF and the ALE should be correct. With Audio enabled RCX failes to write a correct ALE and the AAF files will not be finalized. There are some weired XML files attached to the AAF files. But as I said, only in 25p (on Mac, never tried on PC). We made lots of MXF from Red One and from Epic without Audio and it works fine this way.
 
Biggest issue here was that I hadn't selected sub folders per clip.
Arrggh, lesson learned, and luckily w a rocket on set, I am able to re do it the right way.

Why is the sub folder per clip an option in RCX if Avid needs that always to happen, in order to get both ale and mxf files out the correct way?
Wouldn't it be good to have that default on once you have selected to transcode aaf and mxf?
We are not shooting hdrx.
 
Last edited:
Subfolders per clip is not necessary to get an .MXF per exported clip, or for Avid exports to perform correctly in general.

MichaelP mentioned the 25 fps issue above, and we are working with Avid for a fix. Until then, your options are to disable exporting of Audio in the export preset. In 487, you can also export your camera audio as a BWF, and perhaps relink that later.

David

Edit -- forget to mention: the issue is Mac only.
 
Thanks for the help guys. I am going to be in touch with another EPIC M owner here who has worked with the same client and had success with the exports.

My next question on this transcoding process: As I set up the AVID export settings in RC-X, there are two fields selectable that state "Audio Only" and the other "ALE Only" ... but they are both selectable at the same time. Doesn't that defeat the purpose of calling it "only" one or the other? For me it seems confusing, but I'm not an expert. Part B to the question is, Is it necessary to have these unchecked or checked for standard uses of this kind of export? I left them both unchecked, assuming that I didn't need one or the other, but all of the above, if you will.
 
Last edited:
Yes, the ALE only export becomes an interesting solution when merging it to proxy capture systems on HD-SDI of the RED camera.

Michael
 
You must log in or register to reply here.
Back
Top