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!!!!
Statistics: Posted by woodslanding — 25 Oct 2017, 18:07
]]>
Statistics: Posted by senso — 20 Sep 2017, 20:14
]]>
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.
Statistics: Posted by woodslanding — 13 Aug 2017, 08:07
]]>
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.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.
One good thing in HH3 is there are now max 64 presets rather than max 32.
Statistics: Posted by sm_jamieson — 11 Aug 2017, 13:00
]]>
Statistics: Posted by gurulogic — 11 Aug 2017, 02:42
]]>
]]>
Just a 'current' input and a 'rewrite' input.
So that's all cool now!
Statistics: Posted by woodslanding — 10 Aug 2017, 22:14
]]>
But I do get annoyed at how little backwards compatibility figures in the HH game plan.
Statistics: Posted by woodslanding — 09 Aug 2017, 00:51
]]>
]]>
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 
Statistics: Posted by woodslanding — 08 Aug 2017, 19:58
]]>
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?
Statistics: Posted by gurulogic — 08 Aug 2017, 07:55
]]>
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.
Statistics: Posted by woodslanding — 08 Aug 2017, 07:40
]]>
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);
Statistics: Posted by woodslanding — 08 Aug 2017, 07:35
]]>
all my PMs are broken
Statistics: Posted by woodslanding — 08 Aug 2017, 07:23
]]>