Josh Olenslager
Forum Replies Created
-
Use the blade tool to slice around the audio you want to change the speed on. Simply adjust inside the cut — it will be affected while everything outside the cut will remain normal speed. Note that as you change the audio speed the video / audio following it will slide as well.
Josh
-
I agree with Michael. It’s probably a confused frame rate. I’ve also seen increasing and significant drift when one file is dropframe and one is non-dropframe. That could account for an increasing drift versus as well.
Josh
-
Paddy,
you need to transcode your footage to .mov instead of .dv. Been a while since I looked at that format footage, so I’m unsure if QT pro can read it or not. (If there is a plugin in QT use the “export” function and select DV output there.) If not, grab something like VLC and output as DV settings with .mov setting. Give that a try–should react better in FCP.
Josh
-
Makes a lot of sense. Always the simple stuff, isn’t it.
Josh
-
Dirty heads could always be an issue. And you’re getting a preview at your capture station? What about the 3 second failures — is a file being created or just straight to the error? I know that the DVCpro deck I used had be be set up perfectly (internally) for things to work right. So you could start there. You don’t have a kona card or the like do you? If so, you might route things through it and see what happens. Also, how is your scratch disk? In the user preferences you might also take a quick peek at the capture settings tab. Try unchecking the abort capture option. Might work. If you’re using non-controllable setting with capture now, it shouldn’t matter if the tapes are funky or not so long as they play back — meaning that it could be something in the system preferences. I know that I’ve also had to fast forward the entire tape and then rewind it using that specific deck. The only thing I could figure is that the tape was wound too tightly when I received it and the deck, for whatever reason, didn’t like that. Once it had wound/unwound the tape itself, I sometimes had success. Something to try at least if the issue persists.
Josh
-
Maybe the tape is just troublesome. You could try using the non-controllable control setup and capture now. Not ideal, I know, but if that lets you capture then it will narrow down your list of possible causes. Also, you have to have some pre-roll. I’ve had the same type of trouble on DVCpro decks when I’ve tried to capture too close to the tapes beginning. Set up your in/out points, but leave about 10 seconds of pre-roll in your capture preferences — or course that means that you’d miss out on that selection of footage. I’m not sure why, but it seemed, at least for me, that I had to have a good amount of lead in so that the disk speed on the capture system and the deck itself had time to get on the same page.
Good times all around.
Josh
-
I believe it is the system settings where you can define this — might be user prefs though. Look for still frame duration and set to your duration. Generally when I’ve worked with image sequences, I open them in quicktime and then import that into final cut. I guess it depends on what you’re doing in edit though.
Good times.
Josh
-
AND
Import color labels defined in finder into FCP so I don’t have to scrub footage twice.
Josh
-
Unless I’ve been terribly misinformed (and incorrectly converting to PAL DV this whole time), field order should actually be upper first for PAL DV; I’m about 90% sure this is the case — although it is true that NTSC DV is lower first.
By the way, what setting are you using in Compressor? The standard DV PAL template? And where is your final output headed, to DVD? Broadcast? It might be worthwhile to export using different codec/package than DV depending on where you intend to go. Plus, if you’re actually trying to retain 50fps you’ll probably need to set that up custom anyway under the video settings dialogue in your compressor setting.
Josh
-
yeah, might just be a bug of some kind. Did you check your auto-save vault? Maybe there’s a file in there that isn’t corrupted, or even a “save as” command. I’m not sure. I don’t know where you’re pulling the media from, but if it’s on an external drive that could also be related. I know that drives like to function with 20% free capacity so as they move data around to deliver it, they don’t start tripping over themselves. Not sure, but something to keep in mind for the dreaded “next time.”
Good luck Jason.
Josh