Page 1 of 1

Is this a bug?

Posted: Sat Dec 20, 2025 11:19 am
by Angie
I am using Version 2.3

There is one track in my session that has the XY Pan engaged and assigned to an output channel of its own being used as a group.
When I select tracks in the multitrack view that don't include that particular track, I get this warning.

"There are active xy-pan assigned outputs with no active xy-pan assigned inputs."

Could this be a bug?

Re: Is this a bug?

Posted: Sat Dec 20, 2025 9:23 pm
by Bob L
If you select tracks for special playback and they are empty with no active regions, that warning is saying there are no tracks that have active data to playback.

Can you explain in more detail please.

Bob L

Re: Is this a bug?

Posted: Sun Dec 21, 2025 6:58 am
by Todd R
Angie wrote:There is one track in my session that has the XY Pan engaged and assigned to an output channel of its own being used as a group.
When I select tracks in the multitrack view that don't include that particular track, I get this warning.

"There are active xy-pan assigned outputs with no active xy-pan assigned inputs."
do you have the OUTPUT TRACK assigned to any of the surround output destinations?

on the OUTPUT TRACKs there are buttons for OUT ASSIGN:
lr front
lr center
lr rear
sub
center

are those not required for using the surround panner control? (I do not know the answer)

do you have surround setup? or using stereo?

I did not set up my surround using those OUT ASSIGN buttons;
I just routed direct device outputs to SMPTE channel order

yes, it makes for a lot of mixing work

Re: Is this a bug?

Posted: Wed Dec 24, 2025 9:23 am
by Angie
Let me see if I can explain this a little clearer.

I have a track that is using the X-Y Pan. Yes, it is assigned using the surround outputs.
When I select tracks in the mult-track that don't include this channel, I get the message. If I select it, no message.
With no tracks selected all is fine and there is no message.

My work around has been to include that track in the selected tracks and just mute it.

It may be normal behavior because of something I am doing wrong.