avid mxf red workflow

[MichaelP]

You need to track the 24TC in the TC24 column so to not have it skip. The START column is counting in 30fps with every 5th dropped to reflect 24fps image capture.

Michael

[jamie parry]

thanks MichaelP
the tc24 column all works ok and the tc 24 value agrees with the "burnin" value (for a bit).
but my DV is not "captured or "imported" it's made in ffmpeg and wrapped in an mxf container.
currently there's no way in ffmpeg to drop the extra frames made in the ffmpeg transcode to DV step so you get "extras" every 5th frame or so which makes the TC 24 go out of sync.
the problem is the extra frame doesn't happen when the avid thinks it should do (because it wasn't in control of the process) so i'm slightly out of luck here i think!
currently if you want to do DV mxf able to relink back to 23.976 DNxHD or other 23.976 sources you'll have to do a metacheater ale and import as DV in a 23.976 NTSC project.
i'll be messing about tomorrow to see if i can at least help that process along.
cheers
j

[MichaelP]

So it's actually making 29.97fps media and not 23.976 media. Try one of the other codecs like 14:1 and see what happens.

Michael

[david m friedman]

OK i will ask for that to go in.
175....we're getting into territory where "offline" doesn't accurately describe what's going on.
Should that bit of the process be called something else?
Prep?
1st stage transfer?
something else???

j

sorry that it's been a while since i responded...

175 for 'offline' would just be 'file transcoding' or as you suggested 'prep'.

the reason i asked about it was that sometimes i don't really need an offline/online workflow, but DO want MXF files and an .ale to load into an avid media composer or avid DS

(now i've gotta catch up on the rest of the thread from the last fortnight.)

david

[jamie parry]

hello everyone
today in jamfuze land....

i finally got around to looking at what those burnin thingies do
so now there are 5 options in the offline jamfuze for burn ins
NONE
ALL DATA
JUST TIMECODE AND FILENAME
ALL DATA JUST ON THE FIRST FRAME
TIMECODE AND FILENAME JUST ON THE FIRST FRAME

all in a nice typewritery font with no silly background stripe. much better.
spoke to grownup developers today.
they have stepped beyond.....and are using the red SDK ooh errr!!
i asked if they were going to do a windows jamfuze they said not yet. So maybe in the future? who knows.
the limitation for me was always that redline is mac os x only. the sdk doesn't have that limitation.
i've managed to sort out the "spaces in filepath" thing in the offline version but not yet in the online version (they're subtly and annoyingly different. what was i thinking?) anyhow time ran out today but i've got a few more hours after a promo on friday maybe i'll crack it then!
j

[Jason Diamond]

jamie this is just getting better and better.
make sure to stay on top of them to get the new RED SDK when it becomes available so we can take advantage of the new color science that's been put forth.

also i think people will want the option of Edgecode or Time of Day in the Burn in options :)

any luck with the DV25? did my method help?

[jamie parry]

what do people actually use edgecode for.....
from a conforming point of view TOD is better no? lees likely to be duplicated?
i've done edgecode as on option for the mxf files in the smokeyfuze offline app i made for jason rayburn (they use a workflow to get DPXs for the smoke that relies on egecode) so i know i can do it but why.....
that's the question. genuine question.

oh yeah the dv25 thing...
i can make 640x480 DnxHD .movs easy (640x480 H264 is much faster though)
i can make an ale that references all those .movs easy
but there's no way from redline to make avid compatible audio in the QT (it's 32 bit I think) so unless the avids understand that now you're outta luck with audio
so you can batch import from the ale that i make and the timecode comes in OK now (media composer 3.5 an later)
does that cover it?
if so then i've done all i can.
I cannot make 23.976 DV from my thing. the avid DOES seem to make that kind of media in its "Import" operation which means OK tracking.
the fit option stretch works ok as long as the material is shot 16x9. if its shot 2:1 everything looks wrong. fit height/width won't work as the output is square not rectangular...
i'll include a DiamondDV option in the next jasonfuze if you like.
I don't think its any better than using red rushes an metacheater though.

j

[jamie parry]

everyone who is using jamfuze...
if you grade in red alert and then use jamfuze to make media with the grade applied (use folder rsx option)
don't tick "use edgecode" when you make the RSX in red alert.
it buggers everything up!
cheers howard in NZ for finding that one!!
developers are coming on nicely and they say it is very quick from the SDK....cool!
I want faster than real time rushes on 1 mac. keep your fingers crossed people!
j

[Jörgen Persson]

what do people actually use edgecode for.....
from a conforming point of view TOD is better no? lees likely to be duplicated?
i've done edgecode as on option for the mxf files in the smokeyfuze offline app i made for jason rayburn (they use a workflow to get DPXs for the smoke that relies on egecode) so i know i can do it but why.....
that's the question. genuine question.

If you shoot slow motion the TOD TC can overlap between shots.
Edgecode will start a new clip where you stopped the last one.

[jamie parry]

thanks for the info Jörgen
is there anywhere where the shooting fps is reported in the metadata (so not 25fps or 23.976 but 120fps or whatever?)
then i could switch to edgecode automatically if an "off speed" shoot was done.
or is it just best to use edge code always?
j