Bitwig

gigaherz · Post by **gigaherz** » Mon Oct 12, 2015 10:22 am

i have some issues with apc40 in win7, both bws 1.2 and 1.3rc1, both with script from github and your site. problem is with clip launcher not updating properly while moving around the project, also track control knob values aren't always updating properly, sometimes values are jumping around. when switching pan/sends, it sometimes takes almost two seconds before it updates on controller. in ableton, the unit is working fine. tried running only this script, disconnected all other controllers, prob still there. haven't tested it in detail, but more problems seems to appear with bigger projects. so maybe it's bitwig related, not script?

yeah, and feature request: pretty please, maybe it will be better to move macro controls to be switchable with device controls? for peforming live, i'd definitely will like to have access to macros and sends at the same time, while not wanting to mess something in the devices itself. or if you can point me out, what to change where in the script, i'm not a programmer, but still can try it at least.

anyway, thanks for your huge amount of work for the community with all the scripts you've done! cheers.

moss · Post by **moss** » Mon Oct 12, 2015 11:32 am

gigaherz wrote:i have some issues with apc40 in win7, both bws 1.2 and 1.3rc1, both with script from github and your site. problem is with clip launcher not updating properly while moving around the project, also track control knob values aren't always updating properly, sometimes values are jumping around. when switching pan/sends, it sometimes takes almost two seconds before it updates on controller. in ableton, the unit is working fine. tried running only this script, disconnected all other controllers, prob still there. haven't tested it in detail, but more problems seems to appear with bigger projects. so maybe it's bitwig related, not script?

Sadly I can't do anything about it. I already have some requests open with Bitwig to look into performance improvements. I hope that they will find some time now that the updates are out of the door. Furthermore, the APC hardware is pretty slow in updating.

gigaherz wrote:yeah, and feature request: pretty please, maybe it will be better to move macro controls to be switchable with device controls? for peforming live, i'd definitely will like to have access to macros and sends at the same time

That makes sense. Will think about it.

moss · Post by **moss** » Sun Oct 18, 2015 10:54 am

I released a small update 3.01:

- Shift+Device On/Off toggles editing of device parameters and macros.
- Fixed: Notes did not cover the full range (octave range extended).
- Fixed: Display of the note range was wrong.

There's also a new tutorial video which explains the new features:

moss · Post by **moss** » Sun Oct 18, 2015 11:05 am

There's also a small update for the APCmini:
- Fixed: Notes did not cover the full range (octave range extended).

moss · Post by **moss** » Fri Jan 01, 2016 6:28 pm

I just released an update 3.02:

* You can now select the root note of the scale. Press Shift and use the first two row buttons (arranged like a keyboard).
* Fixed lag of script especially in combination with other scripts like Push4Bitwig due to very slow processing of LED button updates. The button states are now cached and only updated when changed.

Get it from: http://mossgrabers.de/Software/Bitwig/Bitwig.html

Zetzetovitch · Post by **Zetzetovitch** » Sun Jan 10, 2016 2:31 am

I'm using AKAI APC mini and I have always a bug. If I change "window" by some button ex. "Stop All Clips" or Fader CTRL section I can't back to previous place. Controller crash and is not responding.

moss · Post by **moss** » Sun Jan 10, 2016 10:27 am

Zetzetovitch wrote:I'm using AKAI APC mini and I have always a bug. If I change "window" by some button ex. "Stop All Clips" or Fader CTRL section I can't back to previous place. Controller crash and is not responding.

What do you mean by "change "window""? I tried switching the different modes but could not produce an error.
Do get an error message in the script log window?

moss · Post by **moss** » Sun Jan 31, 2016 2:23 pm

I released a new version for APC and APCmini.

All:
* Fixed: Important performance improvement (updates of button LEDs are only done when changed) which fixes external hardware sync.
APCmini:
* Added options to configure layout in play view with scene buttons.

