Ableton Push support is here

[codec17]

Boom fast as lighting! Works as it should again. Thanx!

About FX after a pad. I knew you couldnt acces the FX-slot. But the FX is placed just after the pad. (so not in FX slot)
Now when i go -Device in- on the pad i see the the overall/global FX of the drummaschine, instead of the fx i placed just for the pad.
But maybe thats what you mean with the bitwig update problem. Its the .16-RC1

Again thanx for all your hard work. Cant say it enough, having a BLAST with script!

[stamp]

From Github: Shift+Duplicate to create a new scene from the currently playing clips

Cool! Really usefull. Thanks!

Another workflow improvement: make the solo/mute/stop/volume/device buttons work in a momentary fashion but with a shorter delay than the session button (actually it's 400ms, a little bit too long IMO, 200ms is better I think)

Thank you!

[The Mantra]

I just got a Push 2.
Every things cool but the vu meters on the push 2 screen aren't working. Any ideas?

[moss]

I just got a Push 2.
Every things cool but the vu meters on the push 2 screen aren't working. Any ideas?

Press Shift+Mix to turn them on/off. Also check the setting in the scripts properties.

[moss]

Time for a last 1.3.x release before we jump into Bitwig 2 fun:

• New: Added button to master mode to turn on/off audio engine.
• New: Adding a track now selects it.
• New: Shift+Duplicate to create a new scene from the currently playing clips
• New: Shift+New: Like New button but without activating launcher overdub.
• Fixed: Changing the Send on Push 1 did show the notification string in the display.
• Fixed: Octave up/down in raindrop sequencer did switch track but should change octave.
• Fixed: Switching between Mute and Solo mode did not work on Push 1 in Drum sequencer.

As usual get it from my homepage: http://mossgrabers.de/Software/Bitwig/Bitwig.html

[moss]

WARNING:
I just pushed the latest code to GitHub which now supports the new v2 API.
https://github.com/git-moss/Push4Bitwig

This version is NOT compatible with 1.3.x! If you are on the Beta list feel free to give it a try.

There are still some regressions in the API, which are documented here: https://github.com/teotigraphix/Framewo ... regression

So please look there first before reporting bugs.

[askewd]

[Moving a PM with moss here for the potential benefit of other users. ]

After trying out the launchpad i see the fun to be had with clip launching controllers so i have decided to buy the PUSH2 as that seems the best one to get and the most future proof. Plus Moss owns one so the script will get MossLove

Anyway i asked Moss three questions, to each the answer was NO. Pasted below:

1) Is there a mode where i can just jam on all 8x8 keys on the Push, where the keys are all colour coded from Bitwig Drummachine cell colours? (I've seen video showing small 4x4 coloured drum pads with a sequencer at the top, but i don't want that, i would prefer one full grid covered in drum cells for 'playing').

Moss: NO
Dales face:

2) Is there a 'scene jam' mode? Ie where each scene is on a different cell. So that i can Jam with scenes? (Tom built my MPD226 script to do this and it works great!).

Moss: NO
Dales face:

3) Does Note Repeat work ?

Moss: NO
Dales face:

ok... this worries me a little bit because these three things are what i am kinda most excited about, and yet they do not exist. I am especially surprised number 1 doesn't exist.

So my new question is - are these features possible to implement? would i please be able to request these features be added? Especially number 1.

thank you
Dale

[stamp]

1) Is there a mode where i can just jam on all 8x8 keys on the Push, where the keys are all colour coded from Bitwig Drummachine cell colours? (I've seen video showing small 4x4 coloured drum pads with a sequencer at the top, but i don't want that, i would prefer one full grid covered in drum cells for 'playing').

Since in Bitwig 2 the API allows to enable/disable observers this could be possible in the future, i guess.
Better ask moss.

[askewd]

Since in Bitwig 2 the API allows to enable/disable observers this could be possible in the future, i guess.
Better ask moss.

I'm not following why this seems a complex thing not a fundamental basic thing?

For example check out 2:10 on this video:

He says, if you want to access the full kit, just tap the layout button on the push 2. That's all I want.

I can't imagine why this would not be possible in bitwig? Surely it's just notes, isn't it?

Best
Dale

[stamp]

I don't know much about scripting myself.
Afaik Ableton scripts are written in Phyton whereas Bitwig uses Java. There must be some difference in performance between the two programming languages that makes it probably more complicated in Java.
I guess that too many observers will have a negative impact on performance and till now the API doesn't allow to enable/disable obsevers...
Moss will explain this stuff better than me since he is the scripting wizard.

[moss]

1) Is there a mode where i can just jam on all 8x8 keys on the Push, where the keys are all colour coded from Bitwig Drummachine cell colours? (I've seen video showing small 4x4 coloured drum pads with a sequencer at the top, but i don't want that, i would prefer one full grid covered in drum cells for 'playing').

