device behaves differently when open

    Nov 09 2018 | 1:38 am
    Can anyone give me any insight as to why my device plays with some strange artifacts when loaded into a track, however as soon as I open it - it behaves as it should. Then if I close it, to return to Live - even without touching anything, it stops working altogether. It is a Max Midi effect used to control some hardware. Another thing is I get errors saying some Colls are missing - but that is not an issue as they are saved with the patch and are definitely working.

    • Nov 09 2018 | 4:22 pm
      Could this be because I only own Max 7 but Live opens with Max 8?
      Or is there a specific order I need to freeze before saving? I think I tend to simply put it in presentation mode, then lock then freeze then save.
    • Nov 09 2018 | 5:11 pm
      try to put a defer object before the midi output. this kind of differences between editor and normal operation in Live are caused by the fact that the editor runs the device in a separate thread (not the Live thread)
    • Nov 09 2018 | 5:21 pm
      Ha!! I literally just finished watching Timothy Place's video on Threading 2min ago. I noted that point about Max for Live devices defaulting to audio interrupt mode, and thought I should check this, as I'm not even sure what my settings in Max were. I will have a play with those objects when I get home. Thanks.
    • Nov 21 2018 | 6:41 pm
      Hi, I am having a similar problem, but with a Max Audio Effect. It sounds strange when loaded into a track, but when I open it in preview mode it works just fine. Could this be a audio driver issue? (I am using the newest version of Max, not the built in in Live10) The core of the device is in a [poly~], also I am using quite a few [gen~] patchers and MC objects. May this be a reason for the faulty behaviour? Any hints on what I may be missing welcome! Thanks