Ableton Push support is here

[stamp]

- Stopping clips by pressing stopclip button and then the top row of buttons works, but wouldn't it be more intuitive to allow holding stop clip and pressing a clip?

Good idea.

Please don't do that. What if the clip you want to stop is outside the grid? You have to scroll the grid to stop it?

Make the stop button work in momentary fashion like in Ableton, instead.

- The big red line that keeps appearing (in session view) is confusing me. I realise it means the track is armed for recording but still finding it disruptive on my eyes and brain. It looks like a row of clips. Is this red line really needed? what purpose is it serving?

Hmm, that's how it is also with Ableton.

I Ableton when you switch to session the track that is armed is automaticaly unarmed. The red line appears only if you arm the track from inside the session view.
Would be nice to have this mechanism also in Bitwig.

- I think double-tap StopClip to stop ALL clips would feel intuitive.

Anopther good idea.

I think shift+stop button wuold work better. And it will avoid accidental stopping of all clips

- duplicate clip - is this possible without having to go into the session view? - Delete clip - is this possible without having to go into the session view?

No. How would you want to trigger that?

Simply pressing duplicate or delete when you are in note mode like in Ableton?

- after *holding* quantise, could you please make it return to the mix/previous view upon tapping it again?

Good idea.

Why not make it work in a temporary fashion?

- sometimes i press overdub to record the sounds i am jaming with - but infact the wrong track is selected in bitwig so it records into the wrong clip. Maybe thats user error, but very frustrating. Is there a way to stop this happening?

I tried to make the track follow the clip but that was buggy and caused more problems than it solved. I need to check that again if might work now.

I think that should be fixed from inside Bitwig. In Ableton when you change track selection it selects the relevant clip/cell in the track, even when doing it via mouse. In Bitwig clip selection doesn't follow the track selection. I allready requested this a couple of times. Perhaps if you, moss, request this they'll listen.

Cheers!

[stamp]

I know it doesn't sound cool, but why don't you simply copy the way the script works in Ableton and than improve on that? If there's something that Ableton did right that is the Push script.
It's super intuitive. Only thing that can be improved in Ableton is the device mode. In Bitwig there's no limit to the parameter of a vst you can control (in Ableton only 128). I would build on that, make it the strong point of the Bitwig script.

[askewd]

There are some good suggestions here. I am genuinely excited about where this can go, especially if Moss is working closer with the bitwig team (screen software built direct into bitwig etc). This is exciting.

Stamp - what do u mean about the stop clip thing? How do you stop clips you can't see? And what is wrong with being able to press stop+clip to stop the clips you can see? Just as an additional method...

Best
Dale

[askewd]

I tried to make the track follow the clip but that was buggy and caused more problems than it solved. I need to check that again if might work now.

