Dan Riley
Forum Replies Created
-
For H.264 viewing people need to have QT 7, which has been out for two years.
And even if they are on a PC, if they have iTunes for the PC,
they have QT 7. So it’s getting pretty good coverage.
But the best coverage BY FAR is Flash. But that really is an art form.If you are encoding for client viewing, I always put a disclaimer
after the file download info that says they need Quicktime 7
or later and provide a link for PC users to QT Downloads at Apple.
Since doing this we have had zero trouble with client downloads.Dan
-
Arnie is right…. what are you playing back in your multiclip?
Great multicam, 4 to 9 angles, can be done with DV.
I can do 4 angle of DVCPRO50 too. But if you go up from there
you are asking for playback troubles. You need a fast RAID
and a recent CPU to do codecs higher than DV, in my experience.FCP’s Multicam implementation is actually pretty good compared to AVID.
It’s much easier to make multiclips with FCP. But using it
is not the same as AVID if that’s what you are used to.Double click your multiclip into the viewer. Then edit that into
your timeline. Then set ganging to “open” and play the timeline.
You’ll now have all angles playing in real time. Mouse click the angle
you want in the viewer as it’s playing. Stop playback and you’ll see
the edits done in your timeline. Then edit down from there.
It works quite well.Dan
-
repeat post. computer malfunction, trying to delete, can’t do it.
Dan
-
repeat post. trying to delete. can’t do it
-
Yeah, I don’t usually spout off something if I’m not sure,
but I was at home and couldn’t look at our old 1800 at the office
to check it out. Should have waited until I was sure.
Our DigiBeta 500 is nice because there is a switch on the front panel
for ref or input video. Comes in handy in a pinch.dr
-
So much for HD features from the iTunes Store on a Windows machine.
Not a good cross platform situation at all.dr
-
So there’s no “reference input video” menu setting on an 1800?
This would do the same thing.Dan
-
Randy,
Never heard that one before. Do you know if this is also true
with Vista?Dan
-
Yeah, Jeremy is right. I’d probably try that first. Simpler solution if it works.
Dan
-
Dan Riley
September 23, 2007 at 2:27 am in reply to: Nesting issues: how do we fix what we’ve done wrong?I’m not in front of my FCP workstation, but if double click on the nest,
the nested sequence should come up, then highlight the v track you want to
match to, go to the edit menu, match frame, source file. This doesn’t work?
I’ll check into it tomorrow to see what I find out.Why did you nest a sequence just to make subclips?
I can’t think of a reason for doing this extra step, so I’m curious.The reason I would not have done it the way you did was, by putting
all those clips on one timeline, you now have new timecode for each clip, so
if you output the sequence for transcribing, the timecode won’t be
the same as the clip you are transcribing. If on the other hand,
you DID lay down all those clips on one timeline, then dragged the
timecode reader filter on to each clip, it would then make a window
of the original timecode which you could then output for your
transcription person. This would work, but not if you nest.All of our shows have interviews and testimonials. We have everything
transcribed. The way I’m doing it now is, exporting a quicktime reference
of the clip, then dropping it into compressor and encoding h.264 and uploading
WITHOUT doing a TC window, BECAUSE with Quicktime 7.1.6 or higher,
your timecode is now shown in the duration window, Mac and Windows
version of Quicktime. This save the window burning step.Dan