Loadbang while toggling between max editor and live device

[toscanini]

Hello,
obviously I was mistaken about loadbang and loadmess' behaviour as I switch from the max device editor to the live nested device and vice versa. I thought that global initialization would happen each time. Now, with the help of the Max window I see that the initialization happens when I open the editor, but not when I close it. Of course it does not mean that the device wouldn't properly initialize when loaded into a Live set, but as far as it concerns editing and testing m4l patches it seems like a drawback to me. How do you guys solve this?

Another question, I have this tap tempo patch I have posted in another thread, with quite some loadbangs over the structure, is this a good way to use it, or should I rather have one loadbang, and define a triggering order?

Thank you for sharing your experiences,
toscanini

[emajcher]

I have found that a good habit to get into is to stay away from Max's implicit message ordering (top to bottom right to left) as much as possible and control the flow of the messages. Instead of having multiple loadbangs try one loadbang going into trigger object so you can guarantee message flow, you will be thankful when as your patches get larger if you are trying to debug. If your patch is too spread out to use one loadbang going into a trigger try using send/receives to the parts of your patch or encapsulate larger portions of code into a sub patcher. Having a minimal loadbang's allows you to test in an easier fashion without having to actually "load" the patch to see if it works, you can always click a loadbang or send it a bang to test the objects listening for the loadbang.

Edward

[pucklermuskau]

so this is relevant to something i have struggled with. I have a m4l patch that uses a hi object, works fine, but sometimes the patch will stop responding to the hid device. I don't get this behaviour when i have the patch open, but if i have the device saved in my live template, it won't work until i delete it and drop in a new copy. What is causing this loss of communication, and how can i implement a 'refresh' in my patch, so i can reestablish connection without reloading the device?

[julienb]

(closebang) can help too, in some tricky cases.

[toscanini]

Cool:) thank you guys for the suggestions!