Ableton Push support is here

[TeotiGraphix]

Make it look like this;

this.surface.pads.lightEx (x, 7 - y, isSet ? (hilite ? PUSH_COLOR2_RED_HI : PUSH_COLOR2_BLUE) : hilite ? PUSH_COLOR2_GREEN_HI

That will make the sequencer's selected steps red.

Mike

Actually, what worked better for me is

this.surface.pads.lightEx (x, 7 - y, isSet ? (hilite ? PUSH_COLOR2_GREEN_HI : PUSH_COLOR2_RED_HI) : hilite ? PUSH_COLOR2_GREEN_HI

Now all already selected steps are red - makes it a lot easier to see.

Sorry man, that is what I meant, I screwed the paste into the forum wrong(I tested on the Push to make sure). I said the code makes the existing steps red, which the steps are blue not green originally, so I forced you to get it right! haha

Mike

[Uplay]

Quick question - where is the version number of the installed script? How can I check if my installed version of the Push4Bitwig on my Mac is the latest one or old?

[moss]

Quick question - where is the version number of the installed script? How can I check if my installed version of the Push4Bitwig on my Mac is the latest one or old?

It's in Push.control.js line 17. Sadly, this information is not yet displayed in Bitwig Studio.

[Uplay]

Quick question - where is the version number of the installed script? How can I check if my installed version of the Push4Bitwig on my Mac is the latest one or old?

It's in Push.control.js line 17. Sadly, this information is not yet displayed in Bitwig Studio.

That's helpful, thanks Moss! I'd appreciate if it could be in the FAQ page until Bitwig implements the the script version display functionality.

[moss]

Quick question - where is the version number of the installed script? How can I check if my installed version of the Push4Bitwig on my Mac is the latest one or old?

It's in Push.control.js line 17. Sadly, this information is not yet displayed in Bitwig Studio.

That's helpful, thanks Moss! I'd appreciate if it could be in the FAQ page until Bitwig implements the the script version display functionality.

Done.

[Bobby L'Avenir]

Just confirmed the browser problem on Push again.
I am on BWS 1.3 OS X with the latest version available on GitHub.
I can move to any contagious instrument track (no audio track in between). using the arrows
If you use arrow Keys to select a any audio, efx, or master track the Push screen goes blank.
Selecting tracks (all types), still works when using any of the 8 track selection buttons.
I do not think it is a ba install of the script, I carefully installed the new one

I wonder if there are OS X specific problems since I cannot reproduce that on Windows (sorry I have no Mac available). I will ask the Bitwig guys about it.

Hi Moss, I have the exact same problem and I'm on windows 7

[Bobby L'Avenir]

I am also having this problem
"Also the arrow keys to scroll tracks now seems to be broken for audio, send and master tracks? They light up and work as they should for instrument tracks but they flash and disappear for audio, nothing at all for sends. Push also doesn't recognise send tracks at all, is it supposed to be like this as it's the same in the last version?"

I can't of corrupted the script by accident as this guy is explaining the exact symptoms i reported but he's on a mac, i'm on a pc running win 7 x64

[moss]

I am also having this problem
"Also the arrow keys to scroll tracks now seems to be broken for audio, send and master tracks? They light up and work as they should for instrument tracks but they flash and disappear for audio, nothing at all for sends. Push also doesn't recognise send tracks at all, is it supposed to be like this as it's the same in the last version?"

I can't of corrupted the script by accident as this guy is explaining the exact symptoms i reported but he's on a mac, i'm on a pc running win 7 x64

Ah, I see now. I did not look very closely on this 2nd problem since I was focused on your report of the non working volume change.
The arrow key were simply not yet implemented for the new Clip View, which is the default for Audio Tracks. I implemented it now so you can select tracks left/right too. But note that the Play View and the Clip View are the only views who actually do this. The other views require the arrow keys for other tasks.

Please check if your other problems remain and if yes please give me more details.

[codec17]

Hi Moss.

Not that of a biggy here and try to explain as good as possible.

If I select a FX-layer device with say 2 FX in it.. And i dive into fx-layer with the arrow keys.
I see of course my fx in it... But when i accidentally touch the tempo knob and/or the playcursor knob, it switch back to top layer...
Of course pay attention not to touch those knobs, but maybe you can solve it, if not well .. i need to pay attention.

Thnx in advance.

[moss]

Hi Moss.

Not that of a biggy here and try to explain as good as possible.

If I select a FX-layer device with say 2 FX in it.. And i dive into fx-layer with the arrow keys.
I see of course my fx in it... But when i accidentally touch the tempo knob and/or the playcursor knob, it switch back to top layer...
Of course pay attention not to touch those knobs, but maybe you can solve it, if not well .. i need to pay attention.

Thnx in advance.

Thanks for reporting! I fixed it and squashed 2 more bugs on the way there

[codec17]

Wow that,s fast! Thnx! Tested and confirmed, working here!

[Bobby L'Avenir]

I am also having this problem
"Also the arrow keys to scroll tracks now seems to be broken for audio, send and master tracks? They light up and work as they should for instrument tracks but they flash and disappear for audio, nothing at all for sends. Push also doesn't recognise send tracks at all, is it supposed to be like this as it's the same in the last version?"

I can't of corrupted the script by accident as this guy is explaining the exact symptoms i reported but he's on a mac, i'm on a pc running win 7 x64

Ah, I see now. I did not look very closely on this 2nd problem since I was focused on your report of the non working volume change.
The arrow key were simply not yet implemented for the new Clip View, which is the default for Audio Tracks. I implemented it now so you can select tracks left/right too. But note that the Play View and the Clip View are the only views who actually do this. The other views require the arrow keys for other tasks.

Please check if your other problems remain and if yes please give me more details.

Thanks for the update Moss, i can use the arrow keys on audio tracks now but still not send tracks? I'm getting jumpy behaviour with the arrow keys now mate, see the gif below. It happens every time i try scrolling through my tracks one by one, what you see in the gif is me scrolling one by one then all of a sudden it jumps through 3/4 tracks really quickly or gets stuck between the current and the next track?

Also the octaves still don't match up to the drum machine in drum mode, C2 triggers pad C1 on the drum machine, E£ on push trigger pad E2, so on and so forth?

The fine gain for sends and pan seems to be working ok though

By the way what line can i go to so i can change the colour of a selected audio track that has no input assigned? At the moment it's a very similar colour to the mute colour below as it doesn't turn red if there's no input assigned. I don't assing inputs to my audio tracks so i can see the meters if i select that track as they don't show activity if the track is record enabled. Hope that makes sense Moss?

Many thanks

Gif file was too large so get it here
https://www.dropbox.com/s/aa0y4o00wqjzl ... h.gif?dl=0

[moss]

Thanks for the update Moss, i can use the arrow keys on audio tracks now but still not send tracks?

Works fine here. Can you please exactly describe what you are doing? What view is selected?

I'm getting jumpy behaviour with the arrow keys now mate, see the gif below. It happens every time i try scrolling through my tracks one by one, what you see in the gif is me scrolling one by one then all of a sudden it jumps through 3/4 tracks really quickly or gets stuck between the current and the next track?

I noticed that too and made some adjustments till I could not reproduce it any longer on my PC. But that is a general problem because Javascript does not provide any synchronization, therefore I can not fix this.

Also the octaves still don't match up to the drum machine in drum mode, C2 triggers pad C1 on the drum machine, E£ on push trigger pad E2, so on and so forth?

I still cannot reproduce that. Please give a detailed description of what you are doing (starting with an empty project). Have you tried selecting Push as the only input?

what line can i go to so i can change the colour of a selected audio track that has no input assigned? At the moment it's a very similar colour to the mute colour below as it doesn't turn red if there's no input assigned. I don't assing inputs to my audio tracks so i can see the meters if i select that track as they don't show activity if the track is record enabled. Hope that makes sense Moss?

Not quite. There is currently no flag for no-input, therefore there is also no specific color?!

[camenzr]

Hey there,
i have an issue. for performing live i must be able to start clip recording by pressing footswitch2 and stopping it by pressing it again. i didnt find out how to do this. i made footswitch2 work with "toggle recording" but it doesnt record into clips.

is there a workaround for this?

thanks a lot, and thank you even more for programming push4bitwig,
roman

[Bobby L'Avenir]

Thanks for the update Moss, i can use the arrow keys on audio tracks now but still not send tracks?

Works fine here. Can you please exactly describe what you are doing? What view is selected?

I'm getting jumpy behaviour with the arrow keys now mate, see the gif below. It happens every time i try scrolling through my tracks one by one, what you see in the gif is me scrolling one by one then all of a sudden it jumps through 3/4 tracks really quickly or gets stuck between the current and the next track?

I noticed that too and made some adjustments till I could not reproduce it any longer on my PC. But that is a general problem because Javascript does not provide any synchronization, therefore I can not fix this.

Also the octaves still don't match up to the drum machine in drum mode, C2 triggers pad C1 on the drum machine, E£ on push trigger pad E2, so on and so forth?

I still cannot reproduce that. Please give a detailed description of what you are doing (starting with an empty project). Have you tried selecting Push as the only input?

what line can i go to so i can change the colour of a selected audio track that has no input assigned? At the moment it's a very similar colour to the mute colour below as it doesn't turn red if there's no input assigned. I don't assing inputs to my audio tracks so i can see the meters if i select that track as they don't show activity if the track is record enabled. Hope that makes sense Moss?

Not quite. There is currently no flag for no-input, therefore there is also no specific color?!

Thanks for the update Moss, i can use the arrow keys on audio tracks now but still not send tracks?

Works fine here. Can you please exactly describe what you are doing? What view is selected?

Basically i can't scroll to a send fx track or if i select one with the mouse, push says to select a track even though it's selected and i can control it with my frontier control surface. Slecting all other track types works but not send fx tracks. This is the same for all views, clip, send, pan, volume and track?

I'm getting jumpy behaviour with the arrow keys now mate, see the gif below. It happens every time i try scrolling through my tracks one by one, what you see in the gif is me scrolling one by one then all of a sudden it jumps through 3/4 tracks really quickly or gets stuck between the current and the next track?

I noticed that too and made some adjustments till I could not reproduce it any longer on my PC. But that is a general problem because Javascript does not provide any synchronization, therefore I can not fix this.


It works very well in version 5.01 which is what i'm using though? Is the version you tweaked until it went away the same version i tried 5.02 or is there a new update?

Also the octaves still don't match up to the drum machine in drum mode, C2 triggers pad C1 on the drum machine, E£ on push trigger pad E2, so on and so forth?

I still cannot reproduce that. Please give a detailed description of what you are doing (starting with an empty project). Have you tried selecting Push as the only input?

Sorry maybe i should've been a bit more clear, it all works but i was just pointing out that the display on push when selecting octaves in the drum mode doesn't match the drum machine module or the bitwig piano roll. Load a blank project with just one drum machine. Go into drum mode and tap the first pad, you see it triggers C1 of the drum machine and C1 of the piano roll. Now octave down and back up to where you were and you see push says you're on octave C2 to Eb3.

Also I just noticed a similar push read read out error on the piano mode, C-1 is triggering the C1 note in the bitwig piano roll, C0 is triggering C2 in the bitwig piano roll. Shouldn't octaves C1 to C3 trigger notes C1 to C3 in bitwigs piano roll? Did you mean it to be like this in both modes Moss?

what line can i go to so i can change the colour of a selected audio track that has no input assigned? At the moment it's a very similar colour to the mute colour below as it doesn't turn red if there's no input assigned. I don't assing inputs to my audio tracks so i can see the meters if i select that track as they don't show activity if the track is record enabled. Hope that makes sense Moss?

Not quite. There is currently no flag for no-input, therefore there is also no specific color?!

Ok, is that something bitwig need to add so i can send a feature request in? For now though is it possible to change the colour of my mute buttons, they appear bright yellow, maybe if i go dark orange or something it will be clearer to see what's selected from the button lights. What line is the colour for the mutes mate?

Cheers