Pan to right (FIXED)

Coming from here... Ive had a look and think the op has spotted a bug. "Insert 2 new audio tracks on track 1: insert an audio file and disable the master / parent send, add new send to track 2 with the following settings: audio 1 (or 2 is the same). if I move the pan of track 1 to the right vu meter indicates the signal but no sound comes out." Well, that would be correct behavior with the send set to track ch1 but when set to tk ch2, something weird happens. Panning track 1 hard LEFT, the signal from track channel 2 gets sent to tk2, which i think it shouldnt and panning hard right it doesnt which it should. See attached project. Have i got this right?

It's at least quite unexpected and I wouldn't know how to explain it. It is already in 2.57 and it seems just noone noticed because everyone uses stereo pairs for sends, the send pan and it's also only happening when the send is post fader/pan of course, but it's quite odd. (but probably no "yikes they crossed all the wires" showstopper). :) It's like single channels are always routed over what was previously the first/left channel and so panning full right mutes both send channels when not used in pairs. Of course I would expect that the main pan just doubles/counteracts the send pan behind it (like it does for channel pairs) but I have no idea what the actual negative impact of this is and whether this is just a little outlandish, a colateral damage of some brilliant cycle-saving coding trick or a bug.

...and another modified demo. Sending tkch 1 to tk 2 and tkch2 to tk 3...panning track 1 left sends audio to both tracks, panning right sends audio to neither.

I ran into the same problem and posted this thread: This is a pretty serious bug. How can we tell if the cockos is investigating. Is there anything else we can do?

Funny, I started a thread like this on my own. But no matter if it's prefader or not, I don't get sound (if I turn off the plugin I am using, which is STEREO, then I hear sound prefader mode only). Hopefully this will be "fixed" in Reaper 4 (which prerelease should be out by now...)???

Love bump. :)

Can we confirm that when using the new (non-deprecated) pan modes, this bug is fixed? If so, I would be inclined to leave it as is, as to avoid changing the way old projects sound...

Fair call and confirmed, thanks. :)