BrainModular

The manual does not seem to be up to date, but I don't see that 'recall' has merely been renamed.....

all my PMs are broken

okay, the 'current' input seems to work for this.... but I cannot figure out the IML for controlling it.

The code that stopped working is this:
SendInternalMsg2('SET_TARGET_PATCH','SENDER_PATCH');
SendInternalMsg4('SET_VALUE',Pm_name,'recall '+pm_num,'1');
SendInternalMsg4('SET_VALUE',Pm_name,'recall '+pm_num,'0');

I tried changing to 'recall ' to 'current ' but that did not work. Also tried:

SendInternalMsg2('SET_TARGET_PATCH','SENDER_PATCH');
SendInternalMsg3('SET_VALUE',Pm_name,'current '+pm_num);

while I'm asking, I'll bet this code is broken too:

SendInternalMsg2('SET_TARGET_PATCH','SENDER_PATCH');
SendInternalMsg4('SET_VALUE',Pm_name,'num store/remove',pm_num);
SendInternalMsg4('SET_VALUE',Pm_name,'store','1');
SendInternalMsg4('SET_VALUE',Pm_name,'store','0');
SendInternalMsg4('SET_VALUE','STORE','1','0');

Any tips most welcomed! Like to be able to get back on the tip, as this broke in v 126.

This only broke for you recently in the last version? There was a pretty significant change in how presets slots are handled since HH3. Now if example you have three presets

1
2
3

and you delete preset 2 the slot is collapsed and preset 3 becomes preset two and there is no longer an empty slot where preset two was.


I'm a bit sad about this change personally because it makes unable to delete presets without losing remote (or iml) mappings to specific presets, but perhaps you are meaning something else?

I built this using HH3 betas, and it is working same as previous HH versions under 3.115, I think. I tried 3.125, and everything broke. Now I'm trying to fix my script to work with the current version. The names of the PM inputs have changed, but it seems like the IML required has changed as well.

I don't need to delete presets, just rewrite them when necessary. Hopefully that is still possible.....

Still no text input to name presets So they are all called 'unnamed preset' which doesn't help figure out what's going on

Hmm. Sounds like time to file a bug report. But yea, as far as a suggestion and improvement goes, being able to name presets via text input and select preset via string index would make it possible to once again have fixed remote mappings for presets. In fact I have a bunch of suggestions for preset manager. It is such a powerful feature in HH, I would love to have more robust preset management, ie: copy/paste, move, duplicate, even import export. But for now just the basic functions being backwards compatible would be nice.

Hmmm... I suppose it's possible it's a bug, but my guess is I just have the syntax wrong. Hopefully somebody with more knowhow than us will weigh in.....

But I do get annoyed at how little backwards compatibility figures in the HH game plan.

well, gave it some thought, and realized I do not need the script at all!

Just a 'current' input and a 'rewrite' input.

So that's all cool now!

one question though: If I write a preset at 43 when there are only 32 presets, does that get accessed from 43, or from 33?? Haven't tested that yet.

If you have 32 presets and you write at 43, preset 32 is over written. If you are at 43 and you select new, a preset is created at 33.
This new preset manager behavior is is the only thing in HH3 that I am not extremely stoked on. It has made presets very hard to use for me as I need presets to follow fixed MIDI program changes and always be where I put them in the queue. Anyways.. Won't have time for patching for another three weeks, hopefully there's at least some workarounds to help adjust to the new PM behavior.

gurulogic wrote:If you have 32 presets and you write at 43, preset 32 is over written. If you are at 43 and you select new, a preset is created at 33.
This new preset manager behavior is is the only thing in HH3 that I am not extremely stoked on. It has made presets very hard to use for me as I need presets to follow fixed MIDI program changes and always be where I put them in the queue. Anyways.. Won't have time for patching for another three weeks, hopefully there's at least some workarounds to help adjust to the new PM behavior.

If it's one new HH3 feature that enough people complain about, Senso might change it back. I would think fixed slots are much more convenient for setting up patches, which is the whole point of Usine ! And fixed slot would connect better to arrays.
One good thing in HH3 is there are now max 64 presets rather than max 32.

yeah, that's not helpful behaviour!

Does the PM start with 0 presets, or 32/64?

I have a lot of PMs with presets written randomly throughout, that need to be accessed accurately by number. I hope they do not break! And none of them have names, as I have created them all via IML scripts, and there is still no text input to the PM object.

It is looking like all my IML scripts have broken, not just the PM one, so I filed a bug report on that.

solved in the 137
sorry for that

finally back on the tip with .144.

It's looking really great, I'm super happy. Everything is working as expected, load and save times are down, CPU is down, and nothing is broken.

YAY!!!!! THANKS!!!!