Ableton Push support is here

[volker@bitwig]

Good catch, thanks!

Cheers,

Tom

Tom, it seems none of the observers for DrumPadBank actually get fired after initialization.

For instance, having hooked up a drum pad selection listener, i can click in the drum machine and the observer never gets called. can you talk to Claus about this? Is it a know issue?

The observer gets called ONCE on start. So trying to get the color working is a no go until i figure out if I am doing something wrong or it doesn't work yet.

Code: Select all

this.drumPadBank = this.cursorDevice.createDrumPadBank (this.numDrumPadLayers);
for (i = 0; i < this.numDrumPadLayers; i++)
{
    layer = this.drumPadBank.getChannel (i);
    layer.addIsSelectedObserver (doObjectIndex (this, i, CursorDeviceProxy.prototype.handleDrumPadSelection));
}

handleDrumPadSelection never gets called.

Mike

This is probably a bug, i'll look into it. Thanks for finding it!
Volker

[TeotiGraphix]

Volker, its basically all the DrumpadBank observers (15+), so its unusable right now.

Mike

[volker@bitwig]

Volker, its basically all the DrumpadBank observers (15+), so its unusable right now.

Mike

Aight, found the problem and fixed it, will be included in the next beta (coming tomorrow).

[TeotiGraphix]

Volker, its basically all the DrumpadBank observers (15+), so its unusable right now.

Mike

Aight, found the problem and fixed it, will be included in the next beta (coming tomorrow).

Great! If all the observers now work, that is a ton of stuff, mute, solo, name, it all wasn't working.

Mike

[rentboyrenton]

unaware of this thread here, i asked a question in this thread:

http://www.kvraudio.com/forum/viewtopic ... 1#p5934711

about using Push in Bitwig and if you could see some feedback on the pads (flashing) for the notes that are already recorded while you are playing through the track and recording/adding in new notes

is this already implemented and if not would this be possible to implement in the future?

[TeotiGraphix]

unaware of this thread here, i asked a question in this thread:

http://www.kvraudio.com/forum/viewtopic ... 1#p5934711

about using Push in Bitwig and if you could see some feedback on the pads (flashing) for the notes that are already recorded while you are playing through the track and recording/adding in new notes

is this already implemented and if not would this be possible to implement in the future?

Already works for Note, Drum and Sequencer. (1.1 beta)

Mike

[rentboyrenton]

unaware of this thread here, i asked a question in this thread:

http://www.kvraudio.com/forum/viewtopic ... 1#p5934711

about using Push in Bitwig and if you could see some feedback on the pads (flashing) for the notes that are already recorded while you are playing through the track and recording/adding in new notes

is this already implemented and if not would this be possible to implement in the future?

Already works for Note, Drum and Sequencer. (1.1 beta)

Mike

that will come in handy

thanks for the quick reply!

[hibidy]

So do I replace the github version with with the 3.3 version?

[TeotiGraphix]

So do I replace the github version with with the 3.3 version?

GITHub works with RC1, 3.3 is the stable version that works with 1.0.15.

Mike

[hibidy]

Right, but do I put both in since I'm using both?

[TeotiGraphix]

Right, but do I put both in since I'm using both?

Hmm, i think you have hit a limitation. You can't have two controllers with the same UID in the folder, so I guess your stuck.

I don't think 3.3 will work in the RC1 because of API changes and I know GITHub doesn't work with 1.0.15, sorry about that.

Mike

[hibidy]

3.3 works, just doesn't have some of the really cool stuff you guys have been working on. Well, I'm pretty sure I'm going to use 1.1 mainly so I'll just go that route and keep the other around in case there is some catastrophic thing that happens.

[hibidy]

A couple of things:

"add track" works, but all the tracks stay record enabled where as bitwigs "ctrl/T" keeps the tracks one record enabled at a time (preferences is for only one track to be enabled when creating it)

And I'm puzzled. Pressing on a clip when in stop while the track is in record mode doesn count-in start that clip. Is this a bitwig thing, or is it something that could be implimented? While the engine is going this works either by selecting a clip or hitting enter.

[TeotiGraphix]

A couple of things:

"add track" works, but all the tracks stay record enabled where as bitwigs "ctrl/T" keeps the tracks one record enabled at a time (preferences is for only one track to be enabled when creating it)

And I'm puzzled. Pressing on a clip when in stop while the track is in record mode doesn count-in start that clip. Is this a bitwig thing, or is it something that could be implimented? While the engine is going this works either by selecting a clip or hitting enter.

> tracks stay record enabled

I think this is a bug I introduced when i changed the mute/solo button behavior months ago and never got back to fixing it. It should use what you have set in the DAW, I think I was trying to copy Ableton behavior and messed it up.

> doesn count-in

Currently the code calls slots.record(), so really this is probably a "bug" or oversight on Bitwig's end of the API. Since it's an application behavior, it should be taken care of on there end IMHO.

Mike

[hibidy]

Thanks

Found this in the wiki

Hold Fixed Length button to choose the length for new clips.

Since it doesn't do anything other than go back to the track parameters, I wanted to check if this is known or simply something that can't be done currently.