I cannot figure out how to automatically set permissions of
/proc/asound/card1/pcm0p/oss. I tried Having the line
options snd major=116 cards_limit=4 device_mode=0660
in /etc/modutils/alsa, but alsa won't come up, saying: "Unknown symbol
device_mode". Google tell's me that is a common problem. Is there a new
way of setting the permissions of /proc/asound/card1/pcm0p/oss or /proc
in general???
This is on kernel 2.6.4...
--
peace, love & harmony
Atte
http://www.atte.dk
Hi,
I have the EMI 6|2m. The card works ok with Jackd - at 16-bit and with a
large period size. The card records cleanly at 24-bit too but gives
strange noise when connecting Jack ports.
So it works but not perfectly.
If any suggestions on how to ipmrove the performance with jackd would be
more than welcome.
-Jorma
> Thanks again everyone.
> I have decided to get a EMI 6|2 and plug it in to see if it will work.
> If it does not, I plan on shelling out the cash for the VXpocket 440 PCMCIA
> card.
> Thanks again for all of the input. I'll keep you posted on results.
>
> Wade
__
Sano ei kuukausimaksuille. Hanki Suomen edullisin kuukausimaksuton GSM-liittymä osoitteesta http://www.saunalahti.fi. Puhelut vain 0,109snt/min.
> Thanks for the reply,
> As I am only in the posession of a laptop, PCI is not an option.
> Are there any PCMCIA otions out there, or should I wait until
> Firewire/USB 2.0
> becomes more available?
I don't think the audio spec changes with USB 2.0. That would make backwards compatability a little tough, but I may be wrong. I'm not familiar enough with firewire and PCMCIA audio devices to provide useful advice on their pros and cons.
Using a laptop, you may not have much of a choice but to use a USB device. In that case maybe some people on this list could provide you with some advice on success (or lack thereof) when using USB devices with Jack. There's lots of reference to troubles with the Quattro on the Jack Dev list, so try looking around and see if there's anything that works better before settling on what you want to buy.
-Reuben
The first SourceForge release of realtime-lsm (0.1.0) now available.
http://prdownloads.sourceforge.net/realtime-lsm/realtime-lsm-0.1.0.tar.gz?d…
The Realtime Linux Security Module (LSM) is a loadable extension for
Linux 2.6 kernels. It selectively grants realtime permissions to
specific user groups or applications.
There are only a few small differences between this release and the
realtime-0.0.4 version released back in March. If that was working
satisfactorily, there is no need to upgrade. The main purpose of this
release is to take advantage of the services provided by SourceForge.
(*) The module now declares the appropriate kernel vermagic string,
thanks to a patch provided by Guenter Geiger.
(*) Although the SourceForge project name is `realtime-lsm', the
module it builds and installs is still called `realtime' and
supports the same user interface.
This LSM was written by Torben Hohn and Jack O'Quin, who make no
warranty concerning the safety, security or even stability of your
system when using it. But, if you do have problems, we would like to
know about them via the SourceForge bug tracking system.
--
joq
hi all,
since i'm about to rewrite my (pd) performace patch, i'm curious if i
should switch to supercollider ...
i heard that (on macs) supercollider computes much more efficient than
max/msp ... is that somehow compareable to linux / i686 / pd?
has anyone tried to run benchmarks with similar patches on both programs
to compare the cpu usage?
cheers...
Tim mailto:TimBlechmann@gmx.de
ICQ: 96771783
--
The only people for me are the mad ones, the ones who are mad to live,
mad to talk, mad to be saved, desirous of everything at the same time,
the ones who never yawn or say a commonplace thing, but burn, burn,
burn, like fabulous yellow roman candles exploding like spiders across
the stars and in the middle you see the blue centerlight pop and
everybody goes "Awww!"
Jack Kerouac
Hi all,
Few days ago there was discussion in the list about mastering-CD/compressing/
limiting/gain-upping and so on. I have strange feeling from the discussion.
Does it mean, that, indead, we (all CD-listeners) listen DAMAGED with such
compressing music? I don't mean any music/sound engineering work! I'm saying
about market demands (compressed music is more sutable for cheap audio quipment,
isn't it? And compressed sound seems to be better at low volume level, don't it?).
If it is true (i.e., a market demands to damage music) - are there any (software)
tools to anti-compress a dynamic range? And - is it worth even to try to expand
dynamic range?
P.S. I'd like to repeat, I don't say about engineers work - they try to do
their work as good as possible, I think. I'm saying about a market
influence to music quality.
Andrew
Hey,
My crappy, year-old "Mandrake Audio Workstation HowTo" is horribly out of date,
and is still receiving many many hits per day. Since I don't have time to
rewrite it, I've made it community-accessible on my new site. If anyone wants
to help edit/update/add content, they can via the web at http://groundstate.ca .
Todo:
- update to Mandrake 10
- revise for 2.6 kernel
- add MIDI information
- tidy up the hellish HTML
Also, if anyone wants to start another community-edited linux audio book, let me
know.
Austin
I've been lurking on this list for a few months... I haven't even
created a Linux Digital Audio Workstation yet, but I'd like to. I'm
becoming more and more a believer in Open Source Software not only on
the server but also on the desktop... (I digress, sorry).
I'm looking at the latest MIDI sound modules and thinking can't I
achieve many of these things using Linux and my PC?
1) I want to have many sounds available for live playing (via MIDI) on
my keyboard. That's the top priority. Lots of sounds. Good quality
sounds. I'm thinking a sample playback machine or sound fonts
(right?). Can't I even achieve BETTER sounds with my PC than with a
very expensive new sound module?
2) I'd like to be able to sequence those great sounds. It would be
even better if I could use the sequencer WHILE playing live sounds
through this machine.
3) It would be very cool to be able to edit those sounds and tweak
them. Doesn't have to be "live" though.
MY QUESTIONS: Can I achieve these goals without too much fuss
(remember I'm a newbie)? Which "distro" (CCRMA or other?) would be
best/easiest? Do I want to go with sound fonts? What sound card
should I go with (not too expensive, ok?)?
Thank you Linux Audio Gurus!
--
===========================================================
"He is no fool who gives up what he cannot keep
for that which he cannot lose."
-- Jim Elliott
RICHARD K. INGALLS
Director of Information Technology
Glenwood R-8 School District
West Plains, MO
email..ringalls (at) glenwood.k12.mo.us
web....http://glenwood.k12.mo.us
ph.....417.256.4849
fax....417.257.2567
"Miracles are a retelling in small letters
of the very same story which is written across
the whole world in letters too large
for some of us to see."
-- C. S. Lewis
===========================================================
Greetings:
I'm happy to see and hear another release of CheeseTracker, but I have
a couple questions regarding SCons. I'm not opposed to its use, it
appears to resolve many issues for cross-platform builders, but since it
is relatively new (and I'm relatively old) I'm a little confused by it.
The SCons FAQ is pretty much just useless history and doesn't answer the
following questions:
1. Apparently SCons does without the need for anything like 'make
depend' or 'make clean'. If that's true, does it mean that SCons builds
fresh every time, i.e., that it autoerases the compiled objects ?
2. If something like 'make clean' is supported, how do I invoke it ?
What can I do if I don't want automatic erasure of the object files ?
3. No man pages, that sucks on a UNIX/Linux platform. The GNU
autotools have them, SCons should have them too.
4. No 'scons uninstall' ?? Again, if I'm missing it, please inform
me how it's invoked.
CT and Csound are now the only two apps on my system that use SCons.
The maintainers of Csound couldn't make the autotools work for
themselves, so now you must add downloading and installing SCons (and an
up-to-date Python) to the process of building Csound. Happily, that
isn't especially difficult, but it does add another layer of complexity
to the process. More to the point, why don't the mainstrean Linux
distros include SCons as a matter of course ?
Best,
dp