Hello everyone,

I've been working with MC 5 for a few days now as an assistant editor on a french feature film and i've just noticed a pretty serious issue concerning the sync step.

Let me explain, the format is 35mm 3p and the sound is recorded by an AATON Cantar. Everyday, before syncing, i import the wav files that come on on a DVD burnt by the sound ingeneer and duplicate the TAPE ID column into the SOUNDROLL one and the START one into the SOUND TC one, informations that is kept by the synced clip, in order to be able to generate EDL of audio tracks once the editing is done and allow the sound conforming guy to operate (generally by feeding to a TITAN).

Except with my MC 5, soundroll information isn't transmitted to the synced clip. I have to enter it manually for me to avoid any problems.

Does anyone already notice that ? Am I working on a corrupt version of MC5 ?

Thx

Bonjour Edouard,

Strange, I don't see that on my machine, but then my project was started with MC4. You should post in the Film Forum on this board.

OK, I just did a little test, and something odd is happening here too.

Some clips get the Soundroll entry, some don't. My project was started in v4, then continued in v5. This is all source material that was brought into v5.

I would love for some other users to try this out and report back so I can collect some more data for escalation.

Important precision : My project was created on a Symphony 4.0.5 and the problem only appeared as soon as i started working on MC 5.

I think this problem is going to cause some nightmares to assistant editors if it is confirmed by others...

I'd especially like to hear from anyone who is starting a brand new version 5 project.

My test is very similar to that of Edouard, as my project was also started under SN/MC 4.0.4/4.0.5, then moved to SN/MC5.

P.S.: we should move this thread to the Film/24p Forum rather than duplicating it there.

I must have a couple of BWF files on the drive, I'll try to test that later today with a new Test project.

I am moving this thread to the Film and 24P Forum.

I'll ask QA to replicate the issue here. Also, even when AutpSyncing clips, an audio EDL will use the timecode from the START so unless the SooundTC is a different rate and is needed, there is no need to duplicate the same timecode in SoundTC just for the sake of an EDL.

Michael

Hi MichaeIP, I would like to understand more about the specific differences between import and link for iXML and BEXT metadata in the current version. Should the Sound Roll and Sound TC columns in the Bin be automatically populated when using import or link?

I am using Avid Media Composer 2024.12. According to the Editing Guide:

The following describes the differences between importing a BWAV file or linking to a BWAV file using the WaveAIFF Plug-In.
• The import process does not read iXML metadata. Performing a Link operation will read iXML metadata.
• If the BWAV file contains an iXML tape name, this will appear as the “Sound Roll” and will override the BWAV specification of “Tape.”
• Import will automatically group multiple mono clips based on file name patterns. Linked files will not.
• The linked version of the clip may sometimes be one frame shorter than the imported version. This is because import is able to pad the end of the file with silence to fill out a shortage of audio samples in the last video frame.
• During the import process, you are prompted to select the TC rate, and the Sound TC and start time are displayed. During the WaveAIFF linking process, you are not prompted to select the TC rate. The file TC rate comes from a setting (if not present in the file itself), and the Sound TC and TC rate used are displayed in bin columns.

Observed Behavior:

• Regardless of whether I use Import or Link, the Sound Roll and Sound TC values remain empty. This is inconvenient for workflow, as I have to manually copy the values into the columns. In fact, I believe Avid should automatically copy the Audio Tape and Start TC into Sound Roll and Sound TC when performing Import, Link, or AutoSync.
• Since the current version appears to read iXML by default, the Editing Guide should be updated accordingly. Strangely, I haven't found any mention of this change in the ChangeLog, which is quite confusing.

Would appreciate any insights on this!