Debe
Forum Replies Created
-
Ahh, and I was going to chime in with my first generation Blue and White G3 is still an administrative workhorse…but the beige G3 trumps that!
debe
-
If these DVCam tapes are your only source, and you’re in NTSC-land, capture at DV/DVCPro NTSC, unless you have other sources from other formats captured through a I/O card.
I’m guessing since you’re using firewire to capture here, you don’t have an I/O card, but I wanted to cover that base.
Have you upgraded any software since this last worked for you? Since FW is not recommended for media storage, the headroom in FW that may have allowed you to capture before this way may have been repurposed by the app. This is why the second FW bus is recommended.
If nothing has changed, try powering everything down and letting it rest for 5 minutes. Then power up in no particular order, except make sure you turn on the CPU last.
debe
-
“b” selects the blade tool. You still have to click the timeline to actually make the cut.
I think Mike wants a keyboard command that makes a cut at the playhead?
CTRL+V does that on the default keyboard. If you’ve remapped things, search for “add edit” in the command list.
debe
-
Avid should be able to read the EDL. I use GVG, but that’s because I’m an old GVG linear editor. I can read a GVG EDL like it’s a book. Many others use CMX.
EDLs only deal with 1 video layer and up to 4 audio channels. If they used multiple video layers and had more than 4 channels of audio in the FCP timeline, expect multiple EDLs that you will need to sync in the Avid.
Automatic Duck would make this much simpler if it’s a complicated timeline, but it’s not required. If it’s a simple timeline, AD would probably be overkill.
Automatic Duck is a great application! When you need it, it is fabulous!
debe
-
“Debe, get to bed! :-)”
that was my last post last night…
how’d you know, Don?
debe
-
CDs by definition are 44.1 K. Anything else won’t play.
debe
-
In point and out point aren’t the numbers you need to look at. It’s Media Start and Media End.
In point and out point are if you have a mark in and/or a mark out on the clip. Prior to capturing, you shouldn’t have any!
What do the Media Start and Media End times say?
debe
-
One little thing…
A guy I know who travels the country doing PowerPoint for a living practically removed my spleen when I asked if MPEG1 was okay for PowerPoint.
In his vast experience, MPEG1 creates way more problems than it solves. If he HAS to go lower end, it’s AVI. He will NOT use an MPEG1 file in a PowerPoint presentation unless he has ABSOLUTELY no other choice.
But, to each his own. If it works for you, then use it. His reaction to the thought of it was pretty severe, so I thought I should pass that along.
debe
-
If they have masters…
Just tell them that to “re-encode” the Real files into something editable, it would take almost as much time as recapturing from the original tapes. The quality will be MUCH better than recompressing the Real files an extra two times, and they’re really only saving maybe 10% of the cost, but losing perhaps 50% of the quality. Real is not a editable codec, it’s a delivery codec.
If they can argue with you, then they’re just cheap and tell them they get what they’re willing to pay for. If they can’t argue with you, then what they don’t know WILL HELP them.
debe
-
Depends on the PC.
There are plenty of variables, but if they have a recent PC & the most up to date version of Office, WMV file is probably the easiest to deal with.
If it’s an older PC and an older version of Office, an AVI would probably be the best bet.
The PC should have a dedicated video card that doesn’t share system RAM. Playing back video in a PPT takes up a lot of video RAM, and if that RAM is being shared with the system, the video may stutter and/or in the worst case scenario, PowerPoint may crash.
If you can get the specs of the PC that will be used, post back and we might be able to tell you what’s your best-est bet!
debe