-
Really Bad Bug – FCP 6.02 assumes all imported audio is NTSC
This is really annoying. I was sent some 48khz SD2 audio files for the French version of a feature film. I was told it was meant to run at PAL speed. I needed to conform it to NTSC-based speed for this project. The problem was, FCP just assumed it was already NTSC and there was no way I could convince it otherwise.
When I placed it in a PAL 25fps sequence, it automatically alters the speed to convert it to PAL speed (even though it already was). This is a really messed up oversight on Apple’s part!
Essentially, it’s not a “normal” speed change (like when you do it yourself). Even thought the duration changed accordingly, and it shows a green “I need rendering” bar, it was done automatically by the system and it can’t be changed by the user. FCP still said it was “100%” speed, and the option to remove speed attributes was not available (grayed out).
I then tried first converting it to AIFF, MOV, and WAV before importing – it made no difference.
My workaround was so pathetic and it took half the day. I had to import it into After Effects (which doesn’t make stupid assumptions as to what video speed your imported audio should run at), I placed it in a PAL composition, added some bogus video to it (just black) and exported a PAL quicktime file containing both video and audio. Then, and only then, would any QT-based program recognize it as PAL and I could then conform it to 29.97 properly using Cinema Tools.
Totally ridiculous. I don’t know how people who work in PAL regularly have been able to deal with this.
EDIT: Same thing happens if you have audio that has been exported to run at 24.00. Final Cut will assume it’s video speed (29.97/23.98) regardless. F-ing ridiculous! Put it on a 24.00 sequence and automatically conforms it to 24 – assuming it’s 29.97/23.98. Nothing can be done to change it back, and these false assumptions by FCP make doing the math for a manual speed change very, very difficult.
-
9 Replies
-
Its not doing a ‘speed change’ Its changing the sample rate.
Strange thing is, I can’t duplicate what you are talking about. I can bring the same 48k AIFF file into a PAL or NTSC sequence without any issues (No green line, rendering, etc). Not sure what is going on at your end.
-
[John Pale] “Strange thing is, I can’t duplicate what you are talking about. I can bring the same 48k AIFF file into a PAL or NTSC sequence without any issues (No green line, rendering, etc). Not sure what is going on at your end.”
Changing the sample rate is changing speed in a sense. That’s how FCP and Cinema Tools change the assumed playback speed in order to conform audio to different framerates.
I just trashed my preferences and it’s still happening. I’m re-creating the problem with every single WAV and AIFF I have on my machine. What are you running?
My system is:
Intel Mac Pro
FCP 6.02
OSX 10.4.11
QT 7.4.1
AJA Kona 3 installed, latest Tiger driversSean
-
[Sean ONeil] “Changing the sample rate is changing speed in a sense. That’s how FCP and Cinema Tools change the assumed playback speed in order to conform audio to different framerates. “
Yeah…I knew that….you sounded like you thought that FCP was doing a “conventional” speed change
My system is:
power mac G5 Dual 2ghz
FCP 6.02
OSX 10.5.2
QT 7.4.1
AJA Kona 2 installed, latest leopard driversIf you post an audio file, I can try it on my system and see what happens.
-
Thanks, I’ll try it tomorrow on a G5 w/ Leopard we have as well. I tried dozens of audio files. Stuff from our music library even. I don’t think sending you one is going to accomplish anything.
Sean
-
Is this not something us PAL users would have spotted some time ago? Can’t replicate this at all on my system. I think you have a system issue somewhere I don’t think it’s a “bug”
Steve Connor
Adrenalin TelevisionHave you tried “Search Posts”? Enlightenment may be there.
-
How are you exporting the files? QT only Audio from FC? If so they have a TC track that is causing you the problems.
You can try open the file in QT>Com-J> TimeCode Track> Delete
However I think that the suggestion of John is easier. Export as an .aiff and you won’t have time base problems.Mac OX 10.5.2-FC 6.02-QT 7.4.1
G5 2x2Gh 4GbRAM-BlackMagic Extreme
PMBP 17″Core2Duo 4GbRAM-AJA ioHD
JVC DTV-17″
SONY EX-1 . SONY PD170
..and always a big mess on top of the table. -
[rafael amador] “However I think that the suggestion of John is easier. Export as an .aiff and you won’t have time base problems.”
He said he did that. Thats why I wanted to look at these files.
-
I found out what’s happening, and it explains why you guys haven’t re-created it. BTW, I just tested it on two other machines and re-created it on those as well.
Here’s how you re-create it. Set your Easy Setup and video output to AJA or Blackmagic ProRes NTSC. Now create a ProRes PAL sequence (I usually have “Prompt for Settings on New Sequence” turned on so it’s easy to do this). Import any audio file, place it in the PAL sequence and you’ll see a green line through it and the duration will be incorrect.
The opposite is also true. Change your Easy Setup to ProRes PAL, but create an NTSC sequence. Then import any audio file, and you’ll see the same problem.
Looks like Final Cut assumes what playback speed imported audio is supposed to be based on what your Easy Setup is during the time you import the audio file.
The good news is that now that I know this, it can be avoided simply by making sure the Easy Setup is set to what I need at the time I import the audio files.
Sean
-
Good to know Sean.
Glad you figured it out.
Reply to this Discussion! Login or Sign Up