Bitwig

ThomasHelzle · Post by **ThomasHelzle** » Sun Oct 05, 2014 12:15 pm

Interesting. Thanks, I'll add that to my list to check out.

thetechnobear · Post by **thetechnobear** » Sun Oct 05, 2014 1:30 pm

Sorry, never occurred to me to do anything other than drop the instrument on the track

btw, wasn't suggesting anything about coding, its a great piece of work, and bitwig is also a young product, so I thought it may be something a little odd going on.

a couple of thoughts...
a) will there be device selection? i can see you can move the cursor around in the browser, but I cannot find a way to 'accept' it... of course would be nicer if this was on the push display (like abletons browser). Im sure this is on 'your list' already

b) VST, currently you have to assign to 'pages' (sorry not sure what bitwig calls them), will it later be possible to get to the parameters directly?
c) instrument layers... i couldn't seem to find a way to step thru devices/layers on the push.

a bitwig questions...
- is it possible to add selected VSTs to the right click, select instrument on the device rack?
- device mappings, any chance that these can be assigned to devices on a layer (like the knobs can be)

as i said, all really nice... its nice to see some of the limitations of live have already been overcome, and its impressive how well the push is already integrated (even compared to live, which has received high praise)

TeotiGraphix · Post by **TeotiGraphix** » Sun Oct 05, 2014 1:34 pm

thetechnobear wrote:Sorry, never occurred to me to do anything other than drop the instrument on the track

btw, wasn't suggesting anything about coding, its a great piece of work, and bitwig is also a young product, so I thought it may be something a little odd going on.

a couple of thoughts...
a) will there be device selection? i can see you can move the cursor around in the browser, but I cannot find a way to 'accept' it... of course would be nicer if this was on the push display (like abletons browser). Im sure this is on 'your list' already
b) VST, currently you have to assign to 'pages' (sorry not sure what bitwig calls them), will it later be possible to get to the parameters directly?
c) instrument layers... i couldn't seem to find a way to step thru devices/layers on the push.

a bitwig questions...
- is it possible to add selected VSTs to the right click, select instrument on the device rack?
- device mappings, any chance that these can be assigned to devices on a layer (like the knobs can be)

as i said, all really nice... its nice to see some of the limitations of live have already been overcome, and its impressive how well the push is already integrated (even compared to live, which has received high praise)

A: This is a feature request and you can bet they will give us API to do it sooner than later, i don't know if its 1.1 though(doubt it).

B: This is abstracted with the API so having to define them in your own user banks is Bitwig right now. I could see asking them for API to as you say "get all parameters" and we could just list them out by banks of 8. I do like this idea, I will ask about it.

As for the others, Tom I am sure is reading.

Mike

ThomasHelzle · Post by **ThomasHelzle** » Sun Oct 05, 2014 4:09 pm

a.) will probably come at a later date when fully browser access is there.
b.) is currently looked at. Could come in 1.1, but for most more complex VSTs you're far better off with creating parameter pages for the important parameters. VST devs not always name/sort the parameters nicely or logical.

c.) will be available in the 1.1 API but so far looks like a pain to implement logically so you know where you are - at least to me.

d.) no. Probably not in 1.1 either. But it's on the list.
e.) device mappings are per-device by definition while macros can be assigned to everything inside the device and it's slots.

Cheers,

Tom

sardaukar · Post by **sardaukar** » Sun Oct 19, 2014 6:56 pm

Hi, is anyone aware of a way to adjust the pad sensitivity...

fxy · Post by **fxy** » Wed Oct 22, 2014 4:43 pm

Hey, thanks for this nice script.
I see a lot of potential here, because we can´t really change the script for ableton.

One feature request for ableton always was to lock the notes grid to activated channels, so the activated instruments would still be playable live (with visual grid) even if i would navigate into e.g. an effects channel to tweak some devices.
At the moment, if you only use the notes grid to play several synth, you need another controller to tweak devices on other channels. It would be huge thing!

Do you think it´s possible to implement?

Thanks!!!

TeotiGraphix · Post by **TeotiGraphix** » Wed Oct 22, 2014 4:50 pm

fxy wrote:Hey, thanks for this nice script.
I see a lot of potential here, because we can´t really change the script for ableton.

One feature request for ableton always was to lock the notes grid to activated channels, so the activated instruments would still be playable live (with visual grid) even if i would navigate into e.g. an effects channel to tweak some devices.
At the moment, if you only use the notes grid to play several synth, you need another controller to tweak devices on other channels. It would be huge thing!

Do you think it´s possible to implement?

Thanks!!!

