Bitwig

yassinex · Post by **yassinex** » Tue Jul 24, 2018 1:10 pm

Hi Moss,

Thanks for your new beta.
Just tested. My initial feedback.
- Push 2 seems is detected (appearing) automatically in the setting page when you connect the device thru USB. You click on Add...and done... Works great !

- Komplete MK2 device, are not detected the same way ( No USB code implementation for MK2 ? ). You need to add it manually, and then select the ports... it works, but in midi mode. No meters display...and nothing else. Just keys, play stop as a basic midi controller/

Thanks for the fixes !

aMUSEd · Post by **aMUSEd** » Tue Jul 24, 2018 4:29 pm

yassinex wrote: - Komplete MK2 device, are not detected the same way ( No USB code implementation for MK2 ? ). You need to add it manually, and then select the ports... it works, but in midi mode. No meters display...and nothing else. Just keys, play stop as a basic midi controller/

That all worked in the previous build - can't test this one yet as don't have 2.4

distomen · Post by **distomen** » Tue Jul 24, 2018 7:21 pm

Hi, thank you very much for this script. He improved my workflow very much.
Funkcion device: scroll parameter banks not working.

yassinex · Post by **yassinex** » Tue Jul 24, 2018 7:27 pm

aMUSEd wrote: That all worked in the previous build - can't test this one yet as don't have 2.4

Indeed, but no more now with BW 2.4 + Moss beta extension.

moss · Post by **moss** » Tue Jul 24, 2018 8:03 pm

yassinex wrote: - Komplete MK2 device, are not detected the same way ( No USB code implementation for MK2 ? ). You need to add it manually, and then select the ports... it works, but in midi mode. No meters display...and nothing else. Just keys, play stop as a basic midi controller/

The Mk II solution cannot be automatically detected since it communicates via OSC with the Native Instruments Hardware service, which needs to be running in the background.

I guess you selected the wrong script, since mine has only 1 input port.

See my tutorial video here: https://www.youtube.com/watch?v=P_ITpKDPCVk

strovoknights · Post by **strovoknights** » Wed Jul 25, 2018 11:54 am

Edit:delete

llze · Post by **llze** » Wed Jul 25, 2018 12:02 pm

And what is your question?

strovoknights · Post by **strovoknights** » Wed Jul 25, 2018 12:08 pm

EDIT:sorry delete

strovoknights · Post by **strovoknights** » Wed Jul 25, 2018 8:53 pm

Edit:sorry all delete

strovoknights · Post by **strovoknights** » Wed Jul 25, 2018 9:13 pm

.maki wrote:And what is your question?

I can't use Maschine for operation Bitwig,because Maschine4Bitwig development is stoping
But I did using FlexiDriven, I can operate Bitwig with Maschine Studio.
The touch sensitivity of the eight knobs is also active.
Since I finished mapping I thought about sharing, but posting here was my bad. I'm sorry.

llze · Post by **llze** » Thu Jul 26, 2018 4:37 am

strovoknights wrote:
.maki wrote:And what is your question?
Since I finished mapping I thought about sharing, but posting here was my bad. I'm sorry.

No worries, was just wondering because your intention wasn't clear to me. Good job!

yassinex · Post by **yassinex** » Thu Jul 26, 2018 8:02 am

moss wrote: The Mk II solution cannot be automatically detected since it communicates via OSC with the Native Instruments Hardware service, which needs to be running in the background.

I guess you selected the wrong script, since mine has only 1 input port.

No I selected the right script (I just made a typo in my last comment writing inputS instead or input)

Ok I understand the script uses OSC and not USB.

Still even selecting the right script, using the right port (I tried KK MK2 DAW port, then MK2 Port 1 does not help either) only basic Midi, no screen fonctionalities as in the last version.

Did you guys have the same issues ?

Btw, am using BW 2.4 Beta 1 with Moss Beta1 (one file extension). No other extension or file in the BW extension’s folder. Push2 runs at the same time just fine, without the java application anymore (thx Moss).

Best,

moss · Post by **moss** » Thu Jul 26, 2018 12:17 pm

yassinex wrote: Still even selecting the right script, using the right port (I tried KK MK2 DAW port, then MK2 Port 1 does not help either) only basic Midi, no screen fonctionalities as in the last version.

Did you guys have the same issues ?

Btw, am using BW 2.4 Beta 1 with Moss Beta1 (one file extension). No other extension or file in the BW extension’s folder. Push2 runs at the same time just fine, without the java application anymore (thx Moss).

Best,

Works fine here. Did you check the Script Console if there is an exception there? It should also log that it did connect to the NI hardware service.

JohannesTress · Post by **JohannesTress** » Thu Jul 26, 2018 9:16 pm

Hi there, I'm struggling with the osc4bitwig script and 2.4beta1. Everytime I try to assign the script to a virtual midi port in the dropdown menu I get this message:

Screenshot_20180726_231200.png

I'm running Linux (KDE Neon).

yassinex · Post by **yassinex** » Fri Jul 27, 2018 3:05 am

moss wrote: Works fine here. Did you check the Script Console if there is an exception there? It should also log that it did connect to the NI hardware service.

Ok, if it works at your side, it should be an issue with my configuration then.
Unfortunately, I can’t test anymore for the next couple of weeks, am traveling atm for holidays.
If anyone else can do the test and confirm in the meantime, that would be great !

Best,

Bitwig

KVR Audio

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