Hi!
Using linux, support for jackd, the pro audio sound server, would really ease the use of the audio capabilities of QLC+.
Thanks for even just considering…
Greets!
Mitsch
jackd support
-
mitscherdinger
- Posts: 104
- Joined: Fri Oct 30, 2015 12:12 pm
- Real Name:
- Contact:
-
andres robles
- Posts: 187
- Joined: Tue May 17, 2016 7:41 am
- Location: Spain
- Real Name: Andres Robles
Hello
Currently qjack can manipulate all audio and midi connections between all applications.
In the midi section of qjack Qlc + and all connected midi devices appear, (in Qlc output you can do exactly the same
For audio, Qlc + will use pulse audio.
Currently you can connect between applications that support qjack with applications that do not support it, using the qjack-pulse audio bridge, that is, if you run audacious with plugin jack, in the qjack connection manager, connecting audacious with pulse audio, Qlc will listen to audacious, or any other application .....
Hope this can help you. a greeting.
PS: Translated from Spanish to English with Google translator,
I hope you understand something.
Currently qjack can manipulate all audio and midi connections between all applications.
In the midi section of qjack Qlc + and all connected midi devices appear, (in Qlc output you can do exactly the same
For audio, Qlc + will use pulse audio.
Currently you can connect between applications that support qjack with applications that do not support it, using the qjack-pulse audio bridge, that is, if you run audacious with plugin jack, in the qjack connection manager, connecting audacious with pulse audio, Qlc will listen to audacious, or any other application .....
Hope this can help you. a greeting.
PS: Translated from Spanish to English with Google translator,
I hope you understand something.
-
mitscherdinger
- Posts: 104
- Joined: Fri Oct 30, 2015 12:12 pm
- Real Name:
- Contact:
Yeah, I know that several things can be done with those bridges. But my experience is, that using them is a lot more complicated then a native jackd support. QLC+ aims at pro users, so why not supporting a pro audio standard?
Nevertheless, it's just a feature request… It's up to someone, who can program it. I can't, so I must live with the feature set given to me. Feature requests don't need to be realized, but I can announce that this could be useful for me.
Nevertheless, it's just a feature request… It's up to someone, who can program it. I can't, so I must live with the feature set given to me. Feature requests don't need to be realized, but I can announce that this could be useful for me.
-
mcallegari
- Posts: 4712
- Joined: Sun Apr 12, 2015 9:09 am
- Location: Italy
- Real Name: Massimo Callegari
- Contact:
You guys all know I'm a big fan of Linux and that I actually use it to develop QLC+.
However, let's see the numbers.
According to downloads, Windows is 66%, macOS 23% and Linux 11%.
Now these might not be entirely accurate, cause Linux users can download QLC+ from several places, but this indicates me where I should put my efforts first.
A native jack support would be cool also for timecodes, but it's a LOT of effort.
So, very sorry, but this goes at a low priority, since there is an actual solution available right now without changes to QLC+.
For the record, there's a ticket open on GitHub since January: https://github.com/mcallegari/qlcplus/issues/1024
I'll leave it open as a reminder, but I'm not sure if I'll ever been able to pick it up.
However, let's see the numbers.
According to downloads, Windows is 66%, macOS 23% and Linux 11%.
Now these might not be entirely accurate, cause Linux users can download QLC+ from several places, but this indicates me where I should put my efforts first.
A native jack support would be cool also for timecodes, but it's a LOT of effort.
So, very sorry, but this goes at a low priority, since there is an actual solution available right now without changes to QLC+.
For the record, there's a ticket open on GitHub since January: https://github.com/mcallegari/qlcplus/issues/1024
I'll leave it open as a reminder, but I'm not sure if I'll ever been able to pick it up.
-
andres robles
- Posts: 187
- Joined: Tue May 17, 2016 7:41 am
- Location: Spain
- Real Name: Andres Robles
It is clear that being windows the one that dominates the market, is the one that more users of any application have ...
qjackctl can be used in mac and linux, then we can add mac and linux users who would benefit from a "plugin jack".
Even adding them, we would only be 34% of beneficiaries.
Currently, only Linux users can use qlc + with jack as an audio server, and only through the jumper pulse-audio / jack, it really is very beneficial, generating priority to all the processes connected to the jack on the others and being able to connect any source of audio (microphone / application / piano ...) to qlc + to activate scenes.
The current model is extremely powerful but offers serious limitations:
All the audio widwet will always listen to audio, you can connect 1000 applications to qlc +, but they will only affect one widwet, or all at the same time,
The wonderful thing would be to skip the bridge pulse-audio and that each audio widwet appear in the jack patch independently, example qlc-input1, qlc-input2 ... and so with all the necessary widwet, so I can connect the mic hype to a widwet, the voice to another .... and the audio application that will launch the intro to a 3 widwet ........ and all in real time!
Qjackctl really seems extremely complex for the amount of processes it handles, considering that only 34% of qlc + users would benefit ... it is quite discouraging ....
Another thing is that qjackctl starts to be available for Windows .....
qjackctl can be used in mac and linux, then we can add mac and linux users who would benefit from a "plugin jack".
Even adding them, we would only be 34% of beneficiaries.
Currently, only Linux users can use qlc + with jack as an audio server, and only through the jumper pulse-audio / jack, it really is very beneficial, generating priority to all the processes connected to the jack on the others and being able to connect any source of audio (microphone / application / piano ...) to qlc + to activate scenes.
The current model is extremely powerful but offers serious limitations:
All the audio widwet will always listen to audio, you can connect 1000 applications to qlc +, but they will only affect one widwet, or all at the same time,
The wonderful thing would be to skip the bridge pulse-audio and that each audio widwet appear in the jack patch independently, example qlc-input1, qlc-input2 ... and so with all the necessary widwet, so I can connect the mic hype to a widwet, the voice to another .... and the audio application that will launch the intro to a 3 widwet ........ and all in real time!
Qjackctl really seems extremely complex for the amount of processes it handles, considering that only 34% of qlc + users would benefit ... it is quite discouraging ....
Another thing is that qjackctl starts to be available for Windows .....
-
sbenejam
- Posts: 607
- Joined: Sun Apr 12, 2015 6:28 pm
- Real Name: Santiago Benejam Torres
- Contact:
I think that full jack support in QLC+ would offer a lot of possibilities of use on many setups. Normally I use jack with QLC+ on all my shows.
I understand that it is not a priority for the few users that use it. Maybe it would be a good way to make more users use Linux or MacOSX. I have not tried enough jack on the Raspberry Pi.
I understand that it is not a priority for the few users that use it. Maybe it would be a good way to make more users use Linux or MacOSX. I have not tried enough jack on the Raspberry Pi.