Tutorial 1.2 - Remembering Parameter id When Moving Device

[@PLUXARIS]

seems to work alright, however I keep getting a banner that says: "ipatcher: stack overflow -- outlets are disabled until this message is cleared" If I close it, the mapping works perfect, but it's quite annoying. The error appears to be inside of the device_pos_change patcher. Any ideas? I've triple checked my wiring.

[@jack_lion]

Honestly can't be sure just from reading this. I believe it works for everyone else if you follow along and it certainly works on my end. Maybe there is a chance you missed some patch details? I know it's quite a deep patch and it can be easy to miss something.

[@PLUXARIS]

@@jack_lion thanks for the reply. Turned out to be a bug on my end, restarting my Ableton fixed it!

[@blockletter]

I'm having a small issue with this patch. I followed the original tutorial, along with the revisions in this one. Whenever I load the patch in Ableton, I get the following in the console ""live.path: set path: invalid path" Apart from the error message, the device seems to function completely normally. I ended up buying your version of the patch to see where I went wrong, but yours also seems to trigger the same error. Any ideas? I'm running Live 11.3.21 & Max 8.5.6 on OSX 14.3

[@jack_lion]

I can’t be sure exactly what your issue is but most likely it is some typo or mismatched patching. Try and review the videos again

[@blockletter]

@@jack_lion Thanks for the quick reply. I downloaded your version from Gumroad and it is having the same issue. Just figured you might want to know. I also tested it on Live 11.3.1 on Windows 10, same issue. Either way, I appreciate the tutorials.

[@jack_lion]

@@blockletter Does the device still work when you try it? I know there are a few errors that appear in the console that can be safely ignored.

[@jack_lion]

I see that you mentioned that it works fine otherwise. If your concern is over potential side effects from the error it should be okay. I really appreciate the notice though! I believe it is some kind of patching logic deeper within the patch that isn't contributing to the actual functionality. If there are any functional issues then please let me know. But if it works then i'd say no need to worry about those errors my friend.

[@blockletter]

@@jack_lion Yeah, no issues at all with functionality luckily, so I’ll ignore it for now. Cheers

[@HalXu-j5r]

Hi Jack! Thank you for this great tutorial. I think I just spotted another little bug, the mapping still breaks when you move the mapper if the target device is on the other tracks. Do you have any idea how to solve it? Thank you.

[@jack_lion]

Not too sure as I haven’t returned to test this device since Live 12 has been released. I would recommend trying the new somewhat new max object live.map for parameter mappings now. Its supported by the max developers and is more stable than my implementation