Latest News: Bitwig Updates Bitwig Studio to 5.2
DrivenByMoss: Bitwig extension for many hardware controllers (version 23.2.1)
-
- KVRian
- 862 posts since 4 Apr, 2001 from Finland
I am not sure if this is related to the controller script, but I suspect so:
I am very new to Bitwig and got the APC40 mk2 yesterday. I also installed the newest DrivenByMoss extension, which seems very nice so far. However, I have been playing around today and noticed a possible bug:
I changed the top row of knobs to the "user" mode so that I can map them to whatever. I successfully mapped the first four knobs to sends from individual parts from a drum machine and to some controls on a reverb on the send track.
Problem is, when I map the knobs 5-8 they not work reliably. Mapping itself works but the knobs reset thier value to zero by itself just after turning the knob.
Any ideas?
I am very new to Bitwig and got the APC40 mk2 yesterday. I also installed the newest DrivenByMoss extension, which seems very nice so far. However, I have been playing around today and noticed a possible bug:
I changed the top row of knobs to the "user" mode so that I can map them to whatever. I successfully mapped the first four knobs to sends from individual parts from a drum machine and to some controls on a reverb on the send track.
Problem is, when I map the knobs 5-8 they not work reliably. Mapping itself works but the knobs reset thier value to zero by itself just after turning the knob.
Any ideas?
-
- KVRian
- 862 posts since 4 Apr, 2001 from Finland
Ha! Figured this out. I needed to create empty tracks corresponding to the remaining knobs.
Hmm, now on my current project the device control knobs don't follow the selected track anymore. I'll try to figure out why. They work as expected on a new project though.
-
- KVRian
- 862 posts since 4 Apr, 2001 from Finland
A-ha! I had accidentally pressed this:
"Shift + Dev. Lock - Pin the cursor track and the cursor device."
Pressing it again makes it work as I thought again.
Thank you very much for this script. I initially tried the built-in one and the clip buttons didn't always flash properly, depending on the colour. With your script they work fine.
I am starting to like this whole setup quite a lot.
-
- KVRist
- 224 posts since 30 Mar, 2015
I'm having some fun with the moss scripts lately, and ran into something, I'm not sure if its a bug or that I am doing something wrong. I'm trying to replicate the ableton behaviour where the cursor keys can navigate through the clips on the grid. Pressing up/down works fine when invoking it like: this.model.getSelectedTrack().getSlotBank ().selectPreviousItem();
Pressing left/right would need to first select the next/prev track (works fine too), and then the clip at the same row. The problem is with the latter, it seems that this.model.getSelectedTrack().getSlotBank().selectItemAtPosition(position) doesn't do anything?
Pressing left/right would need to first select the next/prev track (works fine too), and then the clip at the same row. The problem is with the latter, it seems that this.model.getSelectedTrack().getSlotBank().selectItemAtPosition(position) doesn't do anything?
- KVRAF
- Topic Starter
- 4145 posts since 13 May, 2004
Hmm, could be that the select() in the method needs to be delayed a bit after the scrollTo (like in selectPrevious).SB-SIX wrote: ↑Sun Mar 17, 2019 11:14 am Pressing left/right would need to first select the next/prev track (works fine too), and then the clip at the same row. The problem is with the latter, it seems that this.model.getSelectedTrack().getSlotBank().selectItemAtPosition(position) doesn't do anything?
- KVRAF
- Topic Starter
- 4145 posts since 13 May, 2004
-
- KVRist
- 224 posts since 30 Mar, 2015
Cool thank you very much for the quick reply. I've tried and it kind of works
I can move up and down the clips using:
Code: Select all
this.model.getSelectedTrack().getSlotBank ().selectPreviousItem();
Code: Select all
final ISlot selectedSlot = this.model.getSelectedSlot();
if (selectedSlot != null){
final int slotposition = selectedSlot.getIndex();
this.model.getTrackBank().selectNextItem();
this.surface.scheduleTask ( () -> this.model.getSelectedTrack().getSlotBank().selectItemAtPosition(slotposition), 100);
} else {
this.model.getTrackBank().selectNextItem();
}
I've tried in several different ways too all with the same result. Can't figure out why, but it looks like the selectedslot is not reporting the right index?
Last edited by SB-SIX on Tue Mar 19, 2019 8:41 am, edited 1 time in total.
-
- KVRist
- 315 posts since 12 Jul, 2015
Hello !
I have found a bug i think on the push 2 version.
When i am on send or master track the "automate" button does not work.
that's all
thanks for your work !
have a good evening
I have found a bug i think on the push 2 version.
When i am on send or master track the "automate" button does not work.
that's all
thanks for your work !
have a good evening
- KVRAF
- Topic Starter
- 4145 posts since 13 May, 2004
- KVRAF
- Topic Starter
- 4145 posts since 13 May, 2004
You are getting the index but then you are using it to set the position. The index is the selection in the current bank page, the position is relative to ALL items in a bank.SB-SIX wrote: ↑Mon Mar 18, 2019 6:49 pm But on the latter I get very strange behaviour. If I press left/right, at first it works, but when I have pressed down (it goes down), and then right, it goes right AND down. After this, pressing left/right works normal again.
I've tried in several different ways too all with the same result. Can't figure out why, but it looks like the selectedslot is not reporting the right index?
-
- KVRist
- 224 posts since 30 Mar, 2015
Thanks again Moss!! I'm going to try it tonight. I'm learning alot along the way.moss wrote: ↑Mon Mar 25, 2019 8:20 amYou are getting the index but then you are using it to set the position. The index is the selection in the current bank page, the position is relative to ALL items in a bank.SB-SIX wrote: ↑Mon Mar 18, 2019 6:49 pm But on the latter I get very strange behaviour. If I press left/right, at first it works, but when I have pressed down (it goes down), and then right, it goes right AND down. After this, pressing left/right works normal again.
I've tried in several different ways too all with the same result. Can't figure out why, but it looks like the selectedslot is not reporting the right index?
- KVRist
- 34 posts since 24 Feb, 2019
Hi I wanted to report a bug, There is no CC40 in the selection choice of the Generic Flexi.
You can see that here:
https://imgur.com/a/QNLNLk3
Thanks a lot for this extension, it's so usefull !
You can see that here:
https://imgur.com/a/QNLNLk3
Thanks a lot for this extension, it's so usefull !
- KVRAF
- Topic Starter
- 4145 posts since 13 May, 2004