Ableton Push support is here

[ceasless]

Would it be possible to add an option to make the lights use the colors from the selected track instead of blue? I like how that behaves in ableton, as it makes it very easy to tell quickly which track is selected...

I might poke around when i have some time and look at submitting a PR, but I wanted to see if there's something missing from the API before i go digging

thanks!

It looks like moss is working on this already, as I get this behavior now when using the latest github code. Though I wouldn't necessarily update at the moment as the drum sequencer's cursor does not appear.

[stamp]

Hi Moss,

are you still developing this script?

[moss]

Hi Moss,

are you still developing this script?

Sure, but I am currently busy with other stuff. Will jump into scripting again next month.

[stamp]

Hi Moss,

are you still developing this script?

Sure, but I am currently busy with other stuff. Will jump into scripting again next month.

Oh god thanks... I was afraid you left us here alone in the dark...
Hope that in the future you'll consider the ergonomics of the script. Jamming with the Push in the cliplauncher is a pain at the moment.

[moss]

Hi Moss,

are you still developing this script?

Sure, but I am currently busy with other stuff. Will jump into scripting again next month.

Oh god thanks... I was afraid you left us here alone in the dark...
Hope that in the future you'll consider the ergonomics of the script. Jamming with the Push in the cliplauncher is a pain at the moment.

Would you mind to elaborate why?

[stamp]

First of all thumbs up for providing us this script for free. If it wasn't for your script I would be still using Ableton.

Sadly in Bitwig when you select a track the corresponding clip is not selected(as opposed to Live) so a lot of time I find myself sequencing my drums inside the clip that's playing the lead (or vice versa) because when I'm in the flow I forget to select the clip I want to edit and select the track in volume mode, instead.
To workaround this situation I used to activate the "select tracks when selecting clips in cliplauncher" option and got used to select clips in session mode (on push) instead of changing tracks via the track select buttons. This way I was able to have the grid in sync with device mode (both were assigned to the same track this way). Not ideal but it worked.
Since you introduced the feature that clips are selected when launched I'm f**cked.
If I'm sequencing drums and want to launch a variation on the bass, to try how it sounds, I have to remember to reselect the drum clip if I want to go back to my drums.
The worst thing is that I also had the option "Auto-Arm selected instrument tracks" activated so I was always ready to go. So now when launching an empty clip (to stop that track) performs the action of creating a new clip and record in it.
My workflow = kaputt
I asked a couple of times earlier in this tread if we can have the option to not select clips on launch.

End of part 1

[codec17]

Hi moss..

Much fun here with script, workflow is so much faster for me now, its incredible.

Ive got a suggestion, and ive seen your push 2 video, and you talked about it and you gave a clear explanation for why you didnt do it.
But i just give it a try! sorry.

Im on push 1 here. And when you push the button track, you see all the tracks in a glance and when solo button enabled its getting off or the color blue!
And with mute they are yellow, now i remember you talked about in the video you can give those buttons the color of the track... so my question, why not use the mute color yellow for trackcolors, because when lit you can see in a glance thats its turned on and when muted its just off.

It was just a thought this evening when working... (and i love colors! )

Thnx in advance


Edit: if possible of course...

[KazRemark]

Recently acquired Push 2 and been using Ableton a couple weeks to wrap my head around the basic functionality and how to best integrate into my workflow. I really don't like using Ableton very much after using Bitwig all year, so now I'm using Bitwig again with this script. One thing I'm missing is the ability to open group tracks, the way you can in Ableton (hitting the track select button multiple times will toggle open/close). Any chance we can get this in the Bitwig script?

[moss]

Recently acquired Push 2 and been using Ableton a couple weeks to wrap my head around the basic functionality and how to best integrate into my workflow. I really don't like using Ableton very much after using Bitwig all year, so now I'm using Bitwig again with this script. One thing I'm missing is the ability to open group tracks, the way you can in Ableton (hitting the track select button multiple times will toggle open/close). Any chance we can get this in the Bitwig script?

