Ableton Push support is here

[_jon]

Thank you SO MUCH to moss and Mike (and whoever else I'm unaware of) for working on this script. This has helped me tremendously in my full conversion to Bitwig and it's amazing what you have accomplished in functionality so far.

I too would love to have a PAD THRESHOLD / SENSITIVITY CONTROL available like in the Ableton version accessible by holding down the "User" button. Velocity curves would be cool too, but much more importantly just a global adjustable threshold setting would resolve the main issue I'm having, which is the lack of fine control in note mote (or drum mode), having to really smash hard to get proper notes and chords out or to sustain.

Another question, I'm sure you guys are familiar with Stray (NativeKontrol) and his PXT ecosystem - I am fairly certain he is working on some kind of PXT-BWS implementation. Have you considered collaborating with him, combining projects? Apologies if this topic has already been addressed but may make sense to unify the parallel development!

[moss]

I too would love to have a PAD THRESHOLD / SENSITIVITY CONTROL available like in the Ableton version accessible by holding down the "User" button. Velocity curves would be cool too, but much more importantly just a global adjustable threshold setting would resolve the main issue I'm having, which is the lack of fine control in note mote (or drum mode), having to really smash hard to get proper notes and chords out or to sustain.

It never appeared to me as a problem that's why I did not address it so far (everything OK with your Push hardwarwe?). I put your request on the wishlist but it will require some research what are the possibilities in that area first.

Another question, I'm sure you guys are familiar with Stray (NativeKontrol) and his PXT ecosystem - I am fairly certain he is working on some kind of PXT-BWS implementation.

I don't think so. I heard about his interest too but that's about it.

[soundsandgear.com]

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.

Thanks for the reply, I appreciate it. The count-in seems to work for normal record, though sometimes it doesn't, but not if I press the "new" button to start a new clip. I use this button a lot due to wanting to use the fixed length optiion

I also noticed I can't initial a new clip to record into by hitting the clip buttons, is this also an issue with the api? Am I required to have a clip in there first before I can record into it?

For comparison, I tried one of the available touch osc templates and pressing a new clip starts the count-in, of course there is no actual "new clip" button like on Push.

Thanks!

[_jon]

I too would love to have a PAD THRESHOLD / SENSITIVITY CONTROL available like in the Ableton version accessible by holding down the "User" button. Velocity curves would be cool too, but much more importantly just a global adjustable threshold setting would resolve the main issue I'm having, which is the lack of fine control in note mote (or drum mode), having to really smash hard to get proper notes and chords out or to sustain.

It never appeared to me as a problem that's why I did not address it so far (everything OK with your Push hardwarwe?). I put your request on the wishlist but it will require some research what are the possibilities in that area first.

Cool, thanks. No problems with my hardware (as far as I know) - I think it's just a matter of preference. I usually set the threshold down to somewhere around -8 or -9 on the Ableton script. Really light touch.

From scanning this PXT-General beta thread on beatwise:
http://beatwise.proboards.com/thread/14 ... ush?page=4

Was able to glean a few clues. It looks like the settings are sent through SysEx (as below). Unfortunately there is not much more info in the thread, just Stray saying he would have to figure it out, then saying it would be currently impossible to do, and then Stray figuring it out and implementing the feature but not really explaining how. Maybe some of this could point you in the right direction.

(self.off_threshold, 4) + to_bytes(self.on_threshold, 4) + to_bytes(self.gain, 8) + to_bytes(self.curve1, 8) + to_bytes(self.curve2, 8)

There may be a workaround simply by opening up Live and making the settings changes there, then closing Live and opening Bitwig. Apparently the pad threshold and velocity curve settings will hold until Push is shut off. I will test this tonight to confirm.

Thanks again moss!

[_jon]

Confirmed workaround. You can indeed change the pad threshold and velocity curve settings in Live, and they will hold after switching over to Bitwig.

[stamp]

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.

Workaround doesn't work here .

Cheers

[Echoes in the Attic]

+1 to having pad sensitivity settings if possible. For melodic performance it's much better to make them more sensitive.

[nori.lam]

Hi Moss,

I've found that navigating tracks in a set has odd behaviour. Sometimes I can navigate tracks (left/right arrows) but then sometimes it will get stuck on a track. I have to use the mouse to select another track before left/right works again but if I navigate back to the previously stuck track, it also gets stuck.

It seems that navigating empty tracks is ok but as soon as I have an instrument or clip, the navigation gets stuck.

Another thing is that when I first open BWS and say add a drum rack. Then hit 'New' I get a clip and can record into the clip but I cant see it in Push's drum sequencer until I manually select the clip with my mouse. Is this normal?

Cheers.

[moss]

I've found that navigating tracks in a set has odd behaviour. Sometimes I can navigate tracks (left/right arrows) but then sometimes it will get stuck on a track. I have to use the mouse to select another track before left/right works again but if I navigate back to the previously stuck track, it also gets stuck.

Can you provide an instruction for how to reproduce this?

Another thing is that when I first open BWS and say add a drum rack. Then hit 'New' I get a clip and can record into the clip but I cant see it in Push's drum sequencer until I manually select the clip with my mouse. Is this normal?

Sadly, yes. This annoys me too but there is currently no function in the API to set the focus. But it is on the TODO-list of Bitwig.

[hibidy]

Can someone use the either of the two back inputs of push to control the expression pedal?

[nori.lam]

I've found that navigating tracks in a set has odd behaviour. Sometimes I can navigate tracks (left/right arrows) but then sometimes it will get stuck on a track. I have to use the mouse to select another track before left/right works again but if I navigate back to the previously stuck track, it also gets stuck.

Can you provide an instruction for how to reproduce this?

Open a new project.
Add a midi track, add a drum rack, select any kit.
On Push.
Hit Note, then select drum
Record a clip using sequencer.
Then I am not able to use the navigation keys on that track.

I made a video. you cant see my Push actions but I im just doing what I described.

https://www.dropbox.com/s/l8wt8f24w6063 ... k.mp4?dl=0

Maybe the selection is focused on the clip instead of being global?

[moss]

Can someone use the either of the two back inputs of push to control the expression pedal?

These connectors are only for on/off-type pedals.

[moss]

I've found that navigating tracks in a set has odd behaviour. Sometimes I can navigate tracks (left/right arrows) but then sometimes it will get stuck on a track. I have to use the mouse to select another track before left/right works again but if I navigate back to the previously stuck track, it also gets stuck.

Ah now I understand. When you are in Drum or any of the other sequencer modes the arrow left/right select the previous/next measure. To navigate tracks from there use the direct track buttons below the display.

[astartes]

Did a quick test with the 1.2 Demo (yes, i´m on the Demo Version still.... but not for long i hope...) and Shove (The Push Template for Liine´s Lemur). The Script works Flawlessly, all Sequencers running and, as far as i can Say, all functions from the original Push are usable on the Lemur as well.

I have to say i have the Template slightly modified as described in the Shove Thread over at the Liine Lemur Forum (to get it working on Live 9.1.6), so i´m not shure if the unmodified Template as you can DL from the Lemur Userlibrary also works. The Modification is, when needed, easy to to. I quote from The Liine Userforum: "Here's what to do.. expand each scene button (in the Lemur Editor) highlight the label instruction , then deselect midi0 in the target field for each of the scene buttons . That will do it."

[moss]

Seems it is time for a christmas present! Fully compatible now with Bitwig 1.1.2.

Get it from: http://www.mossgrabers.de/Software/Bitwig/Bitwig.html
Also see the updated Wiki documentation.

Enjoy!

Changelist:

• Completely rewrote bank selection and navigation of devices (Ableton style)
• Rewrote device selection (Ableton style) but has some open issues due to API limitations:
  • Devices are not correctly selected on the display if there are duplicates with the same name
  • Direct parameters might get screwed
  • Devices in a layer are not displayed with names (there are always 8 dummy names)
• Drum pads in drum view now show mute/solo and active/exists states. To make this work the primary device needs to be the drum machine (which is normally the case).
• Rewrote preset selection mode which makes use of the touch capability of the value buttons.
• Long press User button to adjust the pad sensitivity. Also configurable in the script settings.
• Frame mode (keep Master pressed) now follows selected panel layout and has additional options.
• Shift+Browse toggles Browser. Toggling Inspector is now available in Frame mode. Pressing Browse now always enters preset selection.
• Select+Shift+1st button row to de-/activate a track
• 1st button on 2nd row in device modes dis-/enables device. Except in Macro mode.
• 8th button on 2nd row in device modes displays VST window. Except in Macro mode.
• In flipped Session mode the 2nd button row controls now the Scene starts (before it was the 1st). In that mode the Scene buttons now always control Mute or Solo.
• Currently playing measure in Drum- and Note sequencer is now drawn in green.
• Added 2nd mixed mode to Ribbon: Pitch/CC
• Long press Automation button to bring up the Automation dialog which allows you to change the automation mode.
• If the tempo or play position knobs are touched their values are displayed (and can also be changed with the knobs above them).
• Bugfix: Lighting of Automation button is now working as expected
• Bugfix: Mapping of macros is now only possible in Macro mode
• Bugfix: Reset of crossfader setting not working (Delete + Touch)
• Bugfix: Device parameter bank selection: 8th button was active but has no functionality.