Bitwig

nori.lam · Post by **nori.lam** » Wed Dec 03, 2014 9:03 pm

Hi guys,

Just got my Push and its amazing! Glad I returned the Trigger Finger Pro

I have a few questions that I hope someone can help with

1. In the drum sequencer mode with a native drum instrument, is there a way to scroll up and down the drum instrument banks using the touch strip (like how live has)? I tried but it seems its not working, nor does the octave up and down.

2. Is there a way to add a native device with the up down keys in push?

3. How can I launch clips in the clip view? I seem to be only able to record and play in the arranger view.

Finally, I think I have found a few bugs.
When I am in the drum sequencing mode, I can sequence some notes but when I go to remove the notes (by touching the pads that are blue in the sequence) sometimes the pads disables a different pad. For ex. If i select the first 4 vertical pads so they are blue, then select them one by one again to deactivate, pad 1 will deactivate normally, then pad 2 will deactivate pad 3 and pad 3 deactivates pad 4.

Edit - So it looks like the drum sequencer is a bit buggy in terms of showing the sequence timeline. Meaning the pads should turn green and move from left to right during playback, following the timeline. It was just working but now is not working anymore

Thanks so much for the script

and looking forward to more Push4Bitwig

moss · Post by **moss** » Wed Dec 03, 2014 9:24 pm

nori.lam wrote: Just got my Push and its amazing! Glad I returned the Trigger Finger Pro

I told you so

nori.lam wrote:1. In the drum sequencer mode with a native drum instrument, is there a way to scroll up and down the drum instrument banks using the touch strip (like how live has)? I tried but it seems its not working, nor does the octave up and down.

The API does not provide this functionality.

nori.lam wrote:2. Is there a way to add a native device with the up down keys in push?

Currently you can only add tracks but access to the browser is promised for an upcoming update.

nori.lam wrote:3. How can I launch clips in the clip view? I seem to be only able to record and play in the arranger view.

It might be a focus problem. Ensure that clip launcher panel is selected.

nori.lam wrote: When I am in the drum sequencing mode, I can sequence some notes but when I go to remove the notes (by touching the pads that are blue in the sequence) sometimes the pads disables a different pad. For ex. If i select the first 4 vertical pads so they are blue, then select them one by one again to deactivate, pad 1 will deactivate normally, then pad 2 will deactivate pad 3 and pad 3 deactivates pad 4.

Yes, this was introduced in 1.1. I already reported it to Bitwig.

nori.lam wrote: Edit - So it looks like the drum sequencer is a bit buggy in terms of showing the sequence timeline. Meaning the pads should turn green and move from left to right during playback, following the timeline. It was just working but now is not working anymore

No, idea here.

nori.lam wrote: Thanks so much for the script and looking forward to more Push4Bitwig

There will be

nori.lam · Post by **nori.lam** » Wed Dec 03, 2014 9:41 pm

moss wrote:
nori.lam wrote: Edit - So it looks like the drum sequencer is a bit buggy in terms of showing the sequence timeline. Meaning the pads should turn green and move from left to right during playback, following the timeline. It was just working but now is not working anymore
No, idea here.

If you have seen this behaviour before, should I send this in as a bug report do you think?

soundsandgear.com · Post by **soundsandgear.com** » Wed Dec 03, 2014 11:11 pm

Really cool script indeed, just messing around with it, very happy to see fixed length in there (favorite feature of Push for me)

I had a question about the count-in, is possible to have it start when using the new button? Or is that a current limitation of the Bitwig API?

moss · Post by **moss** » Thu Dec 04, 2014 9:50 am

soundsandgear.com wrote:Really cool script indeed, just messing around with it, very happy to see fixed length in there (favorite feature of Push for me)

I had a question about the count-in, is possible to have it start when using the new button? Or is that a current limitation of the Bitwig API?

I can only de-/activate the metronom via the API. So you should ask Bitwig support if this is a bug.

taoyoyo · Post by **taoyoyo** » Fri Dec 05, 2014 4:27 pm

Hi Moss,

Just installed the latest Github build... am liking where the Parameters/Devices pages are going.

