16 Feb
2013
16 Feb
'13
1:08 a.m.
On Fri, February 15, 2013 3:27 pm,
linux-audio-user-request(a)lists.linuxaudio.org wrote:
Often, but not always, when I start my machine
I'll only get sound from
the left channel.
Is L/R Gang selected on the monitor PCM tab?
I have a permanent /home and my OS on a separate
partition -- could this
be caused by a config file somewhere on /home and if so, where might I
find it to sort this problem out?
Depending on the version of mudita the config file is in either
~/envy24control/profiles.conf or ~/.envy24control/profiles.conf. Newer
versions have the file in .envy24control, I think the placement in
envy24control was just a mistake in version 1.0.
--
Chris Caudle
16 Feb
16 Feb
12:18 p.m.
New subject: Audiophile 24/96 volume weirdness
On 16/02/13 00:08, Chris Caudle wrote:
I have none of those.
Thinking further on it, I wonder whether this is further complicated by
having installed both Ubuntu Studio 12.04 last year and 12.10 this week
without a /home, then post-install editing fstab to point it to my RAID
as /home. I do this because the installer can't handle RAIDs. I wonder
whether it's put the config files somewhere else because of this scenario.
I think the right-channel volume thing started around the same time that
I lost all SPDIF output from the 24/96, which is really annoying. I
swapped the cables over and that made no difference (and it didn't
affect input to the card, i.e. both cables are fine), neither did
swapping the card for another.
In the end I put it down to the DAC in my Focusrite TwinTrak having died
(although I haven't investigated this further) and have had to put up
with analogue out of the 24/96 ever since. If this also turned out to be
a software issue and could be fixed I'd be overjoyed.
Thanks
Q
On Fri, February 15, 2013 3:27 pm,
linux-audio-user-request(a)lists.linuxaudio.org wrote:
It's the DAC2 level on the Analog Volume tab that I've been wiggling to
sort it out.
On the PCM tab I have PCM 3 to 8 L/R ganged and muted. PCM 1 and 2 were
unganged and for PCM 1 the right hand fader was lowered and muted and
for PCM 2 the left hand fader was lowered and muted -- otherwise I end
up with hugely overdriven mono.
Often, but not always, when I start my machine
I'll only get sound from
the left channel.
Is L/R Gang selected on the monitor PCM tab?
I have a
permanent /home and my OS on a separate partition -- could this
be caused by a config file somewhere on /home and if so, where might I
find it to sort this problem out?
Depending on the version of mudita the config file is in either
~/envy24control/profiles.conf or ~/.envy24control/profiles.conf. Newer
versions have the file in .envy24control, I think the placement in
envy24control was just a mistake in version 1.0.
5:37 p.m.
New subject: Audiophile 24/96 volume weirdness
On Sat, February 16, 2013 3:18 am, Q wrote:
Those only show up if you use the save profile part of mudita. They should
not effect the operation of your card though, You should still be able to
turn everything on.
>> I have a permanent /home and my OS on a
separate partition -- could
>> this
>> be caused by a config file somewhere on /home and if so, where might I
>> find it to sort this problem out?
I don't think that should affect mudita as you probably didn't run it when
you had no /home. In any case you should be able to adjust everything with
either mudita or even alsamixer. The kernel module for the ice1712 can be
loaded with a commandline parameter saying which card you have. Is it
possible the module thinks you have a different card?
Depending on the version of mudita the config file is in either
~/envy24control/profiles.conf or ~/.envy24control/profiles.conf. Newer
versions have the file in .envy24control, I think the placement in
envy24control was just a mistake in version 1.0.
I have none of those. I think the right-channel volume thing started around
the same time that
I lost all SPDIF output from the 24/96, which is really annoying. I
swapped the cables over and that made no difference (and it didn't
affect input to the card, i.e. both cables are fine), neither did
swapping the card for another.
In the end I put it down to the DAC in my Focusrite TwinTrak having died
(although I haven't investigated this further) and have had to put up
with analogue out of the 24/96 ever since. If this also turned out to be
a software issue and could be fixed I'd be overjoyed.
You should be able to test your s/pdif out by looping it back into the
s/pdif in. As soon as you do that, the "Hardware Settings tab in mudita
should show IEC958 Input Status - Input Active. You can run some audio
through as a further check, but I am assuming your Focusrite is not
indicating input signal (some LED or something).
I would look at the "Patchbay / Router" Tab in mudita And start with the
whole top row selected just to make sure something isn't funny there. It
sounds like you normally would have your s/pdif outs set to Digital Mix
which should also be ok. But setting things up with the mixer out of
things and just straight I/Os might be the best starting point for trouble
shooting.
--
Len Ovens
www.OvenWerks.net
7:11 p.m.
New subject: Audiophile 24/96 volume weirdness
On 16/02/13 16:37, Len Ovens wrote:
Those only show up if you use the save profile part of mudita. They should
not effect the operation of your card though, You should still be able to
turn everything on.
Okay, I've never bothered saving different profiles. Which prompts the
question in my mind, if there's no saved settings/profile, why is this
volume issue happening? I'd kinda assumed that somehow something had
been saved with the right channel volume muted (although the DAC2 fader
doesn't show this) and I was having to counter this.
I'm positive the SPDIF out works because the problem didn't go away when
I swapped the 24/96 for another one (I have a third one lying around
somewhere that I could try!). I'd not thought about looping the cable
back, but I might give it a try just to confirm.
The Focusrite has no indicator unfortunately.
Interestingly, the Hardware Settings tab says "Unable to read IEC958
Input Status: No such file or directory", but I've never had any
problems with the SPDIF out from the Focusrite/SPDIF input on the 24/96.
Connecting the SPDIF in and out hasn't changed the "unable to read"
message on the Hardware Settings tab but did seem to cause my system to
lock up.
On Sat, February 16, 2013 3:18 am, Q wrote:
when
>> I have a permanent /home and my OS on a
separate partition -- could
>> this
>> be caused by a config file somewhere on /home and if so, where might I
>> find it to sort this problem out?
I don't think that should affect mudita as you probably didn't run it you had no /home.
Ah okay, that makes sense. Yes, I just logged in, edited fstab and
rebooted straightaway.
I don't think that should affect mudita as you
probably didn't run it when
you had no /home. In any case you should be able to adjust everything with
either mudita or even alsamixer. The kernel module for the ice1712 can be
loaded with a commandline parameter saying which card you have. Is it
possible the module thinks you have a different card?
I've only ever had the 24/96 but I guess that's no guarantee that the
module thinks I have the right card. How would I check this?
Depending on the version of mudita the config file is in either
~/envy24control/profiles.conf or ~/.envy24control/profiles.conf. Newer
versions have the file in .envy24control, I think the placement in
envy24control was just a mistake in version 1.0.
I have none of those. I think the
right-channel volume thing started around the same time that
I lost all SPDIF output from the 24/96, which is really annoying. I
swapped the cables over and that made no difference (and it didn't
affect input to the card, i.e. both cables are fine), neither did
swapping the card for another.
In the end I put it down to the DAC in my Focusrite TwinTrak having died
(although I haven't investigated this further) and have had to put up
with analogue out of the 24/96 ever since. If this also turned out to be
a software issue and could be fixed I'd be overjoyed.
You should be able to test your s/pdif out by looping it back into the
s/pdif in. As soon as you do that, the "Hardware Settings tab in mudita
should show IEC958 Input Status - Input Active. You can run some audio
through as a further check, but I am assuming your Focusrite is not
indicating input signal (some LED or something).
I would look at the "Patchbay / Router" Tab in mudita And start with the
whole top row selected just to make sure something isn't funny there. It
sounds like you normally would have your s/pdif outs set to Digital Mix
which should also be ok. But setting things up with the mixer out of
things and just straight I/Os might be the best starting point for trouble
shooting.
When I first lost sound output, I tried all possible combinations in the
patchbay and nothing made any difference. I've tried again now
(unplugging the analogue outputs of course so that I could hear if it
were working!) and no selection for SPDIF outputs results in sound.
Having swapped the card itself, the breakout cable and the SPDIF cable
all to no effect was why I jumped to the conclusion that it was the
Focusrite's DAC that had failed.
Many thanks
Q
7:56 p.m.
New subject: Audiophile 24/96 volume weirdness
On Sat, February 16, 2013 10:11 am, Q wrote:
That sounds like a driver problem, as if it is not detecting the correct
card. I use s/pdif for some of my inputs, so I tend to test it with each
new kernel (at least the ubuntu ones) and I have not had this problem with
my D66. Here is the blurb from the kernel module:
---------------------------8<---------------------------------
Module snd-ice1712
------------------
Module for Envy24 (ICE1712) based PCI sound cards.
* MidiMan M Audio Delta 1010
* MidiMan M Audio Delta 1010LT
* MidiMan M Audio Delta DiO 2496
* MidiMan M Audio Delta 66
* MidiMan M Audio Delta 44
* MidiMan M Audio Delta 410
* MidiMan M Audio Audiophile 2496
* TerraTec EWS 88MT
* TerraTec EWS 88D
* TerraTec EWX 24/96
* TerraTec DMX 6Fire
* TerraTec Phase 88
* Hoontech SoundTrack DSP 24
* Hoontech SoundTrack DSP 24 Value
* Hoontech SoundTrack DSP 24 Media 7.1
* Event Electronics, EZ8
* Digigram VX442
* Lionstracs, Mediastaton
* Terrasoniq TS 88
model - Use the given board model, one of the following:
delta1010, dio2496, delta66, delta44, audiophile,
delta410, delta1010lt, vx442, ewx2496, ews88mt,
ews88mt_new, ews88d,
dmx6fire, dsp24, dsp24_value, dsp24_71, ez8,
phase88, mediastation
omni - Omni I/O support for MidiMan M-Audio Delta44/66
cs8427_timeout - reset timeout for the CS8427 chip (S/PDIF transceiver)
in msec resolution, default value is 500 (0.5 sec)
This module supports multiple cards and autoprobe. Note: The consumer
part is not used with all Envy24 based cards (for example in the
MidiMan Delta series).
Note: The supported board is detected by reading EEPROM or PCI
SSID (if EEPROM isn't available). You can override the
model by passing "model" module option in case that the
driver isn't configured properly or you want to try another
type for testing.
-------------------------------8<------------------------------
I would try model=audiophile first (I am assuming that is what you have),
but delta44 may work as well. The IEC958 Input Status should be either
"Input Active" or "No Signal Detected". Anything else is either a
mudita
bug or a kernel module bug/misconfiguration. Considering you s/pdif is not
working I would suspect the later.
In ubuntu I think the right place to play with module params would be
/etc/modprobe.d/alsa-base.conf, but I am not sure about other distros.
For testing you should be able to just modprobe -r snd-ice1712 and then
modprobe snd-ice1712 model=audiophile or whatever. I don't know if the
cs8427_timeout would help in your case or not. In my case things just work
with no param added. You would have to restart mudita every time I
think... probably stop mudita before removing the module and restart after
loading would be best.
--
Len Ovens
www.OvenWerks.net
You should be
able to test your s/pdif out by looping it back into the
s/pdif in. As soon as you do that, the "Hardware Settings tab in mudita
should show IEC958 Input Status - Input Active. You can run some audio
through as a further check, but I am assuming your Focusrite is not
indicating input signal (some LED or something).
I'm positive the SPDIF out works because the problem didn't go away when
I swapped the 24/96 for another one (I have a third one lying around
somewhere that I could try!). I'd not thought about looping the cable
back, but I might give it a try just to confirm.
The Focusrite has no indicator unfortunately.
Interestingly, the Hardware Settings tab says "Unable to read IEC958
Input Status: No such file or directory", but I've never had any
problems with the SPDIF out from the Focusrite/SPDIF input on the 24/96.
9:13 p.m.
New subject: Audiophile 24/96 volume weirdness
On 16/02/13 18:56, Len Ovens wrote:
>> Interestingly, the Hardware Settings tab says "Unable to read IEC958
>> Input Status: No such file or directory", but I've never had any
>> problems with the SPDIF out from the Focusrite/SPDIF input on the 24/96.
> That sounds like a driver problem, as if it
is not detecting the correct
> card.
And yet the SPDIF in works fine in spite of the input error message,
it's just the SPDIF out that doesn't work.
> I use s/pdif for some of my inputs, so I tend to test it with each
> new kernel (at least the ubuntu ones) and I have not had this problem with
> my D66. Here is the blurb from the kernel module:
> ---------------------------8<---------------------------------
> Module snd-ice1712
> ------------------
> Module for Envy24 (ICE1712) based PCI
sound cards.
> * MidiMan M Audio Delta 1010
> * MidiMan M Audio Delta 1010LT
> * MidiMan M Audio Delta DiO 2496
> * MidiMan M Audio Delta 66
> * MidiMan M Audio Delta 44
> * MidiMan M Audio Delta 410
> * MidiMan M Audio Audiophile 2496
> * TerraTec EWS 88MT
> * TerraTec EWS 88D
> * TerraTec EWX 24/96
> * TerraTec DMX 6Fire
> * TerraTec Phase 88
> * Hoontech SoundTrack DSP 24
> * Hoontech SoundTrack DSP 24 Value
> * Hoontech SoundTrack DSP 24 Media 7.1
> * Event Electronics, EZ8
> * Digigram VX442
> * Lionstracs, Mediastaton
> * Terrasoniq TS 88
> model - Use the given board
model, one of the following:
> delta1010, dio2496, delta66, delta44, audiophile,
> delta410, delta1010lt, vx442, ewx2496, ews88mt,
> ews88mt_new, ews88d,
> dmx6fire, dsp24, dsp24_value, dsp24_71, ez8,
> phase88, mediastation
> omni - Omni I/O support for MidiMan
M-Audio Delta44/66
> cs8427_timeout - reset timeout for the
CS8427 chip (S/PDIF transceiver)
> in msec resolution, default value is 500 (0.5 sec)
> This module supports multiple cards
and autoprobe. Note: The consumer
> part is not used with all Envy24 based cards (for example in the
> MidiMan Delta series).
> Note: The supported board is detected
by reading EEPROM or PCI
> SSID (if EEPROM isn't available). You can override the
> model by passing "model" module option in case that the
> driver isn't configured properly or you want to try another
> type for testing.
> -------------------------------8<------------------------------
> I would try model=audiophile first (I am assuming that is what you have),
> but delta44 may work as well. The IEC958 Input Status should be either
> "Input Active" or "No Signal Detected". Anything else is either a
mudita
> bug or a kernel module bug/misconfiguration. Considering you s/pdif is not
> working I would suspect the later.
> In ubuntu I think the right place to play
with module params would be
> /etc/modprobe.d/alsa-base.conf, but I am not sure about other distros.
> For testing you should be able to just
modprobe -r snd-ice1712 and then
> modprobe snd-ice1712 model=audiophile or whatever. I don't know if the
> cs8427_timeout would help in your case or not. In my case things just work
> with no param added. You would have to restart mudita every time I
> think... probably stop mudita before removing the module and restart after
> loading would be best.
I don't know if it counts for anything, but the card shows up correctly
as M-Audio Audiophile 24/96 in Qjackctl.
When I tried modprobe -r it said "FATAL: Module snd_ice1712 is in use"
but adding with the model type worked fine. I didn't have Mudita running
whilst doing either of these.
I found the alsa-base.conf file, but I wouldn't know what to start
fiddling with. There's no mention in there of snd_ice1712 though, dunno
whether that's indicative of anything.
Many thanks
Q
17 Feb
17 Feb
6:44 p.m.
New subject: Audiophile 24/96 volume weirdness
On Sat, February 16, 2013 12:13 pm, Q wrote:
In use because pulse would have been running and other snd- drivers rely
on it too. When you say worked fine, does that mean s/pdif i/o works fine?
On 16/02/13 18:56, Len Ovens wrote:
with no param
added. You would have to restart mudita every time I
think... probably stop mudita before removing the module and restart
after
loading would be best.
I don't know if it counts for anything, but the card shows up correctly
as M-Audio Audiophile 24/96 in Qjackctl.
When I tried modprobe -r it said "FATAL: Module snd_ice1712 is in use"
but adding with the model type worked fine. I didn't have Mudita running
whilst doing either of these.
I found the alsa-base.conf file, but I wouldn't know what to start
fiddling with. There's no mention in there of snd_ice1712 though, dunno
whether that's indicative of anything.
That means snd_ice1712 auto loads on detection. I am not fluent in messing
with this file either, but I think you can use it to specify options. I
am wondering if the driver loads too soon if it works on reload. In the
alsa-base.conf file there are a number of options lines I think you would
just add a line like:
options snd-ice1712 model=audiophile
I also add one for my internal audio IF with an index=-2 so it loads last
and my ice1712 is always hw:0
--
Len Ovens
www.OvenWerks.net
12:38 p.m.
New subject: Audiophile 24/96 volume weirdness
On 16/02/13 18:56, Len Ovens wrote:
[snip]
> I would try model=audiophile first (I am assuming that is what you have),
> but delta44 may work as well. The IEC958 Input Status should be either
> "Input Active" or "No Signal Detected". Anything else is either a
mudita
> bug or a kernel module bug/misconfiguration. Considering you s/pdif is not
> working I would suspect the later.
> In ubuntu I think the right place to play
with module params would be
> /etc/modprobe.d/alsa-base.conf, but I am not sure about other distros.
> For testing you should be able to just
modprobe -r snd-ice1712 and then
> modprobe snd-ice1712 model=audiophile or whatever. I don't know if the
> cs8427_timeout would help in your case or not. In my case things just work
> with no param added. You would have to restart mudita every time I
> think... probably stop mudita before removing the module and restart after
> loading would be best.
I tried completely removing/re-installing all alsa packages in Synaptic
and that had no effect.
modprobe -r snd-FOO doesn't work for any of the snd modules -- they all
seem to be interdependent and all say "FATAL: module snd-FOO is in use"
Doing modprobe snd-ice1712 model=audiophile seemed to work, but it had
no effect.
I tried running the SPDIF out into an M-Audio Fast Track Pro into which
I plugged headphones. I assume this should have allowed me to hear the
output of the soundcard (again, no SPDIF indicator light on the Fast
Track) but there was nothing -- this would seem to support your idea
that there's a software problem with the SPDIF output from the Audiophile.
What else can I try?
Many thanks
Q
12:50 p.m.
New subject: Audiophile 24/96 volume weirdness
Q wrote:
What else can I try?
You said you swapped in another soundcard, and still
have the problem.
This strongly suggests a software issue.
What about booting a live CD of some other
linux distribution, and seeing if you
get the behavior you expect?
--
Joel Roth
4299
days inactive
4300
days old
linux-audio-user@lists.linuxaudio.org
8 comments
4 participants
participants (4)
-
Chris Caudle -
Joel Roth -
Len Ovens -
Q