14 Apr
2003
14 Apr
'03
5:15 p.m.
Hello!
I have switched to alsa drivers. The sound card (ES1371) works OK.
There is alsa-0.9rc2 in the kernel I use, but the distro, ASP Linux 7.3
(a Red Hat derivative) does not provide alsa-lib. I got alsa-lib,
alsa-lib-devel and alsa-util from freshrpms.net (RPMs for RH 7.3 work on
ASP 7.3); the version is, as I understand, 0.9rc7.
I have compiled fluidsynth again starting with configure, and now it
includes alsa libraries.
But when I start it, as root, with no parameters, and even with X not
running, it just hangs until Ctrl-C.
It starts with -a oss, however. It says that uses midi via alsa-seq,
but audio via oss. And it does not get any data from the MIDI keyboard
(ran it with --verbose to check).
Only when I used full OSS settings:
fluidsynth -a oss -m oss -o midi.oss.device="/dev/midi00"
did it work again. So, it's oss over alsa, not alsa. And yet alsa is
there, for example, alsamixer works. (And, unlike the case without alsa,
it does start an ALSA MIDI input, just gets no data).
What should I do? Can it be the fault of version difference between
alsa-driver in the kernel and alsa-lib/alsa-lib-devel?
I gave it a try; I ununstalled alsa-lib and alsa-lib-devel and
alsa-util, and tried to compile alsa-lib 0.9.0rc2 from the source on
alsa-project.org. But it asked for the alsa-driver package. The kernel
source (which includes alsa-driver) is installed, so I really don't know
what to do next in this case. I'll try to investigate more - IT the
version difference is likely to be at fault...
Perhaps I just need to set some options I don't know about?
--
Sincerely yours, Mikhail Ramendik
14 Apr
14 Apr
5:49 p.m.
Hello!
For alsa-seq midi. I had the same problem. I don't know. But did you run the
aconnect program? If you start fluidsynth or any alsa-seq client it only
offers a port. Normally if it is the first alsa-seq client started this is
port 128. Then you need to connect your soundcards midi-in to 128. Usually
this is:
aconnect 64 128
You can see all input ports with:
aconnect -li
and all output ports with:
aconnect -lo
If you i.e. want to play a midifile to fluidsynth, but not use fluidsynth
directly, then you could do:
fluidsynth (make all settings)
And on another console run:
pmidi -p 128:0 file.mid
This would play midi-data from pmidi to port 128, which is your fluidsynth
port. If you start more midi-apps run aconnect to see apropriate portnumbers.
For your alsa-problem. I defenitely think, that it is a version difference
problem. Maybe the best would be to uninstall your alsadriver package and get
alsa0.9.2 from alsa-project.org and install that (driver, lib, utils). I have
that combination and it works fine on my suse 8.1 (kernel 2.4.20).
I hope that helps it little.
Kindest regards
Julien
Julien Patrick Claassen
jclaassen(a)gmx.de
julien(a)c-lab.de
http://www.geocities.com/jjs_home
SBS C-LAB
Fuerstenallee 11
33102 Paderborn
Phone: (+49) 5251 60 6060
Fax: (+49) 5251 60 6065
www.c-lab.de
6:43 p.m.
On Mon, 2003-04-14 at 23:39, Julien Patrick Claassen wrote:
For your alsa-problem. I defenitely think, that it
is a version difference
problem. Maybe the best would be to uninstall your alsadriver package and get
alsa0.9.2 from alsa-project.org and install that (driver, lib, utils). I have
that combination and it works fine on my suse 8.1 (kernel 2.4.20).
But if I want to change to a new alsadriver package, will I have to
recompile the kernel?
I definitely want to avoid this, in order to be able to install kernel
updates from the distro's vendor.
By the way, it looks like the actual version in the kernel may be
0.9.0rc6, not rc2 (judging by kernel source directories). Is there a way
to check which version of alsa-driver is actually running?
--
Sincerely yours, Mikhail Ramendik
7:31 p.m.
Hi!
About the version-checking I don't know, maybe check your doc directory. On
my suse I have docs under /usr/share/doc/packages. There I find info on all
installed packages.
I think you don't need to compile the kernel (I also would avoid that). If
it is installed as a package, then I suppose that it is just another module.
So you just need to uninstall the module and compile alsa again. Make sure you
have the correct sources installed (they can make trouble), because redhat and
some other distros use patched kernels. And alsa asks for those version.h
files. They can be a real pain in the ass. :-) If you have your kernel sources
installed, then you have the config file for the kernel, serach for alsa and
look if it is m or y. If it is m you're lucky, otherwise, better get the right
package version for lib, devel and utils... :-)
I hope that helps you.
Kindest regards
Julien
Julien Patrick Claassen
jclaassen(a)gmx.de
julien(a)c-lab.de
http://www.geocities.com/jjs_home
SBS C-LAB
Fuerstenallee 11
33102 Paderborn
Phone: (+49) 5251 60 6060
Fax: (+49) 5251 60 6065
www.c-lab.de
15 Apr
15 Apr
9:13 a.m.
On 15 Apr 2003 00:35:23 +0400, Mikhail Ramendik wrote / a écrit:
is there a way
to check which version of alsa-driver is actually running?
on a rpm-based distro, to know the alsa-driver currently installed (so, running) the magic
formula is:
rpm -q alsa-driver
or you can try a 'locate alsa-driver' too. On my redhat+planetCCRMA packages, it
brings me this directory:
/usr/share/doc/alsa-driver-0.9.2
maybe if you dig at roughly the same place you will find the name of your current
alsa-driver.
regards.
Guy CLO~
-----------------------------------------------
#ICQ 37736372
#219055 http://counter.li.org
-----------------------------------------------
http://perso.wanadoo.fr/guy.clotilde/index.html
-----------------------------------------------
14 Apr
14 Apr
8:12 p.m.
On Mon, 2003-04-14 at 23:39, Julien Patrick Claassen wrote:
For alsa-seq midi. I had the same problem. I
don't know. But did you run the
aconnect program? If you start fluidsynth or any alsa-seq client it only
offers a port. Normally if it is the first alsa-seq client started this is
port 128. Then you need to connect your soundcards midi-in to 128. Usually
this is:
aconnect 64 128
This helps, when run while fluidsynth is already running...
Well, when I want just online play in one operation, I'll just use the
oss midi input. No problem.
Thanks.
--
Sincerely yours, Mikhail Ramendik
7845
days inactive
7846
days old
linux-audio-user@lists.linuxaudio.org
5 comments
3 participants
participants (3)
-
Guy Clotilde -
Julien Patrick Claassen -
Mikhail Ramendik