Ableton Push support is here

Post Reply New Topic
RELATED
PRODUCTS
Push

Post

yonhorizon wrote:hello again.
big thanks moss for replying and for your work.
something weird hapenned. i formatted my pc and made a fresh windows install.
now i can browse on push. before couldnt no matter what.
the drum pad view changed its colors.
the record button , which before functioned as record clip, when clip was focused now enables arrangement record.
push still freezes when i quit bitwig.

i have the latest ableton firmware.

before i also had novation launch control connected, with that script for bitwig ( the only one ) and m-audio axiom 61, connected as generic keyboard. havent tried yet connnecting them. can it be some assignment clash ?

btw is there a way to record in session? ( the record button enables arrangement record is there a way to make it start the clip recrding ? )

thanks alot !
I suggest that you watch my tutorials and have a look in the Wiki:
https://github.com/git-moss/Push4Bitwig/wiki
https://www.youtube.com/playlist?list=P ... 9HngDDKF3s

Post

soehngenetic wrote:
pdxindy wrote:
soehngenetic wrote:Why not make your own Device mappings for the VST's you use? Sure it takes some time, but you only have to make a sensible organization once.
Thanks for this advice. As written before, I started using Bitwig about a week ago and I'm still discovering it. As a total Bitwig-noob one of my problems is, that with 1.2 some of the applications behaviour and icons seem to have changed, but the 1.2 manual still shows the ways and screenshots of earlier versions. - So I it would be very kind and cool, if you could PM me (to get not too off-topic here) a link to a tutorial or a short description how to do it. Thanks in advance. :)
First, put a Polysynth on an instrument track. Right click on the header bar of the Polysynth and select 'Edit Panel Mappings'. That will bring up the Device Panel Mappings window. There you will see the fixed sections and parameter pages. Parameter pages is what you are going to make for your VST. Looking at the Polysynth first, you get an idea of how each page of 8 controls is organized. You will notice a big + sign in a rectangle. Clicking on that adds a page. Drag one of the colored dots on that new page to the parameter you want it to control. That is how you build pages.

Now add a simple VST. One thing with mapping VST's is that you cannot drag the dot to the VST GUI. You have to drag the dot to the Device controls for that VST.

Once you create a page and add the mappings for it, remember to hit the save button up in the top left corner of the device panel mappings window.

My biggest feature request for this area is the ability to drag-n-drop the order of parameter pages. Right now, if you create 6 pages, then decide you want to add a parameter on page 1, or add a page in between page 1 and 2, you have to remake all the other pages. So give some thought to the order and page structure you want before you start mapping.

That should get you started.

Post

moss wrote:
yonhorizon wrote:hello again.
big thanks moss for replying and for your work.
something weird hapenned. i formatted my pc and made a fresh windows install.
now i can browse on push. before couldnt no matter what.
the drum pad view changed its colors.
the record button , which before functioned as record clip, when clip was focused now enables arrangement record.
push still freezes when i quit bitwig.

i have the latest ableton firmware.

before i also had novation launch control connected, with that script for bitwig ( the only one ) and m-audio axiom 61, connected as generic keyboard. havent tried yet connnecting them. can it be some assignment clash ?

btw is there a way to record in session? ( the record button enables arrangement record is there a way to make it start the clip recrding ? )

thanks alot !
I suggest that you watch my tutorials and have a look in the Wiki:
https://github.com/git-moss/Push4Bitwig/wiki
https://www.youtube.com/playlist?list=P ... 9HngDDKF3s
Hi Moss,

just wanted to ask if i'm missing something on fine control of fader volume via push, is it in the script yet because i'm holding down shift and adjusting the volume gain but it's still quite coarse?

cheers

Post

I was just ask the same thing.... As Bobby l,aviner.. :D
I cant find it in the script anymore wich value i have to tinker...
It were 2 value,s one with and one without shift.. :party:
You mentioned it before... but really cant find it anymore. :neutral:
Thnx in advance!

Post

codec17 wrote:I was just ask the same thing.... As Bobby l,aviner.. :D
I cant find it in the script anymore wich value i have to tinker...
It were 2 value,s one with and one without shift.. :party:
You mentioned it before... but really cant find it anymore. :neutral:
Thnx in advance!
See https://github.com/git-moss/Push4Bitwig ... own-Issues
number 8. :D

Post

thnx! My iq just dropped to 34 now... :oops:

Post

Moss do you plan on making new tutorials or updating them?
-Tristan
MacBook Pro|MacOS Sierra|Bitwig Studio 2.0
UA Apollo Twin| EVE SC207 Monitors|ATH M50x|Focal Spirt Pro|Komplete 10|Push

Post

TristanMendoza wrote:Moss do you plan on making new tutorials or updating them?
Coming soon :-)

Post

moss wrote:
TristanMendoza wrote:Moss do you plan on making new tutorials or updating them?
Coming soon :-)
I can't wait :)
-Tristan
MacBook Pro|MacOS Sierra|Bitwig Studio 2.0
UA Apollo Twin| EVE SC207 Monitors|ATH M50x|Focal Spirt Pro|Komplete 10|Push

Post

I released a new version which is all about Bugfixes:

- Fine (Shift pressed) changed from 0.5 to 0.25
- Fixed: Changing direct parameters works again (still broken non continuous parameters).
- Fixed: Crossfader B could not be selected
- Fixed: No more flickering of 2nd row buttons in Device mode.
- Fixed: If Fader mode was selected the ribbon lights were not updated if the volume of the track changed. Furthermore, if VUs were enabled they were also not reflected on the ribbon.
- Fixed: The crossfader value was not updated on the ribbon in Session mode.
- Fixed: Notes did not cover the full range (octave range extended).
- Fixed: Prevented midi error with VUs if track is clipping

Enjoy!

Post

moss wrote:I released a new version which is all about Bugfixes:
- Fine (Shift pressed) changed from 0.5 to 0.25
- Fixed: Crossfader B could not be selected
Enjoy!
Thnx! fantastic! i just wanted to ask.. but delivered in a bitwig pace! :tu:

Post

TristanMendoza wrote:
moss wrote:
TristanMendoza wrote:Moss do you plan on making new tutorials or updating them?
Coming soon :-)
I can't wait :)
New tutorial is online :party:


Post

moss wrote:I released a new version which is all about Bugfixes:
Enjoy!
would that be a beta or stable version? (which location do I download from?)

Post

I was just about to post about to post regarding issues with the fine control on the knobs, nice one Moss, I'll try the new version out now :tu:

Post

pdxindy wrote:
moss wrote:I released a new version which is all about Bugfixes:
Enjoy!
would that be a beta or stable version? (which location do I download from?)
When I write "release" it's on my website. Currently, they are identical :-)

Post Reply

Return to “Controller Scripting”