Bitwig

TeotiGraphix · Post by **TeotiGraphix** » Sat May 03, 2014 7:34 pm

p.s. do you think is possible to have the control like ableton for all device parameter (so use little arrow to select banks)and select tracks with only arrow keys instead press track or device then move?

So you are saying, in Device mode, once you get to the end of the current tracks device chain, it selects the next Track and that tracks first device bank correct?

Edit: All this happening while using the in/out buttons

Mike

panox80 · Post by **panox80** » Sat May 03, 2014 8:08 pm

thank you for fast reply
for device parameter i slove now,,arrow are inverted from push button icon

for other thing i try to explain better
try to navigate with keyboard's arrow key in the mix session,you can see the empty clip that follow the selected track,if i move with push arrow keys empty clip don't follow the selected track...in ableton work like i move with arrow keys on keyboard

another one..i see that is possible use push arrow to navigate browser...do you think is possible at this software status map for exapample "select button" like "enter key",or we need to wait modular engine? if it's possible,we could load device from push

Alex

TeotiGraphix · Post by **TeotiGraphix** » Sat May 03, 2014 8:24 pm

for device parameter i slove now,,arrow are inverted from push button icon

Moss and I had a conversation about this, I actually brought it up that is seemed backwards but, then he pointed out the obvious that the left button goes left and the right button goes right through the device chain. So we are keeping it that way, just ignore the icons.

for other thing i try to explain better
try to navigate with keyboard's arrow key in the mix session,you can see the empty clip that follow the selected track,if i move with push arrow keys empty clip don't follow the selected track...in ableton work like i move with arrow keys on keyboard

Ah yes I think I understand, when in device mode the current implementation is arrow keys move through the devices in the current track's device chain. I will have to bring this up to Moss and see what he has to say about, or if he wants to reply.

Anything with the Browser is not implemented by Bitwig yet. We can all be pretty sure that Bitwig is going to allow browsing and instrument/effect insert. When the API is available we can add that in.

Mike

moss · Post by **moss** » Sun May 04, 2014 7:26 am

Today is the day to release V2.0

Get it from: http://www.mossgrabers.de/Software/Push/Push.html

The manual is now in a Wiki: https://github.com/git-moss/Push4Bitwig/wiki

Many changes:
https://github.com/git-moss/Push4Bitwig/wiki/Changes

* Added indication on editable parameters, macros, volumes, etc.
* Added macro control (press Device twice)
* Shift+Record toggles launcher overdub.
* Stop: Keep pressed and select one of the 8 tracks. The playing clip on that track stops.
* Shift+Stop: Stops all playing clips.
* Sequencer Mode:
* Use the Scene buttons to change the grids resolution.
* Session Mode:
* Hold _New_ button and press an empty slot (pad) to create a new clip. Before choose the length by holding the _Fixed Length_ button.
* If Select is pressed when pressing a pad it is only selected and not started.
* Shift + 1st row button returns track to arrangement sequencer.
* Improved track selection on bank change.
* Improved display and pad redraw performance.
* Fixed lighting of Mute and Solo buttons.
* Fixed hang after script restart.

abique · Post by **abique** » Sun May 04, 2014 4:15 pm

Well done!

irtimid · Post by **irtimid** » Sun May 04, 2014 9:18 pm

Nice one!!

Echoes in the Attic · Sun May 04, 2014 10:32 pm

TeotiGraphix wrote: Anything with the Browser is not implemented by Bitwig yet. We can all be pretty sure that Bitwig is going to allow browsing and instrument/effect insert. When the API is available we can add that in.

Mike

But the Nektar Panorama can already browse and load devices/presets. Isn't it just using the API?

TeotiGraphix · Post by **TeotiGraphix** » Sun May 04, 2014 11:12 pm

When I say Browser, I mean in the public API Bitwig has released, you cannot "Browse" the Browser.

Yes there is API to scroll through presets and categories, that has not been implemented in the script yet.

I thought the OP's question was about the Browser content dealing adding devices, etc.

You bring up a good point though, I need to put this on the feature list.

Thanks,
Mike

Echoes in the Attic · Sun May 04, 2014 11:16 pm

TeotiGraphix wrote:When I say Browser, I mean in the public API Bitwig has released, you cannot "Browse" the Browser.

Yes there is API to scroll through presets and categories, that has not been implemented in the script yet.

I thought the OP's question was about the Browser content dealing adding devices, etc.

I'm pretty sure the nectar can add devices, not just presets though.

TeotiGraphix · Post by **TeotiGraphix** » Sun May 04, 2014 11:21 pm

Ok well its not in the public API, or the Add Track button would have been one of the first moss implemented.

I have even opened up the .jar file bitwig loads in the actual DAW and looked at the controller API in the .class files, there is nothing there for adding tracks.

There is DrumRack api that is undocumented and a Scene interface and a couple others, but that is it.

So if you could actually find things doing that, its news to us and we would love to know the methods and where to access them.

Mike

panox80 · Post by **panox80** » Tue May 06, 2014 6:27 pm

little question guys...is there a way to change colours? especially on sequencer

time ago i tried to edit sequencerview file with colour listed in another file of the script...but not work

thanx

TeotiGraphix · Post by **TeotiGraphix** » Tue May 06, 2014 7:30 pm

We have plans for user configuration down the road when the base implementation is complete.

So that being said, I haven't tried to hack the colors, I have been programming some other functionality.

Are you talking about changing the Red in the sequencer?

Mike

panox80 · Post by **panox80** » Tue May 06, 2014 10:53 pm

no,i mean to colour the back of step (red is nice), or,i'm tryng to understand if is possible to edit sequencerview.js like skindefault.py in ableton, to customize colors in push

SequencerView.prototype.drawGrid = function ()
{
var hiStep = this.isInXRange (this.step) ? this.step % SEQ_NUM_DISPLAY_COLS : -1;
for (var x = 0; x < SEQ_NUM_DISPLAY_COLS; x++)
{
for (var y = 0; y < SEQ_NUM_DISPLAY_ROWS; y++)
{
var isSet = this.data[x][this.offsetY + y];
var hilite = x == hiStep;
push.pads.lightEx (x, y, isSet ? (hilite ? PUSH_COLOR_ORANGE_HI : PUSH_COLOR_RED_HI) : hilite ? PUSH_COLOR_GREEN_HI : PUSH_COLOR_BLACK)

i try to change push pad color from black to blue or green for example...don't work

TeotiGraphix · Post by **TeotiGraphix** » Tue May 06, 2014 11:30 pm

Ah ok.

Well honestly, I don't recommend doing what you are try to do.

I am sure we will have a skin like file for the look and feel of all the modes like in Ableton.

I can add that as a feature request and start to look at how to yank the colors used in modes into some type of prefs class that you could change.

But again, we are adding functionality every other day right now and changing the code where you are isn't recommended.

Mike

moss · Post by **moss** » Wed May 07, 2014 7:10 am

panox80 wrote:no,i mean to colour the back of step (red is nice), or,i'm tryng to understand if is possible to edit sequencerview.js like skindefault.py in ableton, to customize colors in push

The Sequencer is still in a quick prototype state. E.g. one open issue is to put the current scale in the background (white and blue). Therefore I would suggest to wait a little bit longer. However, always feel free to make your own mods

Bitwig

KVR Audio

Ableton Push support is here