Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Control via Midi CC - Issues
#1
I would hope the team could do a thorough check of all functions controllable via CC from a DAW.

1/ What is very obvious is the 'flashing' of the display, that does not happen when editing locally.
2/ When driving from CC's often a red 'MTC' will appear which is distracting and probably unnecessary
3/ CC47 DIV is not functioning
4/ CC48 and CC50 trigger bad screen flashes and a yellow 'NO' in the bottom LHS
5/ Events (especially notes) triggered via CC are way slower than when triggered via notes. Example: Bitwig keyboard Vs Bitwig button CC's, both piped through the same signal flow i.e Bitwig>NDLR>Bitwig Instrument
6/ In Bitwig there is only latched buttons on/off available to trigger notes, modes, scales etc via CC. So what happens is when selecting another button, instead of triggering a new event and killing the old one....the CC's are summed. 
ex: Press a D,E,F,G,A or B note, press again to release and the C drone is triggered.
ex: Press a 2,3,4,5,6 or 7 Mode, press again to release and the 1 mode is triggered
ex: Press mode 2 + 3 and mode 5? is triggered etc....
i.e additive behaviour when using CC's ....a bit like the old rhythm machines where you could hold down multiple buttons to combine rhythms.
Reply


Messages In This Thread
Control via Midi CC - Issues - by MKS30 - 01-10-2019, 11:27 PM
RE: Control via Midi CC - Issues - by Darryl - 01-11-2019, 02:21 AM
RE: Control via Midi CC - Issues - by Steve - 01-11-2019, 05:39 PM

Forum Jump:


Users browsing this thread:
1 Guest(s)