Login / Register  0 items | $0.00 NewWhat is KVR? Submit News Advertise

Ableton Push support is here

simmo75
KVRist
 
234 posts since 25 Mar, 2016, from Seattle

Postby simmo75; Thu May 18, 2017 12:08 pm Re: Ableton Push support is here

moss wrote:
simmo75 wrote:
moss wrote:
simmo75 wrote:Am i the only one here that cannot get the Push2display working.
It's so weird, the version that only works with beta's that you get from GitHub worked fine but the new version from Moss site i always get a permission error. I've done as the instructions ask.
I'm totally confused.


Are you on Mac?
https://github.com/git-moss/DrivenByMos ... ion-on-mac


Yes, on mac. And yes, the instructions are what i followed and i'm still getting the permission error.

Can you please help? i appreciate the link but thats what i have already... I'm sorry, i'm not a data programmer, just a musician.

edit: when i enter the line in terminal i get 'permission denied'.


I guess you need to open the console as administrator. Please google how to do that, I am not a Mac user.

BTW This horrible installation nightmare will be gone in the near future when the next Bitwig update is coming up, since this will allow to integrate that tool into the Extension.

This is great news for me, thanks Moss.
Quick question.. Does the new Push2display just replace the old one or does it replace Push4Bitwig completely?
User avatar
moss
KVRian
 
1000 posts since 12 May, 2004

Postby moss; Thu May 18, 2017 12:10 pm Re: Ableton Push support is here

simmo75 wrote:
moss wrote:
simmo75 wrote:
moss wrote:
simmo75 wrote:Am i the only one here that cannot get the Push2display working.
It's so weird, the version that only works with beta's that you get from GitHub worked fine but the new version from Moss site i always get a permission error. I've done as the instructions ask.
I'm totally confused.


Are you on Mac?
https://github.com/git-moss/DrivenByMos ... ion-on-mac


Yes, on mac. And yes, the instructions are what i followed and i'm still getting the permission error.

Can you please help? i appreciate the link but thats what i have already... I'm sorry, i'm not a data programmer, just a musician.

edit: when i enter the line in terminal i get 'permission denied'.


I guess you need to open the console as administrator. Please google how to do that, I am not a Mac user.

BTW This horrible installation nightmare will be gone in the near future when the next Bitwig update is coming up, since this will allow to integrate that tool into the Extension.

This is great news for me, thanks Moss.
Quick question.. Does the new Push2display just replace the old one or does it replace Push4Bitwig completely?


This is just the application for the Push 2s display.
simmo75
KVRist
 
234 posts since 25 Mar, 2016, from Seattle

Postby simmo75; Thu May 18, 2017 12:15 pm Re: Ableton Push support is here

moss wrote:
simmo75 wrote:
moss wrote:
simmo75 wrote:
moss wrote:
simmo75 wrote:Am i the only one here that cannot get the Push2display working.
It's so weird, the version that only works with beta's that you get from GitHub worked fine but the new version from Moss site i always get a permission error. I've done as the instructions ask.
I'm totally confused.


Are you on Mac?
https://github.com/git-moss/DrivenByMos ... ion-on-mac


Yes, on mac. And yes, the instructions are what i followed and i'm still getting the permission error.

Can you please help? i appreciate the link but thats what i have already... I'm sorry, i'm not a data programmer, just a musician.

edit: when i enter the line in terminal i get 'permission denied'.


I guess you need to open the console as administrator. Please google how to do that, I am not a Mac user.

BTW This horrible installation nightmare will be gone in the near future when the next Bitwig update is coming up, since this will allow to integrate that tool into the Extension.

This is great news for me, thanks Moss.
Quick question.. Does the new Push2display just replace the old one or does it replace Push4Bitwig completely?


This is just the application for the Push 2s display.


Yes, thats what i can't get to work. Does it live inside the old Push4Bitwig folder in Bitwig controller scripts or do i no longer need the Push4Bitwig folder?
User avatar
moss
KVRian
 
1000 posts since 12 May, 2004

Postby moss; Thu May 18, 2017 12:21 pm Re: Ableton Push support is here

simmo75 wrote:Yes, thats what i can't get to work. Does it live inside the old Push4Bitwig folder in Bitwig controller scripts or do i no longer need the Push4Bitwig folder?


Delete the Push4Bitwig in the controller scripts folder completely. Put the push2display folder in the Extensions folder together with the bwextension file.
simmo75
KVRist
 
234 posts since 25 Mar, 2016, from Seattle

Postby simmo75; Thu May 18, 2017 12:25 pm Re: Ableton Push support is here

