PC midi msgs problems in VC chaser

Ask a generic question about the usage of QLC+, not related to a particular operating system
Post Reply
vector
Posts: 91
Joined: Fri Sep 23, 2016 9:25 pm
Real Name: Mark Sy

Hi all,
I am having some issues with FCB1010 midi msgs. But I dont believe its FCB related.
Sending note msgs to control a VC chaser {play,stop,prev,next} seem to be ok but PC msgs may work once then the chaser goes deaf(unresponsive).

I have FCB1010 UNO and their setup software so its easy to see/ program its parameters.
Looking at a midi monitor app, msgs from FCB look correct.
In qlc setup the "joystick" is working as expected (midi set to universe 2, dmx Uni 1)
The input profile editor correctly sees and maps all msgs from FCB.
I have also checked this with the autodetect feature on VC item.

If I assign FCB to sending note msgs (C,D,E,F etc) and link that with the chaser transport control {play,stop,prev,next} everything seems fine.
If I assign FCB to send PC changes PC 128,PC 127 translated as channel 512,511 etc It may work once but then the chaser becomes deaf to further PC msgs.
If I assign the same msgs to VC buttons(for debug purpose) they work.ie the buttons toggle but the chaser is still deaf. I realise this last test may cause strange behaviour but it proves that QLC is receiving and decoding the midi msg correctly and that its the chaser that is broken. (ie remove the "debug" buttons and the chaser still does not work.
reloading qlc may allow the chaser to work(via the PC msgs for perhaps 1-3 msgs but then it just becomes unresponsive.
Attachments
FCB-1010.qxi
input profile-simplified
(1.7 KiB) Downloaded 66 times
FCB-prblm3.qxw
basic workspace
(6.9 KiB) Downloaded 22 times
Post Reply