Ableton Push support is here

[moss]

It would be nice to have a 64 pad drummachine.

I already looked into this. With the current API it would mean to have duplicated observers for all the drum data with a 64 pad array. This would give a bad performance impact. I hope that this will change in the future.

[dplduffy]

MOSS!

I just bought a Push with that sale and damn man this script is awesome. I love you.

[goatgirl]

Is there a way to make the Macros the default set of parameters instead of the panel stuff? I find I keep switching to the Macro set each time I browse the presets.

Thanks Moss and TeotiGraphix, for making the script. I'm looking forward to seeing it develop. Had a lot of problems when I first started to use it, but I think that is down to it losing focus on things.

[TeotiGraphix]

Is there a way to make the Macros the default set of parameters instead of the panel stuff? I find I keep switching to the Macro set each time I browse the presets.

Thanks Moss and TeotiGraphix, for making the script. I'm looking forward to seeing it develop. Had a lot of problems when I first started to use it, but I think that is down to it losing focus on things.

I did this in the Maschine4Bitwig code but I don't know if moss implemented such a feature. What I ended up doing was adding per project configuration where it allowed you to set the default device page for when the controller started up.

Mike

[goatgirl]

I did this in the Maschine4Bitwig code but I don't know if moss implemented such a feature. What I ended up doing was adding per project configuration where it allowed you to set the default device page for when the controller started up.

Thanks Mike, its good to know this would at least be possible.

[codec17]

It would be nice to have a 64 pad drummachine.

I already looked into this. With the current API it would mean to have duplicated observers for all the drum data with a 64 pad array. This would give a bad performance impact. I hope that this will change in the future.

Ah ok... well you did your best! So we,ll wait... Its working fine now! But im a addict when it comes to put my sounds on pads.

I almost dont dare to ask but ive got 2 questions.

1: and i dont really know if i have to ask it here, but i use a dual monitor setup, and when i select a clip on the second screen it sometimes wont focus somehow, when i go to my first screen it,s all fine.
But i think thats one of the minor flaws i would guess?

2: when in drummachine mode it sometimes loses focus of the device? Specially when select+pad.It would be nice no matter what panel mapping your in(tone,AEG,EG2 etc...), you always can select the pad and that your on the same panel editting mode for that new selected pad.
You mentioned it in one of your videos, i would guess thats one of the "squirks" ? (or how do you type that word? )
Why the question? now you have to constantly use the arrow keys to go back and forth,to go to the top level of drummachine and "dive" into the new pad. not that of biggy, and im hoping thats one of the API "limitations"?

Nevertheless ive got to much fun already with all the options you put in!
And it completly overhauled my workflow in terms of the speed i "produce" now.
The music is getting more funky by the day....

Thnx!

[TeotiGraphix]

1. Has to do with the fact the framework is not setup for this, there becomes multiple instance of things and the oncorrect observers are not called OR listened to.

I ran into this problem when testing Maschine, when 1.2 comes out, I want to see if I can isolate this issue and get it fixed in the Framework4Bitwig code that all ours scripts share.

I use dual screens a lot, I don't know if Moss does or not, if he doesn't he may not even know this issue exists.

Mike

[codec17]

1. Has to do with the fact the framework is not setup for this, there becomes multiple instance of things and the oncorrect observers are not called OR listened to.

I ran into this problem when testing Maschine, when 1.2 comes out, I want to see if I can isolate this issue and get it fixed in the Framework4Bitwig code that all ours scripts share.

I use dual screens a lot, I don't know if Moss does or not, if he doesn't he may not even know this issue exists.

Mike

Aaah ok... well as i said its not that of problem for me but its nice too see you guys working/thinking on it, and i can hit every question at you and theres an answer or you guys know of the "problem" !

And i totally forget to thank you also teotigraphix for the ridicolous amount of work you all put into this!
(shame on me.... )

[moss]

1: and i dont really know if i have to ask it here, but i use a dual monitor setup, and when i select a clip on the second screen it sometimes wont focus somehow, when i go to my first screen it,s all fine.

Wrong thread. I only use 1 monitor.

2: when in drummachine mode it sometimes loses focus of the device? Specially when select+pad.It would be nice no matter what panel mapping your in(tone,AEG,EG2 etc...), you always can select the pad and that your on the same panel editting mode for that new selected pad.

I am not sure if that is possible because when you change a pad you select a different "channel" which can contain any kind of device and therefore may not have the same parameter set. Nevertheless, I will put it on my list and have a look.

[codec17]

2: when in drummachine mode it sometimes loses focus of the device? Specially when select+pad.It would be nice no matter what panel mapping your in(tone,AEG,EG2 etc...), you always can select the pad and that your on the same panel editting mode for that new selected pad.

I am not sure if that is possible because when you change a pad you select a different "channel" which can contain any kind of device and therefore may not have the same parameter set. Nevertheless, I will put it on my list and have a look.

Didnt thought about that one (any kind of device )
Well, thnx for taking a look at it and maybe even in consideration IF!! possible.

[lamouette/rck]

So now the 1.2 beta is out, which features are implemented on the API, loading VST from the push ? Can't wait for new update (but take your time guyz )

[TeotiGraphix]

So now the 1.2 beta is out, which features are implemented on the API, loading VST from the push ? Can't wait for new update (but take your time guyz )

Volker added full API for the browser filters etc are all implemented. I am reading through the API docs right now, seems you can even load samples. (don't take my word for it, there is a lot of new API but it pretty much covers all the browser's functionality)

Mike

[goatgirl]

One thing I have noticed that I would call a bug. If you touch the play head encoder above the touch strip, it will also show the tempo under the first encoder slot(above the display). While this is displayed, turning the left hand encoder above the display will then change the tempo.

I find that while I am changing a parameter using the first encoder, I will sometimes touch the playhead encoder and acccidentally change the tempo. It would be nice if this did not happen.

[TeotiGraphix]

One thing I have noticed that I would call a bug. If you touch the play head encoder above the touch strip, it will also show the tempo under the first encoder slot(above the display). While this is displayed, turning the left hand encoder above the display will then change the tempo.

I find that while I am changing a parameter using the first encoder, I will sometimes touch the playhead encoder and acccidentally change the tempo. It would be nice if this did not happen.

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

If it's a bug, it will get taken care of there, if you have a GitHub account.

Mike

[goatgirl]

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

If it's a bug, it will get taken care of there, if you have a GitHub account.

You mean I have to write it all out again some where else ???

hehe, thanks Mike, i will report it in its proper place .