>> This is supposed to be the functionality of the user additions section.
>> Writing up a specific .asoundrc for every card supported is an awesome
>> task. It would require the developers (usually Takashi or Jaroslav) to
>> spend the time for every device known to work. That means less actual
>> coding. However there are plenty of people who use the devices and
>> figure out the syntax for the .asoundrc by themselves. Recently I have
>> been recieving about 4 useful additions per week.
>> [...]
>what about editing of the user submitted notes?
>when the number of submissions increases, it becomes harder
>to digest the information, some of it being better than others.
>Ideally it might be nice to integrate good comments into the body
>of the page. As its obviously far too much for Takashi and Jaroslav,
>how about assigning responsibility for this to someone who owns
>one of the cards. Eg i currently use the cmi8738 and would be willing
>to be editor for this card. I can imagine there might be problems
>with this, but....
Or perhaps automate it by allowing voting (was this entry useful to you?)
then allow sort by votes.
Clemens,
Hi. I made the required change to .asoundrc to map OSS to playback 5
& 6.
pcm_slave.hdsp {
pcm "hw:0"
channels 26
}
pcm.playback_5_6 {
type dshare
slave hdsp
ipc_key 314159265 # some unique number
ipc_key_add_uid yes # "no" to let multiple users share it
bindings {
0 5
1 6
}
}
pcm.dsp0 {
type plug
slave.pcm playback_5_6
}
The results were not positive. xmms starts, but as soon as hit the play
button it exits with the following message:
bash-2.05b$ aoss xmms
xmms: alsa-oss.c:222: oss_dsp_hw_params: Assertion `err >= 0' failed.
/usr/bin/aoss: line 9: 10892 Aborted
LD_PRELOAD=${exec_prefix}/lib/libaoss.so $*
bash-2.05b$
For kicks I tried mapping it to channels 0 & 1 instead, but got the same
results.
bash-2.05b$ aoss xmms
xmms: alsa-oss.c:222: oss_dsp_hw_params: Assertion `err >= 0' failed.
/usr/bin/aoss: line 9: 11022 Aborted
LD_PRELOAD=${exec_prefix}/lib/libaoss.so $*
I checked that libaoss from yesterday's Alsa-1.0.0rc1 release and it
seems to be:
bash-2.05b$ slocate libaoss.so
/usr/lib/libaoss.so.0
/usr/lib/libaoss.so
/usr/lib/libaoss.so.0.0.0
bash-2.05b$ ls -al /usr/lib/libaoss.so*
lrwxrwxrwx 1 root root 16 Dec 1 12:19
/usr/lib/libaoss.so -> libaoss.so.0.0.0
lrwxrwxrwx 1 root root 16 Dec 1 12:19
/usr/lib/libaoss.so.0 -> libaoss.so.0.0.0
-rwxr-xr-x 1 root root 43606 Dec 1 12:19
/usr/lib/libaoss.so.0.0.0
bash-2.05b$
However, what is interesting is that my 'wrong' example before will
actually work in aoss, except it maps xmms OSS audio to playback
channels 1 & 2. This is correct, in the sense that I get only 2 playback
channels, but they are mapped incorrectly.
<WRONG, BUT WORKS SORT OF>
pcm.dsp0 {
type plug
slave pcm.playback_5_6
}
I'm confused by this. Is this an aoss problem? Is it a driver problem
WRT my HDSP 965 specifically2? Something else?
BTW - These results are vaguely familiar. I think this happened before,
and I stumbled on this 'working' option just by my trying to understand
the language and doing a bit of guessing. What I don't understand is
*why* this option that uses the language incorrectly is even allowed to
run instead of producing some message about bad parsing of .asoundrc.
Comments?
For further kicks, and it likely makes no sense at all, but I decided to
try the 'right' format in .asoundrc, but use plughw:0 instead of hw:0.
That produced an interesting message from xmms:
pcm_slave.hdsp {
pcm "plughw:0"
channels 26
}
bash-2.05b$ aoss xmms
Segmentation fault
You've probably found a bug in XMMS, please visit
http://bugs.xmms.org and fill out a bug report.
Xlib: unexpected async reply (sequence 0x6d8)!
Thanks in advance for all your help.
Cheers,
Mark
Sorry for being too newbie again but how do I play the sounds in
ZynAddSubFX with my midi keyboard? I think it's a configuration problem
since I don't get any sound even with the Virtual Keyboard.
Thank you for your patience,
Eduardo.
Sorry for spamming,
This was intended for Eduardo directly but our mailserver failed to find
he's mailadress.
/Robert
-------- Original Message --------
Subject: Re: linux audio & midi question
Date: Mon, 1 Dec 2003 22:53:12 +0100
From: Robert Jonsson <robert.jonsson(a)dataductus.se>
To: Eduardo Guerrero <felixe(a)domovolcanico.com>
References: <3FCBB52B.5050202(a)domovolcanico.com>
Monday 01 December 2003 22.39 skrev Eduardo Guerrero:
> > I would also advice you to install a newer version of muse, check
> > rpm.nyvalls.se/sounds9.1.html.
>
> Hi Robert, thank you for your help. I have one more question: how do I
> add the rpm's in nyvalls.se site to my urpmi database? I'm afraid I need
> the full command line.
Hi Eduardo,
It's on the page actually ;)
urpmi.addmedia thacs.rpms http://rpm.nyvalls.se/9.1/RPMS with hdlist.cz
for 9.1.
if you like to try the absolutely newest you should use the repository
for 9.2. (many of the apps work with 9.1 as is, though not all)
(rpm.nyvalls.se/sounds9.2.html)
As for MusE I think we will release an even newer version in a week or
so, 0.6.3, maintenance release while waiting for 0.7.0 :).
/Robert
Joerg wrote:
"... it does not occur as rarely as you might think."
This was a comparison, not an absolute measurement. The comparison
results suggest (not prove) that it's something else, not the driver.
If it's the driver, then why is there a measurable difference between
two sf2 files playing the same MIDI file with the same patch number
and same channels? It could be, but I see no proof.
"It is practiaclly impossible to play these examples without
dropping notes. Especially if the drum or percussion fails
this is very angry."
Compared to the dropping of notes by Rosegarden (older version) and Muse
for other reasons, this wavetable synthesis problem is a minor annoyance.
The timing for both of these sequencers is noticeably off, and the older
version of Rosegarden gets certain MIDI files completely wrong with stuck
notes, etc. on my system. A good test example is bohemian.mid in Nathan
Laredo's playmidi.
"It happens also if I use the FluidR3 font. And - to make this clear -
independend of whether I play with NoteEdit or the exported MIDI files
with any arbitary MIDI player and/or sequencer or whatever you have in
mind, as long as these MIDI player/sequencer uses the hardware wavetable
synthesis."
"And more important: It never occurs with AWE64 independend
of the soundfond and/or the MIDI player and/or sequencer."
This is to be expected for both a driver problem and a loading problem
or timing problem. It could also be some sort of firmware problem,
a circuit design problem, logic problem in the chips on the soundcard,
etc. It still seems premature to conclude that this cannot be anything
else other than a driver problem. Maybe it is, maybe not.
Hi,
How can I get info from an ogg file that tells me things like sample
rate, bit-depth and other information? sndfile-info doesn't seem to know
about ogg files. (A surprise to me...)
Thanks in advance,
Mark
Joerg wrote:
"Known bugs:
- MIDI on SB live drive not working properly.
- wavetable drops notes sometimes. (a good test example wanted.)"
Exactly. No information on the cause, nor whether it is driver or not.
It is simply noted that notes are sometimes dropped with wavetable
sythesis. No definite conclusion can be drawn from this "bug report.".
"http://rnvs.informatik.tu-chemnitz.de/DROP/gap.html"
This file caused NO problems for emu10k1 and pmidi w/EXTERNAL synth (N264).
Rosegarden (older version) dropped many, many notes; Muse dropped many notes
under certain types of load (switching desktop, for example), even with
external synth, even with Terratech EWX 24/96 and Roland XV-3080.
With wavetable synthesis, I did now finally see 2 or 3 dropped notes with
pmidi. The 8mbgmsfx.sf2 soundfont supplied by Creative Labs was worse
than a 4 MB Steinway piano-only soundfont file. The Steinway soundfont
VERY RARELY dropped any notes. But I could make the problem much worse by
adding load, just as Muse and Rosegarden do. I'm not at all convinced
that this is a driver issue. Wavetable synthesis should be more difficult
for the system than external midi, so timing with O/S's such as Linux and
Windows could be and eventually will be affected.
Anyone actually know in detail the emu10k1 driver situation? The bug
report isn't really of any help to determine the cause.
Specimen is a midi controlled sampler, and it's very first public
release is available from http://www.gazuga.net/specimen.tar.gz
In all honesty, I advise against downloading this in it's current
state unless you intend to hack on it or play with it for sheer
amusement value only. There are a few TODO items that must be taken
care of before this can be considered usable software (as the next
release will be). The main reason for this release is because I said
I was going to make a release in a couple of weeks 15 days ago.
It's very nascent stuff.
You have been warned.
[pb]
I am trying to record some phonograph records using arecord. I get xruns of
about 0.5s or so. I have tried increasing the buffer size which worked up to
a point. I have tried running as root which didn't help.
Is there anything I could do short of applying the low-latency patch to get
this to wok?
thanks,
KD