Device only usable after I click the Edit Button?
I just finished up an instrument and exported it to a M4L file, but for some reason I can't get it to work when I put it in Ableton. If I click the "Edit Button" to edit it in Max 8 and then close out of it (literally without changing anything), it suddenly works. I tried rebooting everything, but for some reason it will never output audio until I open it in Max and then close out of it. Has anyone ever had this happen before? It's receiving midi, and presumably everything's working, but it's almost impossible to troubleshoot; as soon as I open it up to find out what's wrong, it works!
Ideas? Help?
[Ableton 10, Max 8, Mac High Sierra]
you sure you took the "Max Audio Effect" device as a starting point, and integrated your stuff into it?
It's actually a heavily modified existing M4L device (the "More Simpler" device from the Ableton Time and Pitch pack or whatever it's called). It's set up to export as an instrument. Like I said, I can get it to work, but I have to open it for editing in Ableton and then close it, then suddenly it's functional. It's really perplexing.
really hard to say, but I would suggest to check the initialization of the device. The timing of live.thisdevice and loadbang might be different when it comes from the max editor so that it "repairs" any erroneous init sequence of the device. Adding prints and observing the timing on the console will help finding the issue. But it is just a shot in the dark...
I removed all loadbangs in hopes that would respond better to Ableton, but to no avail. The problem with prints and observations is that opening the device makes it work, so it's impossible to debug it without opening it and thus having it suddenly work.
it is possible to see the prints if you use the MaxForLive console (not the max console)
in ableton, right click on device title, select "open max window". for problems like yours, it is the best you have, unfortunately
When I've encountered similar behavior it was when I had a device which could cause a stack overflow on load. And I agree with hollyhook about the use of the MaxForLive console and lots of printing of values. I normally connect one [funnel] to one [print] for this , just make sure it's on the far right side of the patch.