Bitwig

moss · Post by **moss** » Sun Sep 06, 2015 6:41 am

TristanMendoza wrote:Any new scrips we can test Moss? I have a three day weekend!

The version on GitHub is now compatible with Beta 7. Also see the Changes list on the Wiki.
Open Bitwig bugs related to the script are documented here: https://github.com/teotigraphix/Framework4Bitwig/issues
Please check before reporting duplicated items.

fluxmachina · Post by **fluxmachina** » Sun Sep 06, 2015 11:14 am

Added Volume Fader Control of current track as a ribbon option.

Thank you very much!

codec17 · Post by **codec17** » Sun Sep 06, 2015 3:14 pm

moss wrote:
codec17 wrote:Heeeello! push4bitwig users!

I ran in this "problem" a couple of times now.
When i use a drummachine and put a sample on one of the pads sometimes push OR?? bitwig shifts the notenumbers or pads by 4(or one row)
As you can see on the picture where i put my finger on the second row of the pads it will play the sound.DUH..
(but as you can see on the push the first pad is indicating blue.)
As you can see on the drummaschine it shifts the bleu pad selection 1 row up...
I tried to save the project and duplicate the track to see if it solves the problem. but didnt help and didnt find a solution. Did somebody ran into this "problem" as well?

I dont know if i should report it to bitwig or maybe its a well know bug maybe?
It's a hard to catch Bitwig bug: Sometimes the source midi coming from the Push is also send to Bitwig, not only the transformed midi data. The workaround is to set the input channel from "All" to only Push.
If you find a way to replicate this please send to Bitwig, so they can fix it!

Yes !!!!! They fixed this one!!! Sorry but not very important post but forr me this is a BIG one!

moss · Post by **moss** » Sun Sep 06, 2015 7:08 pm

codec17 wrote:
moss wrote: It's a hard to catch Bitwig bug: Sometimes the source midi coming from the Push is also send to Bitwig, not only the transformed midi data. The workaround is to set the input channel from "All" to only Push.
If you find a way to replicate this please send to Bitwig, so they can fix it!

Yes !!!!! They fixed this one!!! Sorry but not very important post but forr me this is a BIG one!

In Beta 8? I just had it several times with Beta 7.

codec17 · Post by **codec17** » Sun Sep 06, 2015 7:52 pm

huh? weird.. because when i (with 1.1) didnt began filling the drumMaschine with c1 it was messed up, now i can drag it everywhere and move around with samples no matter what.. the color coding keeps following etc.
That with the beta for 1.2 from github that is.
Only pianoroll cant keep it up with the names...
(maybe im talking about something totally different

, because internal coding or things under the hood, am a total NOOB.)

So i think it is "solved" for my visual needs? i dont know. But im more then confinced your RIGHT that it,s still there.
Sorry for my enthusiasm when it didnt been fixed..

mrfrenkie · Post by **mrfrenkie** » Tue Sep 08, 2015 5:07 pm

It seems the new fader mode has no observer

moss · Post by **moss** » Wed Sep 09, 2015 5:44 pm

mrfrenkie wrote:It seems the new fader mode has no observer

What do you mean?

mrfrenkie · Post by **mrfrenkie** » Wed Sep 09, 2015 7:49 pm

moss wrote:
mrfrenkie wrote:It seems the new fader mode has no observer
What do you mean?

The current value is not updated when you switch to another track. Without it new fader mode does not make sense.

moss · Post by **moss** » Wed Sep 09, 2015 7:56 pm

mrfrenkie wrote:
moss wrote:
mrfrenkie wrote:It seems the new fader mode has no observer
What do you mean?
The current value is not updated when you switch to another track. Without it new fader mode does not make sense.

It's updated fine here. Are you running 1.2 Beta 7? If yes, please tell me step-by-step what you are doing.

mrfrenkie · Post by **mrfrenkie** » Wed Sep 09, 2015 8:58 pm

Of course i use Beta 7 and your latest script update from today.

moss · Post by **moss** » Thu Sep 10, 2015 6:55 am

mrfrenkie wrote:Of course i use Beta 7 and your latest script update from today.

I only tested in Track mode, maybe there's a problem in Volume mode. Will check but won't have time before the weekend.

mrfrenkie · Post by **mrfrenkie** » Thu Sep 10, 2015 11:58 am

moss wrote: I only tested in Track mode, maybe there's a problem in Volume mode. Will check but won't have time before the weekend.

In Volume Mode i get same problem.

svervs · Post by **svervs** » Fri Sep 11, 2015 1:17 pm

In Beta7 the "Device on" parameter shows up on the Macros page. Is this known? A betabug?

Thanks for the work and effort that already went into this script!

moss · Post by **moss** » Sat Sep 12, 2015 6:54 pm

mrfrenkie wrote:
moss wrote: I only tested in Track mode, maybe there's a problem in Volume mode. Will check but won't have time before the weekend.
In Volume Mode i get same problem.

I cannot reproduce that. Can you give me a step-by-step example or send me a project where that happens?

moss · Post by **moss** » Sat Sep 12, 2015 6:56 pm

svervs wrote:In Beta7 the "Device on" parameter shows up on the Macros page. Is this known? A betabug?

I guess you mean the Direct mode? Bitwig told me it is intentional but I do not like it either.

Bitwig

KVR Audio

Ableton Push support is here