Dan Riley
Forum Replies Created
-
What do you mean, “analog video doesn’t work” ?
Dan
-
Matt,
I did two tests, one like you said from FCP, making the ref movie first
then dropping that into compressor and yes, I see timecode now. Very cool.
Then I did another test, dropping a DV original captured clip into compressor
and making the h.264 and it also showed me timecode. Great.Funny that is doesn’t work if you export to Quicktime conversion in FCP.
You have to do this extra step, but it’s not that big a deal.
Thanks very much for finding this out.Dan
-
I hadn’t had a crash in weeks until yesterday’s quicktime update.
It took two restarts of the Mac and today, no crashes all day.
Anyway, it brought up this problem because when FCP crashes and you bring it back up,
you have to go through a bunch of steps to get back to where you were.
First it starts up in a very old save, then you have to go to arrange
and get your window setting back, then you have to restore the project.
It’s too many steps I think. If I’m the only one who thinks this way,
OK, so I’m weird.Dan
-
Maybe Walter just got a bad batch of units. Glad to hear yours are working Jim.
I believe the price between the Sonnet and the CalDigit is about the same.
So now it gets even more interesting.Dan
-
I just did a test. I put a clip in the viewer and exported, Quicktime Conversion to
h.264. Played back in Quicktime player, no timecode.
Next I exported a short sequence that started at 58:45:00. Same type of export.
No timecode in quicktime player.The only place I see the new Quicktime 7.1.6 reading timecode is from my
original captured clips. This is not nearly as useful as I had hoped.
I’ve read the new Compressor in FCS 2 will be able to add the window burn
during encoding, so we’ll have to see it that works correctly.Dan
-
I’m also considering the Sonnet Fusion RAIDs. I saw them at NAB. The card is made by ATTO
for Sonnet and is not sold separately. The units are competitively priced and seem to be
built well. But so did the CalDigit units. Decisions Decisions.Dan
-
Not so fast maybe.
I’m not seeing timecode from exported h.264 files that I would upload to our
ftp site and have writers, directors, composers and clients view. You certainly
can’t upload a 6 gig 30 minute dv captured file, which is the only thing I’m seeing
that the quicktime player sees timecode on, as well as the uncompressed
10 bit SD files. Maybe I’m missing a check box somewhere, so please test
for yourself and prove me wrong.Dan
-
That’s not a big problem. People do it all the time. Usually we have the same
timecode associated with both the video and the audio, but you can still do it and
sync up manually.Load in both the video and the audio you don’t like from your DV camera.
(use that as a reference for sync).
Then load in your external audio. (I’m not sure how you plan to do that
since you didn’t mention the device you will use to record the audio).
Now bring them both onto a timeline and while listening to all the audio
tracks, slide one or the other around until they are synced.
Pretty simple once you do it a few times.
After you get them in sync, simply delete the audio tracks you don’t want to use.It gets complicated when you have many takes and the camera starts and stops,
but if this is what you want to do, that’s how you do it. Of course, if you can
use a timecode generator and feed both the camera and a hard drive audio
recorder with the same timecode, then you do what a lot of us do on shoots
to protect our audio feed. But that costs more, obviously.Dan
-
I’m having no problem with it running in my production machine,
FCP 5.1.4 OS 10.4.9.I just did the update too and it works fine.
The timecode viewing, I know some people won’t care too much about it,
but for having to send out DVDs (used to be VHS) with window burns
for transcripts or a quicktime for music composers, this is great. I hope Apple
released it for Windows too because that’s what our transcription people use
and also most of our clients.Dan
-
I would also use the 1402 for mic inputs, or other audio inputs,
but to do that you would need A to D converters,
because the K3 has no analog audio (or video) inputs
correct Bob? AJA has converters you recommend?Dan