Hi all,
I know there are many discussions in the forums, but:
Would it be possible to get a list of recommended compatible hardware for QLC+ (i.e. MIDI controllers). Information available is often outdated, or the fact that something *works* does not automatically mean it is a good idea to get such a device.
Further, the compatibility list at http://www.qlcplus.org/discover/compatibility is also not really helpful, because (esp. with the DMX interfaces) there are a lot of discontinued products listed there.
My recommendation: Create a list of featured / recommended hardware and keep them up to date on the homepage. Discontinued or further compatible hardware can still be listed, but not right at the top.
What do you think? I would really appreciate this.
Suggestions for which devices are currently worth considering are much appreciated by me, too.
Recommendations for Controllers / Hardware
-
- Posts: 717
- Joined: Wed Feb 08, 2023 10:24 am
- Location: Nederland
- Real Name: Michel Sliepenbeek
It is supported: just connect it to your PC (power it on) and then start QLC+. If you go to the Inputs/Outputs tab it will show up as MIDI.
It is important to give your Midicon its own universe and select it for Input and output.
Now if you go to your Virtual Console and select a Button or Slider you can use AutoDetect to attach a Button or Slider of your Midicon as External Controller.
You can use your Midicon without an Input Profile (as long as you only use AutoDetect) but with a profile everything becomes easier.
As far as i know there is no Input Profile available for the Midicon Pro, but you can create your own (watch this video: https://youtu.be/DDKXLsjCYEI?feature=shared).
You can save some time by making a copy of the Input Profile for the Midicon (model 1), that is available and then adapt it to the Midicon Pro.
It is important to give your Midicon its own universe and select it for Input and output.
Now if you go to your Virtual Console and select a Button or Slider you can use AutoDetect to attach a Button or Slider of your Midicon as External Controller.
You can use your Midicon without an Input Profile (as long as you only use AutoDetect) but with a profile everything becomes easier.
As far as i know there is no Input Profile available for the Midicon Pro, but you can create your own (watch this video: https://youtu.be/DDKXLsjCYEI?feature=shared).
You can save some time by making a copy of the Input Profile for the Midicon (model 1), that is available and then adapt it to the Midicon Pro.
A QLC Workspace is like a Bob Ross painting: "it's your world, you can create whatever you want!"
-
- Posts: 435
- Joined: Thu Apr 23, 2015 6:43 am
- Real Name: Ken Coughlin
-
- Posts: 717
- Joined: Wed Feb 08, 2023 10:24 am
- Location: Nederland
- Real Name: Michel Sliepenbeek
There are a lot of USB DMX interfaces that are designed to only run with specific software.
Some examples are:
- Sushi (DMXSoft)
- Soundswitch
- Sunlite.
- Chamsys (MagicQ)
- LightShark
- Obsydian (Onyx)
Maybe it is an idea to put a warning on the compatibilty list, that those interfaces have "a built in protection not to work with CLC+".
Some examples are:
- Sushi (DMXSoft)
- Soundswitch
- Sunlite.
- Chamsys (MagicQ)
- LightShark
- Obsydian (Onyx)
Maybe it is an idea to put a warning on the compatibilty list, that those interfaces have "a built in protection not to work with CLC+".
A QLC Workspace is like a Bob Ross painting: "it's your world, you can create whatever you want!"
-
- Posts: 435
- Joined: Thu Apr 23, 2015 6:43 am
- Real Name: Ken Coughlin
If a user doesn't check the list for a compatible device, they aren't going to see any list of incompatible devices.MichelSliepenbeek wrote: ↑Sat Jun 15, 2024 10:32 pm There are a lot of USB DMX interfaces that are designed to only run with specific software.
Some examples are:
- Sushi (DMXSoft)
- Soundswitch
- Sunlite.
- Chamsys (MagicQ)
- LightShark
- Obsydian (Onyx)
Maybe it is an idea to put a warning on the compatibilty list, that those interfaces have "a built in protection not to work with CLC+".