Ableton Push support is here

[stamp]

A lot of times in channels with drummachine the drumpads loose the assigned track color and it's impossible to mute/solo pads.
Even closing and reopening the project the problem persist.

[djpremacy]

Another suggestions regarding the session view.
1. You can currently select a pad/clip etc and duplicate that with the duplicate button.
Wouldnt it be nice to be able to press :
Option A : Select -> Scene selection button (the ones you use to start playing a scene), so it selects the whole scene in bitwig. (the white markers are around the scene play button in Bitwig). Then press duplicate and it will duplicate the whole scene.
Option B : Maybe also keep it simple and just long press the currently playing scene button to duplicate. (inserting below, and not overwriting the next scene)
Option C : Long press duplicate and then select the scene playing button.
Option D : Shift/select simulatinously and then selecting the playing scene button.


Comment: Make sure the scene is copied (inserted) not overwriting the scene below the current one.

2. There is an option in the api to create a new scene from the playing clips. Maybe this can be used on the controller?

3. When in session view you can select clip, then duplicate and it will duplicate the clip. Can for exampe Select ->Clip be implemented. As long as you press select and multiple clips it will play and select those clips (white square around them). Then duplicate and it will duplicate the selected/playing clips. (there is an option in the api to create new scene from playing clips)

4. Also, maybe an option to create a new blank scene. (currently only possible to create new clip)
Long press of the NEW button to insert (not overwriting) a blank scene below the current one.

Quantize option suggestion :

When pressing shift-> quantize button you will be able to select the groove menu. Maybe extend the shift quantize menu adding new screen button for quantize resolution (used when quantize button pressed on recorded clip), and input quantize resolution(including off).
Also, why dont you use long press quantize button to show the menu? Probably because of the risk of hitting quantize to short and it will quantize the clip)

[moss]

A lot of times in channels with drummachine the drumpads loose the assigned track color and it's impossible to mute/solo pads.
Even closing and reopening the project the problem persist.

To make the display of mute/solo/exists states and colors work, the primary device needs to be the drum machine (which is normally the case).

[stamp]

A lot of times in channels with drummachine the drumpads loose the assigned track color and it's impossible to mute/solo pads.
Even closing and reopening the project the problem persist.

To make the display of mute/solo/exists states and colors work, the primary device needs to be the drum machine (which is normally the case).

The drum machine is always the primary device here. By the way I've noticed the problem persist after reopening only if I've saved after loosing color and mute/solo ability.
Using the last beta from github Win7 1.3.6 rc2.
Will try with stable releases and report back.

Edit: Ok, now I got it. But don't understand how it lost its status of primary device. Thanks!

[codec17]

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.

Hi moss! Thats a bummer. Its grope in the dark?
Do the devs know? (i bet they they do ) I send in one of those crash things when loading bitwig after major crash.
I got the feeling that its happening more often now. And i dont use drummaschine anymore because of this.
Must be a regression or something? Because never had it before.
Does it make sense that i report about it also? (because i dont got a clue when it comes down to scripting. )
Thnx.

Sven.

[moss]

Hi moss! Thats a bummer. Its grope in the dark?
Do the devs know? (i bet they they do ) I send in one of those crash things when loading bitwig after major crash.
I got the feeling that its happening more often now. And i dont use drummaschine anymore because of this.
Must be a regression or something? Because never had it before.
Does it make sense that i report about it also? (because i dont got a clue when it comes down to scripting. )
Thnx.

Sven.

The 1.3.6 changes note that it is fixed. I just did some quick tests but it seems to be working again.

[codec17]

Hmmm weird.
I did test it again couple of hours now, and still happens a couple of times now.
Not only with drummaschine but also fx-layers, specially when "diving" in or out the devices.
Push-1 hangs on a displayscreen or bitwig just crashes.
Cant really get my finger on it... test further to hopefully get a more sensible comment.

