Manually resend values from Live preset? Bpatchers in big patches missing values

Yuli Levtov

I've come across a problem relating to Live presets with big patches. It would seem 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. 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 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.

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

Thanks!
Yuli

S4racen

I use one live.thisdevice per patcher... it fires out a bang whic h i convert to a 1 sent to t s ---initgate object, each Live GUI object is fed into a gate which isn't turned on until the whole patch is therefore initialised...

I'll then send a bang to a r ---initbang object and connect the s ---initbang to every parameter i want to restore in my patch..

This process removes many of the errors associated with trying to restore values before a patch is initilaised...

Cheers
D

Yuli Levtov

Hi S4racen,

Thanks for the info, but I'm not sure how this recall's the preset information from Live? Are you sending a bang to a specific object to make Live resend the values? If you have an example patch that would be very helpful...

Thanks,
Y

Yuli Levtov

Embarrassed to say that I was, in fact, resetting some of the values that I was trying to recall myself!

Resolved - if only I could delete threads...