This can be implemented. Then why isn't it already there? As stamp already tried to explain, currently you have to register all the data you are interested in during startup of a script. For Push4Bitwig this means nearly everything, even if you only need the data partially, depending what mode you are in. Adding this 8x8 matrix would add to that. With the upcoming v2 API it is now possible to disable data you are currently not interested in. Therefore, an performance improvement can be implemented but that needs some careful thought. So stay tuned.

2) Is there a 'scene jam' mode? Ie where each scene is on a different cell. So that i can Jam with scenes? (Tom built my MPD226 script to do this and it works great!).

You are the first one requesting that and it is also not in the Ableton version. But it is an interesting idea.

3) Does Note Repeat work ?

That's currently just not possible. I would like to see that too.

[askewd]

This can be implemented. Then why isn't it already there? As stamp already tried to explain, currently you have to register all the data you are interested in during startup of a script. For Push4Bitwig this means nearly everything, even if you only need the data partially, depending what mode you are in. Adding this 8x8 matrix would add to that. With the upcoming v2 API it is now possible to disable data you are currently not interested in. Therefore, an performance improvement can be implemented but that needs some careful thought. So stay tuned.

ok i see. So would it be correct to saythat it only the COLOURS that are the issue? Because there are already normal 'piano note' modes i could use to play the synths or drumskits, right?

Coloured pads would make much more sense but i can wait for this , as long as there a regular piano-note mode that doesn't force a musical 'key', but instead lets you use ALL the keys?

You are the first one requesting that and it is also not in the Ableton version. But it is an interesting idea.

its really great for recording final arrangement structures. It also helps the transition for people coming from regular DAWS into a clip-based environment/concept. I don't even have clip mode on my MPD, only Scene jamming really does make arranging tracks fast (i guess you can already do this in a clip launcher, its just harder if there are more than 8 because u can't instantly jump from scene 1 to scene 24, for example. A scene jam mode would solve this problem.)

Does Note Repeat work ?
That's currently just not possible. I would like to see that too.

Ohhh no!! sounds like such a simple thing to implement. Guess its not. Is it because of Javascript timing issues? Lets hope the Devs implement it into V2.

as an idea, which you've probably already thought of, would it be possible to utilize your screen-app (for the push2) as a workaround for note repeat. My thiking being that it sits inbetween bitwig and the controller, and uses Java so may have better timing...just an idea (i'm no programmer so i'm probably speaking nonsense!)

thanks
Dale

[moss]

Does Note Repeat work ?
That's currently just not possible. I would like to see that too.

Ohhh no!! sounds like such a simple thing to implement. Guess its not. Is it because of Javascript timing issues? Lets hope the Devs implement it into V2.

as an idea, which you've probably already thought of, would it be possible to utilize your screen-app (for the push2) as a workaround for note repeat. My thiking being that it sits inbetween bitwig and the controller, and uses Java so may have better timing...just an idea (i'm no programmer so i'm probably speaking nonsense!)

Believe me, I already tried a lot of ideas What is needed is support for this in the host, an alternative is to utilise the ARP devices. To do so I would need a function to insert a specific device and to search it.
Look here: https://github.com/teotigraphix/Framewo ... /issues/20

[askewd]

Believe me, I already tried a lot of ideas What is needed is support for this in the host, an alternative is to utilise the ARP devices. To do so I would need a function to insert a specific device and to search it.Look here: https://github.com/teotigraphix/Framewo ... /issues/20

Ok. Glad I'm not the only one eager for this.

Maybe the devs just don't realise why that feature is so damn useful!

[askewd]

Just reading the Moss-manual and watching the Moss video tutorial, have to say getting VERY excited about getting a Push2!

Can i please suggest a few small features:

1) A preference to allow the reverse behaviour of the record and overdub functions. For example, at the moment it says press "record" to record (into the arrangement) and "shift+record" to activate OVERDUB.

In my case, coming from a MPC workflow, i would much prefer the record button to toggle overdub. I would not use full record very often until i am ready to record arrangements. Therefore record = overdub (Without Shift) would be a much friendlier and faster for me.

Question - does the unit give clear visual feedback when overdub is activated? or do you need to glance at the computer instead to check?


2) As 'layout' does not seem to switch to 'full drum pad mode' like in Live (YET), may i suggest as a temporary work around that the button takes you to a mode that is the simply just the same as a piano-note mode. However the only difference is that you colour the pads in a more attractive way - maybe 4x4 coloured squares to let the user know they are in a drum-esq mode. This should not involve extra observers should it? (Because it's the same as the note mode that is already there) .

Let me know if they make any sense.

thank you
DALE