Ableton Push support is here

[moss]

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...

The "chmod" command changes the permissions of the start file. You have to run that command once, not add it as an extension to the script execution!

[Ray-Me]

I've edited my post just before you reply. Thanks for your help.

[moss]

New update #7.41:
* New: Smoother value updates
* Fixed: Added missing knob labels in Master mode (Push 2)
* Fixed: Changing discrete direct parameters works again

[stamp]

Hi moss,

so 2.0 is coming. Is there hope we will see some fixes/improvement to the current script before 2.0 drops? I'm not talking about new features but mainly ergonomics.

1. When I'm in sequencer mode (grid) while editing a synth (device mode) that has more than 8 pages of parameters to see parameters of page 9-16 I have to switch to session mode, move to the desired page with the arrows than go back to sequencer. A bit convoluted.
The functions Expand/show Macros/show Parameters can be accessed in two different places while in device mode (from the track state buttons and holding the device button).
Would you be so kind to remove this functions from the track state buttons and replace them with two buttons to move between parameter pages by a factor of 8?
This way we will be able to edit notes and tweak synths or effects with lots of parameter pages without switching modes while the arrows cuold be kept just for moving inside the clip. This way we can also change track focus while in device mode without having to access volume mode when the grid is in Play/Piano mode.

2. Can you make the note button blink when a track is armed? Can you add a shift-note button combo so we can arm/disarm tracks while in device mode without having to enter volume mode, arm track and turn back to device mode to record notes/automation and than again volume mode, disarm track, and back to device mode to keep on tweaking?

3. When pressing the New button a new clip is created, selected and starts overdubbing.
Can you please add a shift+New button combo that creates a new clip, selects clip but does NOT engage overdub?

Imo this little changes wuold significantly improve the feel of the script

Thanks for your time and consideration!

Have a nice sunday!

[moss]

so 2.0 is coming. Is there hope we will see some fixes/improvement to the current script before 2.0 drops? I'm not talking about new features but mainly ergonomics.

My focus is currently on 2.0 adaption but there might also appear some minor changes (2 are already on GitHub). I will not change anything in the devices section since this changes big time in 2.0.

Thanks for your suggestions, which are all good comments and suggestions. Will see what I can do about it.

[stamp]

Well, i see.
May I ask you a cuople of questions?

1. Does 2.0 fix the issue where the grid doesn't update as expected when changing track focus?
2. Does the 2.0 api enable you to activate/deactivate observers?
3. Will we be able to select clip portions like in Ableton? (thus freeing the arrows for other duties when in sequencer mode)
4. Can we expect more advanced sequencing (set velocity/position/lenght per note)?
5. Will clip selection be in sync with track selection?

That was more than a cuople, sorry.
I'm still on the fence between subcribing or stick with Ableton.

Thanks!

[moss]

Well, i see.
May I ask you a cuople of questions?

1. Does 2.0 fix the issue where the grid doesn't update as expected when changing track focus?
2. Does the 2.0 api enable you to activate/deactivate observers?
3. Will we be able to select clip portions like in Ableton? (thus freeing the arrows for other duties when in sequencer mode)
4. Can we expect more advanced sequencing (set velocity/position/lenght per note)?
5. Will clip selection be in sync with track selection?

That was more than a cuople, sorry.
I'm still on the fence between subcribing or stick with Ableton.

Thanks!

There are some bigger changes going on with the API currently, so I cannot really comment. Except, #2 is a yes.

[stamp]

There are some bigger changes going on with the API currently, so I cannot really comment. Except, #2 is a yes.

Well, that's good news. Thanks!

[codec17]

I cant freaking wait to give it a spin moss... Good to hear/read you and bws team already working on it.
Christmas again!

[stamp]

From Github: Shift+New: Like New but without activating launcher overdub.

Nice! thank you!

I hope you consider my suggestion about the Note button...

Cheers!

[twumpy]

Hi again!

I've become a fan of the raindrop sequencer, it's great addition to adding backing melodies. Couple of issues I've encountered (using latest rev. from GitHub)

1. I noticed that when you use octave up/down buttons, it actually shift between tracks instead of octaves.
2. Also, after playing some time with the raindrop sequencer, creating and modifying tracks, and then trying to save Bitwig gives an error "Could not save, too many clips". Haven't experienced it when not using raindrop sequencer, and it requires some time working with it. Trying to use "save as..." crashes Bitwig.
3. Occasionally the raindrop sequencer locks onto a different track/clip. The correct track is armed, and clip chosen with mouse, and it could still be modifying a different clip. Unfortunately I haven't found a pattern how to reproduce this.

(Using Mac with El Capitan).

[moss]

1. I noticed that when you use octave up/down buttons, it actually shift between tracks instead of octaves.

Thanks for reporting! I fixed it and you can get it from GitHub.

2. Also, after playing some time with the raindrop sequencer, creating and modifying tracks, and then trying to save Bitwig gives an error "Could not save, too many clips". Haven't experienced it when not using raindrop sequencer, and it requires some time working with it. Trying to use "save as..." crashes Bitwig.

Sorry, no idea. You should report that (with the crash log) to Bitwig.

3. Occasionally the raindrop sequencer locks onto a different track/clip. The correct track is armed, and clip chosen with mouse, and it could still be modifying a different clip. Unfortunately I haven't found a pattern how to reproduce this.

Weird. Keep trying to find a pattern.

[codec17]

Hi moss.

When in drummaschine edit mode. --> Drumachine track --> Dive into track --> Slap pad to select pad. And then when i go to SOLO mode with push button, it doesnt let me go back to MUTE mode with the push button..?
When go back to tracks it stays that way. It only happens when you dive into a drummachine and switch the mode SOLO/MUTE. (so when not using the drummaschine all is fine)
EDIT: i just discoverd it only happens in NOTE mode so in SESSION mode all is good .


And something i cant remember anymore... (didnt use bitwigs native drummaschine for while )
But lets say ive got a snare on a pad and put an EQ after it, I cant see the EQ device to select it on my push-1 screen? I can select it with mouse on monitor and then it pops up in my push screen.

Hope im clear in explanation. Thanx in advance

[codec17]

deleted

[moss]

When in drummaschine edit mode. --> Drumachine track --> Dive into track --> Slap pad to select pad. And then when i go to SOLO mode with push button, it doesnt let me go back to MUTE mode with the push button..?
When go back to tracks it stays that way. It only happens when you dive into a drummachine and switch the mode SOLO/MUTE. (so when not using the drummaschine all is fine)
EDIT: i just discoverd it only happens in NOTE mode so in SESSION mode all is good .

Good catch! I fixed it on GitHub.

But lets say ive got a snare on a pad and put an EQ after it, I cant see the EQ device to select it on my push-1 screen? I can select it with mouse on monitor and then it pops up in my push screen.

You need to press the "Device in" button again. I just noticed that there seems to be a Bitwig update problem if you dragged the EQ to the pad (then it did not appear). The FX in the FX slot cannot be accessed if that was the question.