Ableton Push support is here

[djpremacy]

I also have a suggestion (if possible and not mentioned before).
The Convert button on the push in bitwig script is not used.
Would it be an idea to use that like this :

Press convert -> Converts clip to drumrack
Press Shift Convert -> Converts clip to multisample

Even better, that the button only lights up when an audio clip is present in the slot.
There is an key assignment for the slice to drum maschine and slice to multisample.

Also maybe use the repeat button to add and activate the arpeggiator to the selected track? (nektar panorama p4 has this implemented)

[moss]

Edit 2: Hmmm it seems it solved itself? Strange... because i could reproduce it a couple of times today and evn bitwig closses itself a couple of times ,and now i try and try and it doesnt appaer anymore. (so forget it this one for time being, I could delete post but i didnt, cause i swear it happened a couple of times.) Ill check out more.

There is definitvely a bug in Bitwig when navigating layers. I had several crashes as well. Therefore, it is hard to tell if there is a bug in the script as well since always when I tried to test I crashed Bitwig.

[moss]

I ve noticed some lags from time to time when you change for example from scale mode to another like track overview.(1-2 seconds) sometimes it feels like push lost his self and find his self after a few seconds back.
Sometimes he just hangs up.

I noticed that in very rare cases too. I am not sure what is responsible for that effect but tend to blame the script engine.

I 've tried today push in combination with ableton and the handling is real smooth.it change for example automatically in drummode as soon as he detected a drumkit.

That works different with P4B: You first have to select the drum sequencer view which is then remembered for the track.

[moss]

I also have a suggestion (if possible and not mentioned before).
The Convert button on the push in bitwig script is not used.
Would it be an idea to use that like this :

Press convert -> Converts clip to drumrack
Press Shift Convert -> Converts clip to multisample

Even better, that the button only lights up when an audio clip is present in the slot.
There is an key assignment for the slice to drum maschine and slice to multisample.

That's actually a great idea! I can not send key commands but had a look at the actions which I did not do for a while. Luckily there are actions for both functions.

I checked in a test version on GitHub. Also see the Changes list on GitHub.

By doing this I could also track down the behaviour of the infamous focus problem and documented it here:
https://github.com/teotigraphix/Framewo ... issues/109

So, before using it make sure the Convert button is lit.

Also maybe use the repeat button to add and activate the arpeggiator to the selected track? (nektar panorama p4 has this implemented)

This is not possible via the API. I guess they are using their trick sending key commands for which you need an additionally utility.

[djpremacy]

I also have a suggestion (if possible and not mentioned before).
The Convert button on the push in bitwig script is not used.
Would it be an idea to use that like this :

Press convert -> Converts clip to drumrack
Press Shift Convert -> Converts clip to multisample

Even better, that the button only lights up when an audio clip is present in the slot.
There is an key assignment for the slice to drum maschine and slice to multisample.

That's actually a great idea! I can not send key commands but had a look at the actions which I did not do for a while. Luckily there are actions for both functions.

I checked in a test version on GitHub. Also see the Changes list on GitHub.

By doing this I could also track down the behaviour of the infamous focus problem and documented it here:
https://github.com/teotigraphix/Framewo ... issues/109

So, before using it make sure the Convert button is lit.

Also maybe use the repeat button to add and activate the arpeggiator to the selected track? (nektar panorama p4 has this implemented)

This is not possible via the API. I guess they are using their trick sending key commands for which you need an additionally utility.

Good ! I will try if it works
Maybe adding an option to bounce in place as well from a midi clip? For example select -> Convert = Bounce in place. Or long press convert button convert midi clip to bounce in place audio.
Then after that perform the next action slice to drum/sample.. with the (shift) convert.

Also another idea regarding drum maschine. For example with maschine2 (standalone) and push2 in ableton, when you press the pad it autoselects the pad and shows the sampler of that pad.Then you could immediately select the pad/layer settings like pitch etc. Then you do not have to push select->pad. Maybe add a toggle that switch the auto selection of pad on/off.

What I use often with drum maschine is loading sounds in the individual pads and then change the pitch of the pads to match with the other sounds in the drumkit. It would be great if the layer option for the drum maschine can be accessed quicker than the current page left, page right. So as above, selecting the pad and then it shows the sampler parameters of that pad.(volume, pan,pitch, sample length etc)

Btw, is there an option so switch directly to macro mode when pressing device on an instrument track? Like double click device button.....

Also, in the device view (track view with multiple devices). When you have for example 2 devices shown in the tabs. The only way to dive deeper into the parameters of the selected device is to press page left. Can something be done that you can press once the button below the device to select, and double click or long press the specific device selection button to enter the parameters (macro etc)?
Maybe shift -> Device or select->device will also be an option?

[moss]

Maybe adding an option to bounce in place as well from a midi clip? For example select -> Convert = Bounce in place. Or long press convert button convert midi clip to bounce in place audio.
Then after that perform the next action slice to drum/sample.. with the (shift) convert.

Also another idea regarding drum maschine. For example with maschine2 (standalone) and push2 in ableton, when you press the pad it autoselects the pad and shows the sampler of that pad.Then you could immediately select the pad/layer settings like pitch etc. Then you do not have to push select->pad. Maybe add a toggle that switch the auto selection of pad on/off.

