Bitwig

Ghislain2b · Post by **Ghislain2b** » Tue Aug 07, 2018 4:04 am

Dear Moss,

I use your last driver with Komplete Keyboard Kontrol s61 mk2 and Bitwing 2.4 beta 2.

When the track volume is set to 0 in Bitwig, the keyboard display -2.2dB.
By the way, the sound level meter on the keyboard is higher than Bitwig.

Please, can you check.

Thanks a lot.

bM3w · Post by **bM3w** » Tue Aug 07, 2018 6:41 am

Hi Jürgen,

As mentioned in the YouTube comment section I can't get your extension to work with my NI Kontrol S49 MK I. I'm running Bitwig 2.4 Beta 2 on Windows 10 Pro x64 (1803/17134.191). Here's the error message from the script console as requested:

bsJ: Could not open device: Entity not found
pXN: bsJ: Could not open device: Entity not found
at TYA.EBr(SourceFile:737)
at TYA.LcL(SourceFile:160)
at TYA.<init>(SourceFile:127)
at Hyf.LcL(SourceFile:251)
at Hyf.QGb(SourceFile:343)
at Hyf.QGb(SourceFile:202)
at kob.run(SourceFile:91)
at Hyf.run(SourceFile:102)
Caused by: bsJ: Could not open device: Entity not found
at btY.LcL(SourceFile:148)
at com.bitwig.flt.control_surface.proxy.UsbDeviceImpl.open(SourceFile:66)
at TYA.EBr(SourceFile:733)
... 7 more

Any help is well appreciated.

Thanks!

moss · Post by **moss** » Tue Aug 07, 2018 7:47 am

bM3w wrote:As mentioned in the YouTube comment section I can't get your extension to work with my NI Kontrol S49 MK I. I'm running Bitwig 2.4 Beta 2 on Windows 10 Pro x64 (1803/17134.191). Here's the error message from the script console as requested:

The exception simply says that the device could not be found. Is this exception appearing directly when you add the extension or after you selected the device from the drop down list?

Did anyone here successfully use the extension with the S49, S61 or S88?

gmg16 · Post by **gmg16** » Tue Aug 07, 2018 2:14 pm

First, I just want to thank you for producing these great Bitwig controller integrations. I don't know how you do it. Respect!

I just wanted to report that the APC40 script is crashing immediately and with one hundred percent consistency. It works perfectly on my system with 2.3.5. Hopefully this can be easily fixed at some point in the not-too-distant future.

I am using:

2017 MacBook Pro running High Sierra.
Steinberg UR22 interface.
Akai APC40 (original)

killmaster · Post by **killmaster** » Tue Aug 07, 2018 2:45 pm

moss wrote:
bM3w wrote:As mentioned in the YouTube comment section I can't get your extension to work with my NI Kontrol S49 MK I. I'm running Bitwig 2.4 Beta 2 on Windows 10 Pro x64 (1803/17134.191). Here's the error message from the script console as requested:
The exception simply says that the device could not be found. Is this exception appearing directly when you add the extension or after you selected the device from the drop down list?

Did anyone here successfully use the extension with the S49, S61 or S88?

I tried this with my S61 (MK1) and the extension doesn't even show up as an extension in 2.3.5. Is this because it only gets detected in 2.4 now? Thanks for the amazing work!

moss · Post by **moss** » Tue Aug 07, 2018 6:02 pm

killmaster wrote: I tried this with my S61 (MK1) and the extension doesn't even show up as an extension in 2.3.5. Is this because it only gets detected in 2.4 now? Thanks for the amazing work!

The DrivenByMoss Beta versions require 2.4 Beta 2!
Did you try with 2.4?

moss · Post by **moss** » Tue Aug 07, 2018 6:05 pm

gmg16 wrote: I just wanted to report that the APC40 script is crashing immediately and with one hundred percent consistency. It works perfectly on my system with 2.3.5. Hopefully this can be easily fixed at some point in the not-too-distant future.

