JVM bitwig extension not showing in vendor list

Post Reply New Topic
RELATED
PRODUCTS

Post

I’m pulling my hair out right now. I’ve built a couple bitwig extensions in kotlin, I’ve had no problem getting the first two I wrote to show up in the list of vendors. I’m really enjoying the api bitwig provides. I’m working on a new extension for the midi fighter twister, and for some unknown reason I can’t get it to be detected by bitwig. The new extension when built is sitting directly next to my other two in the extensions folder bitwig watches. I verified the meta-inf has the expected configuration, and I generated a new guid several times just to be absolutely sure there wasn’t some kind of conflict. I’m on windows if that matters. Does anyone have any troubleshooting steps for why my extension would not show up in the vendor list when creating a new controller?

Post

Here is the PR I'm working on, if anyone is generous enough to take a peek at it.

https://github.com/whodevil/bitwig-exte ... ll/7/files

Post

I know that it is being deployed to the correct directory because I changed the vendor in my um-one extension, and the vendor updated in the vendor list in bitwig.

Post

I guess you forgot to change the UUID.

Post

I just double/triple checked the UUID.

For my um-one I have: "f8830c3e-8757-4a1f-8230-8f31e63b7570"
https://github.com/whodevil/bitwig-exte ... ion.kt#L11

For the twister I have: "d55aa17f-5317-4bb0-a8fe-65b81c41a168"

And for my Akai MPD I have "f9382f14-c30e-4c1a-9ee9-f79de8fa449a"
https://github.com/whodevil/bitwig-exte ... ion.kt#L11

Is there anything else that could potentially cause this situation?

Thanks for your help!

Post

You could remove the other extensions to be sure that it is not a collision.
Also check the Bitwig log file for a crash on instantiation of the extension.
Did you add it to the service file?

Post Reply

Return to “Controller Scripting”