In the patching forum I mentioned that my wkp was not recalling presets correctly because I had multiple racks with the same name (even though they had different titles.) When I reloaded my preset, all my racks had the same settings, because when the wkp gets saved, the racks are referenced by name.
Although I have found a workaround by managing my wkp presets from text files (which is actually a much more robust approach for me, insuring I can manage and maintain file compatibility myself) I can't help but think this is a bad way of saving presets.
I don't know how others use HH, but I would just think that if you had 'awesome multi-effect rack x' which you'd written dozens of awesome presets for, you might want to use it more than once in a wkp!!
And of course you wouldn't realize it didn't get saved correctly until you tried to load the wkp later and discovered all the 'awesome multi-effect rack x's in your WKP had the same settings.
Why not save racks by number? The rack number is guaranteed to be unique! Is there some reason this is not possible or practical?
[EDIT] I should also mention that I quite accidentally discovered that this was the source of a long-standing bug where the text busses on certain channels in my WKP did not work. It appeared on different channels every time, and nothing at all showed in the trace (need at least some kind of a warning about recalling a duplicate-named rack, if it is going to cause these kinds of problems) and I had never even gotten as far as saving or loading a single preset! Once I implemented my own preset manager, I deleted the WKP PM, and the problem instantly disappeared.
WKP master PM rack save behaviour
-
woodslanding
- Member
- Posts: 1327
- Contact:
If you found a bug try to isolate it and post a bug report. I'll solve it.
It's not easy to test if 2 presets are recalled at the same time as they are processed in separated threads.
Also preset are stored by "ID's" not by name. It means that, each object have an unique ID (a kind huge number) and pm value are dispatched according their ID. sometime, for historical reasons some objects can have the same ID and it can give strange pm recall. In this case just change ID's in the /settings/remote tab.
It's not easy to test if 2 presets are recalled at the same time as they are processed in separated threads.
Also preset are stored by "ID's" not by name. It means that, each object have an unique ID (a kind huge number) and pm value are dispatched according their ID. sometime, for historical reasons some objects can have the same ID and it can give strange pm recall. In this case just change ID's in the /settings/remote tab.
Olivier Sens
www.brainmodular.com
www.brainmodular.com
-
woodslanding
- Member
- Posts: 1327
- Contact:
okay, thanks!
My channels are all created by a single script controlling a 'create rack' object. Would that cause them to have the same ID?
My channels are all created by a single script controlling a 'create rack' object. Would that cause them to have the same ID?
Custom Ryzen 5900x MATX build, Win10, Fireface UFX, touchscreen
Custom 2 manual midi keyboard
Usine, Kontakt, Reaktor, Synthmaster, Byome, Arturia, Soundtoys, Unify
Custom 2 manual midi keyboard
Usine, Kontakt, Reaktor, Synthmaster, Byome, Arturia, Soundtoys, Unify
Who is online
Users browsing this forum: No registered users and 43 guests
