Ableton Push support is here

[moss]

Would it be possible to use the 64 pads as fader like on novation controller launchpad, for example you press shift + Vol and so the 64 pads move the volume like the rotary knob ? Same thing for PAN, SEND, ...

Yes, it would be possible but I do not like it since I always felt how e.g. the Launchpad did it was a bad workaround for not having knobs or sliders. However, the script is open source, you could have your own go at it

Would it be possible with a special combinaison of key shift + ??, that the 8 rotary knobs and the 2 x 8 pads at the top become standard midi controller that we can assign with BWS, im my case i want to assign the rotary knob to a hipass filter for live?

That's already possible if you go to Device and then select the User mode. There you can learn 8 CCs. With the latest release of Push4Bitwig the last mode you had selected in Device is remembered, so you just have to push the Device button to get to your controls.
Note: The latest Push4Bitwig version on GitHub which contains that feature is very experimental since it is adapted to the 1.2 Beta.

[cedrelo]

Would it be possible to use the 64 pads as fader like on novation controller launchpad, for example you press shift + Vol and so the 64 pads move the volume like the rotary knob ? Same thing for PAN, SEND, ...

Yes, it would be possible but I do not like it since I always felt how e.g. the Launchpad did it was a bad workaround for not having knobs or sliders. However, the script is open source, you could have your own go at it

Would it be possible with a special combinaison of key shift + ??, that the 8 rotary knobs and the 2 x 8 pads at the top become standard midi controller that we can assign with BWS, im my case i want to assign the rotary knob to a hipass filter for live?

That's already possible if you go to Device and then select the User mode. There you can learn 8 CCs. With the latest release of Push4Bitwig the last mode you had selected in Device is remembered, so you just have to push the Device button to get to your controls.
Note: The latest Push4Bitwig version on GitHub which contains that feature is very experimental since it is adapted to the 1.2 Beta.

Hi,

I think too, that the launchpad workaround is not good, but it could be useful for live set when we don't want to bring two controllers.
Your script is open source, so i could do it , but after i will have to merge my source with yours everytime you release a new version.


Ok perfect for the device user mode.

Thanks for all

[codec17]

1. Has to do with the fact the framework is not setup for this, there becomes multiple instance of things and the oncorrect observers are not called OR listened to.

I ran into this problem when testing Maschine, when 1.2 comes out, I want to see if I can isolate this issue and get it fixed in the Framework4Bitwig code that all ours scripts share.

I use dual screens a lot, I don't know if Moss does or not, if he doesn't he may not even know this issue exists.

Mike

Hi Mike!

Is there any news on this on this with the 1.2 beta?

EDIT: damn didnt copy my question only your answer. ..
its about the focus of a clip when selected on your 2nd screen...

[TeotiGraphix]

1. Has to do with the fact the framework is not setup for this, there becomes multiple instance of things and the oncorrect observers are not called OR listened to.

I ran into this problem when testing Maschine, when 1.2 comes out, I want to see if I can isolate this issue and get it fixed in the Framework4Bitwig code that all ours scripts share.

I use dual screens a lot, I don't know if Moss does or not, if he doesn't he may not even know this issue exists.

Mike

Hi Mike!

Is there any news on this on this with the 1.2 beta?

EDIT: damn didnt copy my question only your answer. ..
its about the focus of a clip when selected on your 2nd screen...

Haven't tested it yet, I will post when I do. So far since the Group nav is not finished impl wise I have been waiting to test deeper with the controllers.

Just helping out with general app bugs and crashes right now.

Mike

[codec17]

bugs and crashes priority number one!
THNX..

[codec17]

Hi moss and Mike!

If you got time to take a look at this video @2.50, it would be super!

I,ve seen it a couple a days ago and didnt get it out of my mind.... So i took the change too ask.
I was wondering if this was something that the nektar has as hardware or their script...??

What,s the question???
Well you can see if he slaps the pad of the nektar it immediately selects the parameters of that drumpad in his display.
Is this possible with the script or API ? or maybe 1.2?? Maybe a drawback of push?
It would make your drum sound editting so much faster.

thnx in advance!

here,s the video, so @2.50 :

[TeotiGraphix]

Hi moss and Mike!

If you got time to take a look at this video @2.50, it would be super!

I,ve seen it a couple a days ago and didnt get it out of my mind.... So i took the change too ask.
I was wondering if this was something that the nektar has as hardware or their script...??

What,s the question???
Well you can see if he slaps the pad of the nektar it immediately selects the parameters of that drumpad in his display.
Is this possible with the script or API ? or maybe 1.2?? Maybe a drawback of push?
It would make your drum sound editting so much faster.

thnx in advance!

here,s the video, so @2.50 :

Seems to me there is some funky chicken custom happening int he way they digest a drum machine.

Each channel of the drum machine can be edited as parameters so what they have exists, just nt in your face like they have it.

