Well, input profiles can be considered presets, don't they ?
The MIDI plugin has a configuration dialog that can be easily improved.
If I'd had to do that, I would add a tab with a list of presets with checkboxes and a LineEdit field where the user can enter a custom init sequence.
If any is selected, the MIDI plugin, will send the sequence upon device initialization.
Should be quite simple to implement.
The "only" tricky part is to make raw messages to work on Linux, Windows and OSX.
APC 20 and APC 40 controller
-
Joep Admiraal
I played a bit with the configure midi plugin screen (see attachment).
What do you think about it?
I have all three os's so if I am done it will work on all of them.
What do you think about it?
I have all three os's so if I am done it will work on all of them.
- Attachments
-
- Schermafdruk%20van%202013-09-29%2016%3A49%3A55.png (3.98 KiB) Viewed 1630 times
-
Massimo Callegari
Not bad at all !
One last thing. I would like presets to be stored in a XML file (I know, it's boring to read them) but in this way a user can edit the XML file and have their handy one-click presets
One last thing. I would like presets to be stored in a XML file (I know, it's boring to read them) but in this way a user can edit the XML file and have their handy one-click presets
-
Massimo Callegari
Also, I had a quick look at what the BCF2000 supports via Sysex.
Please donwload the "BCF2000 factory presets" from this page:
http://www.behringer.com/EN/Products/BCF2000.aspx
As you can see, it has some complex presets. That's why it would be impossible to write them manually (therefore XML stuff)
Please donwload the "BCF2000 factory presets" from this page:
http://www.behringer.com/EN/Products/BCF2000.aspx
As you can see, it has some complex presets. That's why it would be impossible to write them manually (therefore XML stuff)
-
Joep Admiraal
Wow those presets are indeed much more extensive as those of the APC 
XML file would be handy indeed, i'll add that when the basics are working.
XML file would be handy indeed, i'll add that when the basics are working.
-
Joep Admiraal
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
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
-
Daniel Curry
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.
@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.
-
Jano Svitok
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.
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.
-
Daniel Curry
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.
-
Daniel Curry
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.
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.
-
Daniel Curry
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.
- Attachments
-
Akai-APC40.qxi- (12 KiB) Downloaded 151 times
-
Massimo Callegari
Thanks Daniel.
I'm gonna check it and eventually include it in the incoming 4.7.0 version
I'm gonna check it and eventually include it in the incoming 4.7.0 version
-
thomas
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 ... PYBEK0DMDM
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 ... PYBEK0DMDM
-
Jano Svitok
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.
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.
-
thomas
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 
-
Daniel Curry
@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.
@ 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.
-
Joep Admiraal
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.
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.