It's definitely possible with API but how it would be implemented with the current script wouldn't be straight forward.

Right now all the code is tied to the cursor track in the display and knobs. It might be as easy as creating another mode like Device right now and assign channels to the lower buttons to toggle between the focus track being edited.

This is a great idea and i will be sure to add it to the feature requests, either moss or i will see if its possible.

Note for all; Right now the script on GITHub is 1.1 beta5 and is in huge flux with device navigation among other things, so its is going to be a bit before any release happens that is stable.

Mike

taoyoyo · Post by **taoyoyo** » Wed Oct 22, 2014 6:38 pm

Just wanted to add that I'm really njoying this script with BWS and Push... am interested to see how it develops as the API expands (browser capabilities similar to that used in Live would be top of my list).

Also... not sure if this is a reported issue but the script does not 'close' on Push for me (OSX, 10.9.5) after quitting Bitwig... anything shown on Push before quitting remains (I have to switch Push off and on manually).

Nice work guys!

TeotiGraphix · Post by **TeotiGraphix** » Wed Oct 22, 2014 6:48 pm

taoyoyo wrote:Just wanted to add that I'm really njoying this script with BWS and Push... am interested to see how it develops as the API expands (browser capabilities similar to that used in Live would be top of my list).

Also... not sure if this is a reported issue but the script does not 'close' on Push for me (OSX, 10.9.5) after quitting Bitwig... anything shown on Push before quitting remains (I have to switch Push off and on manually).

Nice work guys!

Browser functionality will be there when the APi is, right now 1.1 does not allow for Browser navigation.

The quit bug seems to be Bitwig. The controller code has full implementation for and exit() and flushes buttons and display. I know I have the same issue when i am working on it.

Mike

ThomasHelzle · Post by **ThomasHelzle** » Wed Oct 22, 2014 7:23 pm

Yeah, Browser access would be on my list as well.
And yes, the exit() function is broken for anything more involved than deleting a variable.

Cheers,

Tom

TeotiGraphix · Post by **TeotiGraphix** » Wed Oct 22, 2014 8:05 pm

ThomasHelzle wrote:Yeah, Browser access would be on my list as well.
And yes, the exit() function is broken for anything more involved than deleting a variable.

Cheers,

Tom

I remember reading about that. Yeah its probably as simple as the process is garbage collected before the script interpreter can send all the MIDI messages to the controller, the Push has at least 300+ messages to do a proper clear.

Mike

ThomasHelzle · Post by **ThomasHelzle** » Wed Oct 22, 2014 8:30 pm

Yeah, something like that. And it's not trivial to get that right so it had to wait for 1.1 being done...

Cheers,

Tom

ansolas · Post by **ansolas** » Thu Oct 23, 2014 11:59 am

The manual says to put the folder here under OSX:

~/Bitwig Studio/Controller Scripts/

Shouldn't it be:

~/Documents/Bitwig Studio/Controller Scripts/

Anyways I tried both, but the controller do not show up ?
https://www.dropbox.com/s/6foewmb2u19a6 ... 5.png?dl=0

In the Scripting Console I get:
"
Can't find method com.bitwig.base.control_surface.ScriptScanningHost.defineController(string,string,string,string,string). (Push.control.js#17)
"
At line 17 we find:
host.defineController ("Ableton", "Push", "4.0", "D69AFBF0-B71E-11E3-A5E2-0800200C9A66", "Jürgen Moßgraber & Michael Schmalle");

Removing the last argument fixes the error above and lets me add Push !

But now I get this error:

Code: Select all

TypeError: Cannot find function getPreferences in object 
com.bitwig.flt.control_surface.intention.sections.HostSection@4df90256. (Config.js#44)

TeotiGraphix · Post by **TeotiGraphix** » Thu Oct 23, 2014 12:15 pm

ansolas wrote:The manual says to put the folder here under OSX:

~/Bitwig Studio/Controller Scripts/

Shouldn't it be:

~/Documents/Bitwig Studio/Controller Scripts/

Anyways I tried both, but the controller do not show up ?
https://www.dropbox.com/s/6foewmb2u19a6 ... 5.png?dl=0

Yes, ~/Documents/Bitwig Studio/Controller Scripts/ is correct., I will fix this.

You're using the zip from moss's site right? The code from GitHub will only work within the 1.1 betas.

Mike

TeotiGraphix · Post by **TeotiGraphix** » Thu Oct 23, 2014 12:17 pm

It's correct on the wiki; https://github.com/git-moss/Push4Bitwig ... stallation

Are you reading that from his site?

Mike

Bitwig

KVR Audio

Ableton Push support is here