Doh, here we go again...
BWF DOES NOT have a framerate, nor does it have timecode!
BWF contains timestamps, and with that you (or your software) can calculate any TC you want.
TC 00:00:01:00 is described in BWF as 48000 (assuming you recorded 48Khz...)
Now most recorders start on a round number of seconds. (Meaning, a multiple of 48000 samples)
Thus if you don't slow down / speed up the sound, the outcome of Pal, 24 or NTSC (df) tc is always the same.
Now you can flag the file to be slightly faster / slower than 48000 (typically 48048) to make files compatible between true 24 and video 29.976.
This has nothing to do with the actual speed it was recorded, just 4 bytes are changed describing how many samples per second the file is. By 'misintepreting' this number, the sound speeds up / slows down without quality losss (at the cost of a .1 % pitch change)
Now to alter those parameters, indeed Wave Agent is the way to go.
As for syncing in FCP, if the start is good and the file drifts out of sync, you got a wrong setup. FCP interprets the BWF based on the last choosen setup. So pick the correct setup for a new project (you don't have to actually USE that project), QUIT fcp, open it again and import your BWF.
Bouke
http://www.videotoolshed.com/
smart tools for video pros
Reply
Like
