Bitwig

moss · Post by **moss** » Fri May 30, 2014 1:54 pm

Another big update is here. Enjoy!

Many thanks to Mike for his support! Until 1.0.9 arrives and brings us new API goodies this version is regarded as feature complete.

http://www.mossgrabers.de/Software/Push/Push.html

# 3.00
* Sequencer Mode now uses Scales.
* Press Device twice to select editing of device parameters, common and envelope parameter, user parameters and macros
* The played keys are lighting red if global or clip recording (does not work if recording clip is outside of the monitored 8x8 matrix).
* Changed behaviour of new button: It creates now a new clip on the selected track and slot, starts play and enables overdub.
* Long press Accent to change fixed accent value.
* Press Shift+Quantize to access the Groove options.
* Double click Play to move play cursor to start of song.
* Footswitch 2 now triggers the new button.
* Small fix for tap tempo.
* Fixed that right/left arrows incorrectly refresh playing pads
* Fixed turning off blinking when switching from Session to other views.

panox80 · Post by **panox80** » Fri May 30, 2014 2:34 pm

need to try...big thanx mate

ThomasHelzle · Post by **ThomasHelzle** » Fri May 30, 2014 3:41 pm

Congratulations!

Cheers,

Tom

giacometti777 · Post by **giacometti777** » Fri May 30, 2014 6:55 pm

First let me say the work on this has been phenomenal and none of us opportunistic lurkers deserve the fruits of your labor.

Second I'll say this update didn't really work for me like the past ones did - unlit pads upon startup, keys not turned green when pressed when they were still sending MIDI etc.

TeotiGraphix · Post by **TeotiGraphix** » Fri May 30, 2014 7:16 pm

Second I'll say this update didn't really work for me like the past ones did - unlit pads upon startup, keys not turned green when pressed when they were still sending MIDI etc.

This sounds weird. I have tested this quite a bit since I use Bitwig and Push at least every other day.

Are these the only problems you are having? We have changed quite a bit of things, maybe you don't have lit pads because an Instrument track is not selected yet?

not turned green when pressed when they were still sending MIDI etc

This sounds suspicious as well dealing with modes. If you could, can you try to reproduce exactly what you are doing to get the controller in this state? Then I can try it myself and try to fix the problem if there is one.

Thanks,
Mike

giacometti777 · Post by **giacometti777** » Fri May 30, 2014 8:02 pm

Annnd it was a shitty USB cable. I can't believe I'm that guy. Thanks!

TeotiGraphix · Post by **TeotiGraphix** » Fri May 30, 2014 8:38 pm

That's good to know.

Jurgen and I basically rewrote all the code and made it pretty modular, the benefit of this is most all functionality has it's "little" place so bugs should really be squashed and stay squashed.

Also why what you were describing sounded "off" for what we have been doing.

Thanks for your support!
Mike

pdxindy · Post by **pdxindy** » Fri May 30, 2014 10:30 pm

I have not touched Bitwig in weeks... once it gets to 1.0.9 I'll try it again. I look forward to buying Bitwig at some point and using it with my Push so your efforts are appreciated!

panox80 · Post by **panox80** » Thu Jun 12, 2014 8:13 pm

thanx for continue to update this script guys...i think BITWIG Team must considered to stycky this post

TeotiGraphix · Post by **TeotiGraphix** » Thu Jun 12, 2014 8:26 pm

Ha, we are not going anywhere man. Jurgen and I switch back and forth on dev so we don't have any nasty javascript conflicts.

Right now I am refactoring some stuff getting ready for 1.1 API updates when it comes. The script should get a l lot of new functionality then.

I have a bunch of ideas for it after we get some more API from Bitwig.

When 1.1 is released, we will have huge flexibility at saving your custom settings, more on this later.

Mike

panox80 · Post by **panox80** » Sat Jun 14, 2014 10:27 am

hi mike
good news from you and for 1.1 update...hope is possible to increase knobs sensibility (coarse note pitcher knob don't work fine yet...i suppose this problem is for other devices)..i can just see add track ,effect,quantize and maybe repeat mode??

cheers

TeotiGraphix · Post by **TeotiGraphix** » Sat Jun 14, 2014 10:37 am

possible to increase knobs sensibility

Until we have Bitwig preferences you will need to do this in the script, right now its in;

Config.js
Config.fractionValue = 1; <- change 1 to a higher amount

I experimented with this and 6-8 gives you a decent live tweak for automation on the knobs.

I have a GIT issue that should add Shift+Turn to do the fine control and non shift to do coarse control. So we will have to configs but eventually you won't even have to adjust these in the script.

add track ,effect

Waiting on Bitwig API

quantize

You mean quantize clip notes right? This is waiting on Bitwig as well for more Clip API.

maybe repeat mode

Has to be done on Bitwig's side, javascript cannot do this correctly, Jurgen already tried.

Mike

panox80 · Post by **panox80** » Sat Jun 14, 2014 11:14 pm

thanx for knobs..i don't know that..i will try

for quantize i mean that

i must to told you a thing...sometimes is impossible to reach device knobs control in device mode...now i don't understand if is a script problem or bitwig or what...but i have only menu of macro,evenlope ecc,and no device knobs control (today is happened on an old project i done)..i think is a bug because it do randomly ...if re-happen i try to make a video to understand better

and for arrows control on push is there some news to have a control like arrows keyboard or, is always an api problem??

cheers and thanx a lot

Alex.

TeotiGraphix · Post by **TeotiGraphix** » Sat Jun 14, 2014 11:30 pm

i must to told you a thing...sometimes is impossible to reach device knobs control in device mode...now i don't understand if is a script problem or bitwig or what...but i have only menu of macro,evenlope ecc,and no device knobs control (today is happened on an old project i done)..i think is a bug because it do randomly ...if re-happen i try to make a video to understand better

We DID change the behavior, actually I rewrote the device handling and display a couple weeks ago. I have never run into a bug with the devices, so I need to understand what is going on with you.

I am in the process of making youtube videos of how to use all the functionality in this script, maybe that will help you to see if its a bug or something I changed that you didn't notice.

and for arrows control on push is there some news to have a control like arrows keyboard or, is always an api problem??

I think you are asking to have different ways to navigate with the arrows, this could be implemented when we get preference saving within the DAW. Right now it needs to stay how it is. But I think I get what you are asking, just remember, there is A LOT going on with mode switching, so we need different flags(preferences) to allow for this type of per user customization with things as big as arrow navigation.

The way it currently functions is how Jurgen implemented it from the start, so we will revisit this.

Mike

sardaukar · Post by **sardaukar** » Wed Jun 25, 2014 1:03 pm

Hey, this integration is great

.

btw..

Does Bitwig provide transport midi note information for the selected track? so that the pads can light up, as a track is being played (per note)...?

Bitwig

KVR Audio

Ableton Push support is here