Hi all,
Ive come across quite an odd problem.
When playing audio via my Revo7.1 card using ALSA, i get a high pitched tone (est
~14khz) mixed with the audio im playing.
The tone is constant and is not effected by the volume controls.
The tone is only present while an app (for example aplay) is using the card.
Some apps cause the tone to be louder thea others (but the tone is of the same
constant freq).
What makes the problem strange is that if i use JACK to play audio through the
card, the tone isnt present at all.
Has anyone else come across this problem?
BTW, im using the latest kernel (2.6.5) with the ALSA drivers that came with it.
Thanks,
Mark.
Greetings:
A client has asked me to get some opinions regarding AMD CPUs and
recommended motherboards. He's planning to replace an SMP system that
has apparently never worked quite right. He doesn't want another SMP
mobo, and a friend is advising him to go with a uniprocessor system
built around a recent AMD CPU. The recent JACK problem with AMD CPUs was
a revelation for me: I'd never had any problems with AMD chips, but now
I'm feeling reluctant to recommend them. Am I just being paranoid, or
are there particular reasons to go with Intel instead of AMD ? My
client is considering a P4 instead of the AMD, hence this infoquest...
Also, what's a recommended motherboard ? Are there any mobos that
should definitely be avoided ?
TIA for any help you guys can proffer, it's much appreciated.
Best regards,
dp
> -----Original Message-----
> From: linux-audio-user-bounces(a)music.columbia.edu [mailto:linux-audio-
> user-bounces(a)music.columbia.edu] On Behalf Of Mark Knecht
> Sent: Thursday, May 06, 2004 1:47 PM
> To: A list for linux audio users
> Subject: Re: [linux-audio-user] Is there a shortcut to merely test a
> mididevice?
>
>
> A nice feature in Reaktor Session is the ability to play a patch using
> the standard keyboard. z-? provide an octave with a few keys in the
next
> row up (s,d,f,h,j, etc.) providing sharps.
>
> Does no Linux soft synth provide some capability like this?
Pd has this functionality with the [keys] object. But there is also the
stand alone vkeybd.
I think a number of soft synths come with vkeybd, most notably (IMO)
ZynAddSubFX.
m.
_________________________________________________
Scanned on 06 May 2004 21:38:33
Scanning by http://erado.com
Hi all,
I've been playing the new game ut2004 on my Fedora ccrma box. This
game uses OpenAL for 3d sound which uses ALSA to route the audio through
my on-board Nforce2 sound module. It sounds very good, however sometimes
(not everytime) when I stop the game and check "ps aux" I notice esd is
running and I know it usually doesn't run so it must be starting for the
game. Should this be running at all since I'm using ALSA and OpenAL? If
not, should I just remove it? I'm not really clear about what function
esd actually serves.
TIA
Rick B
Hello,
I would like to do some simple WAV editing. Actually, minimum
pre-mastering of an audio CD: normalizing, cutting out pieces, dividing
into tracks, altering volume in some places.
My problem is, at this point alsa drivers are not working for me. And in
itself this is not a problem. The audio source is not the sound card, so
I don't do realtime audio capture. And as I only want simple editing, I
don't care about playback latency.
Which WAV editor should I use? I'd like it to be able to work with OSS
(perhaps via jack-oss?).
Yours, Mikhail Ramendik
Kai Vehmanen wrote:
> Hello all,
> this year's first stable Ecasound release is now out!
> And while I'm at it, here are some recent interesting Eca-related
> links and news items:
> * http://4ms.org/influx9/
> * http://www.agnula.org/documentation/dp_tutorials/no-x/
> * http://emi.thevtek.com/
> But now, back to the 2.3.3 release. CVS is tagged with 'v2_3_3' as usual,
> and here are the details...:
> 1. Summary of changes
I'm having trouble compiling ecasound, but I can't compile 2.3.2 now
either, so I think there's something wrong with my system. I'm just
wondering if anyone else is having problems with this.
make fails like this:
PROCEDURE_TIMER::to_string() const':
kvu_procedure_timer.cpp:147: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
make[2]: *** [kvu_procedure_timer.lo] Error 1
make[2]: Leaving directory
`/home/eric/audio_code/recent_releases/ecasound-2.3.3/kvutils'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/home/eric/audio_code/recent_releases/ecasound-2.3.3'
make: *** [all] Error 2
System details below.
Thanks,
Eric Rz.
asus a7v8x-x
athlon XP 2800+ (2071.203 MHz)
1.5GB PC2700 RAM
12GB / /dev/hda2 (actually a 40G disk)
160GB /mnt/audio/ /dev/hdc1
2GB swap /dev/hda1
(onboard via8235 -- disabled)
ice1712 M-Audio Delta-66 w/omni i/o
ymfpci guillemot maxisound fortissimo -- midi only
debian testing (sarge)
2.6.5 (pre-empt on -- kernel.org sources compiled via make-kpkg)
drives tuned in kernel config
alsa-1.0.4rc2 drivers compiled in kernel tree
realtime-0.0.4 lsm (insmod'ed since make install screws things up)
alsa-1.0.4 (lib, envy24control, tools)
libsndfile-1.0.9 from tar.gz
libsamplerate-0.1.0 from tar.gz
jack-0.98.1
./configure --enable-capabilities --enable-optimize
--with-default-tmpdir=/dev/shm --disable-portaudio --disable-oss
ecasound-2.3.3
./configure --enable-pyecasound=c --disable-oss --disable-arts
--with-largefile
Taybin Rutkin wrote:
>What is the problem with JACK and AMD cpus? I haven't heard of one.
>
>
>
Not so long ago a release of qjackctl in Planet C failed due to (IIRC)
JACK getting compiled with an SSE call (or calls) that killed it
completely on my Duron. The problem was simply and quickly solved, and
I'm perhaps off-base accusing JACK but that's where the problem came
from. Maybe it was a bad make ?
Anyway, if it's the opinion of the LAD developers that AMD is OK then
that's what I need to know. As I stated, I've had only that one
difficulty with AMD and Linux audio software, so I think I'm just being
paranoid.
Best,
dp
Hi all,
Initially posting on Tim Orford's Linux VST Compatibility Page, my quest has
been to test all Win-only FreeVSTi's featured on the K-v-R database under Linux
thanks to some of Kjetil Matheussen's apps and to report the way they work in my
language, to speed up things a bit!
I've posted the list on the K-v-R forum:
http://www.kvr-vst.com/forum/viewtopic.php?t=42640
Because that's where i've found most of the plugins:
http://www.kvr-vst.com/get.php
Alternatively, until the nodes change while I update my bookmarks, you can
browse all links to devs there:
http://theremin.free.fr/hunchback/index.php?nodes=|0|461|897|1098|1103|/
Let me quote one of the first answers to the thread: "The stuck notes in some SE
VSTi are most likely due to CK's Unison modules that are a little twitchy."
Have your copy saved on a text file, so that you can emulate a database search.
Ex: getting all interesting working plugins among all plugins stored on a text
file named "VSTi":
cat VSTi | grep ': W!'
NB:
Do you want to practise your french?
http://fr.audiofanzine.com/apprendre/mailing_forums/index,idtopic,60705.html
Cheers,
Mr°Freeze
Using a Turtle Beach Santa Cruz card or should I say experimenting...on
the 2.6.5mm-2 kernel from Thac's repository.
I'm curious if I can get some additional discrete outputs in jack via
the good ol' mystery .asoundrc file? I have wondered with all of these
supposed 5.1 cards that have a rear and front as well as center channels
as to why this is not possible? The one thing I see different about the
Santa Cruz is that it seems to show dedicated pcm slots for center and
rear in /proc/asound/pcm?
Having 4 discreet outs on a 5.1 card would be usefull for some things me
thinx.
R~
Hi Steven:
Forgive me for this late reply, I was in Karlsruhe when your message
arrived.
For the most part I had already discovered the answers to my original
queries, but read on... ;-)
>As Juan indicated, this behavior is supported by run "scons -c".
>A number of other software packages that are beginning to use SCons set
>up an alias in their SConscript files so you can still type "scons clean"
>at the command line.
>
That would be good. We autotoolers are quite familiar with the 'make;
make install; make clean' process...
>> 3. No man pages, that sucks on a UNIX/Linux platform. The GNU
>>autotools have them, SCons should have them too.
>>
>>
>
>How are you installing SCons? We do have a very thorough man page, but
>it sounds like you've stumbled into a hole in the process that prevents
>it from being installed. Can you help me understand what it is so we
>can fix it? Is this from one of the SCons packages you downloaded, or
>is it from the scons/ or scons-local/ package shipped internally with
>CT or CSound?
>
This is an odd one. Apparently the install step is not installing the
man page by default (someone else mentioned that they manually placed it
in /usr/local/man). I downloaded, built, and installed the SCons package
available from the home site, and I *think* I followed the instructions
exactly. At any rate, SCons itself works perfectly. :)
>> 4. No 'scons uninstall' ?? Again, if I'm missing it, please inform
>>me how it's invoked.
>>
>>
>
>As Juan indicated, this is something the SConscript writer has to supply.
>
I guess that's okay. I'd be happy if it were de rigeur for autotools too...
>> 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)
>>
>>
>
>SCons itself is very intentionally written to run on an old Python version
>(1.5.2) so you don't have to install an up-to-date Python to use it.
>CT and Csound may require later versions of Python to handle Python 2.x
>code they've put in their SConscript files, though.
>
Mea culpa, sorry about that. Now it needs to become a de facto component
in all significant distros.
>Although SCons has been around a while now, it's only just now beginning
>to reach the sort of critical mass that makes all of the distro owners
>sit up and take notice. The more voices that request it of other distros
>(such as RH), the easier this will get...
>
>In the meantime, we're trying hard to continue to make SCons as easy as
>possible for both software developers and end users to use, so I'm very
>glad to receive the feedback. Thanks for posting your questions/comments,
>and if there are other ways SCons can be improved to make this sort of
>transition a little easier, please don't hesitate to let me know.
>
Thanks, Steven. Your response is much appreciated, and I'll be sure to
contact the SCons team if/when I run into any major difficulties.
Best regards,
Dave Phillips