I recently purchased a Presonus Faderport 16 controller specifically because it was listed as "officially supported" for Bitwig. Unfortunately a significant issue I encountered while using is that the native Faderport script doesn't allow you to control channels within a group channel. This prevents anyone from using the Faderport script to control all channels! Deal Breaker!
As a temporary solution, I have been using the Faderport in Mackie MCU mode, driven by moss but its not ideal, and I believe its not officially supported as a mossgrabber script I dont think.
When I physically touch one of the faders to change the track volume, all the faders will move and wig out and kinda glitch. Moss, is there a reason this would be happening? Also when you boot up the Faderport there is a few modes to put it in, MCU, Ableton, Logic, and native Studio One mode. Do you know which one I should put it in? Do you know how to fix the glitching? Thank you!
Presonus Faderport 16 driven by moss script... strange behavior
-
- KVRer
- Topic Starter
- 19 posts since 2 May, 2004
Kevin
www.myspace.com/kevinalvesakagift
Baroque, Blackhole, Lost Language, Solaris
Bestport artist: Gift
www.myspace.com/kevinalvesakagift
Baroque, Blackhole, Lost Language, Solaris
Bestport artist: Gift
- KVRist
- 327 posts since 12 Apr, 2020
Sounds strange... If its a driven by moss extension you want to post in that thread. That is where moss handles support for it.
----------------------------------------------------------------------
http://instagram.com/kirkwoodwest/
http://soundcloud.com/kirkwoodwest
http://instagram.com/kirkwoodwest/
http://soundcloud.com/kirkwoodwest