![]() |
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#1
|
|||
|
|||
![]()
I'm curious where/how the metadata for Channel names comes from.
I receive all of the audio via AAF, usually Media Composer, and often find that the channel names displayed are incorrect - ie Channel A3 shows channel name "Boom" but really it's "Don", A4 shows "Don" but really it's "Sally". 75% (?) of the time, the names are correct but enough is incorrect that I need to take the time to make sure I'm selecting the proper clip, or go by Track Channel A3/A4, etc - but that can change on different shoot days with the same people. Is this all on the location sound person to get right, or is does it have to do with how it's imported into MC? Just curious if where this breaks down. Really not a huge issue - but it would be nice if we could rely on that info... Thanks! |
#2
|
|||
|
|||
![]()
The issue is with the location sound person. That's where the data is put in and it isn't altered after that unless someone went in specifically and changed the channel names in Media Composer (but it would have to be intentional.)
__________________
Pro Tools Ult 2023.3, RME BBF Pro + MADIface Pro • Mac Mini 14,12 - 12 core - macOS 13.3.1 • RAM 32GB, SSD 4TB, GPU 19 core • QNAP TVS-872XT 148TB TB3 Pro Tools Ult 2022.7, HDX 3, MTRX/SPQ, HD Omni • S1 x 2, FireHD x 2, Dock, iPad • Mac Pro 5,1 - 3.06 GHz 12 core - macOS 10.13.6 • RAM 64GB, SSD 4 x 4TB, GPU GTX 980 4GB |
#3
|
||||
|
||||
![]()
I've noticed incorrect channel names in AAFs exported from MC. This wasn't caused by the sound recordist setting the channel names incorrectly as loading the original poly WAVs into Pro Tools showed that the metadata was set correctly. Either MC didn't translate the metadata correctly while importing the WAV files, or while exporting the AAF. From memory I think it had something to do with poly WAVs that had mute channels or a channel sequence where the recordist had say recorded A1, A2, A4, A6. In this case I think MC wasn't assigning the channel names by the actual channel number, but by channel count.
This is one of the reasons you might consider assembling a PT session using the original location WAVs so the correct metadata is loaded, and to make sure all channels that were recorded on location are available. For more information check out the new EdiLoad Assembly window that I created. A full demo video is available in this blog post. Best regards, Mark
__________________
Mark Franken, MPSE Dialogue editor/supervisor IMDb Creator of 'EDI' applications for sound post editors www.soundsinsync.com |
#4
|
|||
|
|||
![]()
Thanks for that insight, Mark.
These are generally HGTV type renovation shows and time is tighter than ideal to manage that workflow - I would love to, but :-( And in truth, it’s just a slight annoyance and I was mostly just being curious curious the cause. |
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Field Recorder Workflow with Live PT sessions as Field Recordings | SlickSlack | Post - Surround - Video | 9 | 11-10-2022 05:45 AM |
Replacing a Clip with a Matching Segment from a Matching Field Recorder Channel | srdm77 | Pro Tools 2020 | 6 | 12-31-2020 01:22 AM |
Field Recorder Matching Channels Resulting in Wrong Channel Name | Felix Andriessens | Post - Surround - Video | 3 | 06-05-2019 11:47 AM |
Any ideas on channel spill for Field Recorder "Functionality"? | Ray JB | Post - Surround - Video | 24 | 06-14-2016 05:21 PM |
Field recorder channel and play lists | grant howarth | Pro Tools 10 | 6 | 01-03-2012 06:43 AM |