Hi all
With the release of Ardour 0.9beta1 on Sourceforge at
http://sourceforge.net/projects/ardour, Slackware 9.0 packages are now
available for immediate download. Download links, as well as md5sums, can
be found at http://www.audioslack.com/packages/ardour.
It is also worth noting that http://www.audioslack.com will hopefully
become a repository of binary packages of Audio software to be used on the
Slackware Linux Distribution. Please check out the site if you are
interested in helping out. Your help would be much appreciated.
Please feel free to contact me if you have any site suggestions, or have
any problems with the packages on the site. I don't offer specific package
help, but am willing to lend a hand with the installation and configuration
of packages posted there.
Regards
Luke
----------------
Luke Yelavich
AudioSlack Founder and main package maintainer
Audio software packaged for the Slackware Linux Distribution
http://www.audioslack.com
luke(a)audioslack.com
Stepping gingerly back into the pond...
I have a desktop Mandrake 9.1 system, on which I'd like to do rather
simple audio stuff (nothing particularly audiophile or
performance-oriented for now). It has an onboard soundcard which plays
sufficiently well, but records quite badly, with most things that I
record from cassettes and the occasionaly DAT distorting quite badly. I
have a Roland UA-30 USB Audio device, but so far I've found that
plugging it in when the system is running crashes the machine
completely, and that the machine fails to finish booting when I boot it
up with the device already hooked in.
Is it worthwhile getting another soundcard? Would something as simple
and inexpensive as a Soundblaster 16 PCI be sufficient?
I'm not all that sure what software I have running at the deep level,
since I've installed enough stuff that has pulled in other things via
dependency catching in urpmi that I'm not clear, for example, on whether
I'm using ALSA or not. For the user-end apps, I've been using Audacity
and Gnusound to record and edit and XMMS for most playback.
I'm having trouble configuring alsa drivers,
dmsg returns a line which says :
EMU10K1/Audigy soundcard not found or device busy
where it locates the card it returns:
Creative EMU10K1 PCI Audio Driver, version 0.19, 23:04:08 Jun 24 2003
PCI: Found IRQ 7 for device 00:09.0
IRQ routing conflict for 00:09.0, have irq 11, want irq 7
emu10k1: EMU10K1 rev 7 model 0x8071 found, IO at 0x3100-0x311f, IRQ 11
ac97_codec: AC97 codec, id: 0x5452:0x4123 (TriTech TR A5)
I'm trying to configure alsa drivers in the hopes that I will be able to
fix problems with full-duplex recording
Version 1.1 of the Linux Audio Workstation distro has been released!
This release, named "message in a bottle", features:
-- Verified on Redhat 9, 8.0, and 7.2
-- CVS'd at Sourceforge as law-distro
-- iso image at http://www.newyorkmusicunion.com/LAW-audio-distro
-- Upgraded to ALSA 0.9.4, alsaplayer 0.99.75
-- L.A.W. documentation page for each audio app
-- Now works with graphical or text system login
You can go to http://newyorkmusicunion.com/LAW-audio-distro and check
it out
jacob robbins.....
Is anyone successfully using this controller keyboard with linux audio
apps?
I just got one and wondered if anyone had experiences to share.
I might be sending mine back. I haven't turned it on yet, but some of
the buttons stick very badly. There are 4 function buttons on the right
side, F1-F4. F3 and F4 are stuck down completely. F1 and F2 come back up
if you wiggle them a little. I've never owned any type of keyboard
before, but this just doesn't seem right.
Besides build quality issues, has anyone tried one of these with any
linux audio software?
Thanks,
Eric Rz.
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?