AndyTheDude Posted November 17, 2023 Share Posted November 17, 2023 I am getting a C++ error every time I click on midi learn button and then Ableton crashes. Screenshot attached. Can anyone check if it's the same for them before I open a support ticket? To duplicate: open Native 3.70 and click on the midi learn button right next to "MIDI In" slider in Automation pane. Quote Link to comment Share on other sites More sharing options...
TadekTadek1111 Posted December 12, 2023 Share Posted December 12, 2023 I am having the same problem. 3.70 native, both on Ableton and Logic Pro. Logic says that the plugin is at fault... Quote Link to comment Share on other sites More sharing options...
craiganderton Posted December 16, 2023 Share Posted December 16, 2023 I'm having the same problem with Studio One 6.5. If you know the MIDI Controller number and you specify it under the Controller Assign function without using MIDI Learn, then it works. It seems the problem happens as soon as you click on MIDI Learn. At least in Studio One, sometimes it's easier to choose a Knob as automation, and then assign the controller (e.g., footpedal) to the knob. Quote Link to comment Share on other sites More sharing options...
randychesbro Posted January 1 Share Posted January 1 Im using LogicPro on Mac Studio m1 OS Sinoma. and 2.70 Helix Native. As soon as I click the midi learn button the Helix Native goes bye bye.. Can't find any info on it so fare. Quote Link to comment Share on other sites More sharing options...
JeffersteinVS Posted January 17 Share Posted January 17 Same issue here with 3.71 and cubase 13. It happens when you go to midi assign page and remove a assignment. after that the preset bugs out. Quote Link to comment Share on other sites More sharing options...
datacommando Posted January 17 Share Posted January 17 On 1/17/2024 at 3:29 AM, JeffersteinVS said: Same issue here with 3.71 and cubase 13. It happens when you go to midi assign page and remove a assignment. after that the preset bugs out. Hi, As your screenshot seem to indicate the exact same error as the one provided by the OP, I would suggest that you raise a ticket with Customer Support. The OP says he contacted Support, but then he never reported back here with any solution, or let others know what he was told. If you do contact Support, please report back here - it may assist other users, but it will also make CS aware there is an issue that needs to be resolved. Hope this helps/makes sense. Quote Link to comment Share on other sites More sharing options...
AndyTheDude Posted February 22 Author Share Posted February 22 I have raised a ticket with customer support. They were able to replicate the error and passed it on to the coding team to get it fixed with the next update. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.