John Heagy
Forum Replies Created
-
We gave it a try over a year ago and while the DAX plug in for CatDV was very slick we didn’t like the DAX onto top of BRU architecture. BRU is very back-up centric and we felt it was limiting when asked to do archiving.
-
So it was Media Manager that made the -v files? We don’t use Media Manager (thankfully) or the merge command, but doesn’t the -v indicate separate video and audio files? They’re aren’t a matching set of -a files anywhere?
Tell me if I have the steps correct…
1) 23.98 Alexa shoot
2) 23.98 dual audio
3) Both synced in FCP on location
Given there was drift I assume the syncing was done clip by clip on the timeline and not using the merge command? If so how were the clips joined? Were these synced clips exported or only existed as “clips” in a FCP Bin?
4) These synced clips were edited into a seg.
5) Seq Media Managed which produced error prone clips with -v that can’t be opened anywhere? -
[Jeremy Garchow] “Hmm. Wonder what the TypeCode is?”
No MacType, should be MooV, and no CreaterType, FCP is KeyG and QT is TVOD
[Jeremy Garchow] “What if you mark in and out on the orig, copy, make a new container, paste and save as self contained?”
That should work.
-
[Jeremy Garchow] “Did you try a quick conform in CT?”
The Conform button is grayed out when opening original Alexa QTs. We also captured footage direct to a KiPro (needed audio) and conform is active for those. Definitely someth’n up with Alexa QTs.
Modifying Camera Original files is something we would never consider anyway… even names. We would need to copy them first, in which case I’d just use CatDV to batch export as self contained and fix them that way.
[Jeremy Garchow] “Meaning without resaving as a self contained?”
Yes trim then Save, modifying the original file.
-
[Jeremy Garchow] “And finally ProRes 4×4 doesn’t play on kipros no matter what the source.”
Correct… These were ProRes(HQ) directly from an Alexa and would not play on a KiPro unless exported from a FCP timeline or via a QT Save As…
The Media Manager and KiPro issue point to a QT wrapper/media disconnect. I know for a fact the KiPro ignores the wrapper and looks at the media track. Try trimming a movie in QT and see if the KiPro respects it… it won’t.
John Heagy
-
Glad to help. You may be able to get away with just making new ref movies. I have a feeling it’s the wrapper that causing issues so a ref movie would solve that. I’d try using FCP’s batch export to quickly make ref “copies” of all the Alexa media. Just take are not to isolate the ref from it’s “kin”.
-
There is something odd about Alexa QTs. They don’t play in KiPros for example. I had to do a simple Save As… in QT to get them to work. It may be the way they are recorded. To avoid complete file corruption if powered down while recording the Alexa opens and closes the movie for every frame it records.
-
[John Heagy] “What name are the cards formatted with prior to recording? Just the 3 digit serial?”
That one I can now answer: All cards are formatted as ARRI_UDF Certainly beats NONAME!!!!
John Heagy
-
Are you using a Kona3 card? If that card is referenced to 29.97 and you load a 23.98 seg… FCP will be very unhappy. If the above is the case either switch your ref to 23.98, feed a 23.98 HDSDI signal and switch sync to input, or switch to Free Run.
John Heagy