moss wrote:
simmo75 wrote:Yes, thats what i can't get to work. Does it live inside the old Push4Bitwig folder in Bitwig controller scripts or do i no longer need the Push4Bitwig folder?


Delete the Push4Bitwig in the controller scripts folder completely. Put the push2display folder in the Extensions folder together with the bwextension file.


Thanks Moss :)
reflex58
KVRist
 
52 posts since 30 Jul, 2014

Postby reflex58; Thu May 18, 2017 10:20 pm Re: Ableton Push support is here

Just wondering if there anyway to decrease the scroll rate of the knobs when the broser is in use.
I find them extremely touchy the only way i can use the broser is by using the buttons.
User avatar
svervs
KVRist
 
301 posts since 16 Mar, 2013, from BLN

Postby svervs; Thu May 18, 2017 11:14 pm Re: Ableton Push support is here

svervs wrote:Unfortunately with my Push1 the display
- is lagging up 30sec
- not changing at all
- and shows tracks from already closed projects (maybe it's just very long lag)


Found the cause for this: It happens when you have two Push1 connected at the same time.
As soon as the second is connected it starts lagging (just the display, all change of button lights work fine). When turned off, the lag stays.
With the old scripts it was working fine. Any chance this may be fixable?

I tried using a second copy of the script, but this doesn't create a second controller slot.
User avatar
moss
KVRian
 
1000 posts since 12 May, 2004

Postby moss; Thu May 18, 2017 11:31 pm Re: Ableton Push support is here

reflex58 wrote:Just wondering if there anyway to decrease the scroll rate of the knobs when the broser is in use.
I find them extremely touchy the only way i can use the broser is by using the buttons.


That is something I am also not that happy about. I tried some slow down stuff which I also did not like. Need to think about it a bit more.
simmo75
KVRist
 
234 posts since 25 Mar, 2016, from Seattle

Postby simmo75; Fri May 19, 2017 6:01 am Re: Ableton Push support is here

moss wrote:
simmo75 wrote:
moss wrote:
simmo75 wrote:Am i the only one here that cannot get the Push2display working.
It's so weird, the version that only works with beta's that you get from GitHub worked fine but the new version from Moss site i always get a permission error. I've done as the instructions ask.
I'm totally confused.


Are you on Mac?
https://github.com/git-moss/DrivenByMos ... ion-on-mac


Yes, on mac. And yes, the instructions are what i followed and i'm still getting the permission error.

Can you please help? i appreciate the link but thats what i have already... I'm sorry, i'm not a data programmer, just a musician.

edit: when i enter the line in terminal i get 'permission denied'.


I guess you need to open the console as administrator. Please google how to do that, I am not a Mac user.

BTW This horrible installation nightmare will be gone in the near future when the next Bitwig update is coming up, since this will allow to integrate that tool into the Extension.


Hi moss, 2.1.1 beta is out today, does this update allow to integrate the Push2Display tool into the extension? Thanks.
richielg
KVRist
 
34 posts since 24 Jun, 2012, from Leeds

Postby richielg; Sun May 21, 2017 10:04 am Re: Ableton Push support is here

Hi Moss

Im just checking the new push script and it looks good. I have noticed some issues with navigating in and out of devices on drum machine pads.

I can navigate to any device just fine but when you navigate out of a device in order to select another drum pad every time it reverts back to C1 and I have to navigate up or down to the area I was focusing on before. So if you are working with 16 devices on all of the pads in the G sharp -1 to G sharp 0 range then any time you navigate out of a device to select another pad it will jump up to the C1 range. You can still navigate back to to where you were using the arrow buttons but its a bit frustrating. But also more importantly for me if the cells are empty in the C1 range then you cant navigate back down using the arrow buttons it just says please select drum pad. You have to deselect and reselect the drum machine and then go back into it to select another drum pad. This effects me because I use 8 drum machines with 16 pads on each instance and they span the full note range across all of the drum machines.

Navigating to a device that is nested within a chain does not work I was posting about this the other day because it didnt work on the version before either. The only way you can control device parameters of something inside a chain is by clicking on the nested device. Otherwise on the hardware it just says selected device: chain and you cant go into it. when you initially put the device inside the chain it works as the controller is already focused on it. As soon as navigate out of it you cant get back in.

Personally I would like it if the long press time for navigating back out of something was reduced by around half. I like the new structure for navigating in and out of things accept for the drum machine bug and the button press time but yeah this way of working makes a lot more sense to me.

On my system I am using Bitwig 2.1, Push 1 and Osx 10.12.4

Thanks,

Rich
Previous

Moderator: Bitwig Mods

Return to Controller Scripting