Zetzetovitch · Post by **Zetzetovitch** » Sun Jan 31, 2016 4:50 pm

GREAT!

Synth-Project · Post by **Synth-Project** » Thu Feb 04, 2016 9:21 am

Absolute Great !

Thanks a lot for this perfect script.

Is there a chance with a future update to implement a 6th mode, where the grid is split into two zones ?
Left side, first four tracks as the session mode and the right side, track 5 to 8 for the transport mode, like a have when i push the shift button. So i don't need to push the shift button if i wanna undo something or overdub or create an empty clip.

All the best

Mario

bheinz63 · Post by **bheinz63** » Fri Feb 19, 2016 5:42 pm

Thank you so much for all your hard work on this script. I bought the APC40 MK2 yesterday solely for this script, and it has performed flawlessly so far. However, I have a quick question; Is it possible to set up in the controller/Bitwig that a volume fader value in Bitwig does not change until the physical fader on the APC40 MK2 reaches that value? Currently i get huge jumps in level when adjusting volume on newly controlled tracks as soon as I move a fader. With the knobs this does not seem to be a problem, as when they map to a new device/layer the LED's tell us what value the knob is currently at.

moss · Post by **moss** » Mon Feb 22, 2016 8:38 am

bheinz63 wrote:Thank you so much for all your hard work on this script. I bought the APC40 MK2 yesterday solely for this script, and it has performed flawlessly so far. However, I have a quick question; Is it possible to set up in the controller/Bitwig that a volume fader value in Bitwig does not change until the physical fader on the APC40 MK2 reaches that value? Currently i get huge jumps in level when adjusting volume on newly controlled tracks as soon as I move a fader. With the knobs this does not seem to be a problem, as when they map to a new device/layer the LED's tell us what value the knob is currently at.

I have this on my list for some time but its a bit tricky to implement. Can't promise anything.

bheinz63 · Post by **bheinz63** » Thu Mar 10, 2016 2:55 am

moss wrote:
bheinz63 wrote:Thank you so much for all your hard work on this script. I bought the APC40 MK2 yesterday solely for this script, and it has performed flawlessly so far. However, I have a quick question; Is it possible to set up in the controller/Bitwig that a volume fader value in Bitwig does not change until the physical fader on the APC40 MK2 reaches that value? Currently i get huge jumps in level when adjusting volume on newly controlled tracks as soon as I move a fader. With the knobs this does not seem to be a problem, as when they map to a new device/layer the LED's tell us what value the knob is currently at.
I have this on my list for some time but its a bit tricky to implement. Can't promise anything.

One more quick question. Do the device control knobs map the way they do for native plug ins, for 3rd party VSTs?

moss · Post by **moss** » Thu Mar 10, 2016 7:54 am

bheinz63 wrote:One more quick question. Do the device control knobs map the way they do for native plug ins, for 3rd party VSTs?

You can (and should) map all VST parameters to individual banks in Bitwig (right click on the device and select "Edit Panel Mappings"). These mapped parameters can then be controlled from the APC.

jaytwoeight · Post by **jaytwoeight** » Thu Mar 24, 2016 8:22 pm

Hey Moss,

Thanks so much for writing this script. It works really well and I have one question:

Do you think it's possible to create a dj-style combo filter effect and map it to the knobs at the top of an APC40 mkII (which currently control Pan)?

I tried this via a macro which controls 2 filter effects (high pass and low pass), but it appears that a knob assigned to a macro cannot control the parameters of 2 filter effects, in a way where turning the knob to the left (from the 12 o'clock position) increases the high pass filter, while turning it to the right (from the 12 o'clock) increases the low pass filter.

I have quite a bit of JavaScript experience and if it is possible to do this via a combination of API scripts and built-in macro controls, I can look into modifying your code myself. I just need:
A) to know if you think this is possible at all
B) some pointers on how to accomplish (via "forking" your template)

Thanks!

Bitwig

KVR Audio

APC40, APC40mkII and APCmini support is here!