Bitwig

goatgirl · Post by **goatgirl** » Tue Jun 16, 2015 9:00 pm

Do enhancements go here or on guthib?

Anyway, I have a usability enhancement that I would like to be concidered. At the moment when you move an encoder, Bitwig will show an info box on screen with the parameter and its value.

As some of the parameter names becomes rather cryptic, perhaps it would be usefull to have the info box displayed when you touch the encoder. That way you can see the full parameter name and value without having to move the encoder.

Thanks.

TeotiGraphix · Post by **TeotiGraphix** » Tue Jun 16, 2015 9:06 pm

GitHub always. Moss can keep a consistent eye on it and he gets notified instantly when you add issues, like when you added yours, I got a gmail email.

Besides, Moss has this thing where he has OCD and has to only have that 1 issue in the queue(the collection one), so go for it.

Mike

goatgirl · Post by **goatgirl** » Tue Jun 16, 2015 9:12 pm

Thank you again Mike, I will post it in its righfull place.

codec17 · Post by **codec17** » Wed Jun 17, 2015 4:13 pm

cedrelo wrote:Hi Moss

There is a big issue with Rob Papen Punch plugin, Push with PUSH4BITWIG is unusable and bigwig have high CPU peak as soon as i click on Device button.

Thanks

Cedre

I had the same with Xfer serum.. it totally crashes. But after i set push in preferences on channel aftertouch it was all good.
(i dont really think its related becaue its a drummaschine) but worth a shot.

moss · Post by **moss** » Thu Jun 18, 2015 6:54 am

codec17 wrote:
cedrelo wrote:Hi Moss

There is a big issue with Rob Papen Punch plugin, Push with PUSH4BITWIG is unusable and bigwig have high CPU peak as soon as i click on Device button.

Thanks

Cedre
I had the same with Xfer serum.. it totally crashes. But after i set push in preferences on channel aftertouch it was all good.
(i dont really think its related becaue its a drummaschine) but worth a shot.

Please report to Bitwig. I have no influence in the script on special VST behaviours.

Uplay · Post by **Uplay** » Sun Jun 21, 2015 2:38 pm

As for Arpeggiator FX, the Octaves parameter can only move between 1 oct and 2 oct in Device Direct mode by Push knob. I can increase the value up to 4 oct from Bigwig GUI though.

-Repro step:
1) Open a new project in Bitwig
2) Insert Arpegiattor FX to Inst track. Choose "4 Octave Playa" preset in Arpegiator.
3) Insert Polysynth after Arpeggiator FX.
4) Record long tone in a clip, play it (loop it).
5) On Push, press Device button and choose Direct.
6) Ensure you select Arpeggiator and move the Octaves knob. The value is jumping around.

- Environment:
Bitwig 1.1.8
Mac OS X 10.10.3
Push4Bitwig 4.4

moss · Post by **moss** » Sun Jun 21, 2015 3:19 pm

Uplay wrote:As for Arpeggiator FX, the Octaves parameter can only move between 1 oct and 2 oct in Device Direct mode by Push knob. I can increase the value up to 4 oct from Bigwig GUI though.

-Repro step:
1) Open a new project in Bitwig
2) Insert Arpegiattor FX to Inst track. Choose "4 Octave Playa" preset in Arpegiator.
3) Insert Polysynth after Arpeggiator FX.
4) Record long tone in a clip, play it (loop it).
5) On Push, press Device button and choose Direct.
6) Ensure you select Arpeggiator and move the Octaves knob. The value is jumping around.

- Environment:
Bitwig 1.1.8
Mac OS X 10.10.3
Push4Bitwig 4.4

Sounds like a Bitwig issue. Please send to Bitwig support.

Uplay · Post by **Uplay** » Sun Jun 21, 2015 9:23 pm

moss wrote:
Uplay wrote:As for Arpeggiator FX, the Octaves parameter can only move between 1 oct and 2 oct in Device Direct mode by Push knob. I can increase the value up to 4 oct from Bigwig GUI though.

-Repro step:
1) Open a new project in Bitwig
2) Insert Arpegiattor FX to Inst track. Choose "4 Octave Playa" preset in Arpegiator.
3) Insert Polysynth after Arpeggiator FX.
4) Record long tone in a clip, play it (loop it).
5) On Push, press Device button and choose Direct.
6) Ensure you select Arpeggiator and move the Octaves knob. The value is jumping around.

- Environment:
Bitwig 1.1.8
Mac OS X 10.10.3
Push4Bitwig 4.4
Sounds like a Bitwig issue. Please send to Bitwig support.

Done. Thanks for your prompt reply Moss!

goatgirl · Post by **goatgirl** » Tue Jun 23, 2015 7:36 pm

Well Mister Moss...

After playing with the 1.2 script, I have three words to say to you 'Default Device Mode'

Bloomin marvelous, very well done, thank you

moss · Post by **moss** » Wed Jun 24, 2015 6:42 am

goatgirl wrote:Well Mister Moss...

After playing with the 1.2 script, I have three words to say to you 'Default Device Mode'

Bloomin marvelous, very well done, thank you

You are welcome

TeotiGraphix · Post by **TeotiGraphix** » Wed Jun 24, 2015 10:34 am

goatgirl wrote:Well Mister Moss...

After playing with the 1.2 script, I have three words to say to you 'Default Device Mode'

Bloomin marvelous, very well done, thank you

I count 7 words.

codec17 · Post by **codec17** » Wed Jun 24, 2015 11:43 am

goatgirl wrote:Well Mister Moss...

After playing with the 1.2 script, I have three words to say to you 'Default Device Mode'

Bloomin marvelous, very well done, thank you

Now i really cant wait to give 1.2 a testrun....

Funky puuuuush .... funky PUSH!!

goatgirl · Post by **goatgirl** » Wed Jun 24, 2015 1:19 pm

TeotiGraphix wrote: I count 7 words.

Well, we use the metric system over here

codec17 · Post by **codec17** » Sat Jun 27, 2015 5:10 pm

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?

I hope im clear

because really dont know how to clarify it better...

If not i try it again..

Besides that i have a lot of fun with this script,

moss · Post by **moss** » Sat Jun 27, 2015 7:10 pm

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!

Bitwig

KVR Audio

Ableton Push support is here