I like that function too and already thought about implementing it some time ago. The problem is that I currently do not have support for "double presses" in the framework. This is problematic to implement, since Javascript does not have any kind of locking mechanism. Maybe I will give it a try but cannot promise anything.

[KazRemark]

Ah too bad. Well if you can figure it out would be a fantastic addition. The ability to have multiple layers of nested groups is one area where Bitwig just kills it, but it's less useful if you can't use them with Push Thanks for all your effort on this great script though!

[moss]

Ah too bad. Well if you can figure it out would be a fantastic addition. The ability to have multiple layers of nested groups is one area where Bitwig just kills it, but it's less useful if you can't use them with Push Thanks for all your effort on this great script though!

I had a look at how it is currently implemented in Ableton. Seems I remembered it wrong, therefore my answer was not correct. Currently, if you open a group in Ableton the tracks are shown on the same "level". This is not how it works with the Bitwig API: You either need to navigate into a group or you can get ALL sub channels (all nested ones). Which means the Ableton way can currently not be implemented.
Even if it would be possible it would imply to loose the record dis-/enable feature on second press.

[moss]

Version 7.32 is online!

• New: Octave pads in play, sequencer and raindrop view are now colored in the tracks color.
• New: Added Option: Select Clip on Launch
• New: Added Option: Stop Automation on knob release
• Fixed: Touchstrip LEDs were not set correctly
• Push 2:
  • Push2Display: Restore window position at startup.
  • Push2Display: Show warning message if configuration file could not be stored.

Get it from: http://mossgrabers.de/Software/Bitwig/Bitwig.html

Enjoy!

[svervs]

Thanks for another update!

• New: Octave pads in play, sequencer and raindrop view are now colored in the tracks color.

Great caring for the details!


Has the functionality of Press/Holding the Session button changed?
On the Wiki it still says it's supposed to switch back to Note mode on release. Not working here with Push1 on OS X.
That was very useful ...

[stamp]

[*]New: Added Option: Select Clip on Launch

Thank you! Thank you! Thank you!
That's priceless for me.

I like that function too and already thought about implementing it some time ago. The problem is that I currently do not have support for "double presses" in the framework. This is problematic to implement, since Javascript does not have any kind of locking mechanism. Maybe I will give it a try but cannot promise anything.

In Ableton you press and hold a track selection button to enter a group.

Has the functionality of Press/Holding the Session button changed?
On the Wiki it still says it's supposed to switch back to Note mode on release. Not working here with Push1 on OS X.
That was very useful ...

I've noticed that too. Can you fix this, please?

It would be nice if you could add the momentary function to the volume,device,mute/solo buttons, too.

Another couple of suggestions for cliplauncher oriented Pushing

- The record button starts arrangement record and shift+record starts cliplauncher overdub (same goes for automation). Can we have an option to switch this behavior, please?
Even better: since the script is aware of what we have on the screen it could adapt the function of the record (and automation) button.
So when we are in mix view pressing record activates cliplauncher overdub and when we are in arrangement view it starts arrangement recording.
Maybe add an option to choose the record/automation mode (cliplauncher, arrangement, auto) so everyone will love you.

- Use shift+session to flip sessionview instead of the session button alone to avoid accidental flipping.

- Ability to change track when in device mode using the arrows. This would be huge (specially when performing live).
Since the function expand device, macros and parameter is accessible via the track state buttons in device mode and also pressing the device button I would remove it from device mode and put in two buttons to move parameter page left/right (by a factor of eight would be cool, please).
Two advantages here:
- you can change track when in device mode
- device mode becomes more ergonomic since you do everything next to the screen and you don't have to reach for the arrows while tweaking your basslines.

I think this stuff would really increase the fun factor.

Thank you!

Cheers

[stamp]

Bugs:
- There are still problems with the grid when changing tracks in note mode. Synth tracks still switch to drum mode, etc. This happens most of the times
- Sometimes I can enter the fx track section but I can't select the fx tracks.
- Sometimes when starting Bitwig I have to switch Push on/off to make it work.
- When in session mode the left/right buttons change track. Is this the intended behavior? I think they should move the rectangle instead (by a factor of 1).

I'm on Push 1

Thank you!