Skip to main content
Cutter61
Participating Frequently
May 20, 2024

Multi-Cam Audio audible/not audible depending on track placement - solved in current Beta 24.5 (46)

  • May 20, 2024
  • 5 replies
  • 400 views

I did not see this particular issue addressed in past posts, in either this forum or the beta forum. I am posting mainly to point out the issue that existed pre-beta, which may already be a known bug. (did I search known bugs - no, no I did not...)

 

Multi-Cam audio (details to follow) on A3&4 becomes inaudible as clips are added. Waveforms are still present. Preceding clips from SAME SOURCE are still audible. If said inaudible clips are moved up to Audio 1&2 they then become audible, but the preceeding couple of clips are no longer audible. If all clips are pasted into a brand new sequence, oddity persists. If on a section of the problematic clips is pasted all is audible. Eventually problem returns.

 

Screen capture of this in progress:

https://f.io/bgAAFGtC

 

This certainly seems like a mapping issue, but usually there is waveform evidence of bad mapping, and it certainly wouldn't change given a single source file.

 

Maybe a buffer problem? Or the cache files, are those broken out into portions of the master clip?

 

MC audio setup setup:

Source files:  23.976 MPEG-4 48k AAC, H.264, 7 channel mono playing from SanDisk Extreme over thunderbolt 4.

MC source sequence created with "Automatic" sequence preset & "Automatic" audio channels preset.

Result is 7 channel 48k mono sequence with 14 tracks, 8-14 are muted. Each track is mapped to it's coreesponding output channel.

I then muted 3, 4 & 7 to use only the 4 tracks needed (host lav, host boom, guest lav, guest boom).

I cut this source into a 2 channel master sequence, with everything panned center, patching my 5&6 to 3&4 so as to keep all interview audio at the 'top'. Weirdness eventually shows up...

 

Eventually during troubleshooting, I flattened all of the Multi-Cam audio and this completely eliminated the problem. I would much rather cut with flattened audio anyway, but this involves another step (or several, depending on where you are in the project). The "edit as nested files or individual clips" button was my go-to, but it has been discontinued, I believe.

 

Finally I switched to the (then) current Beta and the problem is solved. The very same squence that was giving me problems played correctly in the Beta 24.5 (45). Still solved in build 46.

 

Troubleshooting steps:

Re-start app

Re-start Mac

Clear all cache files with Premiere.

Manually clear ALL cache files and common files

Switch to laptop

New Sequence

Brand New Project

Cut & Paste small section to new sequence - slightly improved results

Flatten Multi-Cam audio - this solved the problem completely.

Increase I/O buffer

Decrease I/O buffer

Switch to Beta.

 

System Specs:

Mac Studio (2023) M2 Max, 64gRAM, Currently running Ventura 13.6.4, Premiere 24.4 (62) & Beta 24.5 (45)

MacbookPro (16-inch,2021) M1 Max, 64gRAM - Currently running Sonoma 14.4.1, Premiere 24.4 (62)

 

Let me know if I can provide any more info.

Cheers,

Dan Monro

dmonro@mac.om

 

5 replies

Cutter61
Cutter61Author
Participating Frequently
May 24, 2024

No sweat Kevin! I was mainly reporting for documentation purposes.

 

Cheers!

Dan MonroDMONRO, LLCMac Studio (2023) M2 Max, 64gRAM, Currently running Ventura 13.7.2, Premiere 25.1.0 (73) & Beta 25.2.0 (68)MacbookPro (16-inch,2021) M1 Max, 64gRAM - Currently running Sonoma 14.6.1, Premiere 24.4 (62) & Premiere 25.1.0 (73)iMacPro (2017) 3ghz 10-core Intel Xeon W, 64gRAM, Radeon Pro Vega 64 16g - Currently running Ventura 13.6.1 Premiere 23, 24 & 25 & Media Composer 2023.3.1Homemade PC IntelCore i9 3.6ghz, 64gRAM, NVIDIA GeForce RTX 2080 Super - Currently running Windows 10 Pro 2004 & MC 2020.12
Kevin J. Monahan Jr.
Community Manager
Community Manager
May 23, 2024

Hey there, Dan (@Cutter61),

I appreciate the response, and I'm sorry you're suffering from this bug. As a consolation, it sounds like there is a fix in Beta, so you know it will be in the stable version shortly. What a hassle, I know! Sorry about all this. At least you know the cavalry is on the way. Let me know if you need anything else in the meantime.

 

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Cutter61
Cutter61Author
Participating Frequently
May 20, 2024

Hi Kevin,

 

I did try a brand new project. And when I say minor improvements when pasting just a section, I mean it fixed the aduio issue, but as the sequence got longer it cropped back up witha different portion of the source sequence.

 

These files are proxies that my client makes - I'm not sure what the original camera files were. Unfortunately, their proxy workflow is a little, shall we say, inconsistent. The type of proxy changes depending on who makes them.

 

I did NOT try creating my own proxies of the proxies, though, if that's waht you're looking for.

 

~ D

Dan MonroDMONRO, LLCMac Studio (2023) M2 Max, 64gRAM, Currently running Ventura 13.7.2, Premiere 25.1.0 (73) & Beta 25.2.0 (68)MacbookPro (16-inch,2021) M1 Max, 64gRAM - Currently running Sonoma 14.6.1, Premiere 24.4 (62) & Premiere 25.1.0 (73)iMacPro (2017) 3ghz 10-core Intel Xeon W, 64gRAM, Radeon Pro Vega 64 16g - Currently running Ventura 13.6.1 Premiere 23, 24 & 25 & Media Composer 2023.3.1Homemade PC IntelCore i9 3.6ghz, 64gRAM, NVIDIA GeForce RTX 2080 Super - Currently running Windows 10 Pro 2004 & MC 2020.12
Kevin J. Monahan Jr.
Community Manager
Community Manager
May 20, 2024

Hi @Cutter61,

Thanks for all the info you provided. Great job. I am unaware of this issue and will need to do some searching around to find out if it is known.

 

In your troubleshooting steps, you said you copied and pasted the sequence's contents into a new sequence with only minor improvements. Right? Did you try importing the sequence into a new project? If not, see if that might work so the team can isolate this issue.

 

You mentioned your footage was 23.976 MPEG-4 48k AAC, H.264, 7-channel mono. From which camera or source was this footage recorded? Were proxies or transcodes ever tried during troubleshooting?

 

Perhaps @Ben Insler might be able to reproduce this issue. What do you think?

I'm glad the issue is solved for you in Beta 24.5.

 

Thanks,

Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Cutter61
Cutter61Author
Participating Frequently
May 20, 2024

I did not see it listed as a know bug...

Dan MonroDMONRO, LLCMac Studio (2023) M2 Max, 64gRAM, Currently running Ventura 13.7.2, Premiere 25.1.0 (73) & Beta 25.2.0 (68)MacbookPro (16-inch,2021) M1 Max, 64gRAM - Currently running Sonoma 14.6.1, Premiere 24.4 (62) & Premiere 25.1.0 (73)iMacPro (2017) 3ghz 10-core Intel Xeon W, 64gRAM, Radeon Pro Vega 64 16g - Currently running Ventura 13.6.1 Premiere 23, 24 & 25 & Media Composer 2023.3.1Homemade PC IntelCore i9 3.6ghz, 64gRAM, NVIDIA GeForce RTX 2080 Super - Currently running Windows 10 Pro 2004 & MC 2020.12