Mark Spano
Forum Replies Created
-
Only thing I can think of is perhaps your timeline is set for 16-bit audio. The Dolby E stream is 20-bit, so only a 24-bit timeline would preserve the stream intact.
-
only other thing I can think of is some sort of timing issue. Make sure both decks are receiving the same reference signal and that it is selected (i.e. Servo Ref = EXT / Ext Ref = SD). Also, the system setup must be identical. If you’re trying to do any kind of frame rate conversion, the Dolby E will not hold up through that.
I have almost the same setup and never had the problems you’re describing. And I’ve only had problems if the recording deck’s audio channels were not set to DATA. Setting it to DATA bypasses the bit rate / sample rate converters built in to the deck and preserves the stream integrity.
-
Must set your HDCAM deck channels to DATA instead of audio for those channels where the E stream is to land. This is in the VTR Setup menu somewhere, should be called NON AUDIO SELECT.
-
If you can have both sides use a QuickTime Player to view your files, then you could use something like QT Sync to insert a timecode “text” track into the file, which takes zero seconds to do since it is rendered within the QuickTime Player application. Try it out (it’s free and fairly intuitive).
-
FYI – FCP has no way of using audio LTC in your clips without some third party tool. However, this functionality is built in to Avid Media Composer, in the form of the Read Audio Timecode command. Extremely simple to use.
-
If you can consolidate your audio edit to fewer than 24 tracks, you can export an AAF to pass to the edit. The editor can load your AAF, make changes, then export an AAF back to you. From there, you can load the new AAF in, align the tracks with your old tracks, and scan through each track to see where things changed.
-
That usually does it for me. Can’t think of anything else to fix it. Next step would be to create a new project on that space and copy the bins over to the new project.
-
Why not just clone your boot drive and do the demo install / QT update on the clone? This will save you tons of potential grief.
-
Are you on a Unity style shared storage system? Open the project folder and remove the folder inside which has the name of the computer. Then try opening the project again.
-
Like you, I use this all the time, and the workflow in MC is very easy to adopt. I mapped the Extend function to the N key (as it seems a logical place for it and I don’t think there was anything there before) and always remember ‘exteNd’. (also mapped Fit-to-Fill as shift-N)
– activate track you want to extend
– park play head where you want to extend to
– clear any ‘IN’ / ‘OUT’ marks
– mark ‘IN’ if you are extending backward / mark ‘OUT’ if you are extending forward
– hit Extend