-
32kz capture
How exactly should I set up to capture 32khz 12bit audio correctly from DVCam? No, I don’t know why the shooter used it, they just did.
But there aren’t any capture presets for 32khz. So I’m creating my own and there’s no setting at all for 12bit. The closest I can come is 32khz 16bit. It seems to work, but just wondering if I’m missing something.
Using standard DV capture throws off all kinds of warnings about audio rate mismatch, and even rendered, the audio sounds horrible.
I could’ve sworn that in previous versions of FCP 32khz capture wasn’t an issue. I never bothered to even check what the camera op shot. But now, if you load it wrong, it’s nasty.
Bret Williams
Web Design ? -
11 Replies
-
I have never, ever had any issues with 32k audio on a 48k timeline.
The consideration is that that capture is based on SECONDS, not SAMPLES, anyway.
So 58 seconds of 32k audio plays in 58 seconds.
And 58 seconds of 32k audio plays in 58 seconds.Just go ahead and capture at 48k and see.
I’ll bet it won’t give you any problems. -
Sorry,
My “fabulous analogy” fell flat due to poor proofreading.
It SHOULD read:
58 seconds of 32k audio plays in 58 seconds.
58 seconds of 48k audio plays in 58 seconds.
-
I don’t have access to FCP at the moment but you’re on the right track about creating your own capture preset. In order to get the audio bit rate down to 12 you need to go to Audio/Video Settings>A/V Devices. Choose 4 channels instead of 2 and that will allow you to change to 12 bit and also set the sample rate to 32 Khz in that dialogue box as well. Name your new capture preset DV NTSC 12bit 32Khz. Then you’ll be able to access that preset in the log and capture window.
You’re right: capturing 32Khz 12 bit audio using the regular 48Khz 16 bit preset invites all kinds of audio glitches, including audio/video sync issues.
– Don
“Please take a moment to fill out your profile, including your computer system and relevant software. Help us help you.”
-
That’s what I thought as well, but if you look at the dialog there in AV devices, you’ll see it says “playback settings”
That’s the only way to get 32khz 12bit out of FCP. You have to change that setting and I’m familiar with it.
So, I went ahead and changed it. You never know. But still when you create a capture preset the only audio options for DV are 48 16 or 32 16bit. There is no such thing as a 32khz 16bit DV signal. But I tried it. Guess, what, all the clips are out of sync!
So, I can go back to 48 and they’re in sync, but have strange audio gaps and pops, because the clips themselves are trying to do some weird on the fly conversion.
I’d pull my hair out if I had any left.
-
I don’t ever have sync or other problems with 32kHz files.
Try exporting the audio and convert it to 48kHz with iTunes or QTPro.
-
Save yourself the hassle and dub it to another firewire tape using 48k audio.
-
But you do get the error message that says the audio rate doesn’t match your capture settings, right? Or have you made a custom 32khz 12bit setting somehow?
Anyway, here’s my discovery… We have been using an xl1s to load in because the DV deck is in the shop. So, I brought one of the tapes home to my system tonight and tried it with my DSR-11. I got the same error message when loading 32khz into the standard DV 48khz easy setup, but there were no problems with the file. No sync issues, no pops or gaps.
I conclude, that it’s 32khz being loaded from the XL1s over firewire. It sounds fine being monitored.
The only other difference is that the other system we were using is 5.1.2 and my system is 5.1.4. But I don’t think there’s any 32khz bug with 5.1.2.
-
That’s just a ridiculous solution. There is no reason FCP shouldn’t be able to load 32khz audio. It has had no trouble mixing 32khz with 48 since version 1.0. You’re also asking to dub 7 masters of 1 hour each. Only a total of about 60 minutes even needs to be captured. Once you make the dub, you’ll still have to capture. And wait, if you dub firewire to firewire, won’t the copy be 32khz anyway? I think so if you make a clone. Which you would, because the tc needs to be retained of course. Nah.
Anyway, see above post. I think it’s the XL1s we were loading from. I brought a tape home and had no trouble from my DSR-11. Blame Canon again.
-
[Bret Williams] ” I brought a tape home and had no trouble from my DSR-11.”
That was what I was trying to say earlier.
The sample-rate difference has never given me any trouble in years of editing FCP.Sync, even in very long clips, simply has been dead-on, 32k or 48k.
As to the Canon issue:
I have vowed long ago never to purchase ANYTHING with a Canon nameplate.
Ever since the problematic XL1’s (75% of the time, the heads simply don’t match any other DV unit) and my GL1 with its “dead pixels” appearing right after the warranty ended.I even threw out my Canon printer and bought Epson, just so i would not give Canon any more money for INK.
-
[Bret Williams] “That’s just a ridiculous solution.”
Hey, whatever man. I am not asking you to do anything. By the time it’s taking you to fix this, you could have dubbed and captured all of the media by now. There’s ways to dub tapes with slaved timecode and different audio settings. It’s not rocket science. Don’t blame Canon, blame a shotty DP who doesn’t know how to use his camera.
Good luck in your endeavors.
Reply to this Discussion! Login or Sign Up