Possible routing bug Solo and Sends (FIXED)

mlprod · 04-06-2017, 02:51 PM

Hey

Check attached project. Put an audio file on the "clean" track. Solo the clean track, both clean and FX is heard through the HW outs, all good.
Solo just the FX only FX is heard, also good.

Solo BOTH, only FX is heard.
Is the really to be expected?

This is causing trouble for friend of mine who is mixing on an SSL console and send indivdual track to mix ch inputs.

karbomusic · 04-06-2017, 03:04 PM

Quote:

Originally Posted by mlprod

Hey

Check attached project. Put an audio file on the "clean" track. Solo the clean track, both clean and FX is heard through the HW outs, all good.
Solo just the FX only FX is heard, also good.

Solo BOTH, only FX is heard.
Is the really to be expected?

This is causing trouble for friend of mine who is mixing on an SSL console and send indivdual track to mix ch inputs.

I can hear both tracks in the following scenarios, *after* I remove all the hardware routing (couldn't get any output is why I removed) so I assume it's the routing or how he is monitoring it (duh on my part):

1 soloed, 2 not
2 soloed, 1 not
both soloed

That's as far as I can dig in (concerning what it should do) at the moment as I'm working from a machine with the demo installed and not at the studio.

mlprod · 04-06-2017, 03:13 PM

Ok, though i am specifically after what happens with the hw outs. When both are soloed, both should be sent to their respective output...right? Possibly an unintentional side effect of the previous bug with sidechain monitoring when using hw outs?

mlprod · 04-11-2017, 04:54 AM

Bump on this, curious if this is an actual bug or a sideeffect. Any thoughts devs?

akademie · 04-11-2017, 07:15 AM

Hmmm, it is really strange.
If you create your own intermediate BUS-MASTER TRACK (with hardware outs assigned) and send both source tracks to it, then it will work as expected.
So I would assume it may be a bug.

akademie

mlprod · 04-11-2017, 12:23 PM

Quote:

Originally Posted by akademie

Hmmm, it is really strange.
If you create your own intermediate BUS-MASTER TRACK (with hardware outs assigned) and send both source tracks to it, then it will work as expected.
So I would assume it may be a bug.

akademie

Ahh I never tried that, but indeed you are right! I would definitely guess it's a bug. Strange that this has slipped through...

Devs?

EvilDragon · 04-11-2017, 12:35 PM

Quote:

Originally Posted by mlprod

Devs?

Are taking some chill time this week.

mlprod · 04-18-2017, 09:32 AM

Devs are back I hope and here's a bump=)

Dstruct · 04-18-2017, 03:01 PM

To me it looks like a bug. Confirmed (5.40 x64).

FIXED (5.60pre7)

mlprod · 04-24-2017, 11:20 AM

Yes, feels like one of those that should be fixed asap imho.

mlprod · 05-18-2017, 02:09 PM

A little bump here

mlprod · 05-24-2017, 12:59 PM

Annnnnd another one!

mlprod · 05-31-2017, 01:52 PM

Another reminder.

Justin · 05-31-2017, 07:26 PM

This is by design-- the idea being that if you have multiple tracks sending to the Fx, and you want to hear just one track's Fx, you would solo both

solo trackx = hear trackx+fx(trackx)
solo fx = hear fx(track*)
solo trackx and fx = hear just fx(trackx)

mlprod · 06-01-2017, 12:57 AM

Quote:

Originally Posted by Justin

This is by design-- the idea being that if you have multiple tracks sending to the Fx, and you want to hear just one track's Fx, you would solo both

solo trackx = hear trackx+fx(trackx)
solo fx = hear fx(track*)
solo trackx and fx = hear just fx(trackx)

Ahh ok I see!
BUT, that doesnt seem to work like that here. When I solo Track 1 + FX I hear also Track 2s FX send in the FX channel.
This happens both with the HW outs on each individual channel, and of I go via the master track.

akademie · 06-01-2017, 04:04 AM

Quote:

Originally Posted by Justin

This is by design-- the idea being that if you have multiple tracks sending to the Fx, and you want to hear just one track's Fx, you would solo both

solo trackx = hear trackx+fx(trackx)
solo fx = hear fx(track*)
solo trackx and fx = hear just fx(trackx)

Hello Justin,
please, read my post #5, where it works "OK" when using intermediate bus track. So according to your clarification that it is by design, then is it right that it works differently when sending to master-bus or track-bus?

Thanks for info
akademie

mlprod · 06-07-2017, 01:50 PM

Justin, should I send a sample project?

mlprod · 09-25-2017, 01:56 PM

Quote:

Originally Posted by Justin

This is by design-- the idea being that if you have multiple tracks sending to the Fx, and you want to hear just one track's Fx, you would solo both

solo trackx = hear trackx+fx(trackx)
solo fx = hear fx(track*)
solo trackx and fx = hear just fx(trackx)

@Justin
I thought I should bring this up again, since what you wrote above should happen, but does in fact not currently happen i Reaper. At least not here=)

