Support for Novation Launchpad Pro and Launchpad MkII is here

[submeditation]

thanks for your fast reply . I`ve found it. But i have a little problem here. When i change one single bit of code in your script, Bitwig (1.3.15) doesen`t seem to recognize it anymore. (Launchpad Pro doesen`t appear in the controller menue as selection anymore). Is this an error or am i doing something wrong ?

If it does not appear you made a serious programming error. Look in the script console, which should display it.

Hi moss, thank you i`ve found it ! it was my fault... i was using notepad to make changes. When i saved the script it converted the textformat now i`m using visual studio code to make changes and now it`s working. it`s all good ! thanks for your support

cheers
Carsten

[submeditation]

Hello Moss, i`ve just testet with the Launchpad Pro together with Bitwig 2.0 Beta 1 and got following error :
"LaunchpadPro4Bitwig did something wrong, Parameter offset must be >=0"
Can you fix this ?

Cheers
Carsten

[moss]

Hello Moss, i`ve just testet with the Launchpad Pro together with Bitwig 2.0 Beta 1 and got following error :
"LaunchpadPro4Bitwig did something wrong, Parameter offset must be >=0"
Can you fix this ?

Cheers
Carsten

Beta compatible version is in the works. Watch this space.

[submeditation]

thank you. that`s great news !

[moss]

WARNING:
I just pushed the latest code to GitHub which now supports the new v2 API.
https://github.com/git-moss/LaunchpadPro4Bitwig

This version is NOT compatible with 1.3.x! If you are on the Beta list feel free to give it a try.

There are still some regressions in the API, which are documented here: https://github.com/teotigraphix/Framewo ... regression

So please look there first before reporting bugs.

[incubus]

Well, I'm only 1.3.x so..................

So far it (for the aforementioned ) is fine.

[submeditation]

WARNING:
I just pushed the latest code to GitHub which now supports the new v2 API.
https://github.com/git-moss/LaunchpadPro4Bitwig

This version is NOT compatible with 1.3.x! If you are on the Beta list feel free to give it a try.

There are still some regressions in the API, which are documented here: https://github.com/teotigraphix/Framewo ... regression

So please look there first before reporting bugs.

Yeah thank you moss !

[incubus]

n/m, I forgot it's not ok for me to post potential issues.

[Netsu]

Is the plan to keep the script backward compatible with Bitwig 1?

[moss]

Is the plan to keep the script backward compatible with Bitwig 1?

New developments will target v2. However, the v1 compatible version will still be available. I also created a release on GitHub for the 1.3.15 compatible version.

[vincenzoml]

Hi,

thanks for your script! And in this thread I learned about quite some interesting features that I'm looking forward to try.

I am using bw 1.3.16 (rc), but the script has some nasty bug. After just some tests, the launchpad went in "note mode" by default, and now it does that all the time, I have to change the mode on the LP after starting bitwig. And the worst, faders don't work at all since this happened. I also tried removing and adding the controller again. I saw another user with similar problems in this thread but no reply, and he at some point said he reinstalled bw to get rid of the problem. No I won't delete my bw configuration directory

[moss]

I am using bw 1.3.16 (rc), but the script has some nasty bug. After just some tests, the launchpad went in "note mode" by default, and now it does that all the time, I have to change the mode on the LP after starting bitwig. And the worst, faders don't work at all since this happened. I also tried removing and adding the controller again. I saw another user with similar problems in this thread but no reply, and he at some point said he reinstalled bw to get rid of the problem. No I won't delete my bw configuration directory

I get the impression the those Launchpads sometimes have a life of their own :-/ Do you use it also with Ableton or only Bitwig?
I just had the strange effect that I have to hit the faders in send mode very hard while they work fine in other modes (and the code is absolutely the same).

I am currently in Bitwig v2 testing and script adjustments I can do some further research after that.

[vincenzoml]

I only use bitwig, and only on linux. I could as well backport bugfixes for the bitwig1 version of the script until I will buy v2

[vincenzoml]

Also the "new drum modes" since v 1.11 don't work: if I select one of the other two, the grid becomes empty and seems to keep sequencing somehow. How can I tell which version of the controller script I have?

[submeditation]

WARNING:
I just pushed the latest code to GitHub which now supports the new v2 API.
https://github.com/git-moss/LaunchpadPro4Bitwig

This version is NOT compatible with 1.3.x! If you are on the Beta list feel free to give it a try.

There are still some regressions in the API, which are documented here: https://github.com/teotigraphix/Framewo ... regression

So please look there first before reporting bugs.

Hi Moss,
I`m not sure if this is in the list. The error sometimes appears in Bitwig Beta 3 when i`m using drum mode :

"Launchpadpro4 Bitwig" crashed
TypeError:this.clip.getLoopStart().setRaw is not a function

Ok to report this here or should i post this in the Beta Group ?

Cheers
Carsten