Small subject alteration.
Paul Perkins said:
> Well, the WIKI page on ALSA config files at
>
> http://alsa.opensrc.org/index.php?page=.asoundrc
>
> has evolved to where it is beginning to sound useful. But it doesn't take you
> all that far, and it needs explanations of basic terms like "pcm" (in its
> peculiar ALSA meaning), "slave", and "plugin". The "detailed" material on
> plugins it references
> (http://www.alsa-project.org/alsa-doc/alsa-lib/pcm_plugins.html) is just a
> list of plugin names and plugin argument names, padded with some boiler-plate
> text that rarely adds anything that isn't implicit in the names.
>
I have to say, this has been an issue for me also. Things have improved muchly
in the last year, but there still is a way to go. There's a lot of translation
needed between Those-Who-Read-The-Source and Those-Who-But-Point-n-Click.
I'd like to contribute to the documentation.
One thing i've been bothered by. (Maybe this doesn't bother LISP hackers, i
dunno)
Not enough example .asoundrc files. The few I find are always useful to me,
but i can't find very many. Maybe people don't want to pollute the list, maybe
everybody
else is smarter than me, who knows.
I'll make an offer: Mail me (cliffw(a)easystreet.com) your .asoundrc file + name
of hardware.
If you have a quick example of What It Does For You, email me that too.
I'll attempt to boil off the excess and add something useful to the wiki.
cliffw
> I don't measure the power of a computer or of software by what it can do. I
> measure power by how much faster or better I can do what I want to do with
> the computer or software, than without it. Including the learning time. By
> this definition, good documentation makes software more powerful, and
> documentation that requires a lot of hunting around and trial-and-error to
> make sense of, makes software less powerful.
>
> As for how far I am willing to go, that depends on what I expect to find when
> I get there. I'm a pretty good C and Python programmer with a smattering of
> C++ and Java, I'll edit fstab, modules.conf, XF86Config, and so on with vi
> when I have to (but these days count it as a bug in the distribution when I
> do have to). I use Linux for pretty much all my computer activities these
> days, except music recording / synthesizing / effects / mixing. I'd like to
> use Linux for that as well, but it just doesn't seem to be ready yet. When
> Ardour is stable it might be time for me to make another attempt to switch
> over (from the evil empire os). Music is enough of a challenge for me, I
> don't need to be on the software bleeding edge at the same time.
>
> On Sunday 22 June 2003 11:55 pm, Patrick Shirkey wrote:
> > Paul Perkins wrote:
> > > On Friday 20 June 2003 01:30 pm, Patrick Shirkey wrote:
> > >>Paul Perkins wrote:
> > >>>... and I'm still waiting for the day when someone explains ALSA
> > >>>configuration files
> > >>>in a way that I can understand....
> > > What don't I understand? I would like to see each concept that the ALSA
> > > configuration file language is intended to be able to express, and then
> > > the syntax used to express that concept. Then some examples with clear
> > > explanations of why each thing in the config file was put there. As in a
> > > good programming language tutorial. What I've seen instead is a lot of
> > > chunks of strange-looking syntax "explained" by saying "try stuffing this
> > > in <some file somewhere>, and good luck." Which leaves me blundering
> > > around in the dark, hoping to get lucky :-).
> ...
> > "Don't bend the
> > spoon... Let the spoon bend you..."
>
> Maybe if I had any idea what you mean by "let the spoon bend you" I would also
> find the ALSA documentation crystal clear ;-).
>
> Paul Perkins
> sigmotto: Liberty is theft.
>
>
>
>
Hi all,
Just heard the news (rumors) of new Macs that are going to hit the
streets on Monday. Seems like Apple is finally going to catch-up with
the PC world: there's talk of using IBM's PowerPC 970 64-bit CPU's.
Makes me wonder what repercussions this will have on the whole LAD/LAU
community, considering that they supposedly will have built-in optical
audio I/O and with the recent announcement of Trolltech to make OS X Qt
GPL-ed, leaves less and less advantages in Linux's favor (apart from the
obvious untouchable open architecture and perhaps faster growing
user-base -- according to recent news, can't remember where I exactly I
read it tho, sale of factory-built Linux boxes should surpass Apple's
this year, and that does not even include people with home-built
machines and dual-booters).
Please don't get me wrong. I am still in favor of Linux, obviously due
to its open architecture. But at the same time I am becoming a bit weary
of having to "hack" my advanced audio settings rather than use
user-friendly tools. That, coupled with still anemic direct vendor hw
driver support has really made me pay closer attention on Macs (as scary
as that sounds). Yet, I feel such a sense of accomplishment when my
Linux purrs just right with my desktop being uniquely configured and
tailored to my needs. After all, I am a geek. :-) And the inner struggle
goes on...
Anyone care to comment or (please) dissuade me from potentially making a
costly mistake? ;-)
Ivica Ico Bukvic, composer & multimedia sculptor
http://meowing.ccm.uc.edu/~ico
Hello,
As far as I know, no NoteEdit mailing list exists. So I have to ask
here...
I have installed NoteEdit and am trying to use it (or actually, to
help mu musician wife use it). But we don't understand a couple of
things.
First, to create two staves that are for the same instrument? This is
common in piano scores - one staff with the trebke clef for the right
hand, plus one staff with the bass clef for the left hand. Bars,
repeats, etc. should go across both staves.
Such staves are usually joined by a brace (accolade?), but as NoteEdit
is not a direct printing editor, the absence of the brace itself may
be quite understandable.
Second, is it possible (and if yes, how) to enable some sort of line
wrapping, as common in printed scores? Working with one long line is
somewhat inconvenient.
--
Best regards,
Mikhail mailto:mr@ramendik.ru
I am trying to install MusE, which means installing Jack as well.
The first issue that I have run into is that MusE requires glibc 2.3.1 or better to compile. My RH 8.0 has glibc 2.2.93-5. Will updating to 2.3.1 cause my previously installed binaries (i.e., the entire system) to stop working? Or is 2.3.1 backwardlycompatible with 2.2.93-5? Or can you have both libraries on one system simultaneously? In other words, what are the ramifications of updating glibc?
Then there are the same considerations for updating qt 3.0.5-17 to 3.1.0 or better, except that it is my impression that qt is much less central than glibc. Would anything (everything?) need to be recompiled with this new version of qt?
Another issue relevant to both of the above is the question of RPM vs source installation. There are i386 +/or i686 RPMs for both qt and glibc on the Red Hat site. Any suggestions as to whether I should install from source or from those RPMs? Which of the RPMs would be better to install on a Celeron 300A?
Finally, in preparing to install MusE I installed fluidsynth and
libsndfile. Fluidsynth seemed to go without a hitch (tho I haven't used it yet) but libsndfile's configuration summary suggested that I add /usr/local/lib/pkgconfig to the PKG_CONFIG_PATH variable because other programs compiled against libsndfile might need it.
Sure enough, when <./configure>ing jack, it couldn't find sndfile.pc, and while <make>ing jack, it exited with an error. I tried:
env $PKG_CONFIG_PATH=/usr/local/lib/pkgconfig
and it listed all the env variables with the appropriate entry appended. Thinking that everything was set, I tried to re<./configure> and <make> jack, but it exited with the same error. Double checking with <env> showed that the new entry had disappeared. I double checked this, and every time I set the variable with env, it lists it once, then it disappears on further <env>s.
Anyone know what is going on here?
Thanks,
Barton
P.S. I tried a different way to send mail. This is supposed to send text without all the redundant html coding. Is it any better?
Hi all
I have sort of resolved it.
My default distro configuration, from Slackware 9 compiles ATAPI CD-ROM
support, the main SCSI support, and the ISO9660 filesystem into the kernel.
I usually make these as modules, to make the kernel a little smaller and
thus use less memory. If I leave these options compiled into the kernel,
there is no problem. However, if they are all as modules, it doesn't work.
DMA is enabled by default, and my DVD-ROM drive is set up to be mounted
from /dev/cdrom which is symlinked to /dev/scd0 when using SCSI emulation,
and /dev/hdc when using straight IDE. I usually have SCSI emulation set up
for burning.
This has never been a problem for me in previous kernel versions. I will
live with it now, as I guess it is a small kernel size increase and should
not change the performance in any great deal.
Thanks again
Luke
Yes, on my laptop....(IBM Thinkpad T30) I experience lockups (Kernel
-oops once in a while) during bootup. It seems to be the ide-scsi module
thats causing the problem. If I ensure that its not loaded during bootup
then it seems to be fine. I can load it later manually using 'modprobe
-a ide-scsi'
If you can figure out whats causing this....it will be much appreciated.
Luke Yelavich wrote:
> I wrote earlier:
> > Hi all.
> > I am wondering whether anybody else has experienced lock-ups when
> trying to mount a CD-ROM device using kernel 2.4.21 with low > latency
> and preempt?
> >
> > I have tried with SCSI emulation, as well as normal IDE. I am
> currently re-compiling without low latency and pre-empt, but wondering >
> whether this is a reported kernel problem, or a problem that these
> patches may have introduced?
>
> > Any ideas or suggestions are welcome.
>
> > Regards
> > Luke
>
> Ok. This didn't help, so I am going to scour my kernel configuration and
> see if there is anything amiss.
>
> Luke
>
>
>
>
I wrote earlier:
> Ok. This didn't help, so I am going to scour my kernel configuration and
see if there is anything amiss.
>
> Luke
Ok haven't found the source of the problem, but I am able to successfully
mount CDs in my burner, but not in my DVD-ROM drive.
Still open to suggestions.
Luke
Hi all.
I am wondering whether anybody else has experienced lock-ups when trying to
mount a CD-ROM device using kernel 2.4.21 with low latency and preempt?
I have tried with SCSI emulation, as well as normal IDE. I am currently
re-compiling without low latency and pre-empt, but wondering whether this
is a reported kernel problem, or a problem that these patches may have
introduced?
Any ideas or suggestions are welcome.
Regards
Luke