• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Single Channel Input from Multi-track Source records full mix of audio channels [Rodecaster Pro]

Community Beginner ,
Jan 18, 2024 Jan 18, 2024

Copy link to clipboard

Copied

The Problem

I'm attempting to map and record single inputs from my Rodecaster Pro II (multi-track source) in Adobe Audition. A few months back everything worked perfectly fine. I run a 3-person podcast and each person has their own mic and their own channel. Now, no matter the channel selected from my input source, it always records the same audio (the full mix of it). It's also not just the Rodecaster Pro II, I was also using an intermediary software that acted as a multi-track interface for other projects and that no longer works as expected. I've submitted a support request to Rode, but this seems like an Adobe issue and I need help fixing it. Is there some magic trick I've missed to make this work again? Why did it suddenly break after months of working just fine?

 

My Specs

CPU: Apple M1 Max

MEM: 64GB RAM
OS:
macOS Sonoma 14.2.1 (23C71)

Audition Version: 24.0.3.3

Rodecaster II Firmware Version: 1.2.2

Garage Band Version: 10.4.10

 

All My Troubleshooting

 

Debugging Audition

  • I have cleanly uninstalled and reinstalled Audition 24.0.3.3
  • I have cleanly uninstalled Audition 24 and installed the last known version of Audition 23 that was working for me.
  • I've checked basic troubleshooting requirements like...
    • Ensuring that the Recording "R" was selected
    • Ensuring the proper audio channel was selected
    • Testing multi-track recording with unique tracks selected for each
    • I've hard reset Prefrences (Shift+Opt on start of Audition) just in case 

 

Debugging Rodecaster

  • I've factory reset my Rodecaster
  • I've downgraded the firmware, then re-upgraded after it didn't fix anything

 

Debugging macOS

  • I've updated the OS for any subsequent patches
  • I've tried recording in different programs, looked at the MIDI program and Garage Band as comparisons. Both correctly recognize and capture the audio of different tracks.

 

I've uploaded two videos comparing Audition to Garage Band to prove I'm not hallucinating. Located in this google drive folder: https://drive.google.com/drive/folders/16_8RJO_HF_Pb6NdzpMu62ElZPyibBuyR?usp=sharing

 

I also tried to link the core audition video via Youtube, but the linking mechanism keeps saying it's private since it was initially marked unlisted. It's now public (enjoy the 23 seconds with friends) https://youtu.be/DH0K2E3BCT0

 

Views

284

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Community Beginner , Jan 27, 2024 Jan 27, 2024

I guess I'll call this resolved. I was not able to pinpoint the exact solution, but it must've been something within macOS's audio config. One detail I completely spaced on was I was using Rogue Amoeba's ACE program to capture browser audio. Even after uninstalling that the issue didn't go away, but a full wipe and fresh OS setup did the trick. I'm guessing that had a hand in this unfortunate debugging business, and I guess I won't be using that software until it gets a confirmation for Sonoma c

...

Votes

Translate

Translate
Community Expert ,
Jan 19, 2024 Jan 19, 2024

Copy link to clipboard

Copied

I have to ask you - have you successfully followed all the instructions in the specific Rodecaster setup guide for Audition Mac? It's available from Rode here as a .pdf.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jan 19, 2024 Jan 19, 2024

Copy link to clipboard

Copied

Understandable inquiry. Yes, I've followed this doc to the letter. I did it when I reset the Rodecaster and I did it again when I reset/reinstalled my Audition.

 

It's mostly aesthetic channel naming. The initial USB input configuration is straightforward and doesn't seem like there are any hidden settings on the Rodecaster or Audition that would be mixing everything down before recording.

 

The Rode support team just got back to me as well and asked the same thing. I'm going to give them the update and a link to this page, will report back if they produce anything that resolves the issue on their side. But again it seems the device is working fine with Garage Band's multi-track config, so I'm inclined to speculate it's either something misconfigured in Audition (not sure how it would have happened since my config isn't that involved) or something between macOS and Audition.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jan 22, 2024 Jan 22, 2024

Copy link to clipboard

Copied

Update:


I had a friend with the same version of Audition come over with his Macbook and hook up to my device. It looks like his inputs work perfectly fine. Which points to either a deeper issues with my Audition configuration or a problem with something in my Mac's system details. I have no idea at this point, but figured it was worth posting here.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jan 22, 2024 Jan 22, 2024

Copy link to clipboard

Copied

There's nothing else to configure within Audition, so I'd be looking carefully at the way the audio is aggregated - that's the most likely source of the problem. The only other thing (and this is a very wide shot) is to check the security settings to find out whether the extra channels need to be authenticated separately. That's all I've got, I'm afraid. But when you do figure it out, it would be good to hear what it was...

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jan 23, 2024 Jan 23, 2024

Copy link to clipboard

Copied

Will report back as soon as I know. For now, I'm backing up all my projects and see if there's a security setting. If not, I'll just factory reset my Mac and see if that resolves it. If that doesn't work... I will throw everything in a lake.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jan 27, 2024 Jan 27, 2024

Copy link to clipboard

Copied

Welp. So far it doesn't appear to be a security settings issue. I even wiped my Macbook and reinstalled macOS Monterrey to see if that would fix it, might've made a mistake in restoring a Time Machine back up rather than just starting fresh all over again. Still no luck either way.

 

Security settings seem fine. Audition has a fresh configuration. Rodecaster is up to date.

 

I have no idea what to do here.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jan 27, 2024 Jan 27, 2024

Copy link to clipboard

Copied

LATEST

I guess I'll call this resolved. I was not able to pinpoint the exact solution, but it must've been something within macOS's audio config. One detail I completely spaced on was I was using Rogue Amoeba's ACE program to capture browser audio. Even after uninstalling that the issue didn't go away, but a full wipe and fresh OS setup did the trick. I'm guessing that had a hand in this unfortunate debugging business, and I guess I won't be using that software until it gets a confirmation for Sonoma compatibility.

 

Case Closed for now.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines