Wishlist: Any chance of trowaSoft multiSeq port?

as, Id commented it’d be relatively easy here, thought I should put my money where my mouth was :laughing:

so had a quick crack at it…
not sure, how functional they are , partly as Ive not even loaded them up in vcv so dont know how the modules work.

voltSeq

I know you didn’t ask for this, but it actually comes for ‘free’, as the MultiSeq is a specialised form of it… which also means, its probably worth test / getting working first, as its the foundation.

overall seems ok on initial glance, UI is up, its moving thru steps, parameters available

but I really need to load it up in vcv check out how it works, then test (and no doubt fix it)

MultiSeq

this one is not doing anything, e.g. I cannot see steps animating, but not sure if its suppose to in an unconnected state - again, need to really test in vcv - then can go from there.

overall, UI is up, parameters showing, doesn’t crash (lol). im not sure how functional it is.. as I can see much going on - but again, I need to play with it on vcv to see what its supposed to do.
however I suspect this’ll require a bit more extra work over the voltseq.

general approach

took me a bit longer than expected, as I decided NOT to just rip (osc) code out of the vcv module code base, but rather to make it conditionally compile with or without OCS support.

this has a few (big) advantages :
a) code could be merged back into the original authors code base
b) future updates from original author can easily be merged in
c) for debug/testing, I have the original code still in place - so easier to see which changes may have caused issues

the main disadvantage is its a dev slower process, at least initially, as it requires a lot of ‘conditional’ blocks - and frankly, the osc code is very tightly integrated into these modules.
(went a bit deeper than I was expecting tbh)

I’ll also say there are some other ‘oddities’ with the original code, their is a bit of a misalignment between the Rack API version it uses vs the one used for metamodule.
I think possibly, the module uses an older version (of v2) that the one used by meta module.
that said, its only in a few places, but could throw up some extra bugs.

so… next steps.
a) get familiar with the original modules
so, I have an idea what they are suppose to do :wink:
b) test/fix my VCV desktop build with and without OSC.
this’ll allow me to know the changes have not broken the desktop
c) test/fix the metamodule build
once I know the desktop build works, then I can see if the metamodule ‘port’ has introduced any oddities.


all that said, no promises/timescales, I’ll fiddle with it as I have time.
but thought id show, where my quick dabbling with it.

frankly, its very hot here (Spain) and getting hotter…
so not sure how much dev time I’ll have…so spend the days at the lake with my dogs :slight_smile:

4 Likes