Ableton Push support is here

[sardaukar]

Hi,

Not sure if this is the correct place I should be asking this but, I have the following post

http://www.kvraudio.com/forum/viewtopic ... 7#p5830867

it contains:

knob sensitivity/curve, per soft controller assignment (with ableton push)?

Anyone know if this is possible at all? At the moment, soft controller assignments seem kind-of crippled.

would need this on a per-assignment basis I think. Some parameters are way too coarse/fine. I think the curve would need to be configured to...

[Raffi]

Hi,

When in Device mode (on the Push) and changing the master volume it always reverts back to Track mode. It works correctly with all other modes (i.e. reverts back to the selected mode after volume change).

Hope this can be fixed

Thanks!

[TeotiGraphix]

Hi,

When in Device mode (on the Push) and changing the master volume it always reverts back to Track mode. It works correctly with all other modes (i.e. reverts back to the selected mode after volume change).

Hope this can be fixed

Thanks!

I think I remember this bug and wanted to fix it but got side tracked.

I added an issue in GIT for it, if its a bug(don't have Bitwig open right now) I will get it fixed.

Mike

[Raffi]

Great! Thanks

[TeotiGraphix]

Hi,

When in Device mode (on the Push) and changing the master volume it always reverts back to Track mode. It works correctly with all other modes (i.e. reverts back to the selected mode after volume change).

Hope this can be fixed

Thanks!

Fixed in master of GIT, also fixed a bug when i changed colors/map of the Frame and device page modes (they were blinking yellow).

Mike

[garyboozy]

controller knob acceleration has been added - great news
doesn't quite work at the minute (faster acceleration when turning to the right than to the left) but i guess this is because it's not the stable release version?

is it possible to make the Touch automation mode work only when touching/moving the Push encoders, like it does when click-hold-adjust with the mouse button?

thanks again

[TeotiGraphix]

controller knob acceleration has been added - great news
doesn't quite work at the minute (faster acceleration when turning to the right than to the left) but i guess this is because it's not the stable release version?

is it possible to make the Touch automation mode work only when touching/moving the Push encoders, like it does when click-hold-adjust with the mouse button?

thanks again

Moss added the Knob acceleration the other day, today I actually noticed what you are talking about with the directions (left right). I will look into it if he doesn't.

is it possible to make the Touch automation mode work only when touching/moving the Push encoders, like it does when click-hold-adjust with the mouse button?

I will have to look into this, I think there is something in the API we are not using IE touch(), I need to do some research. I will add this to the issue queue so it doesn't get forgotten about.

Mike

[TeotiGraphix]

controller knob acceleration has been added - great news
doesn't quite work at the minute (faster acceleration when turning to the right than to the left) but i guess this is because it's not the stable release version?

Fixed in master on GIT. Don't forget you can hold [Shift + Knob] for minute adjustments as well.

Mike

[garyboozy]

will try it out now, thanks mike

[TeotiGraphix]

FYI users of the Push script;

Major performance improvement with pad lighting and display. Knobs move great with nice updates.

The VU meters for tracks and master are hooked back up! The controller is much more responsive now.

To try it check the Git repo's master.

Mike

[ThomasHelzle]

Curious: What solution did you go with in the end?

Cheers,

Tom

[TeotiGraphix]

Curious: What solution did you go with in the end?

Cheers,

Tom

The refresh callback was at 5ms, its changed to 70ms now.

Edit: This is not a loop though, only 70ms callback when a surface.flush() is called.

Its funny because in the beginning when Moss and I were tweaking that value, it didn't seem to make a difference.

I'm thinking as the script became more robust, and observers were added a lot more invalidation were happening especially with vus.

I am still going to try a custom invalidation system some time in one of my projects but for now the controller is like night and day with playing.

Mike

[ThomasHelzle]

Brilliant!

Yeah, makes sense, especially the VUs are rather heavy and constantly firing...
You could also check with Claes if the system can be improved.

Cheers,

Tom

[moss]

Curious: What solution did you go with in the end?

Hi Tom,
I stumbled upon this when I developed the Novation Remote script. The display of the Remote is slower than the one of the Push controller. After I wiggled the volume knob pretty quickly the script slowed down massivly (about 4 seconds) even after stopping the knob movement.
I guess that something in the JS engine screws up and the timeout callbacks do not get cleaned up.
If you want to experiment just lower it down to 5 ms again in the Novation script.
Cheers!

[ThomasHelzle]

Hm - not sure if there is a kind of limit to the number of timers maybe?
Would it make sense to only have one timer going, write the value-while-wiggling into the same variable where it is retrieved when the time is up, so it doesn't accumulate?
Didn't analyse the script, just a quick hunch

Basically: one timer, flags for dirty or not, if dirty -> retrieve value when timer is up, rinse and repeat. ?

Cheers,

Tom