BrainModular

recall patches directly from pm

2011-03-06T16:11:56+02:00

The internal structure of the PM is very complex and very optimized. For now changes have to be implemented with the maximum of precautions. That's why we can't consider your suggestion as a simple improvement, but like a very deep modification. So not easy... I keep in mind your suggestion for the time we will rewrite the PM engine.

Statistics: Posted by senso — 06 Mar 2011, 15:11

recall patches directly from pm

2011-03-06T04:39:02+02:00

I think it would be ok? The patch doesn't need to save and load as fast as the preset data would because when the preset manager were in "patch manager" mode, normal preset store/recall parameters would not be needed as the entire patch would be stored and recalled, essentially the same as the loadpatch method but without the micro-management of patch names, loadpatch variables and the file/ save dialogues per patch. The preset manager would in this case be responsible for generating a unigue file name for the patch, storing it to disk and restoring it in place when the preset were selected..
For another aspect, if it were optional to choose to store a preset within workng memory so that load times could be almost instantanious, this could also be cool.

Statistics: Posted by gurulogic — 06 Mar 2011, 03:39

recall patches directly from pm

2011-03-04T23:31:44+02:00

yes good suggestion, but actually it's not so easy because the preset manager is very fast and not very compatible with a "load patch" which is very slow.
let me time to think about this idea.

Statistics: Posted by senso — 04 Mar 2011, 22:31

recall patches directly from pm

2011-03-03T23:57:30+02:00

How about an option to store and recall a patch or subpatch via the preset manager, without use of the loadpatch module?

Storing a preset with this option enabled would automaticly save a copy the patch to disk (uniquely named) that would be loaded when the preset were recalled. If this could also be applicable to subpatches being reloaded in place (assuming all the patch inlets and outlets were the same), this would be even handier.
My reasoning for this suggestion is that management of the patches when using the loadpatch module across many patches in a workspace is a bit of a headache. It would be nice if there were no need to sub-manage patch naming, saving and loadpatch load variables. Just click and done.

Anyways, just a thought..

Statistics: Posted by gurulogic — 03 Mar 2011, 22:57

recall patches directly from pm

2011-03-06T16:11:56+02:00

Statistics: Posted by senso — 06 Mar 2011, 15:11

recall patches directly from pm

2011-03-06T04:39:02+02:00

Statistics: Posted by gurulogic — 06 Mar 2011, 03:39

recall patches directly from pm

2011-03-04T23:31:44+02:00

yes good suggestion, but actually it's not so easy because the preset manager is very fast and not very compatible with a "load patch" which is very slow.
let me time to think about this idea.

Statistics: Posted by senso — 04 Mar 2011, 22:31

recall patches directly from pm

2011-03-03T23:57:30+02:00

Statistics: Posted by gurulogic — 03 Mar 2011, 22:57