APC40, APC40mkII and APCmini support is here!

Post Reply New Topic
RELATED
PRODUCTS
Bitwig Studio 6$399.00Buy

Post

I just got an APC mini and your script is the boss. Thank you VERY much!

:hug:

Post

Wondering if anyone else is experiencing this. I have 9 tracks open,when I try to switch from track 8-9 the clip bank moves from 1-8 to 2-9 but instead of the track selection jumping to track 9 it jumps back to track 9 and I have to scroll all the way through the new bank. This has only happened since 2.2 I believe.

Any help would be amazing. Thank You.

Post

Hi moss. First off, let me say how amazing your APCmini script is :tu: I used to own an APCmini but gave it to a friend. I now have come across an APC Key 25 which I would like to use your APCmini script with. Both controllers have very similar layouts and commands. It seems the keys on the controller however misbehave and I believe it is because the APCmini script ignores midi channel? The keys on the APC Key 25 come from midi channel 1 and the rest of the buttons come from midi channel 0, just like the APCmini. I believe I need to tell your script to ignore any messages coming from midi channel 1 so they keys play the proper notes. I'm a novice programmer so any advice you have would be awesome! Thanks again for all your hard work on these beautiful scripts!

P.S. Is there a way to extract the APCmini script from your bwextension? I am currently modifying an old script (3.10) as this is the last posted APCmini script on your website. Thanks!

Post

There is something strange with the top eight encoders on the APC40MKII: when I map the encoders to some controls in [user] mode (not [sends]/[pan]), the last 2 or 4 encoders lose their value as soon as I release them. Sometimes it happens with encoders 5-8, sometimes it happens with 7-8.
As soon as I touch them they send a zero value, then they work as intended until I stop turning them.
When the encoders lose their value, the LED ring resets to unlit state.
Any idea ?

(Bitwig 2.2.3 / Linux / up-to-date version of Drivenbymoss script)

Post

I released a little update:

# 5.10
Requires Bitwig 2.2.
* New: Display the view names when switching between them.

Post

And another one:

# 5.11
* New: Shift + Dev. Lock pins the cursor device.

Post

moss wrote:And another one:

# 5.11
* New: Shift + Dev. Lock pins the cursor device.
Great updates! Thanks a lot for your work!

Is there also a way to pin the cursor track? As of now, this only pins the cursor device which means that whenever I click on another track it will change to that track. It would be nice to be able to pin the cursor track as well so that the APC can stay with that track.

Post

Here is a little update:

# 5.12
Requires Bitwig 2.3.

* New: Shift + Dev. Lock pins now also the cursor track because only pinning the device does not work.

Post

Hi Jurgen, the new version is not inside the Drivenbymoss.zip file. Could you tell me where it can be found?
(excuse me if i am blind to the obvious)
Thank you! Nathan

Post

stufflin wrote:Hi Jurgen, the new version is not inside the Drivenbymoss.zip file. Could you tell me where it can be found?
(excuse me if i am blind to the obvious)
Thank you! Nathan
What do you mean by "it is not inside"? The file to use is DrivenByMoss.bwextension. Or do you mean the new feature does not work?

Post

I am sorry to bother you jurgen. I was looking for .js-files.
My bad. (Shouldve went to the wiki/instructions)

Thanks for your work!!

Post

There is a new update available.

To make my life a bit easier I decided to centralise the info in one thread:
http://www.kvraudio.com/forum/viewtopic ... 8&t=502948

You can keep posting in this thread or in the new one, whichever you prefer.

Post Reply

Return to “Controller Scripting”