One way to do that is to use the Java drivers, which provide an option to use left/right/both channels of the selected output. For ASIO drivers I have added a secondary output selector to the measurement dialog in 5.17 beta 4.
Ok, thanks... does this mean with the new beta it will work exactly like before the timing reference feature was added?One way to do that is to use the Java drivers, which provide an option to use left/right/both channels of the selected output. For ASIO drivers I have added a secondary output selector to the measurement dialog in 5.17 beta 4.
Actually, if you select the checkbox and choose the 2nd channel under the first THEN it works *at least for me*.I believe I am having the same problem. Been using 5.13 up until today without issue. Decided to upgrade to 5.16 and the same issue described here is happening to me as well. Downgraded to 5.15 and still the same issue. Just upgraded to 5.17 beta 5 and still the same issue but you did add to the new drop down box but I don't think that is solving anything.
When I first launch the Measure page, everything is fine. See "REW Output 1.jpeg" attached.
When I close the Make a Measurement page and then click on Measure again, the second output disappears. I have to shutdown REW completely and the relaunch to get it back but it immediately goes away again after doing so.
Is there a workaround for this? If not, I have to revert back to 5.13.
I do that and it still does not working for me. I've been playing with it and it seems like I have to have the timing reference turned on to take any meaningful measurements.Actually, if you select the checkbox and choose the 2nd channel under the first THEN it works *at least for me*.
(The selection on the right of the first channel doesn't work and disappears like you mentioned on 2nd measurement sweep.)
The timing reference output selector shouldn't appear when not using a timing reference (it isn't being used for anything), it was being shown in error when the measurement dialog first opened but correctly hidden after that. I've fixed that for the next beta. It shouldn't make any difference to using the 2nd output channel though, and the second output channel should work fine whether or not a timing reference is being used. It seems to behave correctly when I test it with or without a timing reference.