Ableton Push support is here

[nori.lam]

Using the shift button would be the best IMO so you could choose to create armed/unarmed clips depending on your needs.

Thanks!

Hi Moss,

I agree with 'stamp' that an option to override the armed clip creation would be great. I am just coming back to Bitwig from Live and find this feature a bit of a workflow stopper.

Btw - thanks for implementing velocity sensitivity in the drum sequencer. its awesome!

[moss]

Should I be able to use aftertouch ?
I tried (on the RC beta) to assign the AT-> modulation to cutoff and res on the polysynth, but nothing seems to happen.

The Push sends Poly Aftertouch and it works fine. The problem is that it is hard to find a plugin which supports Poly Aftertouch, the only one I found in my collection is NIs Kontakt.
Most plugins only support Channel Aftertouch including Polysynth. Since this is not very helpful I added now an option to the Push4Bitwig settings where you can enable to convert Poly Aftertouch to Channel Aftertouch. If you like to give it a spin download the latest version from GitHub.

[thetechnobear]

Alchemy, and all of U-he synths support poly AT...

BUT bitwig doesn't send poly AT thru to VSTs anyway. (
you have an api call to say what to do with poly pressure, e.g. make it timbre, but the VST object then doesn't do the translation back - afaik)

but this may be changing in 1.2 due to the MPE device support...

[koalaboy]

Should I be able to use aftertouch ?
I tried (on the RC beta) to assign the AT-> modulation to cutoff and res on the polysynth, but nothing seems to happen.

The Push sends Poly Aftertouch and it works fine. The problem is that it is hard to find a plugin which supports Poly Aftertouch, the only one I found in my collection is NIs Kontakt.
Most plugins only support Channel Aftertouch including Polysynth. Since this is not very helpful I added now an option to the Push4Bitwig settings where you can enable to convert Poly Aftertouch to Channel Aftertouch. If you like to give it a spin download the latest version from GitHub.

That works fantastically well and is truly awsome. Thank you, most kindly, Jürgen

Two enhancements, if I may, would be: 1) Only using the first aftertouch value, as if you have two different ones, they can cause glitching between them, and 2) copying the latest Push firmware to enable the aftertouch threshold under the configuration screen when holding 'user'.

[moss]

1) Only using the first aftertouch value, as if you have two different ones, they can cause glitching between them, and

That's pretty complicated. You can press as many pads as you like. What should be the algorithm to map the data send from all those pads into one?
Use the oldest, the newest or ...?

2) copying the latest Push firmware to enable the aftertouch threshold under the configuration screen when holding 'user'.

Since Ableton documents nothing, someone needs to decompile the Push script coming with latest Beta and then figure out from that code (a big mess) which is the new sysex string and its encoding they are using to do this. Volunteers wanted

[moss]

Time for a new official release 4.4

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

Enjoy!

Changelist:
* New play mode 'Piano' with keyboard like layout
* New scale offsets by 8ths
* Added new settings option to convert the Poly Aftertouch of the pads to Channel Aftertouch or a CC.
* Bugfix: Fixed track navigation for effect tracks.
* Bugfix: Fixed behaviour of Master button: Does no longer select master button if long pressed to enter frames mode. Previous mode gets correctly restored if pressed again.
* Bugfix: Fixed position of note range display in Play mode.

[ToneShop]

Thank you !

[FastTriggerFish]

Moss, thank you for the amazing work !!
I was interested in trying to extend Push4bitwig to add a few things for my own use, and that I would be happy to share if they end up working well:
- Possibility to skip steps, or to repeat them a number of times
- Adding probabilities to steps to be played or skipped
- Adding probability of random jump from one step to another
- A sequencer mode that works like the Intelijell Metropolis.

From having a quick look at the bitwig API it doesn't seem like any of this would be easy or even possible, since for instance skipping a step would require moving the whole data from a clip, which might not be possible to do in real time ?
Am I missing something ? I would be very interested to have your opinion.

[dplduffy]

this question is for anyone that knows the answer.

Is it possible with this script to browse and load the an instrument onto a track after you have created the track? I thought I remembered reading somewhere that you still had to go back and add an instrument using the PC before you could browse the presets, and I was wondering if this had been implemented or if we're waiting for api changes.

I ask because this is the only reason I haven't bought a push yet, and I reallllllly want one!

Good job with the script Moss

[moss]

From having a quick look at the bitwig API it doesn't seem like any of this would be easy or even possible, since for instance skipping a step would require moving the whole data from a clip, which might not be possible to do in real time ?

Regarding sequencers you have to fully rely on clips because it is not possible to get a stable clock or playback from a script. Therefore, everything you can do to a clip via the API is your range of possibility.
Skipping a step is especially problematic and I doubt you get that working. Brute force attempt would be to delete the note(s) of the step, copy all notes till the end one step earlier and shorten the clip (and remember somewhere what you have delete). Another idea would be to move the loop/playback area, that could work.

[moss]

Is it possible with this script to browse and load the an instrument onto a track after you have created the track? I thought I remembered reading somewhere that you still had to go back and add an instrument using the PC before you could browse the presets, and I was wondering if this had been implemented or if we're waiting for api changes.

Browser support (incl. Instrument/FX selection) is coming with the 1.2 update.

[moss]

(duplicate)

[FastTriggerFish]

From having a quick look at the bitwig API it doesn't seem like any of this would be easy or even possible, since for instance skipping a step would require moving the whole data from a clip, which might not be possible to do in real time ?

Regarding sequencers you have to fully rely on clips because it is not possible to get a stable clock or playback from a script. Therefore, everything you can do to a clip via the API is your range of possibility.
Skipping a step is especially problematic and I doubt you get that working. Brute force attempt would be to delete the note(s) of the step, copy all notes till the end one step earlier and shorten the clip (and remember somewhere what you have delete). Another idea would be to move the loop/playback area, that could work.

Thanks a lot moss, that's kind of what I thought.
I hope they extend the API at some point !

[dplduffy]

Is it possible with this script to browse and load the an instrument onto a track after you have created the track? I thought I remembered reading somewhere that you still had to go back and add an instrument using the PC before you could browse the presets, and I was wondering if this had been implemented or if we're waiting for api changes.

Browser support (incl. Instrument/FX selection) is coming with the 1.2 update.

thats kinda what I figured. Thanks man.

[Bobby L'Avenir]

Hi guys, sorry if this is the wrong place to ask but Push cost £30 more than Launch Pad Pro 2 will cost to pre order so I'm thinking of buying one before the 30% off Ableton sale finishes this week.

Can someone who's used both let me know if push is worth the extra money.

1) I have maschine which I love to death, can push select drum samples, especially
Loops and also included plus 3rd party plugins from the control surface like maschine or will I have to use the mouse for some things?

2) is it correct that push only works with bitwig or live, I can't use it in cubase like I could with launch pad?

3) is the push screen bright enough on only USB buss power?

4) can I perform sample to slices from push

5) can I control 3rd party soft synths with the knobs on push?

6) I'm assuming I can control the included bitwig devices from push including the sampler? (I've only just got bitwig so sorry for asking what may seem dumb questions)

Thanks in advance chaps