Ableton Push support is here

Post Reply New Topic
RELATED
PRODUCTS
Push

Post

4eyez wrote:Here's another from the Control Script Console:

Code: Select all

Called exit()
Called init()
Initialized.
TypeError: Cannot find function canSelectPreviousPage in object [object Object]. (AbstractViewExtensions.js#1299)
Thanks for reporting. I guess that happens if the mode is changed during update. I added a check for that.

The other warnings about "CONTENTS/" can be ignored. These are inconsistencies in the direct parameter API. I am thinking currently about removing the direct parameters completely.

Post

Hi Moss

Thanks for getting back to me, most appreciated.

Sorry, a little new to this process, does that me you've added the update to the version on github? It looks like the last update was 9 days ago, so I'm assuming that tweak isn't up there yet.

And would just like to add to the chorus of respect for making this script, opens up huge doors for working with Bitwig! Many thansk!

Post

4eyez wrote: Sorry, a little new to this process, does that me you've added the update to the version on github? It looks like the last update was 9 days ago, so I'm assuming that tweak isn't up there yet.
No, it's not yet there. I want to do some internal reworking first but I am currently very busy with other stuff. Might get delayed till the Christmas break.

Post

Roger wilco! I'm just stoked to know that it's being chipped away at. Thanks for the reply and for the script. I'm gonna PM you my email address in case you're looking for people to bug test.

Post

Hi Moss,

I recently bought Microtonic (DrumSynth) and want to use the MultiChannel mode (one send for each channel). When I use device mode with Push 2 and set button "Page left" to enter for example the macro values, I only have access to the Sends. Is it not possible to enter the macro values with Push 2 for Multi-Channel-Devices?

Thank you and kind regards,
Alexander

Post

Time for a christmas present! :harp:

It uses all the new API goodies of Bitwig 1.3.15.
  • New: Duplicate+Track-Select duplicates track
  • New: Duplicate+Clip duplicates the clip
  • New: Double/Double Loop: Duplicate the content of the currently selected clip
  • New: Track scrolls into view when selected
  • New: Support for record arm on master track
  • New: Switch to the next/previous opened project (operate from the Master mode)
  • New: Added transpose feature for Sequencer, Raindrops and Session view (use Shift+Octave Up/Down). Select+Octave transposes in 12 steps.
  • New: Use different colors for note starts and lengths in note and drum sequencer.
  • New: Delete+Pad in drum sequencer now deletes all notes on that note not only 32 bars.
  • New: Quantize is now working as expected. Use Shift+Quantize to set the quantize amount. This menu can now also be opened by long pressing the Quantize button.
  • New: Coloured record button when Shift is pressed (for launcher overdub).
  • Fixed: Scale not updated in sequencers when changed.
  • Fixed: Accent mode not working in raindrop sequencer.
Get it from http://mossgrabers.de/Software/Bitwig/Bitwig.html

Enjoy!

Post

Love you. :D :tu: :phones:

Post

XelaBit wrote:Is it not possible to enter the macro values with Push 2 for Multi-Channel-Devices?
You can toggle between Devices and Parameter-Pages with Shift+DeviceIn for multi output VST plugins.

Post

Amazing!!!
Thank you moss!!! :hug:

Post

Hi Moss,
With the new script I got a frozen display when trying to enter a multi-channel-device.
Don't know what's going wrong here. It is 100 % reproduceable.

Kind regards,
Alexander

Post

Hi Moss,
After some reboots, the issue is flown away :-)

Best regards,
Alexander

Post

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.
camenzr wrote:Hi Moss, hi all you programming gurus,

is it possible to add the following footswitch2 behaviour:
-first push starts recording into the next Clip available on the track selected
-another push stops the recording into the clip.

if this is not possible, would it be possible to add the same behaviour that is standard in push for ableton:
-i manually select which clip i want to record in on the push device.
-the footswitch stops the recording into the selected clip.

i prefer bitwig so much over ableton but since i do a lots of live recordings and looping in my performances and need both my hands to do so, this is a very fundamental feature for me.

Or maybe somebody could help me out with the script lines needed to do this. i'm not into java programming unfortunately.

best regards,
roman
Hey,
I just installed Push4Bitwig today, I think it's great. I was also missing the functionality you were looking for so I tried implementing it myself. I didn't spend a lot of time with the API so I don't know if this is how you should do it, but it works anyway ;) I looked at the surrounding code and tried to write it in a similar way.

You can add this in AbstractViewExtensions.js after the case Config.FOOTSWITCH_2_CLIP_BASED_LOOPER block:

