Bitwig

moss · Post by **moss** » Fri Jul 27, 2018 5:07 am

JohannesTress wrote: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

You need to use also the DrivenByMoss Beta, which I posted some entries above.

svervs · Post by **svervs** » Sat Jul 28, 2018 7:58 pm

As always, thanks for the great work here ...

As it's pretty obvious, I'm sure it's already on your bug list, but just in case:
Group tracks don't pass their color to the Push (1), it's shown as grey.

pc999 · Post by **pc999** » Sat Jul 28, 2018 11:37 pm

I am not sure if I posted something like this before but this seems really cool!!

Any chance of getting this on Launchpad

This script for the original launchpad does have some thing like this and I use it a lot, but that launchpad is to limited

and I was thinking in upgrading. Anyway I am posting it here in case it can help you if you decide to implement it

http://www.kvraudio.com/forum/viewtopic ... d#p6151709

moss · Post by **moss** » Sun Jul 29, 2018 8:21 am

svervs wrote: Group tracks don't pass their color to the Push (1), it's shown as grey.

Hmm, it seems that the behaviour changed in 2.4. A group clip now displays ALL colors of the sub-track clips int its' right half. When you try to set a color for it, simply all sub-clips are colored. So, it seems a group clip does not have a color at all (that's why it is grey).

Question is now: What to do about it? Due to the hierachical navigation of the Push implementation I do not even have the information about the sub-clip colors. I guess I need to ask the Bitwig guys.

svervs · Post by **svervs** » Sun Jul 29, 2018 9:42 am

moss wrote:When you try to set a color for it, simply all sub-clips are colored. So, it seems a group clip does not have a color at all (that's why it is grey).

Yes, when a group scene is selected, the color option is just to color multiple clips at once.
Group scenes themselves don't have a color, like in 2.3.5

I think the problem may be with the new option to color master scenes in 2.4.
They don't pass the track color through as it did before.
When master scenes are set to diagonally-striped-"No color" option, they should pass the track color through, as they did until 2.3.5. (just because coloring was not possible)

svervs · Post by **svervs** » Sun Jul 29, 2018 9:47 am

double post

moss · Post by **moss** » Sun Jul 29, 2018 7:55 pm

More on the Beta-Train:
http://mossgrabers.de/stuff/DrivenByMossBeta2.zip

Again, check the change-lists on GitHub:
https://github.com/git-moss/DrivenByMoss/wiki

- Lot's of the extensions now support Cue-Markers.
- Push 1/2: Huge improvement of the clip/scene play mode.

Enjoy!

svervs · Post by **svervs** » Sun Jul 29, 2018 8:16 pm

You already fixed it ..!

Thanks. A. Lot. Boss. Moss.

turbo_kev · Post by **turbo_kev** » Sun Jul 29, 2018 9:01 pm

HI Moss

its your favorite NON musician here

Not sure if this is a bug so be gentle with me if im wrong

with the LPP in clip mode, if I select the master volume in the mixer
and then start a clip, it jumps to the first track , in fact its the same no matter what track I have selected, as soon as i start a clip it jumps to my first track

so for example I select master volume track , ready to turn it down if its to loud
then I start a clip , and bam it jumps to my first track, so I have to then re-click the master volume again to be able turn it down

I hope this makes sense to you
im using driven by moss beta 2
cheers
Kev

larsomat · Post by **larsomat** » Sun Jul 29, 2018 9:08 pm

You are awesome, Moss!

Thank you so much for your work.

strovoknights · Post by **strovoknights** » Mon Jul 30, 2018 12:30 am

Many Thanks!!

Octanone · Post by **Octanone** » Mon Jul 30, 2018 12:58 pm

hi jürgen

I updated bitwig 2.4 beta2 and installed your Beta 2 of DrivenByMoss extensions.

i have following error message.

Starting UDP server on port 7000.
Address already in use (Bind failed)
USB error 3: Unable to claim interface.: Access denied (insufficient permissions)

do you know what i am doing wrong?

PS: Before bitwig 2.4 beta everything worked fine with the push 2 and your extensions.

moss · Post by **moss** » Mon Jul 30, 2018 5:47 pm

Octanone wrote:hi jürgen

I updated bitwig 2.4 beta2 and installed your Beta 2 of DrivenByMoss extensions.

i have following error message.

Starting UDP server on port 7000.
Address already in use (Bind failed)
USB error 3: Unable to claim interface.: Access denied (insufficient permissions)

do you know what i am doing wrong?

PS: Before bitwig 2.4 beta everything worked fine with the push 2 and your extensions.

You do not need to run Push2Display anymore...

turbo_kev · Post by **turbo_kev** » Mon Jul 30, 2018 6:01 pm

Hi Moss
What about my problem. Is it a bug or am I making a mistake when using
the LPP

the jumping to the first tack happens even if I start the 2nd or 3rd
clip not just the first clip as shown in the video

cheers
Kev

moss · Post by **moss** » Mon Jul 30, 2018 6:14 pm

turbo_kev wrote: with the LPP in clip mode, if I select the master volume in the mixer
and then start a clip, it jumps to the first track , in fact its the same no matter what track I have selected, as soon as i start a clip it jumps to my first track

Turn off "Select clip on launch" in the LPP settings.

Bitwig

KVR Audio

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