What I use often with drum maschine is loading sounds in the individual pads and then change the pitch of the pads to match with the other sounds in the drumkit. It would be great if the layer option for the drum maschine can be accessed quicker than the current page left, page right. So as above, selecting the pad and then it shows the sampler parameters of that pad.(volume, pan,pitch, sample length etc)

Btw, is there an option so switch directly to macro mode when pressing device on an instrument track? Like double click device button.....

Also, in the device view (track view with multiple devices). When you have for example 2 devices shown in the tabs. The only way to dive deeper into the parameters of the selected device is to press page left. Can something be done that you can press once the button below the device to select, and double click or long press the specific device selection button to enter the parameters (macro etc)?
Maybe shift -> Device or select->device will also be an option?

Some good ideas in there. Will need to think about it.

[stamp]

@ djpremacy Cool suggestions
@ moss Clips still get selected when launched. Can you change this, please?

[moss]

@ moss Clips still get selected when launched. Can you change this, please?

That is intended. What's your problem with it?

[stamp]

Btw, is there an option so switch directly to macro mode when pressing device on an instrument track? Like double click device button.....

@ moss What about putting the macros in the first page of the fixed section (so the order is macro, common, etc) and make the macro-assignement accessible via a the shift button (or add another page for macro assignement). Only one button to access macros this way.

Best,
s

[stamp]

@ moss Clips still get selected when launched. Can you change this, please?

That is intended. What's your problem with it?

For example: I'm fiddling with the cutoff of a synth. I want to launch a different drum pattern and continue fiddling. I can't because the channel with the drums gets selected.

[djpremacy]

Maybe adding an option to bounce in place as well from a midi clip? For example select -> Convert = Bounce in place. Or long press convert button convert midi clip to bounce in place audio.
Then after that perform the next action slice to drum/sample.. with the (shift) convert.

Also another idea regarding drum maschine. For example with maschine2 (standalone) and push2 in ableton, when you press the pad it autoselects the pad and shows the sampler of that pad.Then you could immediately select the pad/layer settings like pitch etc. Then you do not have to push select->pad. Maybe add a toggle that switch the auto selection of pad on/off.

What I use often with drum maschine is loading sounds in the individual pads and then change the pitch of the pads to match with the other sounds in the drumkit. It would be great if the layer option for the drum maschine can be accessed quicker than the current page left, page right. So as above, selecting the pad and then it shows the sampler parameters of that pad.(volume, pan,pitch, sample length etc)

Btw, is there an option so switch directly to macro mode when pressing device on an instrument track? Like double click device button.....

Also, in the device view (track view with multiple devices). When you have for example 2 devices shown in the tabs. The only way to dive deeper into the parameters of the selected device is to press page left. Can something be done that you can press once the button below the device to select, and double click or long press the specific device selection button to enter the parameters (macro etc)?
Maybe shift -> Device or select->device will also be an option?

Some good ideas in there. Will need to think about it.

thanks! what I noticed is that when I use push2 with ableton.
When in mix mode showing all the channels. When you select and long press the button below the drum rack, it will immediately dive into the individual drum rack pads that are also selectable. Also when selecting a track group and long press it will dive in (expand folder/track group) and show the individual tracks. Long press again and back to the folded track view. So my suggestion to have the long press implemented in more places . A huge time saver instead of using the page left and right which I think is very confusing.

Ofcourse I understand this might be a lot of work and might break the push1 script.

[stamp]

@ moss Clips still get selected when launched. Can you change this, please?

That is intended. What's your problem with it?

For example: I'm fiddling with the cutoff of a synth. I want to launch a different drum pattern and continue fiddling. I can't because the channel with the drums gets selected.

I have the option to select tracks when clips are selected turned on (prefs) to avoid confusion.

[nonplussed_]

Hey, I'm having a problem with your script and I'm curious if it's something you've heard of before.

(I've been using it for as long as it's existed basically and had a lot of success; here I took some time off music to focus on school and came back to find the versions of my Bitwig and Push4Bitwig causing the following error)

I have Bitwig on two computers: one w10 laptop currently with Bitwig at version 1.3.4 (where Push4Bitwig works without a problem), and one desktop w7 with Bitwig at 1.3.5. On this desktop, push4bitwig's light-up feature lags behind by up to a few seconds (4-5). Is this a problem you've encountered before? Any quick fix?

[moss]

Hey, I'm having a problem with your script and I'm curious if it's something you've heard of before.

(I've been using it for as long as it's existed basically and had a lot of success; here I took some time off music to focus on school and came back to find the versions of my Bitwig and Push4Bitwig causing the following error)

I have Bitwig on two computers: one w10 laptop currently with Bitwig at version 1.3.4 (where Push4Bitwig works without a problem), and one desktop w7 with Bitwig at 1.3.5. On this desktop, push4bitwig's light-up feature lags behind by up to a few seconds (4-5). Is this a problem you've encountered before? Any quick fix?

Are you running any other script on the lagging computer?

[djpremacy]

Maybe the problem has already been mentioned. When I am using track groups, the note settings (drum,play,sequencer etc) are not remembered for the tracks.(in most cases). When using only tracks without track groups it works fine.

For the rest I am really having a lot of fun with the script. Hopefully some of my suggestions can be implemented on the future.
And I will also spam Bitwig about the API to add the "add new device" and "delete device" mapping.