26 Mar
2019
26 Mar
'19
8:45 a.m.
On 2019-03-26 09:44, Jörn Nettingsmeier wrote:
On 3/26/19 5:28 AM, liebrecht(a)grossmann-venter.com
wrote:
Sorry I disagree, qjcakctl has given me nothing but trouble and still
does.
It goes much better without it.
All it arguably does is to formulate a jack string....which the user
should do on command line anyway, and then output mystery log errors
which are substandard to reading the logs yourself.
I have never found any constructive use for it other than "feelgood".
Mixbus worked great once I removed qjackctl on my previous system.
qjackctl was single most annoying interference problem.
After jack is installed, I try to start it
through mixbus which is
about the only application I found that can actually start jack. I
used mixbus for about 6 months with jack on another distro. qjacktcl
does nothing but parse irrelevance and promisses so I dont use it
anymore.
That remark is bullshit and shows that you really need to change the
way you're thinking about problem solving.
Simplify the problem.
First, look at aplay -L to see if hw:VSL,0 is alive and well.
As I reported already in another post it is recognised.
Now, start jack on the command line, starting with the
paramters
mixbux helpfully suggests:
jackd -t 200 -p 2048 -R -T -d alsa -n 2 -r 48000 -p 128 -d hw:VSL,0
It should fail in the same way you described above. If not, there is
something fishy in the way mixbus starts jackd.
As already reported, mixbus starts jack and jack runs IFF I dont start
jack with qjackctl. Once qjackctl started jack, mixbus wont work. Mixbus
starts jack with a string they disclose in the terminal output and it
works.
According to patchage as I reported in a previous post, mixxbus is
connected to jack, but I get no signals from jack for the 1818vsl inputs
in mixbus.
-n2 p128 looks like a pretty aggressive timing for a
multichannel
interface. Try -n3 for a start, and -p1024, then gradually lower the
latency, but only if you really need it.
I know I am just trying my documented default settings that worked
perfectly before.
26 Mar
26 Mar
9:24 a.m.
New subject: [Jack-Devel] Uninstalled Pulseaudio Jack/jackd2 Jack Reinstalled still wont start.
Granted qjackctl and jackd have a rather shallow learning curve. But in my opinion,
qjackctl is above all doubts. It works reliably for me for ten years now.
Are you moving from windows? Maybe you need to rethink the signal procesding chain in
linux?
Whats more, Linux Mint for example every once in a while breaks qjackctl/jackd2
dependencies. Thus it is adviseable to compile all your audio stuff by yourself, except
mixbus obviously...
BR,
Ck
Am 26. März 2019 15:44:58 MEZ schrieb liebrecht(a)grossmann-venter.com:
On 2019-03-26 09:44, Jörn Nettingsmeier wrote:
Sorry I disagree, qjcakctl has given me nothing but trouble and still
does.
It goes much better without it.
All it arguably does is to formulate a jack string....which the user
should do on command line anyway, and then output mystery log errors
which are substandard to reading the logs yourself.
I have never found any constructive use for it other than "feelgood".
Mixbus worked great once I removed qjackctl on my previous system.
qjackctl was single most annoying interference problem.
--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
On 3/26/19 5:28 AM,
liebrecht(a)grossmann-venter.com wrote:
> After jack is installed, I try to start it through mixbus which is
> about the only application I found that can actually start jack. I
> used mixbus for about 6 months with jack on another distro. qjacktcl
does
nothing but parse irrelevance and promisses so I dont use it
anymore.
That remark is bullshit and shows that you really need to change the
way you're thinking about problem solving.
Simplify the problem.
First, look at aplay -L to see if hw:VSL,0 is alive and well.
As I reported already in another post it is recognised.
Now, start jack on the command line, starting
with the paramters
mixbux helpfully suggests:
jackd -t 200 -p 2048 -R -T -d alsa -n 2 -r 48000 -p 128 -d hw:VSL,0
It should fail in the same way you described above. If not, there is
something fishy in the way mixbus starts jackd.
As already reported, mixbus starts jack and jack runs IFF I dont start
jack with qjackctl. Once qjackctl started jack, mixbus wont work.
Mixbus
starts jack with a string they disclose in the terminal output and it
works.
According to patchage as I reported in a previous post, mixxbus is
connected to jack, but I get no signals from jack for the 1818vsl
inputs
in mixbus.
-n2 p128 looks like a pretty aggressive timing
for a multichannel
interface. Try -n3 for a start, and -p1024, then gradually lower the
latency, but only if you really need it.
I know I am just trying my documented default settings that worked
perfectly before.
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org 
9:38 a.m.
New subject: [Jack-Devel] Uninstalled Pulseaudio Jack/jackd2 Jack Reinstalled still wont start.
On Tue, 26 Mar 2019 16:24:38 +0100, Christoph Kuhr wrote:
Whats more, Linux Mint for example every once in a
while breaks
qjackctl/jackd2 dependencies. Thus it is adviseable to compile all
your audio stuff by yourself, except mixbus obviously...
Be careful with such statements, for my concerns against Mint I was
attacked and finally banned from LAU and my statement wasn't that
negative as yours.
However, perhaps the OP missed to disable a script by Qjackctl's
Setup... > Option tab or the Misc Tab contains a D-Bus mismatch.
9:38 a.m.
New subject: [Jack-Devel] Uninstalled Pulseaudio Jack/jackd2 Jack Reinstalled still wont start.
On 2019-03-26 11:24, Christoph Kuhr wrote:
Granted qjackctl and jackd have a rather shallow
learning curve. But
in my opinion, qjackctl is above all doubts. It works reliably for me
for ten years now.
Are you moving from windows? Maybe you need to rethink the signal
procesding chain in linux?
No, gave up on windows in 1997 and used Linux since then.
Whats more, Linux Mint for example every once in a
while breaks
qjackctl/jackd2 dependencies. Thus it is adviseable to compile all
your audio stuff by yourself, except mixbus obviously...
I compile most what I do no problem there, but for Debian stretch it
doesnt seem necessary at all.
I used AVLinux, which unfortunately had a lot of other trouble that
became unresolveable and no functional usergroup although jack/mixbusd
did work there.
I moved to Debian Stretch, where I battle to get jack to run properly as
it did in AVlinux.
BR,
Ck
10:54 a.m.
New subject: [Jack-Devel] Uninstalled Pulseaudio Jack/jackd2 Jack Reinstalled still wont start.
On Tue, March 26, 2019 10:38 am, liebrecht(a)grossmann-venter.com wrote:
I moved to Debian Stretch
Finally after five days you provide the requested distribution information.
Now just a few more days to send the version information of jackd and
qjackctl and everyone will have the information I pointed out you should
have provided in your first post.
Perhaps someone could have pointed out the very strange packaging choice
that Debian made for jackd, there is a jackd package which depends on
either jackd v1 or jackd v2.
I do not use Debian frequently so I do not remember how you choose which
version to install, but others on the list will be able to help.
I do see from looking at the repository that the default version of jackd2
is quite old:
1.9.10+20150825
1.9.12 was the latest formal release, and even that was a couple of years
ago.
--
Chris Caudle
11:10 a.m.
New subject: [Jack-Devel] Uninstalled Pulseaudio Jack/jackd2 Jack Reinstalled still wont start.
On 2019-03-26 12:54, Chris Caudle wrote:
On Tue, March 26, 2019 10:38 am,
liebrecht(a)grossmann-venter.com wrote:
I am glad I could supply relief.
You should have asked a bit louder, I somehow did not hear.
# cat /etc/*lease*
NAME="MX"
VERSION="18 (Continuum)"
ID="mx"
VERSION_ID="18"
PRETTY_NAME="MX 18 (Continuum)"
ANSI_COLOR="0;34"
HOME_URL="https://mxlinux.org"
BUG_REPORT_URL="https://mxlinux.org"
PRETTY_NAME="MX 18.1 Continuum"
DISTRIB_ID=MX
DISTRIB_RELEASE=18.1
DISTRIB_CODENAME=Continuum
DISTRIB_DESCRIPTION="MX 18.1 Continuum"
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
# cat /proc/version
Linux version 4.19.0-1-amd64 (stevep(a)mxlinux.org) (gcc version 6.3.0
20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP Debian 4.19.5-2~mx17+1
(2018-12-12)
I moved to Debian Stretch
Finally after five days you provide the requested distribution
information.
Now just a few more days to send the version information of jackd and
qjackctl and everyone will have the information I pointed out you
should
have provided in your first post.
Perhaps someone could have pointed out the very strange packaging
choice
that Debian made for jackd, there is a jackd package which depends on
either jackd v1 or jackd v2.
It is a good point, and may be a source of the problems I have with
qjackctl.
I did not want to install jackd2, and things work properly without it on
AV (where it caused a lot of problems) I used to use.I get some use out
of jack as soon as I only use jackd on debian.
I notice that whenever I install qjackctl, it immediately installs
jackd2 with it as a dependency.
So, just uninstalling the troublesome qjackctl, things start working.
As reported, most is solved and I now only have trouble with routing
signals from the 1818VSL. All routing to the 1818VSLK (Non midi) now
seems to work.
I do not use Debian frequently so I do not remember
how you choose
which
version to install, but others on the list will be able to help.
I do see from looking at the repository that the default version of
jackd2
is quite old:
1.9.10+20150825
1.9.12 was the latest formal release, and even that was a couple of
years
ago.
I am using the MX flavor of stretch as I dont want systemd as default as
is now the case with debian causing boatloads of system applications to
fail, making system administration hell if all your scripts are sysv
dependent.
I will in future move to a forked debian version as it makes much more
sense for my applications and interests not to go the systemd way and
stick with systemv init or a variant of it.
1855
days inactive
1855
days old
jackaudio@lists.linuxaudio.org
5 comments
4 participants
participants (4)
-
Chris Caudle -
Christoph Kuhr -
liebrecht＠grossmann-venter.com -
Ralf Mardorf