Bitwig

TeotiGraphix · Post by **TeotiGraphix** » Fri May 02, 2014 9:49 am

Is there already support for the drummachine and pattern sequencer?

Moss implemented a drumsequencer in a primary state using what he had available with the controller API (press Note twice).

I am tackling the drummachine but I spent a bit of time yesterday taking notes on what I needed to get it even close to what users expect in Live and Bitwig's API doesn't allow for most of the operations yet.

So for the time being it would have the bottom left scroll/play pad, top step sequencer. We can't change clip length or navigate into drummachine devices yet. As well as not being able to change step resolution, so as you can see it would be pretty limited right now.

Mike

Naoleo · Post by **Naoleo** » Fri May 02, 2014 1:07 pm

Yes ! Pattern sequencer like in session in ableton would be really good! This might work for more steps than sequencer what you do now.. Please like in ableton for drum machine ))) Yes!

Naoleo · Post by **Naoleo** » Fri May 02, 2014 5:30 pm

And please add accent button for pads, please with knob for change accent 127 or 95 or 70 like in pxt general - this is will be very good

TeotiGraphix · Post by **TeotiGraphix** » Fri May 02, 2014 5:46 pm

We are still working on the foundation and getting the base stable.

I will add this as a feature request but, this will probably be added when pad touch and double tap etc. are implemented. Once these gestures work, it will be possible to adjust the velocity and gate time of pressed step pads.

Mike

irtimid · Post by **irtimid** » Fri May 02, 2014 7:12 pm

Thanks for your reply & good work TeotiGraphix
Can Push already do the same things as Livid base + bitwig?

TeotiGraphix · Post by **TeotiGraphix** » Fri May 02, 2014 7:26 pm

Hi,

You can read current issues or feature enhancements in the works here;

https://github.com/git-moss/Push4Bitwig ... state=open

You can also check out the closed issues there as well.

The below is a raw HTML help file that is included in moss's download from his site which for now is the stable release;

https://github.com/git-moss/Push4Bitwig ... /Push.html

If you look in the 1.XX list, those are the pending committed features in the next release, everything else works in that feature set.

Download stable zip: http://mossgrabers.de/Software/Push/Push.html

It's up to moss if we will have a stable download available from github. I hope to eventually have a develop branch and the master branch will just mirror what is in the zip file (stable release).

Mike

TeotiGraphix · Post by **TeotiGraphix** » Fri May 02, 2014 10:46 pm

I added a simple wiki for those wondering what the base functionality of the Push script is at the moment.

https://github.com/git-moss/Push4Bitwig/wiki

The wiki will be expanded as new things are added.

There is quite a bit coming up in the next release.

Mike

irtimid · Post by **irtimid** » Sat May 03, 2014 7:51 am

Very exciting

Thanks Mike & Jürgen!

Is it possible to see the correct clip colors on the push?

TeotiGraphix · Post by **TeotiGraphix** » Sat May 03, 2014 8:28 am

Is it possible to see the correct clip colors on the push?

Yes, quite nicely right now in fact(they update instantly when changed in Bitwig as well).

I am using the Push for some "production" right now at the same time testing, nice combination music/testing.

Mike

irtimid · Post by **irtimid** » Sat May 03, 2014 12:12 pm

thats great to hear.
will have to get push now too

Echoes in the Attic · Post by **Echoes in the Attic** » Sat May 03, 2014 1:53 pm

I'm surprised to hear that the Bitwig API is missing so much from Live's scripting. I was under the impression it was going to be more powerful, given that's it's a feature they advertised and Ableton never really talk about their own scripting. Can't change the clip length from hardware? Things like that I thought for sure would be available.

As for the Push script, I'm looking forward to trying it, thanks for your work!

TeotiGraphix · Post by **TeotiGraphix** » Sat May 03, 2014 1:58 pm

It probably will be more powerful but this is 1.0.

I am positive Bitwig has probably 1/3 to 1/2 the API not documented but implemented.

I have seen many "hints" in some code I have looked at about undocumented features such as DrumBank etc that are not in the docs.

With what moss and I are working on with what we have, the Push script does a lot and can already speed up workflow and creativity in Bitwig right now.

This next release adds a lot more to the feature set. Look at 2.0 (unreleased)

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

BTW, to test out the unreleased, for now its master and you can just download the zip from github.

Mike

Echoes in the Attic · Post by **Echoes in the Attic** » Sat May 03, 2014 4:36 pm

My Push is packed up for a while but I have a question - Using Push with Ableton, you can select the device you want to control from the LCD. So for example if you had an instrument and 6 effects after it, you could just select the effect you wanted to control by pressing the button under the device name. You don't have to hit a button 6 times to go over to the effect you want to control. Does it work this way with this Bitwig script? You can see the device names and select the one you want?

Also, is the a method to scroll through parameter pages and see the names of the pages? Or do you have to hit next/previous page? I imagine that would be tough with plug-ins having 20 or so parameter pages.

moss · Post by **moss** » Sat May 03, 2014 5:48 pm

Would like to have it too that way but this is not possible.

panox80 · Post by **panox80** » Sat May 03, 2014 6:22 pm

it seem work fine zip on github..great work guys..really

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?

Bitwig

KVR Audio

Ableton Push support is here