Input Assignment Disabled When Switching Speakers

After updating to version 17 Beta and all versions as of today, I've noticed that my Input assignment reverts to No Input when I switch speakers. I have my main speakers set up as Main and my Focusrite Interface set as the speakers for Near.

When I assign an input to a track and record a track using headphones from the interface (Near), and then switch to Main to monitor from the speakers, the Input assignment reverts back to No Input instead of holding on to the assignment so I can jus go back to recording. Now I have to assign it each time I switch.

Is there a setting or is this a bug?

Are you switching between Main and Near via the Monitoring panel?

System spec? viewtopic.php?f=21&t=90190

I'm doing what I've been doing for a year. I'm in the Fairlight page and Under the meters, there is the Main output designated as Bus 1 > Main or Bus 1 > Near.

In previous versions I would just use the dropdown to switch between Main and Near and it was always fine. The Input assignment wouldn't change. Now it's reverting back to No Input, which makes no sense. Switching Speakers shouldn't do that.

This is definitely a "Do it my way" suggestion, but...the advantage of those is that they pretty much always work. (It's why I do it that way. )

Use speakers with a headphone jack. Don't switch.

In previous versions I would just use the dropdown to switch between Main and Near and it was always fine.

Are you also experiencing this behaviour in Fixed Bussing mode or only in Flexi mode?

Project Preferences > Fairlight > Audio Busing Mode

Note: The checkbox is only enabled with new Projects and empty Timelines
(same behaviour as the Timeline Frame Rate).

Thanks for the response. Very good question.

I don't think I've seen the option for Fixed Bussing or Flexi Mode. That means that it's in whichever mode is default.

I'll take a look and let you know.

The issue is still there regardless of Bus mode.

Am I the only one that is having this happen? I find that hard to believe. Weird change to the software.

Never had this with v15 or v16.

I don't get it.

Am I the only one that is having this happen?

System spec? viewtopic.php?f=21&t=90190

Not reproducing this behaviour on macOS, switching between the five different I/O devices configured.

I'll check it on my Mac, but I've been using the studio version on my PC running Windows 10 for over a year and all was fine. Now, with v17 this new behavior has changed. My system has no problem running the application or rendering video, etc. All works perfectly except for this new bug.

Just checked it on my Mac. No issues. It behaves as it should when you switch between Main and Near speakers.

It seems to be a bug in v17 Windows.

How do I report this bug or speak with someone that can look into it?

Am I the only one that is having this happen?

System spec? viewtopic.php?f=21&t=90190

Not reproducing this behaviour on macOS, switching between the five different I/O devices configured.

Just to be clear, this has nothing to do with I/O device. I tried with multiple devices and it doesn't change the behavior. It doesn't matter what the input assignment. If there is an input assignment, just switching between Main and Near speakers makes it happen.

I'm finding it hard to believe that I'm the only one seeing this behavior. It doesn't seem like it could be a glitch in my system.

Are there any other Windows 10 users running Resolve 17 beta that can check this out to see if it's happening to you too?

I was having some issues with Resolve and decided to install the last stable version of Resolve 16. The Input assignment doesn't change and their is no weird behavior when switching speakers.

Apparently, that issue only exists in Resolve 17 beta for Windows.

I may just stick with 16 until some of the bugs are worked out of 17.