I have a question that pertains to the behavior of the Bitwig-supplied controller script for the Arturia Keylab 49. This behavior is the same on both my Mac and Windows 10 computer.
When using the included control script, when I turn the knob mapped to the device selection function, the selected primary device will change on whatever track has the focus at the time. If I turn the track knob, a different track will be selected and if I turn the device knob than it will change which device had been set as the primary device in that track so that I can page through the different device panel mappings for that device and use the color-coded controls.
This is all very good but the device knob will only allow me to select a device in whatever the current level of nested device chains I happen to be in. I can move left and right between devices in the same level of nesting but I cannot move further to the left and right to access other devices on the same track that happen to be at a different level of nesting.
For example: if I have three devices nested inside a polysynth FX chain, and one of them is set as the primary device, I can turn the knob on my Keylab to access any of the three devices nested inside the polysynth. But if the whole polysynth (and all of the devices nested inside its FX chain) is itself located within another device's FX chain, like an LFO or Audio Mod, then I cannot use the knob to get all the way out to the polysynth's "parent" device, in this example the LFO or Audio Mod.
I don't mind learning out how to modify my controller script, but I was wondering:
1) if someone with more controller script experiences thinks this will be at all possible for me to do or is it a waste of time
2) where the best controller script and API docs are
3) where in the Bitwig-supplied Keylab Controller you think I ought to be looking to study the current behavior and make my modification.
I'd like to make the behavior of my knob be to be able to set the primary device to be anywhere on the current track's device rack regardless of nesting, and to expand out the GUI display of an FX chain if a device becomes primary and it is not currently visible.
Thanks,
Scott
Behavior of Device Selection Knob on Arturia Keylab 49
Moderator: Bitwig Mods
Behavior of Device Selection Knob on Arturia Keylab 49
2015-10-04T18:09:04+00:00
I have a question that pertains to the behavior of the Bitwig-supplied controller script for the Arturia Keylab 49. This behavior is the same on both my Mac and Windows 10 computer.
When using the included control script, when I turn the knob mapped to the device selection function, the selected primary device will change on whatever track has the focus at the time. If I turn the track knob, a different track will be selected and if I turn the device knob than it will change which device had been set as the primary device in that track so that I can page through the different device panel mappings for that device and use the color-coded controls.
This is all very good but the device knob will only allow me to select a device in whatever the current level of nested device chains I happen to be in. I can move left and right between devices in the same level of nesting but I cannot move further to the left and right to access other devices on the same track that happen to be at a different level of nesting.
For example: if I have three devices nested inside a polysynth FX chain, and one of them is set as the primary device, I can turn the knob on my Keylab to access any of the three devices nested inside the polysynth. But if the whole polysynth (and all of the devices nested inside its FX chain) is itself located within another device's FX chain, like an LFO or Audio Mod, then I cannot use the knob to get all the way out to the polysynth's "parent" device, in this example the LFO or Audio Mod.
I don't mind learning out how to modify my controller script, but I was wondering:
1) if someone with more controller script experiences thinks this will be at all possible for me to do or is it a waste of time
2) where the best controller script and API docs are
3) where in the Bitwig-supplied Keylab Controller you think I ought to be looking to study the current behavior and make my modification.
I'd like to make the behavior of my knob be to be able to set the primary device to be anywhere on the current track's device rack regardless of nesting, and to expand out the GUI display of an FX chain if a device becomes primary and it is not currently visible.
Thanks,
Scott
scottboyan
https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=366859
-
- KVRer
- 22 posts since 22 Sep, 2015
Post by scottboyan »
Post Reply
1 post
• Page 1 of 1
Return to “Controller Scripting”
Jump to
- The Main Forums
- ↳ KVR Studio Manager
- ↳ Getting Started (AKA What is the best...?)
- ↳ Instruments
- ↳ Effects
- ↳ Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)
- ↳ Guitars
- ↳ Mobile Apps and Hardware
- ↳ Soundware
- ↳ Samplers, Sampling & Sample Libraries
- ↳ Hardware (Instruments and Effects)
- ↳ Modular Synthesis
- ↳ Sound Design
- ↳ Production Techniques
- ↳ Music Theory
- ↳ Computer Setup and System Configuration
- ↳ DSP and Plugin Development
- ↳ DIY: Build it and they will come
- ↳ Music Cafe
- ↳ Sell & Buy (+Special Offers, Deals & Promos)
- ↳ KVR Experts
- ↳ KVR Developer Challenge 2026
- ↳ Everything Else (Music related)
- ↳ Off Topic
- ↳ Off Topic Classics
- ↳ Machine Learning and AI for Music Creation
- Official Company Forums
- ↳ 2getheraudio
- ↳ accSone
- ↳ Acon Digital
- ↳ AcousticsampleS
- ↳ AcousModules
- ↳ Agitated State
- ↳ AIR Music Technology
- ↳ AMG
- ↳ Ample Sound
- ↳ Antares Audio Technologies
- ↳ Apisonic Labs
- ↳ APU Software
- ↳ apulSoft
- ↳ AriesCode
- ↳ Arts Acoustic
- ↳ Arturia
- ↳ Audjoo
- ↳ AudioSpillage
- ↳ Audiority
- ↳ Best Service
- ↳ Big Tick
- ↳ Bitwig
- ↳ Controller Scripting
- ↳ Blue Cat Audio
- ↳ Cherry Audio
- ↳ CWITEC
- ↳ Embertone
- ↳ energyXT
- ↳ Eventide
- ↳ Expert Sleepers
- ↳ forward audio
- ↳ Future Audio Workshop
- ↳ FXpansion
- ↳ g200kg
- ↳ Harrison Mixbus
- ↳ HG Fortune
- ↳ Homegrown Sounds
- ↳ HoRNet Plugins
- ↳ Ilya Efimov Production
- ↳ Image Line
- ↳ Impact Soundworks
- ↳ Indiginus
- ↳ Insert Piz Here
- ↳ Ju-X
- ↳ Kirk Hunter Studios
- ↳ Kirnu
- ↳ Kong Audio
- ↳ Krotos
- ↳ Kuassa
- ↳ KV331 Audio
- ↳ LennarDigital
- ↳ Les Productions Zvon
- ↳ Liqube Audio
- ↳ Loomer
- ↳ LVC-Audio
- ↳ Maizesoft
- ↳ Manytone Music
- ↳ Media Overkill (MOK)
- ↳ MeldaProduction
- ↳ Mellowmuse
- ↳ MIDIMood
- ↳ moForte
- ↳ Mozaic Beats
- ↳ mucoder
- ↳ MusicDevelopments
- ↳ Tips & Tricks
- ↳ MusicLab
- ↳ MuTools
- ↳ New Sonic Arts
- ↳ NUSofting
- ↳ Oli Larkin Plugins
- ↳ Orange Tree Samples
- ↳ patchpool
- ↳ Photosounder
- ↳ PlugInGuru
- ↳ Polyverse Music
- ↳ Precisionsound
- ↳ Premier Sound Factory
- ↳ Psychic Modulation
- ↳ Realitone
- ↳ Resonance-Sound
- ↳ Reveal Sound
- ↳ Roger Linn Design
- ↳ rs-met
- ↳ S3A: Spatial Audio
- ↳ SaschArt
- ↳ Smart Electronix
- ↳ sonible
- ↳ SonicBirth
- ↳ Sonic Reality / eSoundz.com
- ↳ Soundiron
- ↳ SPC Plugins
- ↳ Sugar Bytes
- ↳ TAL Software
- ↳ Tokyo Dawn Labs
- ↳ Tracktion
- ↳ Tweakbench
- ↳ u-he
- ↳ u-he Linux support
- ↳ UJAM
- ↳ United Plugins
- ↳ VAZ Synths
- ↳ Virharmonic
- ↳ xoxos
- ↳ XSRDO - SynthCraft
- ↳ ZynAddSubFX
- Site Stuff
- ↳ Site Stuff
- Archived Forums
- ↳ AlgoMusic
- ↳ easytoolz
- ↳ Elevayta
- ↳ Hollow Sun
- ↳ LinPlug
- ↳ Muse Research and Development
- ↳ Shuriken
- ↳ SoHa Sound Design
- ↳ Soniccouture
- ↳ Topten Software
- ↳ Valhalla DSP
- ↳ CK Modules & VST
- ↳ Sennheiser AMBEO
- ↳ Muon Software
- ↳ Westgatesounds.net
- ↳ Squaredheads
- ↳ Sonigen
- ↳ CFA-Sound
- ↳ Back In Time Records
- ↳ Livelab.dk
- ↳ Skytopia
- ↳ audioD3CK
- ↳ Inspire Audio
- ↳ Krakli
- ↳ Drumdrops
- ↳ Futucraft
- ↳ OverTone DSP
- ↳ RaXnTraX
- ↳ solar3d-software
- ↳ Signaldust
- ↳ Soundemote
- ↳ ReleaseLab (Powered by Artist Expansion)
- ↳ Wolfgang Palm
- KVR Forum index
- All times are UTC
- Delete cookies
