Forums > Max For Live

Possible bug in live.thisdevice

May 18, 2012 | 7:20 pm

I noticed for a while that sometimes live.thisdevice doesn’t fire when I have edited my patch. So I always kept a bang in my interface while developing in case the thing doesn’t initialize properly.

I think I now found when this happens.

live.thisdevice sends out a bang:
- yes : when you edit the patch and click the "preview mode" button again in live to exit edit mode
- no: when you just close the window in Max.

Sorry I have no time to make an example patch now. But I will do after the weekend if required.
The question is whether it’s a bug or a feature:)


May 18, 2012 | 8:14 pm

If your device has no new changes to be saved when you close it in the editor, it does not need to be reloaded because it already has been loaded the last time you saved. But you do get the notification that you are changing preview mode.

-A


June 1, 2012 | 9:57 pm

Hi Andrew,

I get it that makes perfect sense.

My patch depends on send/receive pairs that are bound to a name derived from a liveapi query on loadbang,

Sometimes after editing these connections are lost, and I need to manually bang the init sequence to get them communicating again. It doesn’t happen often so I can’t quite put my finger on it. I hope I can reproduce it in some way. It might be related to the liveapi/query and not so much the loadbang then.


June 3, 2012 | 5:58 pm

I’ve found this, I always end up just using a loadbang , a live.thisdevice and then a bang for when I manually want to init things. Belt and braces.


Viewing 4 posts - 1 through 4 (of 4 total)