Got it, thanks. As for my original desire to use CV to modulate the song tempo: success! It turns out to be incredibly easy using the EMI and MIDI loopback, so I owe you big time for suggesting that in the first place. All that's needed is to forget all about the knob on the EMI, and use the pitch bend wheel instead, which has much better resolution (16,384 possible values instead of 128). I never would have dared to hope that this would actually work, but it does! I've routed bipolar CV out from an LFO to the pitch bend CV input on the EMI, and am setting the static value for the pitch bend in its automation lane to correspond to the BPM value I want to use as the center of the tempo modulation range. All of the LFO waveshapes are working just fine, and the LFO frequency and amplitude as well as the pitch bend CV range knob on the EMI all work exactly as expected, providing excellent control for modulation with a granularity of 1.000 BPM. It's very easy to set up and use.QVprod wrote:The Panorama has 8 encoders on the right hand side that work across 3 modes for it's mapping. They change function depending on what mode you're in. In transport mode, one of them is assigned to tempo. Could be maybe the 6th knob. That's the deepest answer I can give you as the process is automatic. I assume lua (there is a lua codec) is the culprit as to my knowledge (could be wrong) a remote map just sets source and destination for regular midi mapping.
I understand midi routing, but the actual programing of the Panorama goes over my head as it's beyond a simple remote map.
So, this is great! There are a couple of caveats, however. For one thing, the fact that "Tempo BPM" and "Tempo Decimal" are two separate remotables actually turns out to be a disadvantage here, not an advantage. If there were a single remotable for "Tempo" that encompassed the entire tempo value, it looks like I'd get a nicely continuous sub-BPM granularity with the method I'm using now, just as one does when automating the tempo in an automation lane. Since the two halves of the tempo number are completely separate remotables, however, I'm stuck with a 1-BPM granularity, and I can't think of any way to get around that. The "Tempo BPM" remotable can't do better than a 1-BPM granularity, and the "Tempo Decimal" remotable can do sub-BPM granularity by itself, but I can't think of any way to combine them to get smooth multi-BPM tempo sweeps at sub-BPM granularity. Although, looking at a master list of remotables, it appears there actually IS one for the overall tempo with a value range of "1000 to 999999", which would probably be perfect for my needs, but I have no idea how to access it! It doesn't appear in the "Additional Remote Overrides" list, and there doesn't seem to be an arrow for it in the Remote Override Edit Mode, but it unmistakably appears in my reference list. There's got to be a way to access it, but I can't figure out how... anyone? Anyway, having that extra granularity would be ideal, but even with the 1-BPM granularity this is still pretty darn close to what I need, and I expect to get some great results from it.
There's just one other problem, and unfortunately it's a big one: every time the song tempo is changed via remote override, an entry for that change is added to the undo list. So far so good, except there appears to be some sort of bug here, because it seems to be filling up the ENTIRE undo list with tempo change events as the tempo is continuously modulated, as though every single incremental change to the value is getting its own entry in the undo list. I can't imagine why it's behaving this way, but the unfortunate result is that, as far as I can tell, the whole undo list gets wiped out very quickly while the tempo is being modulated, completely filled up with tempo change events. Essentially, this means that Reason has no usable undo feature at all while tempo modulation is active. That will be a big problem, of course! If anyone reading this has any insight into why this bizarre undo list behavior is occurring, and of course especially if anyone can think of a possible workaround to salvage the undo functionality somehow, I'd love to hear it. And, Props... if you're not going to add a CV input for the tempo, PLEASE at least fix this bug so that those of us who need to do this can hack it via loopback without sacrificing undo functionality! And please make it easier (or possible at all?) to access that overall tempo remotable.