Here is a status update, this work is done in the midi_omni branch in my repo.
1. Midi init messages can be selected from the midi config screen.
2. Midi init messages are red from XML files.
3. It works on Mac and Linux.
4. Windows is almost finished.
Todo list:
1. Sysex messages have a size limit (65k on Mac) so I have to split them if this limit is exceeded.
2. Finish Windows part.
3. Make XML reader less strict. It now expects a pattern (XX XX XX...)
I did my first show with QLC+ and the APC20 last week.
I had several scenes under the buttons and controlled the master/speed/smoke/etc with the faders.
Here is a short video: http://youtu.be/XLoC2q1O3hI
When I have an other gig I'll try to make a more interesting video :-)
Last edit: Joep Admiraal 2013-10-10
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello everyone. I've been playing around with QLC+ for a few months and have lately been trying to use it with an Akai APC40. The APC40 is like the 20's big brother, it is the same as the 20 but with more knobs and buttons. Like the 20, it distributes it's MIDI data across several channels. I'd love to be able to use it with QLC+, but unlike you gentlemen I have very little programming experience and am not too familiar with SourceForge or GitHub.
@Massimo, how do I integrate the MIDI Omni patch you posted in this thread to QLC? I have no need for feedbacks and would be very happy with what you seem to have so far. Thank yo so much for all your work on this project.
@Joep, very nice setup! I hope the show went well. I was able to find your GitHub page but can't tell if that's the version that I want to grab to be able to use my APC40. Will downloading the version listed on your page work?
Thanks again to both of you and the rest of the QLC crew.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
the MIDI omni patch was integrated in November, QLC+ 4.6.0. Profile for APC20 is also included, you most probably can start with that and extend as needed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you very much, I didn't see anything in the changelog about MIDI channel data handling in the changelog so I assumed these features hadn't been integrated yet. Cheers again.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
http://i.imgur.com/wqdiAZn.png
Happily working now! The APC was getting itself into trouble with Ableton and that's why QLC was only noticing the first MIDI channel, like how it used to in QLC 4.5 and earlier. It's slightly different than the 20 in how it responds on starting up.
I'll have a labeled profile for it for sharing soon.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
LED feedback is also functional. Where else should I post this input profile? I don't think it would belong in the Fixture Definitions Thread? I have all buttons, knobs, and faders mapped and labeled as well as I saw the already included definitions, hopefully someone else will find a use for it.
I tried your file but i have no reaction in the software. The slider number 1 react but the second, thirt etc don't work. I put the file in C:qlc+ --> inputs with the apc20. then open qlc+ then input/outpu, i check akaiapc40 but no response.
it doesn't work with my apc40, can you post a picture ? and describe step by step plz. i don't understand...i seach during week end but i didn't find. plz help me ;)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@Massimo and Jano: MIDI Omni must be on but that is likely not the problem he is experiencing. He's probably going through what I did with the APC40 wanting to talk to Ableton before QLC+.
@ thomas, is your APC40 in dumb mode (no lights on?) To put it there, close all open programs, plug in and power on your APC40, open Ableton (make sure there is the colored control box), then close Ableton. All lights should go off on the 40. Now, open up QLC+, select the input profile for the APC40, make sure you're in MIDI omni mode.
The APC20 is different in how you put it into the right mode, but I do not own one. If Joep sees this he can probably offer you help with that one.
I can grab pictures when I get home from work.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is why the MIDI Init Message is added to QLC+.
When go to the MIDI configuration a field called 'Init Message' should be present.
Set this field to 'APC 20 Ableton mode 2' and QLC+ will send the Ableton init message to your controller on startup.
That way you don't need to start Ableton to get the APC in the right mode.
I only tested the code thoroughly on a mac so please let me know if it is working for you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Here's a simplified explanation: MIDI data from the APC40 is like notes on a piano. On a piano and in a musical octave, you do a certain number of notes then repeat the same notes again (A B C D E F G A B C D E F G A...). Each column of the APC40 is the same notes but in a different octave. If only the first channel is working, that's because you only have QLC+ listening to the first channel of data.
To get it your board talking to QLC properly, you have to tell it to talk a different way. The most reliable way of doing this is to plug it into your computer, turn it on, then open Ableton. You should get the coloured box showing that the APC connected to Ableton. Then, close Ableton. All the lights on your board should go off. Now, open QLC+. Look at Joep's picture again: https://sourceforge.net/p/qlcplus/discussion/general/thread/80d7426b/e668/1332/attachment/Schermafbeelding%202014-03-15%20om%2010.52.46.png
Make sure you have it on Midi Omni, and it should work accross all channels now. I believe the 4.7 Release Candidate has the profile for the APC40 I made, you should be able to test that out with it.
Is that working now?
Last edit: Daniel Curry 2014-03-27
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thomas, please provide more information about your setup (OS, QLC+ version).
What happens when you edit a button in the virtual console, press the auto detect button and then press the buttons in the second row on your APC40?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I'm trying to get an APC40 working with QLC+. I set up everything as you suggest, input is working as expected but feedback still has some issues.
- Pushing button on apc40 trigger VC correctly but led button remains off;
- Clicking button on VC make the apc40 button power on
Is APC40 init message different from APC20's one?
I set omni mode 1-16 in MIDI config, then which is the best settings beetwen Program Change, Control Change and Note Velocity?
Tested on Mac and Win with QLC 4.6.1 and 4.7RC
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have both input and feedback on Control Change and LED feedback is working for me on the top grid. The Mute, Activate, and Solo buttons are a bit weirder sometimes, they don't always go on for flash buttons and I haven't figured out why yet.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've done some tests.
QLC+ seems sending feedback to APC correctly, but there are some issues lighting up buttons.
For example feedback for knobs works perfectly!
Using Midi Monitor I got these results:
->STATUS: VC&APC OFF, ACTION: PUSH APC40 BUTTON|
01:01:19.349 From Akai APC40 Note On 1 F2 127
01:01:19.361 To Akai APC40 Note On 1 F2 127
01:01:19.510 From Akai APC40 Note Off 1 F2 127
->RESULT: BUTTON IS LIGHT UP IN QLC VC, NOT IN APC40
->STATUS: VC&APC OFF, PUSH VC BUTTON
01:03:36.258 To Akai APC40 Note On 1 F2 127
->RESULT: BUTTON LIGHTS UP IN APC40 AND VC
->STATUS: VC&APC40 BUTTON ON, PUSH APC40 BUTTON.
01:06:16.241 From Akai APC40 Note On 1 F2 127
01:06:16.254 To Akai APC40 Note Off 1 F2 0
01:06:16.342 From Akai APC40 Note Off 1 F2 127
->RESULT: BOTH BUTTONS OFF
I Attach also a PDF I've found about APC40 Midi Map, maybe will be useful.
Here is a status update, this work is done in the midi_omni branch in my repo.
1. Midi init messages can be selected from the midi config screen.
2. Midi init messages are red from XML files.
3. It works on Mac and Linux.
4. Windows is almost finished.
Todo list:
1. Sysex messages have a size limit (65k on Mac) so I have to split them if this limit is exceeded.
2. Finish Windows part.
3. Make XML reader less strict. It now expects a pattern (XX XX XX...)
I did my first show with QLC+ and the APC20 last week.
I had several scenes under the buttons and controlled the master/speed/smoke/etc with the faders.
Here is a short video:
http://youtu.be/XLoC2q1O3hI
When I have an other gig I'll try to make a more interesting video :-)
Last edit: Joep Admiraal 2013-10-10
Hello everyone. I've been playing around with QLC+ for a few months and have lately been trying to use it with an Akai APC40. The APC40 is like the 20's big brother, it is the same as the 20 but with more knobs and buttons. Like the 20, it distributes it's MIDI data across several channels. I'd love to be able to use it with QLC+, but unlike you gentlemen I have very little programming experience and am not too familiar with SourceForge or GitHub.
@Massimo, how do I integrate the MIDI Omni patch you posted in this thread to QLC? I have no need for feedbacks and would be very happy with what you seem to have so far. Thank yo so much for all your work on this project.
@Joep, very nice setup! I hope the show went well. I was able to find your GitHub page but can't tell if that's the version that I want to grab to be able to use my APC40. Will downloading the version listed on your page work?
Thanks again to both of you and the rest of the QLC crew.
Daniel,
the MIDI omni patch was integrated in November, QLC+ 4.6.0. Profile for APC20 is also included, you most probably can start with that and extend as needed.
Thank you very much, I didn't see anything in the changelog about MIDI channel data handling in the changelog so I assumed these features hadn't been integrated yet. Cheers again.
http://i.imgur.com/wqdiAZn.png
Happily working now! The APC was getting itself into trouble with Ableton and that's why QLC was only noticing the first MIDI channel, like how it used to in QLC 4.5 and earlier. It's slightly different than the 20 in how it responds on starting up.
I'll have a labeled profile for it for sharing soon.
Nice!
Are the led's in the buttons also working?
Last edit: Joep Admiraal 2014-02-26
LED feedback is also functional. Where else should I post this input profile? I don't think it would belong in the Fixture Definitions Thread? I have all buttons, knobs, and faders mapped and labeled as well as I saw the already included definitions, hopefully someone else will find a use for it.
Last edit: Daniel Curry 2014-02-27
Thanks Daniel.
I'm gonna check it and eventually include it in the incoming 4.7.0 version
Hello,
I tried your file but i have no reaction in the software. The slider number 1 react but the second, thirt etc don't work. I put the file in C:qlc+ --> inputs with the apc20. then open qlc+ then input/outpu, i check akaiapc40 but no response.
Do u have an idea ?
edit : Ok, i think i forgot something. like this
http://www.google.fr/imgres?safe=strict&client=firefox-a&hs=ep4&sa=X&rls=org.mozilla%3Afr%3Aofficial&biw=1280&bih=885&tbm=isch&tbnid=rP8zTGGdKFLXfM%3A&imgrefurl=http%3A%2F%2Fsourceforge.net%2Fp%2Fqlcplus%2Fdiscussion%2Fgeneral%2Fthread%2F80d7426b%2F%3Flimit%3D50&docid=NYtrC-fLSO3wpM&imgurl=http%3A%2F%2Fsourceforge.net%2Fp%2Fqlcplus%2Fdiscussion%2Fgeneral%2Fthread%2F80d7426b%2Fe83e%2Fattachment%2FSchermafdruk%252520van%2525202013-09-29%25252016%25253A49%25253A55.png&w=642&h=329&ei=KZQQU7fWBo7X7AaesoDoBQ&zoom=1&iact=rc&dur=116&page=2&start=25&ndsp=31&ved=0CPYBEK0DMDM
Last edit: thomas 2014-02-28
Hi, MIDI mode must be omni, right Joep & Daniel ?
Idea1: we could have a flag in profile to put the MIDI input in OMNI mode automatically when that profile is use.
Idea2: QLC+ would do that automatically, if the profile contains more than one MIDI channel.
Idea3: OMNI would be the default mode for MIDI plugin.
it doesn't work with my apc40, can you post a picture ? and describe step by step plz. i don't understand...i seach during week end but i didn't find. plz help me ;)
Last edit: Daniel Curry 2014-03-08
@Massimo and Jano: MIDI Omni must be on but that is likely not the problem he is experiencing. He's probably going through what I did with the APC40 wanting to talk to Ableton before QLC+.
@ thomas, is your APC40 in dumb mode (no lights on?) To put it there, close all open programs, plug in and power on your APC40, open Ableton (make sure there is the colored control box), then close Ableton. All lights should go off on the 40. Now, open up QLC+, select the input profile for the APC40, make sure you're in MIDI omni mode.
The APC20 is different in how you put it into the right mode, but I do not own one. If Joep sees this he can probably offer you help with that one.
I can grab pictures when I get home from work.
This is why the MIDI Init Message is added to QLC+.
When go to the MIDI configuration a field called 'Init Message' should be present.
Set this field to 'APC 20 Ableton mode 2' and QLC+ will send the Ableton init message to your controller on startup.
That way you don't need to start Ableton to get the APC in the right mode.
I only tested the code thoroughly on a mac so please let me know if it is working for you.
how i put the midi omni mode ? because i make exactly what you describe and don't work ...
I attached 2 screenshots of the settings on my machine. Hope it helps.
It doesn't work... i try but i don't understand. Just the first slider and first colum button on my apc40 work.
Daniel curry, can you help me plz ?
"make sure you're in MIDI omni mode." what is this mode ???
Here's a simplified explanation: MIDI data from the APC40 is like notes on a piano. On a piano and in a musical octave, you do a certain number of notes then repeat the same notes again (A B C D E F G A B C D E F G A...). Each column of the APC40 is the same notes but in a different octave. If only the first channel is working, that's because you only have QLC+ listening to the first channel of data.
To get it your board talking to QLC properly, you have to tell it to talk a different way. The most reliable way of doing this is to plug it into your computer, turn it on, then open Ableton. You should get the coloured box showing that the APC connected to Ableton. Then, close Ableton. All the lights on your board should go off. Now, open QLC+. Look at Joep's picture again:
https://sourceforge.net/p/qlcplus/discussion/general/thread/80d7426b/e668/1332/attachment/Schermafbeelding%202014-03-15%20om%2010.52.46.png
Make sure you have it on Midi Omni, and it should work accross all channels now. I believe the 4.7 Release Candidate has the profile for the APC40 I made, you should be able to test that out with it.
Is that working now?
Last edit: Daniel Curry 2014-03-27
Anyone can contact daniel curry ? I'm very impatient to use my apc40 =) !!!!! I've tried a lot but i don't know ... :( !!!
Thomas, please provide more information about your setup (OS, QLC+ version).
What happens when you edit a button in the virtual console, press the auto detect button and then press the buttons in the second row on your APC40?
Hello,
I'm trying to get an APC40 working with QLC+. I set up everything as you suggest, input is working as expected but feedback still has some issues.
- Pushing button on apc40 trigger VC correctly but led button remains off;
- Clicking button on VC make the apc40 button power on
Is APC40 init message different from APC20's one?
I set omni mode 1-16 in MIDI config, then which is the best settings beetwen Program Change, Control Change and Note Velocity?
Tested on Mac and Win with QLC 4.6.1 and 4.7RC
I have both input and feedback on Control Change and LED feedback is working for me on the top grid. The Mute, Activate, and Solo buttons are a bit weirder sometimes, they don't always go on for flash buttons and I haven't figured out why yet.
I've done some tests.
QLC+ seems sending feedback to APC correctly, but there are some issues lighting up buttons.
For example feedback for knobs works perfectly!
Using Midi Monitor I got these results:
->STATUS: VC&APC OFF, ACTION: PUSH APC40 BUTTON|
01:01:19.349 From Akai APC40 Note On 1 F2 127
01:01:19.361 To Akai APC40 Note On 1 F2 127
01:01:19.510 From Akai APC40 Note Off 1 F2 127
->RESULT: BUTTON IS LIGHT UP IN QLC VC, NOT IN APC40
->STATUS: VC&APC OFF, PUSH VC BUTTON
01:03:36.258 To Akai APC40 Note On 1 F2 127
->RESULT: BUTTON LIGHTS UP IN APC40 AND VC
->STATUS: VC&APC40 BUTTON ON, PUSH APC40 BUTTON.
01:06:16.241 From Akai APC40 Note On 1 F2 127
01:06:16.254 To Akai APC40 Note Off 1 F2 0
01:06:16.342 From Akai APC40 Note Off 1 F2 127
->RESULT: BOTH BUTTONS OFF
I Attach also a PDF I've found about APC40 Midi Map, maybe will be useful.
Last edit: Alessandro Grechi 2014-03-28