Bitwig

Raffi · Post by **Raffi** » Wed Mar 18, 2015 8:50 pm

Hey Moss!

The quick shortcuts when press-holding the Master button are really great. The point is I rarely use it because it then always focuses on the on the Master track (because of the first press) and thus lose focus from the track I am working on. Is there any possibility that you can keep focus on current track when press-hold the Master button?

One other thing; would it possible when in Device mode with the 'Device' setting to have the Macros always displayed (only if there are any) when in top level? This would mimick more of the Live behaviour and would save the hassle of pressing device again, then fixed, 'in' button and then macro.

I do have a slight guess it comes down to the API boundaries, right?

Thanks!

Echoes in the Attic · Post by **Echoes in the Attic** » Thu Mar 19, 2015 2:33 am

moss wrote:Both the 8th scale layout and the keyboard (Piano style) mode are now on GitHub for testing.

Cool man! Wish I could test, but Push is packed up again currently.

moss · Post by **moss** » Thu Mar 19, 2015 8:17 am

Raffi wrote: The quick shortcuts when press-holding the Master button are really great. The point is I rarely use it because it then always focuses on the on the Master track (because of the first press) and thus lose focus from the track I am working on. Is there any possibility that you can keep focus on current track when press-hold the Master button?

That's not intended, will check.

Raffi wrote:One other thing; would it possible when in Device mode with the 'Device' setting to have the Macros always displayed (only if there are any) when in top level? This would mimick more of the Live behaviour and would save the hassle of pressing device again, then fixed, 'in' button and then macro.

I thought if I should put some more intelligence into that area (e.g. change to direct parameters if common ones are empty). So far I did not do it because "automatically jumping around" is pretty confusing to users.

Raffi · Post by **Raffi** » Thu Mar 19, 2015 8:49 am

Thanks!

moss wrote:I thought if I should put some more intelligence into that area (e.g. change to direct parameters if common ones are empty). So far I did not do it because "automatically jumping around" is pretty confusing to users.

If the only automatic / dynamic area is the top level. Which purely always prioritizes macros when they are available it should not be too confusing for people. I know it cannot be perfect as Live works more logical in that sense - macros can only appear in a Rack where as Bitwig doesn't need a container for it so it would be less clear to see if you're dealing with the macros or the actual settings. Still (for me) it would work less confusing than the current static way of working.

If you think otherwise, another more easy solution would be to have direct access to the macro page when pressing the Device button so you're always only one step away from getting there.

Food for thought..

moss · Post by **moss** » Thu Mar 19, 2015 9:52 pm

Raffi wrote: The quick shortcuts when press-holding the Master button are really great. The point is I rarely use it because it then always focuses on the on the Master track (because of the first press) and thus lose focus from the track I am working on. Is there any possibility that you can keep focus on current track when press-hold the Master button?

Fixed on GitHub, please test.

moss · Post by **moss** » Thu Mar 19, 2015 9:54 pm

cedrelo wrote:When i have 10 tracks, and i use Shift + RIGHT ARROW to show the track 9 and 10, it show only track track 9 and 10 then it ask me to select a track and when i select it for example track 9, suddenly it show track 3 to 10 ? Is it a bug ? Is it not possible to show only track 9 and 10 and nothing at the right ?

I tested it: The bank gets automatically adjusted by Bitwig. There's nothing I can do about it.

moss · Post by **moss** » Thu Mar 19, 2015 9:57 pm

cedrelo wrote:Ok it seems to happen with external VST like Dune or Massive, i see in bitwig info window left of the arrangement that none device is selected, and then in push it writes "Please select a Device", and i can't do. The only thing i can do is to click on a device.

I tried with Massive but can't reproduce it. Could you please give a step-by-step description what you are doing? Start with the default project and also note if you execute a function on the Push or with the mouse.

IAmRickyRiot · Post by **IAmRickyRiot** » Fri Mar 20, 2015 4:03 am

Hey Moss I have a quick question. When I'm in the Drum Note View and laying down a pattern with the 16 drum pads, I sometimes mistakenly touch one of the pads that are assigned to create new clips (one of the 16 pads in the bottom right quadrant of the Push). I have big hands so it happens quite often. When I touch one of the pads, the clip that I'm working on in the Arrange View of Bitwig always changes to 1 bar, despite having midi notes already programmed and having the clip at my desired length. Is there any way around those pads not changing the clip length that I already have? It messes with my workflow because I'll be in the middle of laying down a part live in the sequencer and mistakenly hit one of those pads without knowing and will have to go through 3 undo steps to get it back to where it was. Playing live with the smaller pads on the Push causes this to happen on a regular basis and I'm not sure if I can do something to keep it from changing.

Thank you once again for all of your hard work.

Rick

moss · Post by **moss** » Fri Mar 20, 2015 4:25 am

