ArrayArrayArrayArrayArrayArrayArrayArray BrainModular BrainModular Users Forum 2010-06-25T20:41:48+02:00 https://brainmodular.org/forums/app.php/feed/topic/2261 2010-06-25T20:41:48+02:00 2010-06-25T20:41:48+02:00 https://brainmodular.org/forums/viewtopic.php?t=2261&p=14415#p14415 <![CDATA[128 presets or more Manager]]> Statistics: Posted by 23fx23 — 25 Jun 2010, 20:41


]]>
2010-06-25T20:20:19+02:00 2010-06-25T20:20:19+02:00 https://brainmodular.org/forums/viewtopic.php?t=2261&p=14413#p14413 <![CDATA[128 presets or more Manager]]> Statistics: Posted by 23fx23 — 25 Jun 2010, 20:20


]]>
2010-06-25T20:18:33+02:00 2010-06-25T20:18:33+02:00 https://brainmodular.org/forums/viewtopic.php?t=2261&p=14412#p14412 <![CDATA[128 presets or more Manager]]> Statistics: Posted by gurulogic — 25 Jun 2010, 20:18


]]>
2010-06-25T18:33:18+02:00 2010-06-25T18:33:18+02:00 https://brainmodular.org/forums/viewtopic.php?t=2261&p=14411#p14411 <![CDATA[128 presets or more Manager]]> this patch has inspired me something.
In you case you put this add-on in your main patch and our stuffs (what we have to save) in a sub-patch.
The idea is simple:
why don't make the inverse, I mean the addon in a sub patch and our stuff in the main patch.

Actually, it's impossible because the preset module only saves current patch and its sub patches.
So I have create a new parameter in the preset module:
target patch:

- the current patch (and all its sub-patches)
- the parent patch (and all its sub-patches)
- the top parent patch (and all its sub-patches)


will be implemented in the next release v5.18

Statistics: Posted by senso — 25 Jun 2010, 18:33


]]>
2010-06-25T07:11:00+02:00 2010-06-25T07:11:00+02:00 https://brainmodular.org/forums/viewtopic.php?t=2261&p=14383#p14383 <![CDATA[128 presets or more Manager]]> http://www.sensomusic.com/forums/upload ... al%202.pat
Maybe you can figure out why it is doing what it shouldn't be able to do? :)

Statistics: Posted by gurulogic — 25 Jun 2010, 07:11


]]>
2010-06-25T05:59:16+02:00 2010-06-25T05:59:16+02:00 https://brainmodular.org/forums/viewtopic.php?t=2261&p=14382#p14382 <![CDATA[128 presets or more Manager]]> same. i found a workaround but not very clean: it changes the preset to nb+1 then back to nb+0, but it implies two consecutive
reload. yup if by chance you find back the patch i would be intested to see how ya did.

Statistics: Posted by 23fx23 — 25 Jun 2010, 05:59


]]>
2010-06-25T05:34:38+02:00 2010-06-25T05:34:38+02:00 https://brainmodular.org/forums/viewtopic.php?t=2261&p=14381#p14381 <![CDATA[128 presets or more Manager]]> I did actually find a way around the problem and I can load presets back and forth from the last slot of one PM and the first slot of the next , but even looking at it now I don't understand what I did to make it work? It just does...;) I know it was a headache and took me awhile to figure out. hmmm...
Another difference with mine was that it stores and clears whichever preset is currently loaded. (same same but different)

Funny though, I couldn't find my PMx128 in the downloads section? let me know if you need a fresh copy for study...

(PS, I haven't dropped off the face of the earth and will hopefully be spending more time around here soon :) )

edit: OK, I think it's because you need to send a value to the num inlet instead of using the recall inlets to recall a preset that is already selected...

Statistics: Posted by gurulogic — 25 Jun 2010, 05:34


]]>
2010-06-25T01:51:31+02:00 2010-06-25T01:51:31+02:00 https://brainmodular.org/forums/viewtopic.php?t=2261&p=14379#p14379 <![CDATA[128 presets or more Manager]]>
this allows to get access, store, recall, clear, or copy and paste 128 presets or more.

Image

addons/ data


ps I note there is the folowing tiny isue:

it uses in fact several PMs, ie 128 presets is 16PM of 16 presets.
if we acces preset 15 it will be the 15th of the 1rst PM, if accessing preset 16 it will be 0 of second PM ect..
it won't work in some cases if the nb we want acces hasn't changed on the target PM we are accessing to, because
PM won't recall same nb.
as a workaround change to next preset then back. If some have ideas relating how to fix that that let me know..
i don't remember if had same pb on your patch gurulogic? i guess yes..

anyway think it can be still usefull as is...

