Controller scripts breaking because dependencies (eg. ComponentJS) are not updated after version upgrade

[uriwilbury]

Controller scripts breaking because dependencies (eg. ComponentJS) are not updated after version upgrade

[pierrelegall]

Uncaught exception: file:///home/oriol/.mixxx/controllers/midi-components-0.0.js:139: TypeError: Cannot call method 'trigger' of undefined

The problem comes from midi-components-0.0.js. I suppose you copied it from Mixxx sources (and maybe changed it) as I did.

I've got the same problem upgrading to v2.4.0 with my K2. Just get the new version of it (and maybe recustomize it). You could find it there.

[Swiftb0y]

yes, alternatively if you delete the midi-components file from your ~./mixxx/ directory, mixxx will copy the appropriate version into that folder the next time you start it.

[ronso0]

In order to debug this we need the script file ; )
Please create a gist (or fork Mixxx and create a branch) and share a link here.

[uriwilbury]

Not sure if I did it right but there you go :)
https://gist.github.com/uriwilbury/4c66d2b5419b3c95030f38419bc99e77

[JoergAtGithub]

I guess it's the same as #13180 about the official K1/K2 mapping that comes with Mixxx.

[uriwilbury]

So it is a known bug with no solution yet, right?

Is there a way to go back to version 2.3.6 until it is fixed?

thanks

[Swiftb0y]

Can you try deleting the file ~/.mixxx/controllers/midi-components-0.0.js and try again?

[Swiftb0y]

Is there a way to go back to version 2.3.6 until it is fixed?

You can, it depends on your installation method, but it should be possible to downgrade packages using apt (your package manager on Mint I assume). I wouldn't recommend it though. It would get fixed much faster if you stay on 2.4 and properly help us to diagnose the issue.

[Swiftb0y]

I guess it's the same as #13180 about the official K1/K2 mapping that comes with Mixxx.

I doubt it. An exception due to accessing undefined is much less severe and easier to debug than a crash in QV4's memory code... The former is very likely not a related to the latter.

[uriwilbury]

I deleted the midi-components-0.0.js and now the controller is working!

I still got the following error after starting Mixxx with the controller and pushing a couple buttons:

Uncaught exception: file:///home/oriol/.mixxx/controllers/Allen-and-Heath-Xone-K2-scripts.js:121: TypeError: Cannot read property 'columns' of undefined
Backtrace: @file:///home/oriol/.mixxx/controllers/Allen-and-Heath-Xone-K2-scripts.js:121

This can be ignored though on the message error and the controller seems to still work.

I'll keep pushing buttons to see if there is any other issues.

thanks!

[Swiftb0y]

interesting, is that still the same script version as from the gist you posted? Because that code should only run on mapping shutdown.

[macrophone]

Same original issue here, I've renamed midi-components-0.0.js in .mixxx/ and now it seems working fine.
(note that there is no new midi-components-0.0.js in the .mixxx/ folder after reboot.)

[Holzhaus]

Yes, mixxx used to always copy mapping files to .mixxx unconditionally upon selecting it. We fixed that (in 2.3 IIRC), exactly because it does not make sense and leads to mappings not being updated and potentially locking people in with ancient mappings. I suppose the copy you had in that directly was a leftover from an older version before the fix.

[pierrelegall]

Yes, mixxx used to always copy mapping files to .mixxx unconditionally upon selecting it. We fixed that (in 2.3 IIRC), exactly because it does not make sense and leads to mappings not being updated and potentially locking people in with ancient mappings. I suppose the copy you had in that directly was a leftover from an older version before the fix.

Didn't know it was the previous behaviour. Much better like this 👍