IAmRickyRiot wrote:Hey Moss I have a quick question. When I'm in the Drum Note View and laying down a pattern with the 16 drum pads, I sometimes mistakenly touch one of the pads that are assigned to create new clips (one of the 16 pads in the bottom right quadrant of the Push). I have big hands so it happens quite often. When I touch one of the pads, the clip that I'm working on in the Arrange View of Bitwig always changes to 1 bar, despite having midi notes already programmed and having the clip at my desired length. Is there any way around those pads not changing the clip length that I already have? It messes with my workflow because I'll be in the middle of laying down a part live in the sequencer and mistakenly hit one of those pads without knowing and will have to go through 3 undo steps to get it back to where it was. Playing live with the smaller pads on the Push causes this to happen on a regular basis and I'm not sure if I can do something to keep it from changing.

Can I see a photo of your fingers?

For playing live you can use the Play mode: Set the scale to C-Major (default) and enable Chromatic. If you also set the scale layout to "3rd ^" (press the Shift key in Scale mode) you get the same grid layout as in Drum view.

Hope that helps.

IAmRickyRiot · Post by **IAmRickyRiot** » Fri Mar 20, 2015 4:57 am

moss wrote:
IAmRickyRiot wrote:Hey Moss I have a quick question. When I'm in the Drum Note View and laying down a pattern with the 16 drum pads, I sometimes mistakenly touch one of the pads that are assigned to create new clips (one of the 16 pads in the bottom right quadrant of the Push). I have big hands so it happens quite often. When I touch one of the pads, the clip that I'm working on in the Arrange View of Bitwig always changes to 1 bar, despite having midi notes already programmed and having the clip at my desired length. Is there any way around those pads not changing the clip length that I already have? It messes with my workflow because I'll be in the middle of laying down a part live in the sequencer and mistakenly hit one of those pads without knowing and will have to go through 3 undo steps to get it back to where it was. Playing live with the smaller pads on the Push causes this to happen on a regular basis and I'm not sure if I can do something to keep it from changing.
Can I see a photo of your fingers?

For playing live you can use the Play mode: Set the scale to C-Major (default) and enable Chromatic. If you also set the scale layout to "3rd ^" (press the Shift key in Scale mode) you get the same grid layout as in Drum view.

Hope that helps.

As you wish sir...

That definitely does help. I'll keep all of my live programming to that page. I appreciate your quick response. Now back to banging on this thing

moss · Post by **moss** » Fri Mar 20, 2015 6:55 am

IAmRickyRiot wrote: As you wish sir...

Looks quite suitable to me but you have to use the 5 pointy ends not the whole thing at once

Raffi · Post by **Raffi** » Fri Mar 20, 2015 8:02 am

moss wrote:
Raffi wrote: The quick shortcuts when press-holding the Master button are really great. The point is I rarely use it because it then always focuses on the on the Master track (because of the first press) and thus lose focus from the track I am working on. Is there any possibility that you can keep focus on current track when press-hold the Master button?
Fixed on GitHub, please test.

Working perfectly now, thanks!

svervs · Post by **svervs** » Fri Apr 03, 2015 12:36 am

A huge thanks to the developers for the time and work put into bringing this to life … I bought a Push just because of this. Thanks!

The only thing I was "missing" so far was a bit of Bitwig feel, when it comes to colors.
So I gave it a go and looked into those .js files, and with some "Find&Replace" + copypaste I actually managed to come up with a more Bitwig styled color coding. As It turned out better than I expected, I thought I just leave it here for anyone to have a look, and as a discussion starting point for a Bitwig theme.

BUT beware: I have no idea how javascript or this Github stuff works, so this only meant as a test to see if it could work.

I tried to stay within the BW color coding as much as I could, e.g.:
Orange for stuff that’s somehow ON or fixed.
Blue for things that change.
White/lighter grey for selected elements.

Unfortunately, the top row buttons and grid section seem to be limited to much less colors than the pads. Is this hardware related, or did I miss something here?

Below are are some stills.

Video:

The files:
https://dl.dropboxusercontent.com/u/168 ... Colors.zip

Of course I'm hoping to see this one day on startup ...

Happy Easter.

moss · Post by **moss** » Fri Apr 03, 2015 7:17 am

svervs wrote:The only thing I was "missing" so far was a bit of Bitwig feel, when it comes to colors.

Nice orange

svervs wrote:Unfortunately, the top row buttons and grid section seem to be limited to much less colors than the pads. Is this hardware related, or did I miss something here?

Yes, it's a limitation of the hardware.

cedrelo · Post by **cedrelo** » Fri Apr 03, 2015 5:04 pm

moss wrote:
svervs wrote:The only thing I was "missing" so far was a bit of Bitwig feel, when it comes to colors.
Nice orange

svervs wrote:Unfortunately, the top row buttons and grid section seem to be limited to much less colors than the pads. Is this hardware related, or did I miss something here?
Yes, it's a limitation of the hardware.

Very nice!!!!

Hi Moss,

Do you plan to include these colors modifications in your code in github?

Thanks

Bitwig

KVR Audio

Ableton Push support is here