Statistics: Posted by 23fx23 — 25 Jun 2010, 01:51


]]>
BrainModular BrainModular Users Forum 2010-06-25T20:41:48+02:00 https://brainmodular.org/forums/app.php/feed/topic/2261 2010-06-25T20:41:48+02:00 2010-06-25T20:41:48+02:00 https://brainmodular.org/forums/viewtopic.php?t=2261&p=14415#p14415 <![CDATA[128 presets or more Manager]]> Statistics: Posted by 23fx23 — 25 Jun 2010, 20:41


]]>
2010-06-25T20:20:19+02:00 2010-06-25T20:20:19+02:00 https://brainmodular.org/forums/viewtopic.php?t=2261&p=14413#p14413 <![CDATA[128 presets or more Manager]]> Statistics: Posted by 23fx23 — 25 Jun 2010, 20:20


]]>
2010-06-25T20:18:33+02:00 2010-06-25T20:18:33+02:00 https://brainmodular.org/forums/viewtopic.php?t=2261&p=14412#p14412 <![CDATA[128 presets or more Manager]]> Statistics: Posted by gurulogic — 25 Jun 2010, 20:18


]]>
2010-06-25T18:33:18+02:00 2010-06-25T18:33:18+02:00 https://brainmodular.org/forums/viewtopic.php?t=2261&p=14411#p14411 <![CDATA[128 presets or more Manager]]> this patch has inspired me something.
In you case you put this add-on in your main patch and our stuffs (what we have to save) in a sub-patch.
The idea is simple:
why don't make the inverse, I mean the addon in a sub patch and our stuff in the main patch.

Actually, it's impossible because the preset module only saves current patch and its sub patches.
So I have create a new parameter in the preset module:
target patch:

- the current patch (and all its sub-patches)
- the parent patch (and all its sub-patches)
- the top parent patch (and all its sub-patches)


will be implemented in the next release v5.18

Statistics: Posted by senso — 25 Jun 2010, 18:33


]]>
2010-06-25T07:11:00+02:00 2010-06-25T07:11:00+02:00 https://brainmodular.org/forums/viewtopic.php?t=2261&p=14383#p14383 <![CDATA[128 presets or more Manager]]> http://www.sensomusic.com/forums/upload ... al%202.pat
Maybe you can figure out why it is doing what it shouldn't be able to do? :)

Statistics: Posted by gurulogic — 25 Jun 2010, 07:11


]]>
2010-06-25T05:59:16+02:00 2010-06-25T05:59:16+02:00 https://brainmodular.org/forums/viewtopic.php?t=2261&p=14382#p14382 <![CDATA[128 presets or more Manager]]> same. i found a workaround but not very clean: it changes the preset to nb+1 then back to nb+0, but it implies two consecutive
reload. yup if by chance you find back the patch i would be intested to see how ya did.

Statistics: Posted by 23fx23 — 25 Jun 2010, 05:59


]]>
2010-06-25T05:34:38+02:00 2010-06-25T05:34:38+02:00 https://brainmodular.org/forums/viewtopic.php?t=2261&p=14381#p14381 <![CDATA[128 presets or more Manager]]> I did actually find a way around the problem and I can load presets back and forth from the last slot of one PM and the first slot of the next , but even looking at it now I don't understand what I did to make it work? It just does...;) I know it was a headache and took me awhile to figure out. hmmm...
Another difference with mine was that it stores and clears whichever preset is currently loaded. (same same but different)

Funny though, I couldn't find my PMx128 in the downloads section? let me know if you need a fresh copy for study...

(PS, I haven't dropped off the face of the earth and will hopefully be spending more time around here soon :) )

edit: OK, I think it's because you need to send a value to the num inlet instead of using the recall inlets to recall a preset that is already selected...

Statistics: Posted by gurulogic — 25 Jun 2010, 05:34


]]>
2010-06-25T01:51:31+02:00 2010-06-25T01:51:31+02:00 https://brainmodular.org/forums/viewtopic.php?t=2261&p=14379#p14379 <![CDATA[128 presets or more Manager]]>
this allows to get access, store, recall, clear, or copy and paste 128 presets or more.

Image

addons/ data


ps I note there is the folowing tiny isue:

it uses in fact several PMs, ie 128 presets is 16PM of 16 presets.
if we acces preset 15 it will be the 15th of the 1rst PM, if accessing preset 16 it will be 0 of second PM ect..
it won't work in some cases if the nb we want acces hasn't changed on the target PM we are accessing to, because
PM won't recall same nb.
as a workaround change to next preset then back. If some have ideas relating how to fix that that let me know..
i don't remember if had same pb on your patch gurulogic? i guess yes..

anyway think it can be still usefull as is...

Statistics: Posted by 23fx23 — 25 Jun 2010, 01:51


]]>