ArrayArrayArray BrainModular BrainModular Users Forum 2018-01-01T11:06:09+02:00 https://brainmodular.org/forums/app.php/feed/topic/6000 2018-01-01T11:06:09+02:00 2018-01-01T11:06:09+02:00 https://brainmodular.org/forums/viewtopic.php?t=6000&p=38907#p38907 <![CDATA[WKP master PM rack save behaviour]]>
My channels are all created by a single script controlling a 'create rack' object. Would that cause them to have the same ID?

Statistics: Posted by woodslanding — 01 Jan 2018, 10:06

]]> 2017-12-30T12:46:25+02:00 2017-12-30T12:46:25+02:00 https://brainmodular.org/forums/viewtopic.php?t=6000&p=38883#p38883 <![CDATA[WKP master PM rack save behaviour]]> 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.

Statistics: Posted by senso — 30 Dec 2017, 11:46

]]> 2017-11-30T21:01:44+02:00 2017-11-30T21:01:44+02:00 https://brainmodular.org/forums/viewtopic.php?t=6000&p=38637#p38637 <![CDATA[WKP master PM rack save behaviour]]>
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.

Statistics: Posted by woodslanding — 30 Nov 2017, 20:01

]]> BrainModular BrainModular Users Forum 2018-01-01T11:06:09+02:00 https://brainmodular.org/forums/app.php/feed/topic/6000 2018-01-01T11:06:09+02:00 2018-01-01T11:06:09+02:00 https://brainmodular.org/forums/viewtopic.php?t=6000&p=38907#p38907 <![CDATA[WKP master PM rack save behaviour]]>
My channels are all created by a single script controlling a 'create rack' object. Would that cause them to have the same ID?

Statistics: Posted by woodslanding — 01 Jan 2018, 10:06

]]> 2017-12-30T12:46:25+02:00 2017-12-30T12:46:25+02:00 https://brainmodular.org/forums/viewtopic.php?t=6000&p=38883#p38883 <![CDATA[WKP master PM rack save behaviour]]> 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.

Statistics: Posted by senso — 30 Dec 2017, 11:46

]]> 2017-11-30T21:01:44+02:00 2017-11-30T21:01:44+02:00 https://brainmodular.org/forums/viewtopic.php?t=6000&p=38637#p38637 <![CDATA[WKP master PM rack save behaviour]]>
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.

Statistics: Posted by woodslanding — 30 Nov 2017, 20:01

]]>