How is that work going?moss wrote:Just wanted to let you know that I am currently rewriting the framework for all my scripts. Therefore, there will be no updates or bigfixes. However, I noted all of your comments.
Cheers!
Ableton Push support is here
- KVRAF
- 26935 posts since 3 Feb, 2005 from in the wilds
- KVRAF
- Topic Starter
- 4874 posts since 13 May, 2004
Lot's of work! Finished the conversion of the 5th script yesterday, 3 more to go...pdxindy wrote:How is that work going?moss wrote:Just wanted to let you know that I am currently rewriting the framework for all my scripts. Therefore, there will be no updates or bigfixes. However, I noted all of your comments.
Cheers!
- KVRist
- 42 posts since 5 Feb, 2015
Will it be possible to "switch banks" of the V2 remote controls via the Push with the new script? As of now (please correct me if I'm missing something) the Push follows the mouse click on the arrows, but I can't find a way to initiate the bank-switch on the hardware.
- KVRAF
- Topic Starter
- 4874 posts since 13 May, 2004
Simply use the left/right cursor buttons?!Vathek wrote:Will it be possible to "switch banks" of the V2 remote controls via the Push with the new script? As of now (please correct me if I'm missing something) the Push follows the mouse click on the arrows, but I can't find a way to initiate the bank-switch on the hardware.
- KVRist
- 42 posts since 5 Feb, 2015
Thanks for the suggestion, I reckon it's sensible to assume a silly user, but I had tried that of course. Still, I figured it out now. Of course you know about this, but I'll post it anyway in case others hit the same road block. This is on a Push2 btw, don't know if it's any different on a V1. And moss, please correct me if I'm describing it wrong, this is just how the script appears to work for me.
So, when doing as suggested, initially the left/right cursors don't go from bank to bank within a device, but rather the focus jumps from device to device on the same channel. The trick is to press "Page<" first. Then the cursor does switch the banks of remote controls. And it kinda makes sense now that I figured that out. Pressing "Device" puts the focus on a device in a channel, but not 'within' that device. For that another press on "Page<" is needed. Pressing "Page<" twice while in Mix accomplishes the same thing, the first press enters the channel, the second enters the device. And of course pressing ">Page" once gets us out of the device into the channel and another ">Page" gets us one step up to the mixer.
So it's best to look at it like a three level structure: mixer -> channel with devices in it -> the devices themselves. The first two have their dedicated buttons "Mix" and "Device" respectively (and are thus somewhat mislabelled imo), while the lowest level does not have its own button. To get there one has to press "Page<" twice from the Mixer or once from the Device.
Sorry for the long post about sth most folks will probably just shrug "uhm, yeah of course", it took me quite a while to figure out.
So, when doing as suggested, initially the left/right cursors don't go from bank to bank within a device, but rather the focus jumps from device to device on the same channel. The trick is to press "Page<" first. Then the cursor does switch the banks of remote controls. And it kinda makes sense now that I figured that out. Pressing "Device" puts the focus on a device in a channel, but not 'within' that device. For that another press on "Page<" is needed. Pressing "Page<" twice while in Mix accomplishes the same thing, the first press enters the channel, the second enters the device. And of course pressing ">Page" once gets us out of the device into the channel and another ">Page" gets us one step up to the mixer.
So it's best to look at it like a three level structure: mixer -> channel with devices in it -> the devices themselves. The first two have their dedicated buttons "Mix" and "Device" respectively (and are thus somewhat mislabelled imo), while the lowest level does not have its own button. To get there one has to press "Page<" twice from the Mixer or once from the Device.
Sorry for the long post about sth most folks will probably just shrug "uhm, yeah of course", it took me quite a while to figure out.
- KVRAF
- Topic Starter
- 4874 posts since 13 May, 2004
Ah, I see. It is described like that in the Wiki but it might not be so easy to spot. However, this will be changed to a simpler navigation in the next version.Vathek wrote: Sorry for the long post about sth most folks will probably just shrug "uhm, yeah of course", it took me quite a while to figure out.
- KVRist
- 42 posts since 5 Feb, 2015
You're totally right, but I only understand it now that I figured it out myself, haha. No worries though, I'm obviously just getting my feet wet. And I was only testing that with Kontakt, with for example a Bitwig Drum Machine still only the first eight remote controls are available as Page Left enters the actual sounds, out of which only the first eight are selectable again because Page Left enters the sample layer.
The logic makes sense, it just disables direct access to the Remote Controls. I'm aware everybody has their own preferences, but I would prefer easy and direct access to the Remote Controls (which are now in V2 imo clearly geared towards hands on access of performance related parameters) and sacrifice access to editing functions such as sample layering etc rather than the other way around. But that's just me.
edit: I should really test things a bit more thoroughly before posting, with Shift-PageLeft one does have access to the performance pages in the Drum Machine, just not via the cursor keys and only to eight banks (which should be plenty for most occasions). And there's not much sense in talking about a script which will be obsolete soon. So I'll shut up now and just look forward to the new script, I'm sure it'll be fantastic, thank you!
The logic makes sense, it just disables direct access to the Remote Controls. I'm aware everybody has their own preferences, but I would prefer easy and direct access to the Remote Controls (which are now in V2 imo clearly geared towards hands on access of performance related parameters) and sacrifice access to editing functions such as sample layering etc rather than the other way around. But that's just me.
edit: I should really test things a bit more thoroughly before posting, with Shift-PageLeft one does have access to the performance pages in the Drum Machine, just not via the cursor keys and only to eight banks (which should be plenty for most occasions). And there's not much sense in talking about a script which will be obsolete soon. So I'll shut up now and just look forward to the new script, I'm sure it'll be fantastic, thank you!
-
- KVRer
- 2 posts since 5 May, 2017
hi, im having a issue where in clip launching mode random buttons on the grid dont pulse when playing, but others do, is there any reason for this? it started after upgrading to bitwig 2 , iv updated scripts aswell.
cheers
cheers
- KVRAF
- Topic Starter
- 4874 posts since 13 May, 2004
I think that's a bug, should be fixed in the next version.codytc1 wrote:hi, im having a issue where in clip launching mode random buttons on the grid dont pulse when playing, but others do, is there any reason for this? it started after upgrading to bitwig 2 , iv updated scripts aswell.
cheers
-
- KVRer
- 2 posts since 5 May, 2017
moss wrote:I think that's a bug, should be fixed in the next version.codytc1 wrote:hi, im having a issue where in clip launching mode random buttons on the grid dont pulse when playing, but others do, is there any reason for this? it started after upgrading to bitwig 2 , iv updated scripts aswell.
cheers
i have figured out what courses the bug, so on on channel i have to clips, one with loop on and one with loop off, if i start with the looped clip the button flashed, go to the no looped clip it doesnt, go back to the looped clip and it doesnt flash any more. not sure if this helps you figure it out
-
- KVRist
- 58 posts since 24 Jun, 2012 from Leeds
Sorry if this has already been covered but I cant seem to navigate to a device within a chain using the controller at all. Im using Push 1 with Bitwig 2.
The only way to access the parameters is to click on the device inside the chain and then the parameters are accessible from the Push controller. I thought this was fixed but I was probably thinking of something else.
Thanks
Rich
The only way to access the parameters is to click on the device inside the chain and then the parameters are accessible from the Push controller. I thought this was fixed but I was probably thinking of something else.
Thanks
Rich
- KVRAF
- Topic Starter
- 4874 posts since 13 May, 2004
Use the "Device in" and "Device out" buttons (below the Browser/Clip button) to enter and leave device chains.richielg wrote:Sorry if this has already been covered but I cant seem to navigate to a device within a chain using the controller at all. Im using Push 1 with Bitwig 2.
The only way to access the parameters is to click on the device inside the chain and then the parameters are accessible from the Push controller. I thought this was fixed but I was probably thinking of something else.
Thanks
Rich
-
- KVRist
- 58 posts since 24 Jun, 2012 from Leeds
Yeah that doesnt work for me when any device is nested in a chain. I tried on latest stable release and also latest git hub using push 1 with bitwig 2. It does work on devices which are nested on an instrument later or fx layer though so I am just making my chains with these now.
- KVRAF
- Topic Starter
- 4874 posts since 13 May, 2004
Ah, you mean FX chains inside of a device. Yes, that is not supported because the navigation is already very complex and I did not want to add that feature, too.richielg wrote:Yeah that doesnt work for me when any device is nested in a chain. I tried on latest stable release and also latest git hub using push 1 with bitwig 2. It does work on devices which are nested on an instrument later or fx layer though so I am just making my chains with these now.
-
- KVRist
- 58 posts since 24 Jun, 2012 from Leeds
No I just mean an ordinary chain container device with an effect inside it. I will test it on a totally blank project for u later. But in my template it won't work at all.
