Technical question about processing

alexs1

Using Mobius as a plugin, does the function “SelectTrack” run after every time it’s called if the track is already selected? Like, if I have a trigger set to SelectTrack(3) and I press it once, it selects Track 3, and then any more times after that while it’s currently selected does it get ignored at a processing level?

The reason I ask is because I had the idea to translate all drum pad notes in Bome to a single CC that is bound to a SelectTrack function. As a result, punching in any drum samples will automatically select the appropriate track without needing to select it first on a separate bank before proceeding with the pad punching. But I don’t want to do that if I’m tapping a bunch and rapidly calling “SelectTrack” processing it each time a pad is pressed

alexs1

Following up after testing this idea—it seems to be working fine for the most part. The only concern is that there appears to be a bit of instability with the MIDI stream when syncing to Host. After performing several Next/PrevLoop Switches in Host Sync and Selecting between MIDI Tracks in this way, the data stream gets slightly out of sync. Not sure if it’s due to the CC binding I added to SelectTrack, or if there’s some general precariousness around MIDI Tracks and their tightness with Host Sync.

edit: the issue with the data stream dealignment seems to be stemming from LoopSwitch-ing in the TSM (b45).

jeff

SelectTrack doesn't do much if the track is already selected, but there is a small amount of overhead for any binding action. If a redundant action happens a lot, say thousands of times, this can lead to a "memory pool imbalance" which isn't correcting itself as well as it should. I don't think this would impact performance much, but you may notice a gradual increase in memory consumption over the course of an hour or so.

It's one of those things that isn't supposed to cause problems, but it's on the edge of "normal" use so I don't watch it closely. It sounds related to your auto-select-on-threshold idea which would be a good thing. I might want to make that a built-in option.

edit: actually the potential memory issue should only happen when running standalone. If you're using the plugin and getting the MIDI for bindings through the host I would not expect to see it.

alexs1

jeff edit: actually the potential memory issue should only happen when running standalone. If you're using the plugin and getting the MIDI for bindings through the host I would not expect to see it.

It's getting MIDI from both the Host and Plugin through Bome.

jeff If a redundant action happens a lot, say thousands of times, this can lead to a "memory pool imbalance" which isn't correcting itself as well as it should.

I am slightly concerned about this just because I do a lot of tapping pads and pressing keys over extended performances, so would there be a chance it would tip the scale?

jeff

alexs1 Yeah, if you're getting MIDI direct from Bome, you might see the memory creep. If you have several tracks going and are regularly adding new layers, it shouldn't be a big deal since this is a relatively small amount of memory compared to audio data which is many times larger. Still, not an ideal situation. I'd put my concern level at a 1 out of 10, but not zero.