I used midi input in previous release successfully (4.7.4)
In the new 4.8.4 release, the Midi message (CC or PC) is well recognized when assigning it to a button in virtual console using auto-detection. for example, a value of "--program-change 0 102" is recognized as 487: ? for a button in virtual console.
I saved the configuration and send again the same message : The joystick appears in the Input of the dedicated Universe, but the button is never activated in virtual console.
Is there something new in midi configuration or some issue in that area ?
Thank's a lot in advance for your help and answer.
Regards
Alain
QLC+ 4.8.4 Windows7-32b Midi input is recognized but don't work in Vitrtual Console
Here is a simple project file to illustrate :
Regards
Alain
Regards
Alain
- Attachments
-
- BandeSon.qxw
- (22.15 KiB) Downloaded 24 times
Hello Massimo,
It seems only control-change is working fine.
Using program-change has no effect in Virtual Console in Operate mode.
The signal is well recognized but produces no action.
I tried control-change sucessfully with release 4.8.3
Regards
Alain
It seems only control-change is working fine.
Using program-change has no effect in Virtual Console in Operate mode.
The signal is well recognized but produces no action.
I tried control-change sucessfully with release 4.8.3
Regards
Alain
Hey,
so what I would say is the problem is the Input Configuration Profile:
If QLC detects a Midi Device and no Input Profile is selected where anything different is specified QLC assumes that the incoming message is a control change.
I would like to ask you wether you can create a custom input profile where you set the channel to "program-change" and see if it works then.
What this would not explain is why it worked in previous versions. I don't know wether this feature was in 4.7.4 already.
so what I would say is the problem is the Input Configuration Profile:
If QLC detects a Midi Device and no Input Profile is selected where anything different is specified QLC assumes that the incoming message is a control change.
I would like to ask you wether you can create a custom input profile where you set the channel to "program-change" and see if it works then.
What this would not explain is why it worked in previous versions. I don't know wether this feature was in 4.7.4 already.
Thank you for your answer.
It maybe the solution.
In a previous release, I did not used Program-change. I added it in order to obtain more midi choices.
I understand I have to create an Input Profil describing al the combination of Program-change, control-change, and other midi signals I want to capture.
Do I have a correct understanding?
Thank you in advance for your answer and help.
Best Regards
Alain
It maybe the solution.
In a previous release, I did not used Program-change. I added it in order to obtain more midi choices.
I understand I have to create an Input Profil describing al the combination of Program-change, control-change, and other midi signals I want to capture.
Do I have a correct understanding?
Thank you in advance for your answer and help.
Best Regards
Alain
Yes, you are correct. I think this will solve the problem.
You can learn about setting up your own input profile here: http://www.qlcplus.org/docs/howto-input-profiles.html
Read from "Manual Mode" on.
What you do is bascially telling QLC that you are sending programm-change inputs and noch control-change wich it assumes by default. You can do this with all midi input types i think.
You can learn about setting up your own input profile here: http://www.qlcplus.org/docs/howto-input-profiles.html
Read from "Manual Mode" on.
What you do is bascially telling QLC that you are sending programm-change inputs and noch control-change wich it assumes by default. You can do this with all midi input types i think.
I did the change and every thing is OK.
created a profile for theater prompter help.
Thank you and Best Regards
Alain
created a profile for theater prompter help.
Thank you and Best Regards
Alain