Check attached RPP, two dry and one FX track.
What happens is:

solo Dry1 = hear Dry1+fx(Dry1) = all good
solo fx = hear fx(Dry1+2) = all good
solo Dry1 and fx = hear Dry1 + fx(Dry1+2) = not good

Any comments?

mlprod · 09-27-2017, 01:19 PM

bump on this.

Justin · 09-27-2017, 05:09 PM

Confirmed, thanks.

mlprod · 09-28-2017, 03:47 AM

Quote:

Originally Posted by Justin

Confirmed, thanks.

Thank you for fixing!

04-18-2017, 03:01 PM	#9
Dstruct Human being with feelings Join Date: Jul 2006 Posts: 12,525	To me it looks like a bug. Confirmed (5.40 x64). FIXED (5.60pre7) Last edited by Dstruct; 09-30-2017 at 09:21 AM.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

04-06-2017, 03:13 PM	#3
mlprod Human being with feelings Join Date: Jul 2015 Location: Stockholm, Sweden Posts: 1,380	Ok, though i am specifically after what happens with the hw outs. When both are soloed, both should be sent to their respective output...right? Possibly an unintentional side effect of the previous bug with sidechain monitoring when using hw outs?

04-11-2017, 04:54 AM	#4
mlprod Human being with feelings Join Date: Jul 2015 Location: Stockholm, Sweden Posts: 1,380	Bump on this, curious if this is an actual bug or a sideeffect. Any thoughts devs?

04-11-2017, 07:15 AM	#5
akademie Human being with feelings Join Date: Mar 2007 Posts: 4,752	Hmmm, it is really strange. If you create your own intermediate BUS-MASTER TRACK (with hardware outs assigned) and send both source tracks to it, then it will work as expected. So I would assume it may be a bug. akademie Last edited by akademie; 04-11-2017 at 07:23 AM. Reason: mistype

04-18-2017, 09:32 AM	#8
mlprod Human being with feelings Join Date: Jul 2015 Location: Stockholm, Sweden Posts: 1,380	Devs are back I hope and here's a bump=)

04-24-2017, 11:20 AM	#10
mlprod Human being with feelings Join Date: Jul 2015 Location: Stockholm, Sweden Posts: 1,380	Yes, feels like one of those that should be fixed asap imho.

05-18-2017, 02:09 PM	#11
mlprod Human being with feelings Join Date: Jul 2015 Location: Stockholm, Sweden Posts: 1,380	A little bump here

05-24-2017, 12:59 PM	#12
mlprod Human being with feelings Join Date: Jul 2015 Location: Stockholm, Sweden Posts: 1,380	Annnnnd another one!

05-31-2017, 01:52 PM	#13
mlprod Human being with feelings Join Date: Jul 2015 Location: Stockholm, Sweden Posts: 1,380	Another reminder.

05-31-2017, 07:26 PM	#14
Justin Administrator Join Date: Jan 2005 Location: NYC Posts: 16,117	This is by design-- the idea being that if you have multiple tracks sending to the Fx, and you want to hear just one track's Fx, you would solo both solo trackx = hear trackx+fx(trackx) solo fx = hear fx(track*) solo trackx and fx = hear just fx(trackx)

06-07-2017, 01:50 PM	#17
mlprod Human being with feelings Join Date: Jul 2015 Location: Stockholm, Sweden Posts: 1,380	Justin, should I send a sample project?

09-27-2017, 01:19 PM	#19
mlprod Human being with feelings Join Date: Jul 2015 Location: Stockholm, Sweden Posts: 1,380	bump on this.

09-27-2017, 05:09 PM	#20
Justin Administrator Join Date: Jan 2005 Location: NYC Posts: 16,117	Confirmed, thanks.