pyrolator

I am working quite a whle now on a patch with a lot of bpatchers which kind of mutiply (bpatcher within bpatcher) within the patch. (polyrhythmic polyphonic sequenzer with a lot of colls and counters)

The folder with all the patchers and bpatches needed for the project is only about 13mb, and is quite optimized and stable, but when I am making an application or standalone from it it blows up to over 200mb. 

The loading time of the patch is now over two minutes (on a MBP). I even have a start-screen now, which says "calm down, just wait..." :-)

How would you handle the loading of such a huge patcher? Do you load sub-patcher in a predefined sequence? Or all at once?

I am working quite a whle now on a patch with a lot of bpatchers which kind of mutiply (bpatcher within bpatcher) within the patch. (polyrhythmic polyphonic sequenzer with a lot of colls and counters)
The folder with all the patchers and bpatches needed for the project is only about 13mb, and is quite optimized and stable, but when I am making an application or standalone from it it blows up to over 200mb. 
The loading time of the patch is now over two minutes (on a MBP). I even have a start-screen now, which says "calm down, just wait..." :-)

How would you handle the loading of such a huge patcher? Do you load sub-patcher in a predefined sequence? Or all at once?
Any idea on optimizing the load process?

loading-large-patch

i develop quiet large patches, and i didn't solve the loading time problem.

it comes from the json format, which is very verbose (can i use this word

that's why i think a binary format may be a good thing.

you can still trash what's in your max5 preferences folder... it will speed

up things a little bit (but you will lose your prefs).

let me know if you find a solution please.

> I am working quite a whle now on a patch with a lot of bpatchers which kind

> of mutiply (bpatcher within bpatcher) within the patch. (polyrhythmic

> polyphonic sequenzer with a lot of colls and counters)

> The folder with all the patchers and bpatches needed for the project is

> only about 13mb, and is quite optimized and stable, but when I am making an

> application or standalone from it it blows up to over 200mb.

> The loading time of the patch is now over two minutes (on a MBP). I even

> have a start-screen now, which says "calm down, just wait..." :-)

> How would you handle the loading of such a huge patcher? Do you load

> sub-patcher in a predefined sequence? Or all at once?

> Any idea on optimizing the load process?

i develop quiet large patches, and i didn't solve the loading time problem.
it comes from the json format, which is very verbose (can i use this word
like this?).
that's why i think a binary format may be a good thing.

you can still trash what's in your max5 preferences folder... it will speed
up things a little bit (but you will lose your prefs).

>
> I am working quite a whle now on a patch with a lot of bpatchers which kind
> of mutiply (bpatcher within bpatcher) within the patch. (polyrhythmic
> polyphonic sequenzer with a lot of colls and counters)
> The folder with all the patchers and bpatches needed for the project is
> only about 13mb, and is quite optimized and stable, but when I am making an
> application or standalone from it it blows up to over 200mb.
> The loading time of the patch is now over two minutes (on a MBP). I even
> have a start-screen now, which says "calm down, just wait..." :-)
>
>
> How would you handle the loading of such a huge patcher? Do you load
> sub-patcher in a predefined sequence? Or all at once?
> Any idea on optimizing the load process?
>
> best wishes
> Kurt Dahlke
>
>

loading large patch