Chameleon Midi input not working anymore on in Ableton

mnoukens@gmail.com

📁 Original board: Chameleon › Troubleshooting, tips and tricks

Hi,

After W11 update yesterday the Midi input of chameleon is not working anymore in ableton.

The entry in de midi config of ableton is red.

Let me know what the do

It is urgent because i have gig tomorrow

Please who can help me ?

Kind regards,

PabloMartin

Hello Marc
In critical environments, such as a PC you use for your performances, you should keep updates set to manual and instead force the update manually, for example, on Mondays.Or at least configure it so that it only updates on a Monday, ensuring that if something goes wrong, you have enough time to fix any issues.

Regarding this case, I couldn’t tell you what’s happening until we can investigate directly on your PC, as this is not a widely reported error.As a possible solution, back up your templates and their TSI files, then uninstall Chameleon, followed by uninstalling BOME MIDI.Next, reinstall same version of Chameleon you are using.This will likely solve the problem, but I can’t confirm it.If it doesn’t work, you can try rolling back the Windows update to restore it to the previous state. Always make sure to back up before doing this.
Let me know if works.

PabloMartin

Hello, I mark now that issue as solved.

mnoukens@gmail.com

Hi,

Sorry for this very late reaction …

I didn’t get a notification of a response on this forum item.

Today I had the same problem and now I’m sure I found the route case for it and therefore also the solution. Let me share this information with community.

So the problem is/was that Ableton market the midi in port of chameleon in red.

Which means a number of things such as no connection, driver issue, no signal and conflict with another midi device.

In my case it was a conflict with another midi device ….

I had still web page open, Yamaha soundmondo which uses a midi plugin to transfer data to a Yamaha keyboard. Even when it is not connect to a keyboard this web page occupies the midi port and gives a conflict with Ableton.

So after closing this web page this issue was solved.

Normally a restart should solve the problem …. Not in my case because a restart in my case will automatically open all the webpages again that I had in use. So automatically this web page occupies the midi port

Hopefully this information is helpful for others….