Code: Select all (#)

case Config.FOOTSWITCH_2_CUSTOM:
            var tb = this.model.getCurrentTrackBank ();
            var track = tb.getSelectedTrack ();
            if (track == null)
            {
                displayNotification ("Please select an Instrument track first.");
                return;
            }
            // get selected slot in track or choose the first if none is selected
            var selectedSlot = tb.getSelectedSlot (track.index);
            var slot = selectedSlot == null ? track.slots[0] : selectedSlot;
            var slots = tb.getClipLauncherSlots (track.index);

            if (event.isDown ())
            {
                if (slot.hasContent)
                {
                    // If there is a clip in the selected slot that's playing,
                    // toggle overdub
                    if (slot.isPlaying)
                    {
                        this.model.getTransport ().toggleLauncherOverdub ();
                    }
                    // If the clip is recording, launch it and thereby go into a loop
                    if (slot.isRecording)
                    {
                        slots.launch (slot.index);
                    }

                }
                else
                {
                    // If there is no clip in the selected slot, start recording into it
                    slots.record (slot.index);
                    slots.launch (slot.index);
                    this.model.getTransport ().setLauncherOverdub (false);
                }
            }
Then you also need to register this new option in the Config.js file. In the line that starts with Config.footswitch2Setting = prefs.getEnumSetting add a new string with your preferred name of this option at the end of the comma separated list in the square brackets.

Then below that in the switch statement, add a line that tells Bitwig what to do with your new option. Add this line below the others that look the same:

Code: Select all (#)

case "Custom":       Config.footswitch2 = Config.FOOTSWITCH_2_CUSTOM; break;
Then at the top of the same file add this line below the others to introduce your new case to the script:

Code: Select all (#)

Config.FOOTSWITCH_2_CUSTOM       = 8;
I think that's all you need, at least I don't remember anything more now :)

The way the footswitch behaves now is that it starts recording into a selected empty clip in the selected track that you choose. If your clips are not playing yet they will start after the pre-roll and you'll record into the clip. If your clips are already playing, recording will start at the next measure or however you've set it up globally so it will be in time.

Then when you press the footswitch again, recording will stop at the next measure and the clip will start looping.

If you press the footswitch again and you have still selected a playing clip, then overdub will be toggled so you can record additional midi notes if you want, for audio nothing will happen as there is no real overdub for audio. Pressing it again and again toggles overdub back and forth, so you could add more drum hits for example.

If you press the footswitch while selecting a non-empty clip but nothing's playing, nothing will happen. You could change that but I don't know if you'd want something to happen then.

All right, I hope that helps somebody out there ;)

Julius

Post

Hello

I get an error that i do not have access to run.command:

i tried that:
iMac-de-Remy:~ Remy$ /Users/Remy/Documents/Bitwig\ Studio/Controller\ Scripts/Push4Bitwig/push2display/run.command chmod a+x run.command
-bash: /Users/Remy/Documents/Bitwig Studio/Controller Scripts/Push4Bitwig/push2display/run.command: Permission denied
& i tried this :
iMac-de-Remy:~ Remy$ /Users/Remy/Documents/Bitwig\ Studio/Controller\ Scripts/Push4Bitwig/push2display chmod a+x run.command
-bash: /Users/Remy/Documents/Bitwig Studio/Controller Scripts/Push4Bitwig/push2display: is a directory
Help me please

Post

Ray-Me wrote:Hello

I get an error that i do not have access to run.command:

i tried that:
iMac-de-Remy:~ Remy$ /Users/Remy/Documents/Bitwig\ Studio/Controller\ Scripts/Push4Bitwig/push2display/run.command chmod a+x run.command
-bash: /Users/Remy/Documents/Bitwig Studio/Controller Scripts/Push4Bitwig/push2display/run.command: Permission denied
& i tried this :
iMac-de-Remy:~ Remy$ /Users/Remy/Documents/Bitwig\ Studio/Controller\ Scripts/Push4Bitwig/push2display chmod a+x run.command
-bash: /Users/Remy/Documents/Bitwig Studio/Controller Scripts/Push4Bitwig/push2display: is a directory
Help me please
See here: https://github.com/git-moss/Push4Bitwig ... stallation in the section "Installation on Mac"

Post

I've already read your wiki, i followed your instruction like i quoted in my posts above, but it does not work.

And i don't understand why.

I try the first, the terminal response is "permission denied" & i still have error when i open run.command
I try the second, error again...

EDIT

Ok now it works. in your wiky you say to enter the directory first & enter le line after. But it's the contrary.

I enter le line first, hit space, drag & drop run.commad in the terminal, & hit enter.
Last edited by Ray-Me on Wed Dec 21, 2016 10:52 am, edited 1 time in total.

Post Reply

Return to “Controller Scripting”