I agree with stamp that it needs fixing at bitwigs end. (as I'm sure Moss agrees too)

However in the meantime... Im pretty sure Thomas overcame this issue when building my MPD script. Maybe worth asking Tom what the method was & whether it would be easy to code into the push script.

Best
Dale

[moss]

Now it's the time for an official release after we celebrated the Bitwig Studio 2.0 this week:

#8.00
Requires Bitwig 2.0.

• New: New track details mode with option to set track color (keep Select pressed)
• New: New layer details mode with option to set layer/drum pad color (keep Select pressed)
• New: Clip mode
  • Keep Delete pressed and touch 8th knob to reset the accent.
  • You can set the clip color
• New: Basic version of 64 pad drum view (enter drum mode, keep Shift pressed and then press 4th scene button).
• New: Press "Add Device" to add a device after the currently selected one
• New: Press Shift+"Add Device" to add a device before the currently selected one
• New: Browser
  • Press Shift+Browse to cancel browsing
  • Rearrangement of browser layout
  • New: The browser filter columns can be hidden in the settings
  • New: Press Delete + touch knob to reset filter
  • New: Change the tabs of the browser with the left/right cursor buttons (especially useful with the Sampler)
  • New: Hold Browse and select a pad in Session mode to browse for clips
• New: Push 2: Modulation of parameter values is now displayed (Push2Display updated to support this)
• New: Preference to reverse the behaviour of the record and overdub functions
• Fixed: Scrolling with cursor keys could lead to endless scrolling
• Fixed: On Screen parameter notification for empty parameter (displayed ":")

Known issues (due to API bugs):

• The groove parameters are broken
• The metronome volume cannot be adjusted and its display is weird
• Preset scrolling is very sensitive

[pboy]

Thank you, Moss! I've been struggling today with hardly being able to use my Push as usual with BWS2, so this is wonderful!

[pboy]

I seem to be having trouble with the v2.0 scripts from the github.

Script loads up and my push 1 screen has the correct data from whichever project, but the rest of the controller is dark and unresponsive.
Also with github script, BWS cannot auto-detect my controller. This has been going on for the last couple of weeks. When beta was freshly out the 2.0 github script at that time was working fine.

No errors in console.

If I load up the stable 1.3.15 script back into bws2.0 and everything works great with no issues. auto-detect is fine too.

Can I help troubleshoot this in any way?

Not sure, what's going on. However, I was pretty busy this week and could not even test with the final 2.0. I will try to push out an "official" release over the weekend.

Me too! I'm having the same issue as lokid, with script #8.

[moss]

Me too! I'm having the same issue as lokid, with script #8.

- Remove Push controller from Bitwig.
- Make sure to delete all Push scripts from controller folder
- Unpack v2 version again
- Retry.

[codec17]

Moss i cant see the colors of pads because of the sun here!

Thank you so much again!
I guess when in 64 pad mode auto-select drum -> channel isnt working?
Yet?
Or not possible?
Not that of a biggy btw.. Just wondering.

[moss]

I guess when in 64 pad mode auto-select drum -> channel isnt working?
Yet? Or not possible?

I guess I simply forgot that one

[askewd]

Hey Moss. Great work on the v8.0 release. I've spent a few hours again today learning the BWPush2 and i have some more thoughts, bugs, questions and suggestions. SORRY THESE MESSAGES ARE A BIT LONG AT THE MOMENT!



64 Pad mode
Suggestion - Would it be possible to make playing notes flash like in 4x4 drum mode?
Bug - In 64 drum mode, pressing octave button up/down moves the lights around but then things go whack. Pads don't play etc. I think the lights are in the wrong places.

Suggestion - Could you please allow the 'select+cell' thing to work in 64 pad mode like it does in 4x4 mode?


Editing modes
bug/suggestion - Flipping the shift+record button behaviour in options reverses record but currently does not flip Shift+Automate button. It would make much sense if the automation button got flipped too

I'm still having frustration trying to delete stuff. Hope bitwig adds ability to delete a track or a clip consistently. My preffered method would be:

- delete a device sugesstion - DELETE + DEVICE NAME (under screen) whist in Device Mode.

- delete a clip (or simply clear all the notes from a clip) from edit mode : suggestion DELETE + STOPCLIP. [Is there currently any way to 'clear' a clip?]

- delete track suggestion - DELETE + TRACK NAME (underscreen) in Mix Mode



Browser
bug/suggestion - in the browser, if filters are hidden, it's impossible to get 'out of ' the device presets when looking for a new sound, ie to select presets from a different device. For example i only use collections filter and i have some nicely organised collections such as "Drum Kits" "Pianos" etc. So my browsing is very simple - 1) select a collection 2) select a preset. Easy. The problem is that it only works nicely the first time. Next time i press browse i only see presets related to that device. I need a way of changing device back to 'everything' WITHOUT having to enable that filter. Could you maybe program it so that it automatially selects 'everything' if no filters are enabled? (hope that made sense?) this is a key one for me.

Drum Mode
Bug - Changing the octave up/down button often results in the drum pad mode not working correctly. Either playing wrong sounds, or no sounds. Also in Bitwig it looks like the 'zone' is focused in the wrong place.

Suggestion - Selecting a drum cell with Select+Pad works really nicely. I also noticed that if you then press PAGE <   it takes you into the main parameters pages for that drum cell, which is great. But can i please suggest an additional way to enter that menu? - by pressing the drum cell selector button under the display?  This would feel very intuitive i think. (let me know if you don't know what i mean and i'll send you an image.)

Session Mode

Gripe - In session view it's driving me crazy how it starts recording if u click on an empty space. I could live with it making a clip, but that continual recording thing is annoying and so easy to accidenly start. Could it be made harder to accidently record? or the option for it to just create a new clip instead?

Gripe - Surely there has to be an easier way to stop clips?

General workflow issues/ideas

Could you please make it so that Duplicate button duplicates the current clip when in edit modes as well as session mode ?

Duplicate clip overwrites the one after it - even if there is content . Is there any ability to "copy & paste" clips instead, or duplicate 'to end'? (else you could easily accidently overwrite clips).

in drum mode, If you try to draw notes into the grid on a track before you've pressed 'new clip' it records onto the wrong place or doesn't record at all. Maybe an idea would be to detect if no clip present, and automatically do a 'new clip' if none found when you start adding notes...

___

Overall on day 3 of owning push and I am happy and excited for the possibilities it offers. Imo right now there are just a few too many issues to use it as i'd hoped, but i'll keep offering my feedback and suggestions and bugs as i find them and i'm sure it will soon get to that level. I think we all want the same thing - for it to be awesome!!

Best
DALE








 

[stamp]

Imo right now there are just a few too many issues to use it as i'd hoped [...] I think we all want the same thing - for it to be awesome!!

Exactly my thoughts. I don't like repeating myself but as I allready said the Ableton implementation is the most intuitive. I don't want to dismiss moss' work. He's is doing a fantastic job for the comunity (and all for free!).
That said there are some areas where the Bitwig script is superior to Abletons and areas where, with a little bit of thought, Abletons implementation could even be laughable (Abletons device mode feels really like a missed opportunity).
The thing I love the most in Ableton is the fact that the controller is divided in two logical areas: The screen and the grid.
In Ableton the arrows are tied to the grid and only to the grid. They work always in the same way indipendently of the screen mode:
when in session mode the arrows move the 8x8 grid up/down left/right, and when in note mode they change the clip/slot selection (selecting a clips selects the corresponding track). They do only this two things. Simple and straightforward.
In Bitwig the arrows are a mess and this makes the navigation of your set extremly fiddly.
I use Push 1.

Cheers

[KazRemark]

I just installed the new scripts for my Push 2 for use with Bitwig 2. Unfortunately, when I launch Run.Command to start push2display, I get an error that it can't be run because I don't have access privileges. Anyone else experiencing this on MacOS.

[askewd]

I just installed the new scripts for my Push 2 for use with Bitwig 2. Unfortunately, when I launch Run.Command to start push2display, I get an error that it can't be run because I don't have access privileges. Anyone else experiencing this on MacOS.

I think it's quite common.

Open terminal
Type "chmod a+x " (don't press enter yet)
Then drag your "run.command" file on to the terminal window & drop it just after that last command (on same line).
Then press enter.

Should solve it

[moss]

I just installed the new scripts for my Push 2 for use with Bitwig 2. Unfortunately, when I launch Run.Command to start push2display, I get an error that it can't be run because I don't have access privileges. Anyone else experiencing this on MacOS.

https://github.com/git-moss/Push4Bitwig ... ion-on-mac