Edit: with fxlayers its bingo everytime. So if you can try load up a empty project, and just put a fxlayer on a track with 2 layers in it. And one of them a VST in that layer? And go into that layer or and go out. Most of the time it happens first try.

Thnx in advance!

Sven.

[moss]

Hmmm weird.
I did test it again couple of hours now, and still happens a couple of times now.
Not only with drummaschine but also fx-layers, specially when "diving" in or out the devices.
Push-1 hangs on a displayscreen or bitwig just crashes.
Cant really get my finger on it... test further to hopefully get a more sensible comment.

Edit: with fxlayers its bingo everytime. So if you can try load up a empty project, and just put a fxlayer on a track with 2 layers in it. And one of them a VST in that layer? And go into that layer or and go out. Most of the time it happens first try.

Thnx in advance!

Sven.

Then please report again and send your crashes to Bitwig.

[codec17]

Ok.

Did the reports in both ways now.
But i mentioned it here first to get answer maybe, and the shortest way to go.
Sorry for the grizzle,

Sven.

[ceasless]

Ah, that's a great suggestion. I will check tonight! Thanks for the quick response, moss

In fact it seems that a system restart or some other fairy dust fixed it, as I never encountered the problem again after this, even switching between 1.3.6 RCs and 1.3.5, and now 1.3.6.

By the way, the Push 1 leaves today and the Push 2 should arrive tomorrow. I'm really looking forward to seeing the integration. Have there been any major updates since the YouTube video announcing Push 2 support was released?

[moss]

Ah, that's a great suggestion. I will check tonight! Thanks for the quick response, moss

In fact it seems that a system restart or some other fairy dust fixed it, as I never encountered the problem again after this, even switching between 1.3.6 RCs and 1.3.5, and now 1.3.6.

By the way, the Push 1 leaves today and the Push 2 should arrive tomorrow. I'm really looking forward to seeing the integration. Have there been any major updates since the YouTube video announcing Push 2 support was released?

There is full graphical support now:

Changes from 7.00 are here: https://github.com/git-moss/Push4Bitwig/wiki/Changes

[ceasless]

Awesome work, moss! I'm really excited for what I can do already (well, once it arrives...). And even more so by what we still have in store for us as the API expands.

Thanks again for all the efforts.

[goatgirl]

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?

I have the same problem with lights lagging with stable version 7.22. This isnt noticable from the first few notes, but the more notes that are played the longer the lag. This only appears to affect the lights as the sound is still heard on time.

I have tried the stable script and the one on Github and they both show the lag. I have even tried BWS 1.3.5 and 1.3.6 and both lag. Its only when I revert to Push4Bitwig version 6.00 does the lag stop.

Running windows 7x64

[TeotiGraphix]

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?

I have the same problem with lights lagging with stable version 7.22. This isnt noticable from the first few notes, but the more notes that are played the longer the lag. This only appears to affect the lights as the sound is still heard on time.

I have tried the stable script and the one on Github and they both show the lag. I have even tried BWS 1.3.5 and 1.3.6 and both lag. Its only when I revert to Push4Bitwig version 6.00 does the lag stop.

Running windows 7x64

Funny enough, I have been using Ableton lately for a couple things and the Push. There is something funky happening because even in Ableton the lights when playing notes mess up.

I really don't know if there is any correlation, just thought I would mention it.

Mike

[goatgirl]

Funny enough, I have been using Ableton lately for a couple things and the Push. There is something funky happening because even in Ableton the lights when playing notes mess up.

I really don't know if there is any correlation, just thought I would mention it.

Mike

I have not noticed any problems with the lights while running Ableton, though I have been using the Beta version. Not sure if there have been any firmware updates to Push that have contributed to the problem.

Yesterday, I set up a Linux box and ran the Push with the 7.22 P4B script, also without any light problems.

Its looking OS specific, but could also be some other wierd conflict going on. Maybe Microsoft are slowly bugging my system to force me to return to Win 10 </tinfoil-hat>.

Anyway I'll continue using one of the dusty old scripts that work.