I did have one question, is it possible to navigate through Devices directly from Push? (I can get to the first device on a track but can't work out how to move from say, an instrument, to an Effect after it).

Cheers,

Alan

nori.lam · Post by **nori.lam** » Fri Dec 05, 2014 4:57 pm

I dont think browse devices is in the API (I asked a similar question a few posts back).

Cyoon · Post by **Cyoon** » Fri Dec 05, 2014 5:03 pm

you can browse them on a track, but not in the browser and load it yet.

moss · Post by **moss** » Fri Dec 05, 2014 5:49 pm

taoyoyo wrote:I did have one question, is it possible to navigate through Devices directly from Push? (I can get to the first device on a track but can't work out how to move from say, an instrument, to an Effect after it).

The version on GitHub is currently in a work-in-progress state (that's why it says in BIG friendly letters "you have been warned"

).
I already changed the way how device banks are selected and also layer selection is working the same way. But I need 2 functions fixed from Bitwig before I can treat the device selection the same way. That's why there is currently no way to select devices from the Push.

taoyoyo · Post by **taoyoyo** » Fri Dec 05, 2014 6:34 pm

taoyoyo wrote:I did have one question, is it possible to navigate through Devices directly from Push? (I can get to the first device on a track but can't work out how to move from say, an instrument, to an Effect after it).

moss wrote:The version on GitHub is currently in a work-in-progress state (that's why it says in BIG friendly letters "you have been warned" ).

... I know, I was just intrigued to see what was going down.

(If I get scared I can always download the safe version).

moss wrote:I already changed the way how device banks are selected and also layer selection is working the same way. But I need 2 functions fixed from Bitwig before I can treat the device selection the same way. That's why there is currently no way to select devices from the Push.

... But it sounds like it's on the way though?

(I dig the 3 buttons for toggling parts of the Device from Push btw... show/hide Macros etc)

(and just discovered the Toggle Device GUI button too... this is fantastic!

stamp · Post by **stamp** » Tue Dec 09, 2014 10:26 am

Hi guys,
Great job with that script. Since I discovered your script I'm considering to switch to Bitwig!
But....I'm having problems when using Push (stable script) with my Virus TI. Seems like the push is sending some CC (or other type of data) when i hit certain notes. For sure some CC and then something else. It's changing parameters that don't have a corresponding CC,too (velocity mapping of the TI). D2 is the worse pad to play, lots of undesired data coming out. So my Virus gets crazy. I'm using the TI with its own vst (latest version) and I'm routing audio via USB.
Virus and Push are the only hardware connected. I tested with an empty project and init patch (no modulation)
I'm on windows 7 32bit. Integrated audio interface with asio4all.

Thanks for your help!

stamp · Post by **stamp** » Tue Dec 09, 2014 12:43 pm

I've also tried with the beta script. Same problem...

moss · Post by **moss** » Tue Dec 09, 2014 12:47 pm

It noticed that too. As a workaround set the channel input to "Ableton Push" instead of "All devices".
I need to investigate if this is a bug in Bitwig or my script. Might take some time because I do not have time before next week.

stamp · Post by **stamp** » Tue Dec 09, 2014 2:15 pm

Cool!
So I can go back to the beta script.
Thanks for the tip!

And again, thank you for this script!!

D1ofAquavibe · Post by **D1ofAquavibe** » Wed Dec 10, 2014 1:34 am

Hey there guys,
The Push4Bitwig script is fantastic, great job to the creators!
But I have one big issue though - lack of pad sensitivity control.
When used with Ableton, Push has a "PAD THRESHOLD" setting that you can adjust by using the "User" button, which allows you to increase the sensitivity of the pads so that you can play them like a regular keyboard. Without this ability, you have to slam the pads to make your notes articulate, which is very awkward and unnatural (maybe ok for drumming on the pads but not for playing melodies).

I LOVE Push and am really excited about Bitwig, but this one issue is keeping me from making the full leap over to Bitwig (and I'm bummed about it). I've been trying to research solutions to this topic on forums and google for a long while now but I'm really not getting anywhere (some suggest to just use the accent button to set a high fixed velocity setting, but then there will be zero performance dynamics).
Can someone please help with a solution, or maybe some information about this?

Thanks for reading.

Bitwig

KVR Audio

Ableton Push support is here