You need the Beta version of DrivenByMoss I posted above for 2.4 Beta 2.

bM3w · Post by **bM3w** » Tue Aug 07, 2018 7:50 pm

moss wrote:
bM3w wrote:As mentioned in the YouTube comment section I can't get your extension to work with my NI Kontrol S49 MK I. I'm running Bitwig 2.4 Beta 2 on Windows 10 Pro x64 (1803/17134.191). Here's the error message from the script console as requested:
The exception simply says that the device could not be found. Is this exception appearing directly when you add the extension or after you selected the device from the drop down list?

Did anyone here successfully use the extension with the S49, S61 or S88?

I get the error message right after I select the device from the drowpdown - with the option to click DISABLE or RESTART. Clicking on RESTART does nothing other than repeating the pop-up error message.

moss · Post by **moss** » Tue Aug 07, 2018 8:05 pm

bM3w wrote: I get the error message right after I select the device from the drowpdown - with the option to click DISABLE or RESTART. Clicking on RESTART does nothing other than repeating the pop-up error message.

Could you please run USB Tree View (https://www.uwe-sieber.de/usbtreeview_e.html) and send me (or post) the dump for the S49 (select it on the left and see the dump on the right)?

bM3w · Post by **bM3w** » Tue Aug 07, 2018 8:52 pm

moss wrote:
bM3w wrote: I get the error message right after I select the device from the drowpdown - with the option to click DISABLE or RESTART. Clicking on RESTART does nothing other than repeating the pop-up error message.
Could you please run USB Tree View (https://www.uwe-sieber.de/usbtreeview_e.html) and send me (or post) the dump for the S49 (select it on the left and see the dump on the right)?

Will do later tonight when I get home. Thanks in advance for your help!

killmaster · Post by **killmaster** » Tue Aug 07, 2018 9:09 pm

moss wrote:
killmaster wrote: I tried this with my S61 (MK1) and the extension doesn't even show up as an extension in 2.3.5. Is this because it only gets detected in 2.4 now? Thanks for the amazing work!
The DrivenByMoss Beta versions require 2.4 Beta 2!
Did you try with 2.4?

No, unfortunately, the demo is only 2.3.5. And I have that but haven't renewed yet.

bM3w · Post by **bM3w** » Wed Aug 08, 2018 1:53 am

bM3w wrote:
moss wrote:
bM3w wrote: I get the error message right after I select the device from the drowpdown - with the option to click DISABLE or RESTART. Clicking on RESTART does nothing other than repeating the pop-up error message.
Could you please run USB Tree View (https://www.uwe-sieber.de/usbtreeview_e.html) and send me (or post) the dump for the S49 (select it on the left and see the dump on the right)?
Will do later tonight when I get home. Thanks in advance for your help!

Problem solved!

An extension cable between the S49 Keyboard and my PC was to blame

moss · Post by **moss** » Wed Aug 08, 2018 6:52 am

bM3w wrote: Problem solved!

An extension cable between the S49 Keyboard and my PC was to blame

That's the best solution!

M-Prod · Post by **M-Prod** » Wed Aug 08, 2018 7:47 pm

moss wrote:Here is a little update, which fixes a NullPointerException with OSC:

http://mossgrabers.de/stuff/DrivenByMossBeta4.zip

If i install this version it does not show up in Bitwig. Am I doing something wrong?

strovoknights · Post by **strovoknights** » Wed Aug 08, 2018 9:56 pm

In my case.
I'm using Generic Flexi with self mapping for my MIDI Controller.
These mappings or settings sometimes broken with bitwig GUI.
I did try remove file in Extension folder.
after that,
I did click delete my controller in bitwig dashboard controller settings.
next,
retry install Driven,I did add to extension folder.
next,
I'm select flexi file and click import button, recovery success.
But if you don't have backup,recovery is difficult.

Bitwig

KVR Audio

DrivenByMoss: Bitwig extension for many hardware controllers (version 26.6.1)