BrainModular

preset managers behaving badly

2013-03-07T16:04:32+02:00

yup ill do this tonight or tomorrow, iam actually at work

Statistics: Posted by 23fx23 — 07 Mar 2013, 15:04

preset managers behaving badly

2013-03-07T15:32:41+02:00

@ 23fx23: could you update it in the add-ons section? So nobody else will have the same problem...

Statistics: Posted by percuson — 07 Mar 2013, 14:32

preset managers behaving badly

2013-03-06T11:31:18+02:00

@ percusson thx for the fastcallback reminder^^ i was really busy rhose days and you made a nice investigation^^
Cool seamus

Statistics: Posted by 23fx23 — 06 Mar 2013, 10:31

preset managers behaving badly

2013-03-06T10:56:58+02:00

cool!

Statistics: Posted by percuson — 06 Mar 2013, 09:56

preset managers behaving badly

2013-03-06T09:43:50+02:00

it seems to work!! Bravo! Thank you so much! Usine has such a supportive community!

Statistics: Posted by seamus — 06 Mar 2013, 08:43

preset managers behaving badly

2013-03-05T21:14:08+02:00

I'm gonna check this and report back

Statistics: Posted by seamus — 05 Mar 2013, 20:14

preset managers behaving badly

2013-03-05T13:40:35+02:00

thanks 23fx23 for the hint that I can also exclude whole patches from beeing stored in the preset.
I totally forgot that there is an option for doing that at the top of the patch window .

I think your patch should work now. I cannot check this out, because I couldn't get the errors happen on my computer.
So seamus has to do the test.

Statistics: Posted by percuson — 05 Mar 2013, 12:40

preset managers behaving badly

2013-03-05T01:46:23+02:00

i unchecked all the stored to pm and condutor swich in the items and patchs '256'pm and set fastcallback to false,
it 'looks' like is working now but im note sure, maybe give a try:
http://sensomusic.com/forums/uploads.ph ... r%2002.wkp

Statistics: Posted by 23fx23 — 05 Mar 2013, 00:46

preset managers behaving badly

2013-03-05T01:24:05+02:00

so .. i installed usine and when opening the workspace i see that when you clic on the 256pm patch 'not saved in preset' is unchecked,

try with enabling it on each patch, and also click each list box and text field and clic 'edit layout' and enable both swichs 'not stored in preset ' and ' not saved in conductor', this may solve the problem maybe.. gonna try to check more deeply

Statistics: Posted by 23fx23 — 05 Mar 2013, 00:24

preset managers behaving badly

2013-03-05T01:10:30+02:00

