Hi moss, one quick suggestion I hope you can implement: can you allow us to define the background color of the "selected" track/device chain in push2display's control panel?
I ask because in Volume mode, where all tracks are displayed, it's actually very difficult to see which track is selected. The Push 2 itself doesn't help because the brightness of the LED on the track-selector button is only slightly brighter on the selected track. You also have an algorithm where you increase the brightness of whatever the user defines as the background color, on the selected channel. But if we could either define the color, or have a slider to make this contrast more pronounced, that would be amazing. I'm using #1a1a1a as the background color and the selected track is very difficult to determine.
p.s. I still can only set the background color to the config file, all my other custom color selections don't save for some reason, even though I always hit "save". I would just define in the .config file manually, but I can't tell which color format the file is using as it's not 6 digit RGB hex values.
Thanks!!
Ableton Push support is here
-
- KVRian
- 1199 posts since 10 Sep, 2014
Hi moss,
good job on the script. It feels really solid and responsive.
some feedback on the script:
Device navigation is nice. Pressing a track select button to enter inside a track/device is a nice touch. Hold a button to go up the hierarchy is not so nice; it slows things really down when you have to go up 5/6 levels or so. What about a dedicated button in the track state button row that goes up one level when you press it and to the top device level (mind you not to volume mode) when you hold it?
When in note/sequencer mode hold the session button to engage the momentary function doesn't work anymore.
Parameters in clip mode behave erratically: loop parameters don't land on integers (in this case 1.0.0, 3.2.0, 6.0.0, 8.2.0 etc) and accent amount changes in steps of 10%.
good job on the script. It feels really solid and responsive.
some feedback on the script:
Device navigation is nice. Pressing a track select button to enter inside a track/device is a nice touch. Hold a button to go up the hierarchy is not so nice; it slows things really down when you have to go up 5/6 levels or so. What about a dedicated button in the track state button row that goes up one level when you press it and to the top device level (mind you not to volume mode) when you hold it?
When in note/sequencer mode hold the session button to engage the momentary function doesn't work anymore.
Parameters in clip mode behave erratically: loop parameters don't land on integers (in this case 1.0.0, 3.2.0, 6.0.0, 8.2.0 etc) and accent amount changes in steps of 10%.
-
- KVRian
- 1199 posts since 10 Sep, 2014
Are you going to improve the ergonomics some more? In this case I have a lot of cool suggestions especially to improve the live performance espect and the device mode.
Let me know!
Cheers!
Let me know!
Cheers!
-
- KVRist
- 34 posts since 18 Feb, 2017
I'm not moss (unfortunately) but I'm definitely interested in these! I made the mistake of watching some Ableton Push 2 tutorials because I wanted to understand the workflow (as it compares to Maschine etc. for sketching ideas) and I found myself wishing I hadn't because there are some things that just don't work in Bitwig (due to API limitations).stamp wrote:I have a lot of cool suggestions especially to improve the live performance aspect and the device mode.
I still find moss' work extremely usable and well thought out, though, but I am also hoping they continue opening up the API to allow it to approach Ableton-levels of integration.
I do plan to use Bitwig in a live setting, within the year. What improvements did you have in mind? (anything to do with clip-stopping?)
-
- KVRAF
- Topic Starter
- 4868 posts since 13 May, 2004
Hi Netsu, libusb is used in the push2display application to drive the Push 2 display. The communication between Bitwig and push2display is done with a proprietary protocol over UDP.Netsu wrote:Hey Moss, I don't have a push yet, but I see that it uses libusb to control the display. Is it possible to connect to the display interface from Bitwig script level using that library?
-
- KVRAF
- Topic Starter
- 4868 posts since 13 May, 2004
Please check if the config file (or the folder in which it is located) is not write protected.pstare wrote:p.s. I still can only set the background color to the config file, all my other custom color selections don't save for some reason, even though I always hit "save".
-
- KVRAF
- Topic Starter
- 4868 posts since 13 May, 2004
Both is fine but it is easier to track on GitHub.pstare wrote:Also: do you prefer that bug reports be posted here, or in Github Issues?
-
- KVRAF
- Topic Starter
- 4868 posts since 13 May, 2004
Feel free to post any idea you have!stamp wrote:Are you going to improve the ergonomics some more? In this case I have a lot of cool suggestions especially to improve the live performance espect and the device mode.
Let me know!
-
- KVRist
- 34 posts since 18 Feb, 2017
I have checked both, and I just did a chmod a+w on both the config file and the folder it was in (push2display), and it makes no difference. It still only saves my font, text color, and background color. Nothing else. This is on macOS Sierra.moss wrote:Please check if the config file (or the folder in which it is located) is not write protected.pstare wrote:p.s. I still can only set the background color to the config file, all my other custom color selections don't save for some reason, even though I always hit "save".
-
- KVRian
- 1199 posts since 10 Sep, 2014
Ok! Here we go!
@Moss, in all this suggestions there aren't esoteric feature requests (so shuold be all doable).
Every suggestion here is intended to speed things up and making the Push experience smoother both for live perfomance and studio use (I'm a Push 1 user).
It would be nice if you could comment on this.
In any particular order (all equally important I think):
1. Note button: when in note mode press to arm the selected track, note-
button blinks. Press again
to unarm. Hold to enter note view menu.
2. Device mode:
Track state buttons*:
1 - turn device on/off
2 - show/hide vst gui
3-6 - direct access to the first 4 groups of 8 parameter banks. This way any parameter, even of
complex vst's with up to 512 parameters, is always only to button presses away. (That would
be a tweakers dream)
7-8 - prev/next device/group of parameter banks (useless to move from one page to the other as is now imo, but you can put an option for this in the script settings, since we have the 4 direct access buttons)
In/out buttons: go down/up the device hierarchy (I find this a lot faster then it is now. You can keep both methods). Hold the out button to go to the top-level
device (not the volume view!).
* to access show macro/expand device hold the Device button
3. Left/Right arrows:
In note mode: change always track selection in any display mode (even in device mode) when
the grid is in note mode.
In Session mode: move the grid left/right (as what happens when u press Up/Down buttons).
They don't change track selection!
4. Give all these buttons a momentary function:
Volume, Pan& Send, Track, Clip, Mute/Solo/Stop, Scales, Session,
Quantize, Fixed Lenght (Automation is already momentary).
You can set the delay time in ms in the script settings.
5. In Ableton when you press the stop button in volume mode the track
state buttons become red (only if there is something playing in that track
otherwise they are off), same as the mute/solo buttons.
6. When in session mode the track state buttons keep their function
independently of the display mode: they always mute/solo(/Stop) tracks.
this does not happen in device mode. Can we loose the track select
button functions of device
mode and have mute/solo(/Stop) when in session mode, instead.
7. Make the knobs in Browse mode less sensitive.
8. Raise the delay time of the 2 small knobs and the volume knob
9. Visual metronome (don't know if this is possible):
When in note mode the scene launch button duobles up as a visual
metronome synced with the timeline. Every button is one bar. Since the buttons are
always green/yelllow they blink red in this fashion: 1-2-3-4 next button. Your recordings will always start in the right spot and it's cool to watch, too!
10. Store most used scales:
In scale mode select a scale, hold one of the scenelaunch buttons until
display says "Scale stored". In note mode press (hold if you implement the
next request) a scene launch button to recall one of 8 saved scales.
11. Launch scenes in Note mode: press the scenelaunch buttons to launch
scenes while in note mode (playing scene is blinking)
@moss I remember that some time ago you wrote you were working on a prototype of a new drum sequencer where we can set leght/velocity/grid offset per step. How is it going?
That's all for now!
Thank you very much for what you're doing for the comunity. Really appreciated!
@pstare and anybody else please tell us what you think!
Cheers!
@Moss, in all this suggestions there aren't esoteric feature requests (so shuold be all doable).
Every suggestion here is intended to speed things up and making the Push experience smoother both for live perfomance and studio use (I'm a Push 1 user).
It would be nice if you could comment on this.
In any particular order (all equally important I think):
1. Note button: when in note mode press to arm the selected track, note-
button blinks. Press again
to unarm. Hold to enter note view menu.
2. Device mode:
Track state buttons*:
1 - turn device on/off
2 - show/hide vst gui
3-6 - direct access to the first 4 groups of 8 parameter banks. This way any parameter, even of
complex vst's with up to 512 parameters, is always only to button presses away. (That would
be a tweakers dream)
7-8 - prev/next device/group of parameter banks (useless to move from one page to the other as is now imo, but you can put an option for this in the script settings, since we have the 4 direct access buttons)
In/out buttons: go down/up the device hierarchy (I find this a lot faster then it is now. You can keep both methods). Hold the out button to go to the top-level
device (not the volume view!).
* to access show macro/expand device hold the Device button
3. Left/Right arrows:
In note mode: change always track selection in any display mode (even in device mode) when
the grid is in note mode.
In Session mode: move the grid left/right (as what happens when u press Up/Down buttons).
They don't change track selection!
4. Give all these buttons a momentary function:
Volume, Pan& Send, Track, Clip, Mute/Solo/Stop, Scales, Session,
Quantize, Fixed Lenght (Automation is already momentary).
You can set the delay time in ms in the script settings.
5. In Ableton when you press the stop button in volume mode the track
state buttons become red (only if there is something playing in that track
otherwise they are off), same as the mute/solo buttons.
6. When in session mode the track state buttons keep their function
independently of the display mode: they always mute/solo(/Stop) tracks.
this does not happen in device mode. Can we loose the track select
button functions of device
mode and have mute/solo(/Stop) when in session mode, instead.
7. Make the knobs in Browse mode less sensitive.
8. Raise the delay time of the 2 small knobs and the volume knob
9. Visual metronome (don't know if this is possible):
When in note mode the scene launch button duobles up as a visual
metronome synced with the timeline. Every button is one bar. Since the buttons are
always green/yelllow they blink red in this fashion: 1-2-3-4 next button. Your recordings will always start in the right spot and it's cool to watch, too!
10. Store most used scales:
In scale mode select a scale, hold one of the scenelaunch buttons until
display says "Scale stored". In note mode press (hold if you implement the
next request) a scene launch button to recall one of 8 saved scales.
11. Launch scenes in Note mode: press the scenelaunch buttons to launch
scenes while in note mode (playing scene is blinking)
@moss I remember that some time ago you wrote you were working on a prototype of a new drum sequencer where we can set leght/velocity/grid offset per step. How is it going?
That's all for now!
Thank you very much for what you're doing for the comunity. Really appreciated!
@pstare and anybody else please tell us what you think!
Cheers!
-
- KVRer
- 3 posts since 13 May, 2016
Hi All,
Does anyone know if it is possible to use microtonal scales in Bitwig? Seems like the flexible note layouts on Push/Push2 in Bitwig would be a great way to work with scales that divide the octave into more/less than twelve notes.
Sorry if this has been discussed already, but I am just starting to dig my way through all this awesome work that everyone has done.
Thanks!
Does anyone know if it is possible to use microtonal scales in Bitwig? Seems like the flexible note layouts on Push/Push2 in Bitwig would be a great way to work with scales that divide the octave into more/less than twelve notes.
Sorry if this has been discussed already, but I am just starting to dig my way through all this awesome work that everyone has done.
Thanks!
-
- KVRist
- 413 posts since 16 Mar, 2013 from BLN
Couldn't find any discussions about it, but hopefully I'm not alone ...
In "Flipped Session View" on Push1, the second row button don't launch scenes anymore.
Does anyone else miss this?
I've really been trying to get used to it, but it's just so counter intuitiv not being able to do this.
In "Flipped Session View" on Push1, the second row button don't launch scenes anymore.
Does anyone else miss this?
I've really been trying to get used to it, but it's just so counter intuitiv not being able to do this.
-
pentium4powerhouse pentium4powerhouse https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=391290
- KVRer
- 2 posts since 3 Jan, 2017
Hi @Moss,
Loving the scripts
Just wanted to say, I really love playing the Push (Push 1, in my case) in note mode, Chromatic, 4th^.
My problem is I always get thrown off by the scale LEDs. I could really use either
- A chromatic mode where the only LEDs lit are the octave LEDs
or
- Chromatic mode with Octave, fifth, and 4th LED's lit.
I would also be interested in editing the script myself, but I'm not sure where to start or how to edit the extension
Thanks for the awesome scripts, just a little feedback for you to consider.
Loving the scripts
Just wanted to say, I really love playing the Push (Push 1, in my case) in note mode, Chromatic, 4th^.
My problem is I always get thrown off by the scale LEDs. I could really use either
- A chromatic mode where the only LEDs lit are the octave LEDs
or
- Chromatic mode with Octave, fifth, and 4th LED's lit.
I would also be interested in editing the script myself, but I'm not sure where to start or how to edit the extension
Thanks for the awesome scripts, just a little feedback for you to consider.