BrainModular

I was just experimenting with using the load patch module to load fairly cpu and ram heavy patches in realtime with audio and midi streaming through the patches with receive buses and it actually worked quite well with no interuptions to a parallel audio stream so it got me to thinking how valuable this could be for use live as one of the big problems I have is that on a slow computer, complex patches needed just to keep live performance flexible end up using much of my computer cpu just to load the basic patches, before fx and such are even turned on.
If using realtime patch loading, then it would be possible just to wire up the components that are required for each performance.
As I already use a software to resample a loop to play back during song transitions, loading patches in realtime should work much the same way for me.

That being said, I can already do this is Usine, but it is complicated if I use this approach as the LoadPatch module does not accept text input for selecting the name of the patch to load, presumably because once there is a text input to the patch name, LoadPatch no longer has a refence for the root directory the patches are stored in.

Ideally, and my suggestion is that I could tell the LoadPatch module where the root patch directory was and then a listbox etc. could be used via an input bus to select the name of the next patch to load. (which also reminds me that for some reason I seem unable to send text data over a bus?)

Also, in the hopefull future that an audio send bus can be safely disconnected, the above ideas would have even more function if the LoadPatch module could also be set to load sub patches.

Then again maybe I'm crazy and these ideas are no good...?

my opinion is that I think it's possible to create a patch to format the patch name with the "concat strings" modules to achieve what you want?
Also the conductor provides a efficient way to chain workspaces.

So, i'm sure that the loadpatch module can be improved but for me it's not the highest priority?

senso wrote:my opinion is that I think it's possible to create a patch to format the patch name with the "concat strings" modules to achieve what you want?

Perhaps I had better take this to the patching questions forum.. I definately do not understand how that would work.
Just to be clear, I wouldn't want to be just loading the 'next' patch always. I would want to be able to select from the ib any patch to load. One other way I see to do this is to have a set number of loadpatch modules in each patch, each one with the name of another patch load choice but this seems overly complex, especially when I change computers and if the root directory changes.

Also, chaining workspaces does not make sense for me as some items would have to remain constant,
but I understand you have higher priorities, and this is just a new idea for me that may not even be all that practical in real world use.

Now to see if I can figure out "concat strings"

Ok, I have this working...I can use a dispatch to select from one of many Load Patch Modules so long as the multiple copies of the patch template are pre-populated in the root patch folder and each has the same Load Patch Module references as the other patches.

A bit much to wrap my head around at first but I should be able to work with it, though just being able to select a patch name with a listbox connected to the "currently non usefull name input pin" on the Load Patch Module would be much less complex.

(btw, if I connect a text input that says "test1.pat" to the name input of the Load Patch Module, the name reads "dddd1.dad".Is this correct behavior?)

Also I tested moving the patches to another computer and so long as I keep the directory structure the same, the patches load fine so I guess no further suggestions or improvements are really necessary to make this idea work

Thanks for listening...

about the "ddd".
Actually I don't know if it's juste a display pb or something more dramatic....
I'll take a look.

senso wrote:my opinion is that I think it's possible to create a patch to format the patch name with the "concat strings" modules to achieve what you want?

Just in case anyone else is ever wondering how to best use the LoadPatch module, I have finally deciphered Senso's cryptic response ...

What I did not understand is the the name inlet is used to tell the LoadPatch module the directory where the patch is, ie C:UsinePatchExample1.pat

-using Concat Strings, String 1 is the directory name, ie: C:UsinePatch
-then you can connect a listbox with the names of all your patches to the inlet of String 2
-then you connect the String out to the name input of the LoadPatch module so as you select from your listbox you end up with C:UsinePatchExample1.pat, C:UsinePatchExample2.pat, C:UsinePatchExample3.pat etc.

So in my opinion, the LoadPatch module is already perfect! (but somewhat poorly documented )

well done,
maybe you can add your tip in the wiki?

Sure thing, I would be happy to..
What is the best way to add information like this? Should we maybe start a new section called "Tips and Tricks" or... ?

you can create a new page here :
http://www.sensomusic.com/wiki/doku.php ... tips:index

oh this is strange. I can follow your link no problem, but if I go to http://www.sensomusic.com/wiki/doku.php?id=manual:guide I absolutely cannot see a Tips section. Am I blind?

no, you're not blind , some section are hidden for the moment or don't need to be in the index..

yes this place is the right one
http://sensomusic.com/wiki/doku.php?id= ... al_loading