28 Nov
2017
28 Nov
'17
1:47 a.m.
Hi,
Have beat my head against the wall long enough... I have AV Linux,
Hammerfall DSP card, am using Ecasound with ladspa plugins for DSP
crossover, Pianoteq piano model, and Jack to glue things together. I built
2 nice large subwoofers (4 ft3 each) with 12" SBAcoustics drivers. Just
realized the other day that my 5.1 surround sound is missing the .1; the
LFE channel. I want to get it to appear in my PulseAudio sink, map it in
the my Ecasound logic, and split the LFE signal between the 2 subs. Since
I use them for 20 to 80hz, maybe this will sometimes detract from accuracy
of movie music, but still I at least want to learn how to do it and see how
I like it. Problem is, no matter what I do with /etc/pulse/daemon.conf,
default.pa etc. (setting channels=6, channel order, no LFE mixing, etc.), I
can't seem to get the LFE channel to work. I've searched the Internet over
and over, read everything I could find and tried setting things like the
articles say, but still the LFE channel just won't show up. Alsamixer
shows front, rear and center master volume controls only; no LFE.
pulsevumeter, etc., show only 5 channels, nothing shows the LFE channel.
Any idea what I'm doing wrong?
Thanks!!
John
2 Dec
2 Dec
2:36 a.m.
Goodness, I'm so frustrated...
Finally I managed to get the LFE channel to show up as a pulseaudio sink.
Now I have all 6 (5.1) channels there, and last night I managed to get it
all started and watch a movie, and it sounded good. My Pianoteq didn't
work (notes played from the app, but not from the actual keyboard), but I
thought I would be able to figure that out soon. But then I came home
from work and now I'm stuck again. Can't get anything to work!! I don't
really know what I'm doing, so I spend hours trying different combinations,
but I'm not getting anywhere. Here are the pieces of my puzzle:
1. qjackctl and hdspmixer. I know I have to run hdspmixer to get driver
loaded for the RME 9652 card, but now I cannot get Jack Audio Connection
Kit to show the 26 system input and outputs for the RME. It shows just 2
inputs and 2 outputs. Just last night I had it showing the 26 inputs and
26 outputs, but no more; no matter what I do, just 2 and 2. I put snd_hdsp
in my modules.conf, which changed the RME to be at the top of the modules
list, and that seemed to be OK last night. When I include "hdspmixer &"
(OR, hdsploader &) in the "run at startup" here's the messages I see
in
Jack when I let it autostart:
20:19:49.410 Statistics reset.
20:20:07.892 ALSA connection change.
20:20:07.902 Startup script...
20:20:07.902 /usr/bin/hdspmixer &
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping
unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping
unlock
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping
unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping
unlock
20:20:07.914 ALSA connection graph change.
20:20:08.304 Startup script terminated successfully.
20:20:08.304 JACK is starting...
20:20:08.305 /usr/bin/jackd -t2000 -dalsa -r48000 -p64 -n2 -D
-Cplughw:DSP,0 -Pplughw:DSP,0 -o26
20:20:08.309 JACK was started with PID=2918.
20:20:10.520 Could not connect to JACK server as client. - Overall
operation failed. - Unable to connect to server. Please check the messages
window for more info.
20:20:10.576 JACK is stopping...
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping
unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping
unlock
20:20:10.605 JACK was stopped
20:20:10.605 JACK has crashed.
When I don't use autostart, and just run it manually after restarting
Linux, Jack doesn't crash, but I still only see 2 input and 2 outputs.
Doesn't matter if I run hdspmixer before or after qjackctl; always the same
result...
2. Ecasound - I have an ecasound script that implements my DSP ladspa
crossovers and it works fine. It processes the LFE channel fine. But I
can't get far enough to run it anymore.
3. pulseaudio -k. I use this command to start or reset pulseaudio. I
don't seem to have much problem anymore with PA; the LFE channel always
shows up now in the list of pa-jack-sinks. My big problem is #1 above.
But even after I figure out #1, I still have #4 to understand, so I can get
all this work work automatically and don't have to manually run a bunch of
scripts and commands every time I want to play the piano.
4. What to put where. I am just at a loss to understand so much about
Linux. I have AV Linux, by the way. Jack Audio Connection (qjackctl) has
a startup script, and an "after startup" scrip, and 2 shutdown scripts. I
don't know what to put on each. I thought I should put hdspmixer & on the
startup, but that doesn't work anymore. Then there's Sessions and Startup
- Autostart. I don't know what to run there, in the autostart tab. There
are so many possible ways to do all this. Then, there's where to put my
scripts - either in usr/bin, or under my home directory. I don't
understand the difference; it seems it matters, what gets started and from
where, but I don't understand how it matters. I do understand about chmod
a+x.
I had this working fine for months (after much struggle), then I decided to
change from 5.0 to 5.1 and process the LFE channel and BOOM, I've lost it
all. I'm almost ready to go to J. Rivers. Can anybody help me calm down
and learn the many things I need to learn to solve these problems? I need
some detailed, step-by-step help; I have a child and a family I'm kind of
neglecting, I can't spend my life studying this and trying different
things... I would really, really appreciate it... or maybe I'm just not
smart enough for Linux; just tell me if you think I should go back to
Windows... :(
Thanks so much...
John
On Mon, Nov 27, 2017 at 7:47 PM, john gibby <johnalan.gibby(a)gmail.com>
wrote:
Hi,
Have beat my head against the wall long enough... I have AV Linux,
Hammerfall DSP card, am using Ecasound with ladspa plugins for DSP
crossover, Pianoteq piano model, and Jack to glue things together. I built
2 nice large subwoofers (4 ft3 each) with 12" SBAcoustics drivers. Just
realized the other day that my 5.1 surround sound is missing the .1; the
LFE channel. I want to get it to appear in my PulseAudio sink, map it in
the my Ecasound logic, and split the LFE signal between the 2 subs. Since
I use them for 20 to 80hz, maybe this will sometimes detract from accuracy
of movie music, but still I at least want to learn how to do it and see how
I like it. Problem is, no matter what I do with /etc/pulse/daemon.conf,
default.pa etc. (setting channels=6, channel order, no LFE mixing, etc.),
I can't seem to get the LFE channel to work. I've searched the Internet
over and over, read everything I could find and tried setting things like
the articles say, but still the LFE channel just won't show up. Alsamixer
shows front, rear and center master volume controls only; no LFE.
pulsevumeter, etc., show only 5 channels, nothing shows the LFE channel.
Any idea what I'm doing wrong?
Thanks!!
John
10:12 a.m.
john gibby <johnalan.gibby-Re5JQEeQqe8AvxtiuMwx3w(a)public.gmane.org>
writes:
Goodness, I'm so frustrated...
Finally I managed to get the LFE channel to show up as a pulseaudio sink.
Now I have all 6 (5.1) channels there, and last night I managed to get it
all started and watch a movie, and it sounded good. My Pianoteq didn't
work (notes played from the app, but not from the actual keyboard), but I
thought I would be able to figure that out soon. But then I came home
from work and now I'm stuck again. Can't get anything to work!! I don't
really know what I'm doing, so I spend hours trying different combinations,
but I'm not getting anywhere. Here are the pieces of my puzzle:
1. qjackctl and hdspmixer. I know I have to run hdspmixer to get driver
loaded for the RME 9652 card,
No? The driver gets loaded by hdsploader. hdspmixer sets mixer
defaults useful for hearing something, but you can do that
non-interactively using amixer. I have a hdspreset script looking like
#!/bin/sh
amixer -c 1 cset "iface=CARD,name=Precise Pointer" 1
# Inputs to HDSP Mixer
# ========================================================================
# Multiface analogue inputs 1-8 = amixer source channels 0-7
# Multiface ADAT inputs 1-8 = amixer source channels 16-23
# Multiface SPDIF input = amixer source channels 24-25
# alsa_pcm:playback_1-26 = amixer source channels 26-51
#
# Outputs from HDSP Mixer
# ========================================================================
# Multiface analogue outputs 1-8 = amixer destination channels 0-7
# Multiface ADAT outputs 1-8 = amixer destination channels 16-23
# Multiface SPDIF output = amixer destination channels 24-25
# Multiface line (headphone) output = amixer destination channels 26-27
#
# Mapping between Multiface inputs and alsa_pcm:capture channels
# ========================================================================
# Multiface analogue inputs 1-8 = capture_1-8
# Multiface ADAT inputs 1-8 = capture_9-16
# Multiface SPDIF input = capture_17-18
amixer -c 1 cset numid=5 26,0,65535
amixer -c 1 cset numid=5 27,1,65535
That would appear to put through the playback outputs 1 and 2 to analog
outputs 1 and 2.
Don't ask me about the Precise Pointer thing: at some point of time
jackd and pulseaudio needed _different_ settings in order to work
properly. Don't remember which was which or whether this is still the
case.
--
David Kastrup
11:13 a.m.
On Sat, 02 Dec 2017 10:12:22 +0100, David Kastrup wrote:
at some point of time jackd and pulseaudio needed
_different_ settings
in order to work properly
Hi :D
then why did you questioned a while ago that some users don't want to
install pulseaudio, or even recommend to remove it for troubleshooting
purpose, given that some audio cards, e.g. the HDSPe AIO I own doesn't
work properly with Linux at all. The HDSPe AIO of other Linux users
might work without all of the issues I experience, but at least they
must suffer from some issues I experience, too, e.g. Ardour can't be
used with ALSA instead of jackd. So risking that additionally pulseaudio
_could_ cause issues makes no sense. There is no purpose using
pulseaudio for most DAW usage and at least in the past it nearly was
impossible to grant disabling pulseaudio without failure.
IOW your claim maintaining a Linux install without pulseaudio would be
more time intensive, than using pulseaudio, or at least to test if it
should work trouble-free nowadays, while it caused issues for
years, makes no sense, too.
There are just a few use case where pulseaudio might be useful for a
DAW, while for most DAW usages it's completely needless and apart from
some bloated DE's that require it for absolutely no valid reason as a
hard dependency (an empty dummy package to fulfil such a
pseudo-hard-dependency doesn't cause any issues), there is no good
environment that requires pulseaudio as a hard dependency at all.
There are even idiotic attempts to render dummy packages useless, but
actually they fail :p, e.g. enforcing another useless hard dependency
for a DAW that requires a release "=" of pulseaudio, for a rolling
release model distro like Arch Linux, that anyway doesn't allow partial
upgrades, so that the "=" is completely irrelevant.
[rocketmouse@archlinux ~]$ pacman -Si pulseaudio-bluetooth | grep On
Depends On : pulseaudio=11.1-1 bluez bluez-libs sbc
IOW claiming that something is wrong with people who dislike pulseaudio
is strange, seemingly something is wrong with those who are unable to
stop trying to enforce pulseaudio to everybody, by even the most
grotesque efforts.
;)
Ralf
12:07 p.m.
Ralf Mardorf <ralf.mardorf(a)alice-dsl.net> writes:
On Sat, 02 Dec 2017 10:12:22 +0100, David Kastrup
wrote:
I did not "question it" but stated that there were good reasons for
installing it. Which you need to deny over and over by pointing out
repeatedly that you did not install it. Of course one can manage to
make Pulseaudio work even with the HDSP. I don't use the HDSP any more
for serious work (I prefer using my Mackie mixer with Firewire card) and
actually wanted to sell it already. It's a pity that support for newer
cards in ALSA is no longer similarly thorough. Last time I got it out
was because the soundcards I had had no optical S/PDIF input available.
Nothing that can't be cured without a 10EUR converter.
At any rate, that data point is a single card with a curious setting
("Precise Pointer"? Seriously?). My problems were 10 years ago or so
and I have no indication that they would be still around (nor otherwise:
not enough serious use for getting current evidence). That was during
Pulseaudio's infancy as Ubuntu default.
at some point of time jackd and pulseaudio needed
_different_ settings
in order to work properly
Hi :D
then why did you questioned a while ago that some users don't want to
install pulseaudio, or even recommend to remove it for troubleshooting
purpose, given that
some audio cards, e.g. the HDSPe AIO I own doesn't work properly with
Linux at all. The HDSPe AIO of other Linux users might work without
all of the issues I experience, but at least they must suffer from
some issues I experience, too, e.g. Ardour can't be used with ALSA
instead of jackd. So risking that additionally pulseaudio _could_
cause issues makes no sense.
Pulseaudio does a number of things with regard to desktop integration
that Jackd is no alternative for.
Different tools for different purposes. And of course no Pulseaudio for
Ralf. We got that, Ralf. No reason to pontificate all over again.
--
David Kastrup
2549
days inactive
2553
days old
linux-audio-user@lists.linuxaudio.org
4 comments
3 participants
participants (3)
-
David Kastrup -
john gibby -
Ralf Mardorf