I guess you would need to be more specific of what you want the Push to look like and do.

Mike

[moss]

Well you can see if he slaps the pad of the nektar it immediately selects the parameters of that drumpad in his display.
Is this possible with the script or API ? or maybe 1.2??

From the Wiki:

"Hold down the Select button while pressing a drumpad to select it without playing its sound. This also selects the according drum pad layer in the display."

[twumpy]

Hi!

A question concerning performing with Push:

Is it possible to effect a track while working with another?
For example: I have Polysynth track on track 1, and maybe loops playing in tracks 2 & 3.
Is it possible (and easy) to tweak the macros on the 2 & 3, while playing the polysynth with the pads? Obviously not 2 & 3 simultaneously, but jump between the FX racks of those channels.

Great work with the script & videos, can't wait for 1.2.

[moss]

Is it possible (and easy) to tweak the macros on the 2 & 3, while playing the polysynth with the pads? Obviously not 2 & 3 simultaneously, but jump between the FX racks of those channels.

No, that's not possible. Only workaround would be to learn the MIDI CCs of the 8 user controls to the knobs on 2 & 3.

[twumpy]

Thanks for the quick reply! I guess it's a question of workflow or additional controller then.

It's going a bit off topic, but if you had two controllers in Ableton, they would have this annoying habit of jumping to control the same track when you selected one with either of the controllers. Maybe you would have experience on using Bitwig with two controllers and whether they stay put when they need to?

[codec17]

Well you can see if he slaps the pad of the nektar it immediately selects the parameters of that drumpad in his display.
Is this possible with the script or API ? or maybe 1.2??

From the Wiki:

"Hold down the Select button while pressing a drumpad to select it without playing its sound. This also selects the according drum pad layer in the display."

Yeah i know! thanx....
But it always loses focus of a device so you have to go "up" in your drummaschine all the time...
Hoped in whatever page your on AEG , LFO, GLOBAL you could select+pad.
Yes im a lazy man...

[maschinelf]

So is this one of the best controllers to get for Bitwig, now and in the future?

There is a really good deal on Push where I live (around $350-370), and I'm really tempted. But I'm spoilt for choice really. I have a 49 sl mkII, panorama P1, beatstep, and APC mini. I actually got the mini because I thought it would kill my GAS for the Push back when this deal was announced, but now I'm kind of wishing I'd got the push instead. Is there a compelling enough reason to get it if I already have the above controllers?

What I like about it most is the sequencer modes (particularly the note sequencer), the velocity sensitivity which would be a lot more useful in play mode as well as the sequencer modes, the all-in-one approach (ie as a controller, sequencer and clip launcher, though the apc mini does this too), and what seems like a very intuitive layout with all those function/mode buttons on the left, so it seems really quick to get around. The coloured pads are a plus too.

[moss]

So is this one of the best controllers to get for Bitwig, now and in the future?

There is a really good deal on Push where I live (around $350-370), and I'm really tempted. But I'm spoilt for choice really. I have a 49 sl mkII, panorama P1, beatstep, and APC mini. I actually got the mini because I thought it would kill my GAS for the Push back when this deal was announced, but now I'm kind of wishing I'd got the push instead. Is there a compelling enough reason to get it if I already have the above controllers?

What I like about it most is the sequencer modes (particularly the note sequencer), the velocity sensitivity which would be a lot more useful in play mode as well as the sequencer modes, the all-in-one approach (ie as a controller, sequencer and clip launcher, though the apc mini does this too), and what seems like a very intuitive layout with all those function/mode buttons on the left, so it seems really quick to get around. The coloured pads are a plus too.

The Push is the best. But noone knows what the future brings

[superscalar]

Hi Moss, hi Mike,

first of all, thanks for your great work on the script.
I recently bought a push to control bitwig and i love it...

I have some questions and hopefully someone could give me some hints.

1. Hold down the Select button while pressing a drumpad does not select the according drum pad layer in the display -> is this a 1.2 feature?
2. In sequencer modes in have problems with setting triplets. When choosing 1/4T and select the first note, the second one will be selected too (it is not set in bitwig!). I can dis-/select the third note. OK. But selecting the second one(selected by push when selecting the first one) will disable the first and the second note. Selecting the second, while the first is not selected, is ok. But selecting the first after that, will set the first one in bitwig, delete the second one in bitwig, and both, one and two, are selected on pushs grid. And so on...
3. From time to time everything looses focus. My push does not react anymore and needs to get restarted.
4. Strange display behaviour. Sometimes the column with the device name disappears. The parameter names are not or wrong displayed...
5. Knobs. Sometimes the knobs, while touching, "play" the selected device or some noise. I have to restart push and bitwig to get rid of this.

Maybe i got some buggy hardware???

My bitwig version is 1.1.10

Cheers.
Ingo