Thanks for the suggestion ... but ...chapelier fou wrote: ↑Thu Jul 25, 2024 6:14 pmYou could for instance use the [coll] object to store the data, with « store contents in patcher » enabled in the inspector. Sorry, no computer here for a few days.
The pile of SysEx I need for each of the dozens of patch changes in my set is significant, and I would never have been successful if I had to enter it by hand. So, I developed a perl script that produces all the seq-object format .txt files from a master file, and also hacks a master .amxd file into the dozens of needed M4L devices (and had to recalc the RIFF file chunk sizes). This system allows comments, templates, multiple format for MIDI (decimal, single and strings of hex bytes) along with timing intervals and biases, and it's all generated from a single script.
So, at this point, I'm loathe to move to another ([coll]-based) system.
One thing I stumbled on: I tried to route all the tracks that produce SysEx to a single track that forwards to my hardware (so I would not have to reconfigure each and every track, if a config change was needed). Works fine from Ableton workstation, but not from Push 3S. Tried every configuration available and no dice. There may be an issue with a Push 3S track receiving SysEx MIDI or some such. Monitoring on Push 3S is more limited than on the workstation, so diagnosing is difficult.