Hey all. Just found a bug in the OT to watch out for if you ever use midi loopback. (EDIT - loopback is not a requirement, but it makes this bug easily noticeable). I thought some of you might be interested in this one because it answers some of those WTF? moments. I was using loopback, and could not figure out why changing LFO depth in the LFO setup page of one of my midi tracks was making an audio track cut out. If IRC, @defenestration was trying to identify some of these types of things. Simple to reproduce. Try it out:
Connect midi in to midi out. Make sure that Track 1 is selected in both the midi and audio sections of the OT. Navigate to the midi section of the OT. Go to the LFO setup page, and turn the depth knob up to some value. Now, switch back to the audio section of the OT. Notice how the depth knob of the audio LFO has changed to the same value that you set in the midi section LFO setup page. The same bug exists with the Speed knob, but none of the other LFO setup parameters. The bug only affects twin tracks (i.e. midi track 1 and audio track 1). This bug does not work in reverse, i.e. making a change in the LFO setup page of the audio section does not change the LFO of the midi section. This bug also does not appear if you simply use the regular LFO pages (as opposed to the LFO setup page). Turning Audio CC in to OFF, or Audio CC out to INT, both solve the problem.
So what was happening for me was that I had a Thru machine on audio track 1 set to listen to input AB. Making a change to the depth parameter of the LFO in the LFO setup page of midi track 1 would then make audio track 1 cut out, because its default LFO target is INAB.
EDIT- the audio track and midi track in this test must be set to respond to different midi channels. I.e set midi track 1 to midi channel 1, and audio track 1 to any midi channel other than 1.