17 Sep
2014
17 Sep
'14
10:16 a.m.
Hi,
I've recently gotten my RME Multiface up and working quite
satisfactorally with current Linux kernels. I'm very happy, especially
as I had a long run of it not working for some reason I never teased
out.
So, I find I can aplay and arecord, and I can use ecasound, and a few
other cli tools.
But, I can't use mplayer. Am I the only one? Anyone else tried mplayer
on the Multiface?
For cli tools mplayer gives me the ability to pause, or move backwards
and forwards through the audio file. This is important to me because I
learn music these days by ear.
I know one can do this in the gui, but as a blind user the Linux gui
audio apps aren't particularly friendly in my experience. Besides, it's
so terribly simple, if rather imprecise, to use spacebar, left-arrow,
and right-arrow.
The error I get:
Opening audio decoder: [pcm] Uncompressed PCM audio decoder
AUDIO: 48000 Hz, 2 ch, s16le, 1536.0 kbit/100.00% (ratio:
192000->192000)
Selected audio codec: [pcm] afm: pcm (Uncompressed PCM)
==========================================================================
[AO_ALSA] alsa-lib: pcm_hw.c:327:(snd_pcm_hw_hw_params)
SNDRV_PCM_IOCTL_HW_PARAMS failed (-16): Device or resource busy
[AO_ALSA] Unable to set hw-parameters: Device or resource busy
Failed to initialize audio driver 'alsa:device=plughw=8.0'
Could not open/initialize audio device -> no sound.
Audio: no sound
Video: no video
Exiting... (End of file)
Meanwhile, aplay and ecaplay have no problems. So, I thought I should
ask if anyone else has experienced this before reporting to mplayer
devs.
TIA
Janina
--
Janina Sajka, Phone: +1.443.300.2200
sip:janina@asterisk.rednote.net
Email: janina(a)rednote.net
Linux Foundation Fellow
Executive Chair, Accessibility Workgroup: http://a11y.org
The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Protocols & Formats http://www.w3.org/wai/pf
Indie UI http://www.w3.org/WAI/IndieUI/
17 Sep
17 Sep
10:43 a.m.
On 09/17/2014 10:15 AM, Janina Sajka wrote:
But, I can't use mplayer. Am I the only one?
Anyone else tried mplayer
on the Multiface?
I use mplayer with the jack backend on a RME hdsp card without problems.
I can reproduce the problem you describe with the alsa backend.
-- Giso
For cli tools mplayer gives me the ability to pause, or move backwards
and forwards through the audio file. This is important to me because I
learn music these days by ear.
I know one can do this in the gui, but as a blind user the Linux gui
audio apps aren't particularly friendly in my experience. Besides, it's
so terribly simple, if rather imprecise, to use spacebar, left-arrow,
and right-arrow.
The error I get:
Opening audio decoder: [pcm] Uncompressed PCM audio decoder
AUDIO: 48000 Hz, 2 ch, s16le, 1536.0 kbit/100.00% (ratio:
192000->192000)
Selected audio codec: [pcm] afm: pcm (Uncompressed PCM)
==========================================================================
[AO_ALSA] alsa-lib: pcm_hw.c:327:(snd_pcm_hw_hw_params)
SNDRV_PCM_IOCTL_HW_PARAMS failed (-16): Device or resource busy
[AO_ALSA] Unable to set hw-parameters: Device or resource busy
Failed to initialize audio driver 'alsa:device=plughw=8.0'
Could not open/initialize audio device -> no sound.
Audio: no sound
Video: no video
Exiting... (End of file)
Meanwhile, aplay and ecaplay have no problems. So, I thought I should
ask if anyone else has experienced this before reporting to mplayer
devs.
TIA
Janina
27 Sep
27 Sep
5:46 p.m.
New subject: Jack from CLI [Was: mplayer no go with snd-hdsp]
Hi, All:
Thanks to everyone who responded suggesting I start using jack to solve
my problem with mplayer and my Multiface.
Trying to start jacd from the command line as root I fail for lack of an
X-server.
Starting as my ordinary user I get:
no message buffer overruns
JACK server starting in realtime mode with priority 20
audio_reservation_init
Acquire audio card Audio8
creating alsa driver ... hw:8|hw:8|256|2|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 256 frames (5.3 ms), buffer = 2
periods
ALSA: final selected sample format for capture: 32bit integer
little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer
little-endian
ALSA: use 2 periods for playback
Using port names patch v0.1 (07.04.2010)
Trying to load portnames from /home/janina/.config/jack/cards/Hammerfall
DSP.ss.ports.in
Trying to load portnames from /home/janina/.config/jack/cards/Hammerfall
DSP.ports.in
Trying to load portnames from /etc/jack/cards/Hammerfall DSP.ss.ports.in
Trying to load portnames from /etc/jack/cards/Hammerfall DSP.ports.in
Trying to load portnames from /home/janina/.config/jack/cards/Hammerfall
DSP.ss.ports.out
Trying to load portnames from /home/janina/.config/jack/cards/Hammerfall
DSP.ports.out
Trying to load portnames from /etc/jack/cards/Hammerfall
DSP.ss.ports.out
Trying to load portnames from /etc/jack/cards/Hammerfall DSP.ports.out
And, things just sit there seemingly forever.
All suggestions much appreciated. Please note I can't use gui tools as
none are Orca friendly, afaik.
Janina
Giso Grimm writes:
On 09/17/2014 10:15 AM, Janina Sajka wrote:
--
Janina Sajka, Phone: +1.443.300.2200
sip:janina@asterisk.rednote.net
Email: janina(a)rednote.net
Linux Foundation Fellow
Executive Chair, Accessibility Workgroup: http://a11y.org
The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Protocols & Formats http://www.w3.org/wai/pf
Indie UI http://www.w3.org/WAI/IndieUI/
But, I can't use mplayer. Am I the only one?
Anyone else tried mplayer
on the Multiface?
I use mplayer with the jack backend on a RME hdsp card without problems.
I can reproduce the problem you describe with the alsa backend.
-- Giso
For cli tools mplayer gives me the ability to pause, or move backwards
and forwards through the audio file. This is important to me because I
learn music these days by ear.
I know one can do this in the gui, but as a blind user the Linux gui
audio apps aren't particularly friendly in my experience. Besides, it's
so terribly simple, if rather imprecise, to use spacebar, left-arrow,
and right-arrow.
The error I get:
Opening audio decoder: [pcm] Uncompressed PCM audio decoder
AUDIO: 48000 Hz, 2 ch, s16le, 1536.0 kbit/100.00% (ratio:
192000->192000)
Selected audio codec: [pcm] afm: pcm (Uncompressed PCM)
==========================================================================
[AO_ALSA] alsa-lib: pcm_hw.c:327:(snd_pcm_hw_hw_params)
SNDRV_PCM_IOCTL_HW_PARAMS failed (-16): Device or resource busy
[AO_ALSA] Unable to set hw-parameters: Device or resource busy
Failed to initialize audio driver 'alsa:device=plughw=8.0'
Could not open/initialize audio device -> no sound.
Audio: no sound
Video: no video
Exiting... (End of file)
Meanwhile, aplay and ecaplay have no problems. So, I thought I should
ask if anyone else has experienced this before reporting to mplayer
devs.
TIA
Janina
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user 
6:50 p.m.
New subject: Jack from CLI [Was: mplayer no go with snd-hdsp]
On Sat, Sep 27, 2014 at 11:46:15AM -0400, Janina Sajka wrote:
Trying to start jacd from the command line as root I
fail for lack of an
X-server.
Unlikely, Jack doesn't need X. But you shouldn't run it as root.
Starting as my ordinary user I get:
What options do you use ? You'll need at least something like
jackd -d alsa -d hw:NNNNNN
where NNNNNN is the name of the soundcard to use.
You can find out the name by running
aplay -l
(lower case L) The names you can use are those directly
following the card number, you should find your Multiface
in that list.
You could also use
jackd -d alsa -d hw:X,0
where X is the card number.
Jack has many more options, use
jackd --help
to see them.
And, things just sit there seemingly forever.
Which very probably means that all is OK. Remember that Jack is
a server. You keep it running and it will do its work. Switch to
another terminal for all other commands.
IIRC you wanted to use mplayer. To make it use Jack, do
mplayer -ao jack <filename>
Audio output should appear at line outs 1 and 2.
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
7:35 p.m.
New subject: Jack from CLI [Was: mplayer no go with snd-hdsp]
Hi,
thanks for the quick help response. Comments in line below.
Fons Adriaensen writes:
Tried several. Currently:
jackd --sync -dalsa -dhw:8
hw:8 is definitely the Multiface. aplay -D plughw:8 plays there just
fine.
On Sat, Sep 27, 2014 at 11:46:15AM -0400, Janina Sajka
wrote:
Glad to
hear. I have no desire to run as root, just that some on line docs
I found seemed to suggest running as root.
Trying to start jacd from the command line as
root I fail for lack of an
X-server.
Unlikely, Jack doesn't need X. But you shouldn't run it as root. Starting as my ordinary user I get:
What options do you use ? You'll need at least something like
jackd -d alsa -d hw:NNNNNN
where NNNNNN is the name of the soundcard to use.
You can find out the name by running
aplay -l
(lower case L) The names you can use are those directly
following the card number, you should find your Multiface
in that list.
You could also use
jackd -d alsa -d hw:X,0
where X is the card number.
Jack has many more options, use
jackd --help
to see them.
Strangely, this gives me:
No such audio driver 'jack'
Could not open/initialize audio device -> no sound.
This is stock rpmfusion build of mplayer 1.1 for Fedora 20 (x86_64). I'm assuming
they include jack support in their build?
And, things just sit there seemingly forever.
Which very probably means that all is OK. Remember that Jack is
a server. You keep it running and it will do its work. Switch to
another terminal for all other commands.
IIRC you wanted to use mplayer. To make it use Jack, do
mplayer -ao jack <filename>
Audio output should appear at line outs 1 and 2.
Yes, that's were aplay sends it.
tia
Janina
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
--
Janina Sajka, Phone: +1.443.300.2200
sip:janina@asterisk.rednote.net
Email: janina(a)rednote.net
Linux Foundation Fellow
Executive Chair, Accessibility Workgroup: http://a11y.org
The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Protocols & Formats http://www.w3.org/wai/pf
Indie UI http://www.w3.org/WAI/IndieUI/
7:57 p.m.
New subject: Jack from CLI [Was: mplayer no go with snd-hdsp]
On Sat, Sep 27, 2014 at 01:35:52PM -0400, Janina Sajka wrote:
I begin to suspect they don't...
There is another solution, copy the following to a file
called .asoundrc in your home directory:
pcm.!default {
type plug
slave { pcm "jack" }
}
pcm.jack {
type jack
playback_ports {
0 system:playback_1
1 system:playback_2
}
capture_ports {
0 system:capture_1
1 system:capture_2
}
}
ctl.mixer0 {
type hw
card 0
}
Then start mplayer without the -ao jack. It should then
use the default ALSA card which we redefined to be a
virtual one connecting to Jack.
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
thanks for the quick help response. Comments in line
below.
Fons Adriaensen writes:
Tried several. Currently:
jackd --sync -dalsa -dhw:8
hw:8 is definitely the Multiface. aplay -D plughw:8 plays there just
fine.
After having started Jack, in another terminal, run
jack_lsp
which should produce a list of Jack ports for your Multiface.
I you have that it means Jack is definitely running OK.
On Sat, Sep 27, 2014 at 11:46:15AM -0400, Janina
Sajka wrote:
Glad to
hear. I have no desire to run as root, just that some on line docs
I found seemed to suggest running as root.
Trying to start jacd from the command line as
root I fail for lack of an
X-server.
Unlikely, Jack doesn't need X. But you shouldn't run it as root. Starting as my ordinary user I get:
What options do you use ? You'll need at least something like
jackd -d alsa -d hw:NNNNNN
mplayer -ao
jack <filename>
Strangely, this gives me:
No such audio driver 'jack'
Could not open/initialize audio device -> no sound.
This is stock rpmfusion build of mplayer 1.1 for Fedora 20 (x86_64). I'm assuming
they include jack support in their build?
8:31 p.m.
New subject: Jack from CLI [Was: mplayer no go with snd-hdsp]
Fons Adriaensen writes:
On Sat, Sep 27, 2014 at 01:35:52PM -0400, Janina Sajka
wrote:
Tried several. Currently:
jackd --sync -dalsa -dhw:8
hw:8 is definitely the Multiface. aplay -D plughw:8 plays there just
fine.
After having started Jack, in another terminal, run
jack_lsp
which should produce a list of Jack ports for your Multiface.
Unfortunately it doesn't. It produces no output, and doesn't return. I have to
Ctrl-C to get the prompt back.
So, I presume this means jack isn't starting correctly?
Janina
Starting as my ordinary user I get:
What options do you use ? You'll need at least something like
jackd -d alsa -d hw:NNNNNN
28 Sep
28 Sep
1:27 p.m.
New subject: Jack from CLI [Was: mplayer no go with snd-hdsp]
On Sat, Sep 27, 2014 at 02:31:06PM -0400, Janina Sajka wrote:
That's not normal. If Jack isn't running it should detect
that and just terminate with an error.
This may have to do with the 'port names patch' which seems
to be applied to your version of Jack. AFAIK it allows you
to change the names of the soundcard ports by creating a
file in ~/.config/jack. Maybe the file *must* be there, I
don't know, this is the first time I hear of this patch.
Could you try to get an unmodified version of Jack, if at
all possible jack1 (because I know that one better). You
currently have jack2.
Note: before installing any new version of Jack ensure that
any others are completely removed. Having more than one
version installed or even parts of another version always
creates strange problems.
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
After having
started Jack, in another terminal, run
jack_lsp
which should produce a list of Jack ports for your Multiface.
Unfortunately it doesn't. It produces no output, and doesn't return. I have to
Ctrl-C to get the prompt back.
29 Sep
29 Sep
8:35 a.m.
New subject: Jack from CLI [Was: mplayer no go with snd-hdsp]
On 09/28/2014 01:27 PM, Fons Adriaensen wrote:
On Sat, Sep 27, 2014 at 02:31:06PM -0400, Janina Sajka
wrote:
That's not normal. If Jack isn't running it should detect
that and just terminate with an error.
This may have to do with the 'port names patch' which seems
to be applied to your version of Jack. AFAIK it allows you
to change the names of the soundcard ports by creating a
file in ~/.config/jack. Maybe the file *must* be there, I
don't know, this is the first time I hear of this patch.
Could you try to get an unmodified version of Jack, if at
all possible jack1 (because I know that one better). You
currently have jack2.
May this be related with dbus support of jack2? If yes, then using jack1
or recompiling jack without dbus support might help. If dbus support is
needed without having X11 then there was a post on the topic by Len
Ovens ('Headless jackdbus (no X11)' on July 22nd 2013).
- Giso
After
having started Jack, in another terminal, run
jack_lsp
which should produce a list of Jack ports for your Multiface.
Unfortunately it doesn't. It produces no output, and doesn't return. I have to
Ctrl-C to get the prompt back.
Note: before installing any new version of Jack ensure that
any others are completely removed. Having more than one
version installed or even parts of another version always
creates strange problems.
Ciao,
10:42 p.m.
New subject: Jack from CLI [Was: mplayer no go with snd-hdsp]
On Mon, Sep 29, 2014 at 08:35:10AM +0200, Giso Grimm wrote:
May this be related with dbus support of jack2? If
yes, then using jack1
or recompiling jack without dbus support might help. If dbus support is
needed without having X11 then there was a post on the topic by Len
Ovens ('Headless jackdbus (no X11)' on July 22nd 2013).
Dbus and X11 should not be related. Except that both the 'session'
dbus and X11 are probably launched by the same entity: the *DM
login manager. And I assume that Jack2 Dbus means 'session' bus,
and not the 'system' one. On a system without a graphical login
(as the OP is probably using) there may not be a 'session' dbus
at all.
I'll be optimistic and assume that jack2 really doesn't *need*
dbus even if it's capable of using it. Maybe I'm too optimistic.
Even if I've seen too much 'desktop', 'session', 'seat' and
whatever other nonsense creeping into a what should be a basic
system.
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
30 Sep
30 Sep
12:10 a.m.
New subject: Jack from CLI
On Mon, 29 Sep 2014, Fons Adriaensen wrote:
On Mon, Sep 29, 2014 at 08:35:10AM +0200, Giso Grimm
wrote:
Used to be x was launched from the dbus-launch command line, but I think
it is upstart or systemd launching them these days.
I have in the past been successful using dbus-launch to run screen on a
headless box and been able to run pulse from one screen terminal and
jackdbus from another (and other jack/dbus apps in other screen
terminals). Absolutely, there is no need for X to make dbus work. I did
(BTW) find pulse -> jack bridging absolutely useless in this case, except
that it was a great test case to show that dbus was functioning correctly.
There are not a lot of CLI audio apps that look for pulse.
May this be related with dbus support of jack2?
If yes, then using jack1
or recompiling jack without dbus support might help. If dbus support is
needed without having X11 then there was a post on the topic by Len
Ovens ('Headless jackdbus (no X11)' on July 22nd 2013).
Dbus and X11 should not be related. Except that both the 'session'
dbus and X11 are probably launched by the same entity: the *DM I'll be optimistic and assume that jack2 really
doesn't *need*
dbus even if it's capable of using it. Maybe I'm too optimistic.
Even if I've seen too much 'desktop', 'session', 'seat' and
whatever other nonsense creeping into a what should be a basic
system.
Probably not. I don't know if running jackdbus is more or less useful in a
headless case. The major upside I can see is the ability to control the
running jack server from jack_control. Certainly jack_control stop/exit is
much cleaner than killall -9 jackd. If this is worth the added complexity
of having yet another service running, I don't know.
In any case, I would suggest chmod -x whichever executable you are not
using (jackd or jackdbus). Or if you are building jack2 just build the one
you want. (the debian jackd2 package is broken IMO for including both)
--
Len Ovens
www.ovenwerks.net
17 Sep
17 Sep
noon
Hey Janina,
I suggest the same as Giso. If you are learning music, you might want to use other audio
apps at the same time anyway. So go for the JACK Audio Connection Kit. I've used it
ever since I started with Linux. I don't have an RME, but I have a multichannel audio
interface.
I hope this is a viable solution for you setup.
Ta-ta, Ffanci
Janina Sajka, Sep 17 2014:
Hi,
I've recently gotten my RME Multiface up and working quite
satisfactorally with current Linux kernels. I'm very happy, especially
as I had a long run of it not working for some reason I never teased
out.
So, I find I can aplay and arecord, and I can use ecasound, and a few
other cli tools.
But, I can't use mplayer. Am I the only one? Anyone else tried mplayer
on the Multiface?
For cli tools mplayer gives me the ability to pause, or move backwards
and forwards through the audio file. This is important to me because I
learn music these days by ear.
I know one can do this in the gui, but as a blind user the Linux gui
audio apps aren't particularly friendly in my experience. Besides, it's
so terribly simple, if rather imprecise, to use spacebar, left-arrow,
and right-arrow.
The error I get:
Opening audio decoder: [pcm] Uncompressed PCM audio decoder
AUDIO: 48000 Hz, 2 ch, s16le, 1536.0 kbit/100.00% (ratio:
192000->192000)
Selected audio codec: [pcm] afm: pcm (Uncompressed PCM)
==========================================================================
[AO_ALSA] alsa-lib: pcm_hw.c:327:(snd_pcm_hw_hw_params)
SNDRV_PCM_IOCTL_HW_PARAMS failed (-16): Device or resource busy
[AO_ALSA] Unable to set hw-parameters: Device or resource busy
Failed to initialize audio driver 'alsa:device=plughw=8.0'
Could not open/initialize audio device -> no sound.
Audio: no sound
Video: no video
Exiting... (End of file)
Meanwhile, aplay and ecaplay have no problems. So, I thought I should
ask if anyone else has experienced this before reporting to mplayer
devs.
TIA
Janina
--
Janina Sajka, Phone: +1.443.300.2200
sip:janina@asterisk.rednote.net
Email: janina(a)rednote.net
Linux Foundation Fellow
Executive Chair, Accessibility Workgroup: http://a11y.org
The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Protocols & Formats http://www.w3.org/wai/pf
Indie UI http://www.w3.org/WAI/IndieUI/
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
Ta-ta
----
Ffanci
* Internet: http://freeshell.de/~silvain
12:13 p.m.
On Wed, 2014-09-17 at 11:57 +0200, F. Silvain wrote:
So go for the JACK Audio Connection Kit.
OT, but perhaps useful, if you should use jackd with several audio apps:
http://sourceforge.net/projects/aj-snapshot/
Likely also available by a package for the distro you're using.
10:57 p.m.
On Wed, 17 Sep 2014, F. Silvain wrote:
I suggest the same as Giso. If you are learning music,
you might want
to use other audio apps at the same time anyway. So go for the JACK
Audio Connection Kit. I've used it ever since I started with Linux. I
don't have an RME, but I have a multichannel audio interface.
I have the Multiface II, and it's nearly impossible to address through
raw Alsa without some deep kung-fu. Though Jack you should be able to
see all of its i/o's and use it with MPlayer or whatever you want.
--
+ Brent A. Busby + "We've all heard that a million monkeys
+ Sr. UNIX Systems Admin + banging on a million typewriters will
+ University of Chicago + eventually reproduce the entire works of
+ James Franck Institute + Shakespeare. Now, thanks to the Internet,
+ Materials Research Ctr + we know this is not true." -Robert Wilensky
18 Sep
18 Sep
3:22 a.m.
On Wed, Sep 17, 2014 at 4:56 PM, Brent Busby <brent(a)keycorner.org> wrote:
On Wed, 17 Sep 2014, F. Silvain wrote:
I suggest the same as Giso. If you are learning music, you might want to
The multichannel RME devices do not support being opened with less than
full channel counts or with the wrong sample format. Any approach that ends
up using plughw:CARDNAME should work just fine. For some, using such a
device name will be deep kung-fu, for others not so much. And it may depend
on the application how easy it is.
use other audio apps at the same time anyway. So
go for the JACK Audio
Connection Kit. I've used it ever since I started with Linux. I don't have
an RME, but I have a multichannel audio interface.
I have the Multiface II, and it's nearly impossible to address through raw
Alsa without some deep kung-fu. Though Jack you should be able to see all
of its i/o's and use it with MPlayer or whatever you want.
7:19 a.m.
On Wed, 17 Sep 2014, Paul Davis wrote:
The multichannel RME devices do not support being
opened with less
than full channel counts or with the wrong sample format. Any approach
that ends up using plughw:CARDNAME should work just fine. For some,
using such a device name will be deep kung-fu, for others not so much.
And it may depend on the application how easy it is.
The last part is the operative part here -- using a Multiface as a
general purpose audio out will depend on all your apps all being able to
handle a single device with 18 i/o's. Some programs will handle that
better than others, and I've seen some fairly involved .asoundrc files
posted on here in the past to try and get around that for people who
really badly want it to be their general desktop audio device.
(PulseAudio handles the situation particularly poorly.)
It's probably best to let a motherboard sound chip do that and keep the
Multiface only for recording.
--
+ Brent A. Busby + "We've all heard that a million monkeys
+ Sr. UNIX Systems Admin + banging on a million typewriters will
+ University of Chicago + eventually reproduce the entire works of
+ James Franck Institute + Shakespeare. Now, thanks to the Internet,
+ Materials Research Ctr + we know this is not true." -Robert Wilensky
3:40 a.m.
On Wed, Sep 17, 2014 at 4:56 PM, Brent Busby <brent(a)keycorner.org> wrote:
On Wed, 17 Sep 2014, F. Silvain wrote:
I suggest the same as Giso. If you are learning music, you might want to
I use a Multiface, too, and keep Jack going 100% of the time for the
machine it is on (I route audio from other sources into it also, including
another computer). Multiface isn't really intended for end-user consumer-y
casual use, but is intended for multitrack studio & Multi I/O kinds of
things.
--
Brett W. McCoy -- http://www.brettwmccoy.com
------------------------------------------------------------------------
"In the rhythm of music a secret is hidden; If I were to divulge it, it
would overturn the world."
-- Jelaleddin Rumi
use other audio apps at the same time anyway. So
go for the JACK Audio
Connection Kit. I've used it ever since I started with Linux. I don't have
an RME, but I have a multichannel audio interface.
I have the Multiface II, and it's nearly impossible to address through raw
Alsa without some deep kung-fu. Though Jack you should be able to see all
of its i/o's and use it with MPlayer or whatever you want.
17 Sep
17 Sep
10:05 p.m.
On Wed, Sep 17, 2014 at 04:15:59AM -0400, Janina Sajka wrote:
I've recently gotten my RME Multiface up and
working quite
satisfactorally with current Linux kernels. I'm very happy, especially
as I had a long run of it not working for some reason I never teased
out.
So, I find I can aplay and arecord, and I can use ecasound, and a few
other cli tools.
But, I can't use mplayer. Am I the only one? Anyone else tried mplayer
on the Multiface?
As others have already suggested: use Jack. For everything.
I have this alias for viewing videos:
alias vv='mplayer -ao jack -fs'
which works everywhere.
Tschuss,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
18 Sep
18 Sep
2:07 a.m.
On Wed, 17 Sep 2014 20:05:01 +0000, Fons Adriaensen wrote :
On Wed, Sep 17, 2014 at 04:15:59AM -0400, Janina Sajka
wrote:
To avoid passing arguments or use an alias,
create a file "$HOME/.mplayer/config" that contains :
ao=jack
fs=yes
--
Marc
But, I can't use mplayer. Am I the only one?
Anyone else tried
mplayer on the Multiface?
As others have already suggested: use Jack. For everything.
I have this alias for viewing videos:
alias vv='mplayer -ao jack -fs'
which works everywhere.
3709
days inactive
3721
days old
linux-audio-user@lists.linuxaudio.org
18 comments
10 participants
participants (10)
-
Brent Busby -
Brett McCoy -
F. Silvain -
Fons Adriaensen -
Giso Grimm -
Janina Sajka -
Len Ovens -
Marc Lavallée -
Paul Davis -
Ralf Mardorf