Went through the Readme and discovered about the new 24fps TC for sound. (See bottom of this message).
I happen to work on a film project, shot on Alexa at true 24fps and sound recorded with an Aaton Cantar. We set up a project in 1080p/24. Camera rushes are prepared in Resolve and are delivered from the studio as DNxHD115 media files, along with the ALE(s) from the camera. Sound is in BWF but imported track by track, and tracks are regrouped in single clips using the ALE created by the Cantar on location. It allows us to carry all the info from the shoot into our bins - neat method pioneered by Job here on this list.
It's still the early ages of the project, so I'm tempted to update to 7.0.3 from 7.0.2 (on which the project was started) - Mavericks support is one of the reasons, but also the new "extra light AAF export" and some bug fixes. At some stage (I think the first time I imported a JPEG file into one of the bins), Media Composer asked to chose an SD resolution (I had never encountered this message before), so we went for PAL since the film will be edited and the finishing happens in Europe. So I should be safe since the Readme talks about 24fps sound in "non-Pal" projects.
But better safe than sorry... I wasn't really able to guess from the Readme if that new 24 Sound TC might create problem down the line when we will move to the sound edit / mixing stage on Protools. I have an assistant on location, doing all the importing and synching, she's on 7.0.2 too, and won't move to 7.0.3 unless asked to.
Happy holidays!
Pierre
> Support for 24 Frame Sound TC in 23fps or 24fps Non-PAL Projects
> Previously, Sound TC was only supported at SD video rates (25 or 30). Historically, sound recording devices generally worked at 30 or 25 based timecode. Now that most 23 or 24 rate production uses 24 based timecode we have added support for this timecode rate for 23 or 24 based projects. The following explains how support has been added for 24 frame Sound TC in projects with rates of 23fps or 24fps (excluding 24p PAL).
>
> There are two main ways to enter Sound TC into the editing application: ALE import and bin entry.
>
> ALE Import
> A new global title (not a column heading) has been added to the ALE format. This new element is called SOUNDTC_FPS and defines the number of frames per second for Sound TC in the ALE. Acceptable values are 30 or 24. If the SOUNDTC_FPS element is missing, you will be prompted to select the Sound TC rate if there is a Sound TC column in the ALE.
>
> The SOUNDTC_FPS element is ignored with a warning in non 23 or 24 rate or PAL 24p projects.
>
> If Sound TC already exists when performing an ALE merge, the new rate defined in the ALE or selected by you will be used.
>
> Manual Entry of Sound TC
> When entering Sound TC manually in the bin, you will be prompted for the Sound TC rate if there is no Sound TC for that clip. If Sound TC is already entered for this clip, the rate of the current Sound TC will be used. Thus, you must clear the Sound TC field if you wish to change the Sound TC rate.
>
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (16) |
No comments:
Post a Comment