Ableton Push support is here

Post Reply New Topic
RELATED
PRODUCTS Push

Post

I can confirm that using Bitwig 2.1 with push 1 on OSX 10.12.4 and the latest github script inside a completely blank project I cant navigate to a device that is nested within a chain container using the push controller. The device its self needs to be clicked inside the software in order to control it. The latest stable release was behaving in exactly the same way the only difference is I have not tested on a blank project yet.
Top

Post

To celebrate the Bitwig 2.1 release, here is the matching Push4Bitwig version!

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

# 9.00
Requires Bitwig 2.1.
  • New: Written now in Java
  • New: Black keys in Piano mode are now using the track color.
  • New: Setting to turn off to display clips of record enabled tracks in red
  • New: Setting to lock the session orientation
  • New: Setting to choose an action for pressing rec armed empty clip in Session mode
  • New: Layout button steps through the play or sequencer modes (depending on which type is active). Shift+Layout button toggles between play and sequencer modes
  • New: All drum modes are now accessible from the track input selection menu (when Note button is pressed)
  • New: To rec arm a track, keep the record button pressed and select the channel (first button row).
  • New: To navigate groups, layers and devices press now the respective first row button. Long press any of the first row buttons to move up the hierarchy again.
  • New: To navigate in a clip use now the Page left/right (device in/out on Push 1) buttons.
  • New: New clip length is now stored in a setting
  • New: Scene lights are now off if the scene does not exist
  • New: Flipping the session view does no longer swap the scene and the 2nd row buttons, since this does not make much sense on the Push 2.
  • New: The cursor keys now consistently always change the track (device, layers) and scene bank, except in browser they change the browser tabs.
  • New: Removed direct parameters because they cause more problems than they help. Use Remote control parameters instead.
  • Fixed: Implemented a workaround for the always empty Groove parameter names.
  • Fixed: Changing the Metronome volume was not working, change now with Select+Knob 9.
  • Fixed: Long pressing Automation did not bring up the automation selection when arranger/clip record was toggled.
Top

Post

As always, Thanks for all the work here!

The download link"DrivenByMoss.zip" currently 404s.
Top

Post

moss wrote:To celebrate the Bitwig 2.1 release, here is the matching Push4Bitwig version!

Get it from: http://mossgrabers.de/Software/Bitwig/Bitwig.html
Is this also for Push 1?
Top

Post

pdxindy wrote:
moss wrote:To celebrate the Bitwig 2.1 release, here is the matching Push4Bitwig version!

Get it from: http://mossgrabers.de/Software/Bitwig/Bitwig.html
Is this also for Push 1?
Sure!
Top

Post

svervs wrote:As always, Thanks for all the work here!

The download link"DrivenByMoss.zip" currently 404s.
Uh, sorry, fixed: http://mossgrabers.de/Software/Bitwig/DrivenByMoss.zip
Top

Post

moss wrote:
pdxindy wrote:
moss wrote:To celebrate the Bitwig 2.1 release, here is the matching Push4Bitwig version!

Get it from: http://mossgrabers.de/Software/Bitwig/Bitwig.html
Is this also for Push 1?
Sure!
I copied DrivenByMoss.bwextension into Documents/Bitwig Studio/Controller Scripts

When I launch Bitwig and go to add controller manually, there is no Ableton option
Top

Post

pdxindy wrote:
moss wrote:
pdxindy wrote:
moss wrote:To celebrate the Bitwig 2.1 release, here is the matching Push4Bitwig version!

Get it from: http://mossgrabers.de/Software/Bitwig/Bitwig.html
Is this also for Push 1?
Sure!
I copied DrivenByMoss.bwextension into Documents/Bitwig Studio/Controller Scripts

When I launch Bitwig and go to add controller manually, there is no Ableton option
Copy that file in the following location depending on your OS:
Windows %USERPROFILE%\Documents\Bitwig Studio\Extensions\
Mac ~/Documents/Bitwig Studio/Extensions/
Linux ~/Bitwig Studio/Extensions/

https://github.com/git-moss/DrivenByMos ... stallation
Top

Post

svervs wrote:
Copy that file in the following location depending on your OS:
Windows %USERPROFILE%\Documents\Bitwig Studio\Extensions\
Mac ~/Documents/Bitwig Studio/Extensions/
Linux ~/Bitwig Studio/Extensions/

https://github.com/git-moss/DrivenByMos ... stallation
Thanks... I just figured that out... I ended up on an older page that said to install to scripts... appreciate the help!!
Top

Post

So far I'm getting these errors:

At first: Push1 was auto detected as Push2
When manual adding it crashes when selecting a port.

After complete restarts: Auto detecting doesn't find anything.
Still crashes with these errors.

Image

BWS 2.1
Sierra 10.12.3
Top

Post

I get the same error (top one) with Push 1
Top

Post

pdxindy wrote:I get the same error (top one) with Push 1
Sorry, for that. :dog:
Please download again, I fixed it.
Top

Post

Am i the only one here that cannot get the Push2display working.
It's so weird, the version that only works with beta's that you get from GitHub worked fine but the new version from Moss site i always get a permission error. I've done as the instructions ask.
I'm totally confused.
Top

Post

Great work moss, looking forward to try it out :) Tell me, how has it felt working with the new Java API?
Top

Post

moss wrote:
pdxindy wrote:I get the same error (top one) with Push 1
Sorry, for that. :dog:
Please download again, I fixed it.
Thanks!! Working now... much appreciated :)
Top
Post Reply

Return to “Controller Scripting”