on each path, i mean for ex here the 256pm, when ou double clic and open it there are 'stored to preset manager' or 'stored to conductor' swichs when you are in the patch, if booth are disable there should be no recall of everything included in the patch, incuding the listbox, and including the script, exept for recall on reopening the patch.
mmm wait ... now i remember.. indeed it has later benn changed and items such list box got this swich in the edit layout now, maybe this was later than when i uploaded it.. man has to check it is unchecked too maybe this would fix the pb, cause teorically if booth are unchecked there won't be any recall.
(i must admit i don't got usine on the computer, made a fresh install recently and was very busy, i ll try to check tomorrow)

Statistics: Posted by 23fx23 — 05 Mar 2013, 00:10

preset managers behaving badly

2013-03-05T01:06:59+02:00

i will download the updated script and see if that solves the problems. Thanks guys!

Statistics: Posted by seamus — 05 Mar 2013, 00:06

preset managers behaving badly

2013-03-04T13:48:34+02:00

when working with IML it's really necessary to disable fast callback. I had usine crashes when making the vst loader until I enabled it.
This could have been the cause for mixing up between tracks. When enabled, Usine produces strange things.
I found this hint on the IML wiki site nearly at the top.
About the setdont I'm not really shure in your script. I fixed my problems when building the hardwired version with it. It also changes preset saving. I enabled this only to eliminate all possible errors. Since your script has no outputs, the chance is high, that it is not necesary.

What do you mean with the "the patch itself got 'don't store to preset ' activeted normally"? Did you mean the list box?

Statistics: Posted by percuson — 04 Mar 2013, 12:48

preset managers behaving badly

2013-03-04T12:31:11+02:00

mmm the setdont save was needed to store and recall the correct list when reopening the patch, i think we need it but i'll check.. anyway the patch itself got 'don't store to preset ' activeted normally nope?? (if not you indeed need to desactivate save to PM when copying the patch). maybe the setfastcallback could be set to false, but it will be less responsive. but try if it solves the pb

Statistics: Posted by 23fx23 — 04 Mar 2013, 11:31

preset managers behaving badly

2013-03-04T07:30:53+02:00

After spending the whole night in building a 'hardwired' version, I think I found 2 mistakes in 23fx23s script...

Try it out please:
download

I set "SetFastCallBack - false" for all inputs
and I set the "setdontsave" command for the text inputs.
I'm annoyed that I didn't take a closer look at the script earlier....
This should really solve the problems.
If not... I finished my hardwired version before finding the errors and could share it.

Statistics: Posted by percuson — 04 Mar 2013, 06:30

preset managers behaving badly

2013-03-03T23:35:14+02:00

i guess by waitig hollyock yes, it will be out soon and sthe scripting engine has been updated , so it should fix the pb

Statistics: Posted by 23fx23 — 03 Mar 2013, 22:35

preset managers behaving badly

2013-03-03T22:39:23+02:00

Yes the names of the presets are getting exchanged.
That's really a shame there isn't a simple solution. I guess it's best to just stick to the simple senso 16 presets.

Statistics: Posted by seamus — 03 Mar 2013, 21:39

preset managers behaving badly

2013-03-03T17:26:51+02:00

sorry im not sure i understood, you mean problem could come from the script setting the listbox text for presets? if so i suspect
iml causes the problem, and maybe sertting it via wire would solve the problem, but indeed it makes a huge array and is quite cpu violent..not ideal mmmmm

Statistics: Posted by 23fx23 — 03 Mar 2013, 16:26

preset managers behaving badly

2013-03-03T09:47:58+02:00

maybe 23fx23 can fix it? Or should i just abandon this way of saving presets for patches?

Statistics: Posted by seamus — 03 Mar 2013, 08:47

preset managers behaving badly

2013-03-03T06:51:49+02:00

I figuered out, that it is a simple script problem:
The script is saved in the preset and it is recalled at older preset values, so the names switch to recent values.
I'll try to build a simple demo to show the effect. But this doesn't explain the mixup between the patches. Maybe this is called by copy and paste.
The solution would be, to set the names by patch and not by script. The prob is, that to create comma text, you need a script.....

Statistics: Posted by percuson — 03 Mar 2013, 05:51

preset managers behaving badly

2013-03-03T04:13:06+02:00

i wonder if in Hollyhock a new system of preset management for patches will exist?

Statistics: Posted by seamus — 03 Mar 2013, 03:13

preset managers behaving badly

2013-03-03T04:11:30+02:00

just the names get mixed up not the faders or settings... but it can still cause problems as you can imagine. Usually i can reload the patch and all is fine

Statistics: Posted by seamus — 03 Mar 2013, 03:11

preset managers behaving badly

2013-03-02T05:34:36+02:00

I'm already trying to hard wire. I did it with a poly sub patch and it uses a lot cpu... when trying to also store the names, I had about 15%

But I have a totally different idea....

@Seamus: Did you check already, if only the names get confused, or if also the settings of faders, etc... mix up?

Statistics: Posted by percuson — 02 Mar 2013, 04:34

preset managers behaving badly

2013-03-01T18:31:26+02:00

the multiproc find is interesting, maybe an 'hardwired' version that don't use iml but real wires would work correctly i think , i will try next week and post if working..

Statistics: Posted by 23fx23 — 01 Mar 2013, 17:31

preset managers behaving badly

2013-03-01T12:25:08+02:00

There shouldn't be any restriction on the hardware side. More cores are simply faster. And the more tracks you have, the more cpu is needed. So you get limited... Do you really need that much presets? And isn't there a patching variant of presets without scripts?
Increasing the level for higher nb values isn't possible, I think...
Hm.... no solution at this time. If I could reproduce the error, it would be much easier.

Statistics: Posted by percuson — 01 Mar 2013, 11:25

preset managers behaving badly

2013-03-01T10:03:01+02:00

now the strange problem i have is that some synths/patches in my setup wont sound unless i have nb up to 4 or more.
So the question is can I run a full setup of several synths with bus audio and bus midi with a setting of nb1?
Or better yet is there a way to make these presets behave in higher nb values? It seems like I am limited to a certain number of tracks with a NB setting of only one.

Statistics: Posted by seamus — 01 Mar 2013, 09:03

preset managers behaving badly

2013-03-07T16:04:32+02:00

yup ill do this tonight or tomorrow, iam actually at work

Statistics: Posted by 23fx23 — 07 Mar 2013, 15:04

preset managers behaving badly

2013-03-07T15:32:41+02:00

@ 23fx23: could you update it in the add-ons section? So nobody else will have the same problem...

Statistics: Posted by percuson — 07 Mar 2013, 14:32

preset managers behaving badly

2013-03-06T11:31:18+02:00

@ percusson thx for the fastcallback reminder^^ i was really busy rhose days and you made a nice investigation^^
Cool seamus

Statistics: Posted by 23fx23 — 06 Mar 2013, 10:31

preset managers behaving badly

2013-03-06T10:56:58+02:00

cool!

Statistics: Posted by percuson — 06 Mar 2013, 09:56

preset managers behaving badly

2013-03-06T09:43:50+02:00

it seems to work!! Bravo! Thank you so much! Usine has such a supportive community!

Statistics: Posted by seamus — 06 Mar 2013, 08:43

preset managers behaving badly

2013-03-05T21:14:08+02:00

I'm gonna check this and report back

Statistics: Posted by seamus — 05 Mar 2013, 20:14

preset managers behaving badly

2013-03-05T13:40:35+02:00

Statistics: Posted by percuson — 05 Mar 2013, 12:40

preset managers behaving badly

2013-03-05T01:46:23+02:00

Statistics: Posted by 23fx23 — 05 Mar 2013, 00:46

preset managers behaving badly

2013-03-05T01:24:05+02:00

Statistics: Posted by 23fx23 — 05 Mar 2013, 00:24

preset managers behaving badly

2013-03-05T01:10:30+02:00

Statistics: Posted by 23fx23 — 05 Mar 2013, 00:10

preset managers behaving badly

2013-03-05T01:06:59+02:00

i will download the updated script and see if that solves the problems. Thanks guys!

Statistics: Posted by seamus — 05 Mar 2013, 00:06

preset managers behaving badly

2013-03-04T13:48:34+02:00

Statistics: Posted by percuson — 04 Mar 2013, 12:48

preset managers behaving badly

2013-03-04T12:31:11+02:00

Statistics: Posted by 23fx23 — 04 Mar 2013, 11:31

preset managers behaving badly

2013-03-04T07:30:53+02:00

Statistics: Posted by percuson — 04 Mar 2013, 06:30

preset managers behaving badly

2013-03-03T23:35:14+02:00

i guess by waitig hollyock yes, it will be out soon and sthe scripting engine has been updated , so it should fix the pb

Statistics: Posted by 23fx23 — 03 Mar 2013, 22:35

preset managers behaving badly

2013-03-03T22:39:23+02:00

Yes the names of the presets are getting exchanged.
That's really a shame there isn't a simple solution. I guess it's best to just stick to the simple senso 16 presets.

Statistics: Posted by seamus — 03 Mar 2013, 21:39

preset managers behaving badly

2013-03-03T17:26:51+02:00

Statistics: Posted by 23fx23 — 03 Mar 2013, 16:26

preset managers behaving badly

2013-03-03T09:47:58+02:00

maybe 23fx23 can fix it? Or should i just abandon this way of saving presets for patches?

Statistics: Posted by seamus — 03 Mar 2013, 08:47

preset managers behaving badly

2013-03-03T06:51:49+02:00

Statistics: Posted by percuson — 03 Mar 2013, 05:51

preset managers behaving badly

2013-03-03T04:13:06+02:00

i wonder if in Hollyhock a new system of preset management for patches will exist?

Statistics: Posted by seamus — 03 Mar 2013, 03:13

preset managers behaving badly

2013-03-03T04:11:30+02:00

just the names get mixed up not the faders or settings... but it can still cause problems as you can imagine. Usually i can reload the patch and all is fine

Statistics: Posted by seamus — 03 Mar 2013, 03:11

preset managers behaving badly

2013-03-02T05:34:36+02:00

Statistics: Posted by percuson — 02 Mar 2013, 04:34

preset managers behaving badly

2013-03-01T18:31:26+02:00

the multiproc find is interesting, maybe an 'hardwired' version that don't use iml but real wires would work correctly i think , i will try next week and post if working..

Statistics: Posted by 23fx23 — 01 Mar 2013, 17:31

preset managers behaving badly

2013-03-01T12:25:08+02:00

Statistics: Posted by percuson — 01 Mar 2013, 11:25

preset managers behaving badly

2013-03-01T10:03:01+02:00

Statistics: Posted by seamus — 01 Mar 2013, 09:03