chapelier fou

In a m4l device how can i have the bpatchers' states saved with a preset object ?

In a m4l device how can i have the bpatchers' states saved with a preset object ?
thanks !


m4l-preset-system-not-recalling-bpatchers-states

I don't have an answer for you, but I feel that we may be having the same problem which I may be able to clarify a bit so that other people on the forum are more inspired to jump in and help. Params in bpatchers can be saved within an M4L preset just like any others (simply make sure that Parameter Visibility is set to 'Automated and Stored' in the parameter's inspector).

If you have already done this, I assume you are coming across the same weird bug as me, where some parameters in your patch are being restored just fine, but for some reason the ones in your bpatchers are not?

I've done some tests and it would appear that as long as your patch is below a certain size/complexity, bpatchers' parameters will be restored, 

 if your patch grows above a certain size, they will not restore. Try it for yourself by creating a patch containing literally just a bpatcher with a live.numbox in it. The parameter will restore. This leads me to conclude that the problem is to do with the fact that the saved values from the Ableton preset get fired out immediately as the patch starts to load, regardless of whether or not the bpatchers etc. have had time to initialise. This means that if the patch is small and lightweight, the bpatchers will load before the values are sent out, and get the messages, but if the patch starts to become a bit big, they’ll won't have initialised in time and will probably miss them.

is there a way of delaying the sending out of the stored values from a Live preset until after the patch is fully initialised?

I've done some tests and it would appear that as long as your patch is below a certain size/complexity, bpatchers' parameters will be restored, but if your patch grows above a certain size, they will not restore. Try it for yourself by creating a patch containing literally just a bpatcher with a live.numbox in it. The parameter will restore. This leads me to conclude that the problem is to do with the fact that the saved values from the Ableton preset get fired out immediately as the patch starts to load, regardless of whether or not the bpatchers etc. have had time to initialise. This means that if the patch is small and lightweight, the bpatchers will load before the values are sent out, and get the messages, but if the patch starts to become a bit big, they’ll won't have initialised in time and will probably miss them.

So, the question is:  is there a way of delaying the sending out of the stored values from a Live preset until after the patch is fully initialised?

i set the parameter's order to 1 in the bpatcher, it seems to fix the problem but i'm not sure

M4L : preset system not recalling bpatchers states