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

Post Reply New Topic
RELATED
PRODUCTS
Bitwig Studio 6$399.00Buy Maschine

Post

artsense wrote: Tue Dec 01, 2020 2:08 pm Everytime i start Ableton after Bitwig my Push2 going crazy with colors of pads and etc until Push2 restart
Yes same here. I restart the push 2 and all is good after :)

Post

zengel wrote: Tue Dec 01, 2020 7:18 pm
artsense wrote: Tue Dec 01, 2020 2:08 pm Everytime i start Ableton after Bitwig my Push2 going crazy with colors of pads and etc until Push2 restart
Yes same here. I restart the push 2 and all is good after :)
Simple solution: don't start Ableton :D :hihi:

Seriously, the problem is that Ableton changes the color palette from time to time, that's why I set my own now. Ableton on the other hand don't expect another app to change it, that's why you have to turn it off and on again.

Post

artsense wrote: Tue Dec 01, 2020 2:08 pm 1. Brightess of the LEDs is always on max after first start of Push. It show right numbers in Setup menu, but always on max untill i touch the LEDs knob
I cannot reproduce that. What is you OS? What are you doing exactly?

Post

Hi Moss and thanks for your impressive work.
I am new to Bitwig and trying to set up my various NI-MIDI-controllers in the best way possible. (M32, Jam & Maschine Mk3 Mikro). I am having an issue with the Komplete M32 receiving a memory error message related to the MIDI output parameters after installing the DBM extension in Bitwig as per your detailed documentation.
See attached screendump.

Bitwig 3.3, DBM 10.9.3 and Windows 10. Decent gaming PC-rig w/ 16GB RAM.

Thanks.
You do not have the required permissions to view the files attached to this post.

Post

Lugerfish wrote: Wed Dec 02, 2020 5:03 pm Hi Moss and thanks for your impressive work.
I am new to Bitwig and trying to set up my various NI-MIDI-controllers in the best way possible. (M32, Jam & Maschine Mk3 Mikro). I am having an issue with the Komplete M32 receiving a memory error message related to the MIDI output parameters after installing the DBM extension in Bitwig as per your detailed documentation.
See attached screendump.

Bitwig 3.3, DBM 10.9.3 and Windows 10. Decent gaming PC-rig w/ 16GB RAM.

Thanks.
This misleading error means that another application has already opened the port. Either this is caused by an application you ran before, which did not close the port properly (or crashed) or you are running another application at the same time which opened the port, also check for any MIDI utilities you might be running in the background. But first try a reboot and see if that fixes the issue.

Post

antic604 wrote: Tue Jul 07, 2020 8:58 am Hopefuly Presonus' new Atom SQ gets Moss' support:

Image

https://www.bhphotovideo.com/explora/pr ... -our-times
any news on this one? i was about to start a topic but then decided to search for it first...are there any people out there in bitwiggin bitwigland who have tried making a script of the presonus atom sq for bitwig? it would be damn nice...:)

Post

rumpelkind wrote: Wed Dec 02, 2020 9:31 pm
antic604 wrote: Tue Jul 07, 2020 8:58 am Hopefuly Presonus' new Atom SQ gets Moss' support:
any news on this one? i was about to start a topic but then decided to search for it first...are there any people out there in bitwiggin bitwigland who have tried making a script of the presonus atom sq for bitwig? it would be damn nice...:)
I am not sure if you can do much with it other than Studio One.

Post

moss wrote: Tue Dec 01, 2020 8:57 pm I cannot reproduce that. What is you OS? What are you doing exactly?
Windows 10.
1. Startup Push2
2. LEDs of pads are too bright
3. Setup button - LEDs 45% but they still too bright
4. Move the LEDs knob a little (to 44% as example) and LEDs becomes less less brighter (as i need)
5. So everytime i start Push2 LEDs works on the max bright, but digits in setup shows last saved change

Post

artsense wrote: Thu Dec 03, 2020 6:30 am
moss wrote: Tue Dec 01, 2020 8:57 pm I cannot reproduce that. What is you OS? What are you doing exactly?
Windows 10.
1. Startup Push2
2. LEDs of pads are too bright
3. Setup button - LEDs 45% but they still too bright
4. Move the LEDs knob a little (to 44% as example) and LEDs becomes less less brighter (as i need)
5. So everytime i start Push2 LEDs works on the max bright, but digits in setup shows last saved change
Could it be that it is off by 1? Have tried with e.g. 20%?

Post

moss wrote: Thu Dec 03, 2020 12:40 pm Could it be that it is off by 1? Have tried with e.g. 20%?
it doesn't matter on how much i set it in Setup.
evety time when i switch off Push2 and start it again brightness of pads is on maximum.

try to set LEDs on 20% or 30%
then restart Push2
you will notice PADs are so bright (like on 100%)
than u go to setup again - little move of LEDs knob and the brightness will move back to the saved position

Post

artsense wrote: Thu Dec 03, 2020 1:07 pm try to set LEDs on 20% or 30%
then restart Push2
you will notice PADs are so bright (like on 100%)
than u go to setup again - little move of LEDs knob and the brightness will move back to the saved position
So, it happens when you turn off/on the Push not restarting Bitwig?
Again, what is your OS? Mac?

Post

moss wrote: Thu Dec 03, 2020 2:43 pm
artsense wrote: Thu Dec 03, 2020 1:07 pm try to set LEDs on 20% or 30%
then restart Push2
you will notice PADs are so bright (like on 100%)
than u go to setup again - little move of LEDs knob and the brightness will move back to the saved position
So, it happens when you turn off/on the Push not restarting Bitwig?
Again, what is your OS? Mac?
Windows 10.
Only when i turn off/on the Push

Post

p.s. found another bug.. hope it possible to fix. because it's really breaks the workflow.

how to reproduce it:
1. you need to add more than 8 Instrument Tracks (i added 11 Polysynths)
2. then you just move from channel to channel from up to down..
and look on push.
3. then you go from down to up. and still look on push.
4. you will notice that when you go from track 9 to 8 trackselection is broken.. LEDs on push are not works, you can't play.
5. same if you just click on track 11 and then to track 8.

here is a little video: https://www.dropbox.com/s/1z9xl6kgkxhh9 ... 3.mov?dl=0

Post

moss wrote: Wed Dec 02, 2020 10:28 pm
rumpelkind wrote: Wed Dec 02, 2020 9:31 pm
antic604 wrote: Tue Jul 07, 2020 8:58 am Hopefuly Presonus' new Atom SQ gets Moss' support:
any news on this one? i was about to start a topic but then decided to search for it first...are there any people out there in bitwiggin bitwigland who have tried making a script of the presonus atom sq for bitwig? it would be damn nice...:)
I am not sure if you can do much with it other than Studio One.
sorry for being a total noob when it comes to scripts etc. but does that mean, that one would get the same functionality bitwig as in studio one or the ableton support of the controller? wouldn it be possible to somehow transfer the ableton-features to bitwig? just asking ;) thank you btw for responding and for all the work you do for the community, moss :hug: :party:

Post

artsense wrote: Thu Dec 03, 2020 3:39 pm here is a little video: https://www.dropbox.com/s/1z9xl6kgkxhh9 ... 3.mov?dl=0
Both work fine for me. It goes off as well on my PC but only for 1 second and then is on again. This is not surprising since there is a little delay implemented to wait till the bank page has changed before the track is selected.
Is your PC exceptionally fast or slow? What are your hardware specs? Seems like there is an issue somehow with timing.

Post Reply

Return to “Controller Scripting”