Thanks!
Out of curiosity: how did you manage to keep binary compatibility?
Maarten
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE T
Hello,
I have been unsubscribed from alsa-devel for a while, so maybe i missed
the discussion about this, but a quick look at the archives did not reveal
anything.
I just downloaded alsa 1.0.0rc2, and discovered that the API changed.
For example (and this is only an example), take the function
sn
This is a nice coincidence, because I just installed Debian Sid
('unstable') on my home workstation.
I am also a convinced Debian user, and all the servers and workstations
I administrate are Debian Woody ('stable'). Now, recently, I have seen
myself forced to install more and more backported pac
there is a rawmidi test program included in the alsa-lib tarball.
(make sure you use it with the -v flag).
though maybe you'd prefer to use the alsa sequencer rather than
rawmidi. really depends on what you want to do though. (and note
that you can always route rawmidi into the alsa sequencer with
> You have to rerun snddevices script available in the alsa-driver package
> (utils subdirectory). The dynamic proc devices were removed on request of
> 2.5 kernel developers.
Ok. It would have been nice to find this information in the kernel 2.5.72
Documentation.
It's a bit strange though that
Hello,
I just upgraded to kernel 2.5.72 (I want to do some LL testing), with the
alsa driver as included in the kernel. The modules load, but I don't get
/proc/asound/dev (to which, as I understand, /dev/snd should link). I don't
use devfs.
Any suggestions?
Maarten
the configure script should check if jack is present, and if not, it
should not compile pcm_jack. i don't know why this fails, but i will
check it on monday (if nobody fixes it before)
maarten
---
This SF.net email is sponsored by: Etnus, maker
Bob Ham <[EMAIL PROTECTED]> wrote:
> The new pcm_jack thing presents a bit of a chicken and egg problem; I
> just compiled alsa-lib twice because jack depends on alsa-lib and if you
> configure alsa-lib with jack support, it depends on jack. Would it be
> possible for pcm_jack to be distributed se
> has anybody else noticed signs of sf.net throttling anon CVS access
> recently? if i try 2 CVS commands with only a very short interval
> between them, the second one fails. wait 1-2 mins, try again, it
> works.
this, and just being down for minutes. i find that sf.net's CVS access
has been ge
> can jaroslav or takashi fill me in on the current state of ALSA CVS
> with respect to JACK? there have been many, many reports of JACK
> crashing machines when run with recent ALSA CVS in real-time mode, and
> mentions here on alsa-devel of configure-time JACK detection that
> causes certain code
Hello Jaroslav,
Something else I need your advice on, is the full duplex operation.
When I try to run the latency test
./latency -c 2 -r 48000 -F FLOAT_LE -m 8192 -M 8192 -Pjack -Cjack -e
(btw, note the bug with the -f / -F flag!)
first of all,
snd_pcm_hw_params_get_period_time(p_para
I wrote:
> Attach you find another pcm_jack patch, that contains some major
> changes.
Forgot to attach it.
Maarten
Index: include/pcm_plugin.h
===
RCS file: /cvsroot/alsa/alsa-lib/include/pcm_plugin.h,v
retrieving revision 1.6
diff
Hello Jaroslav,
Attach you find another pcm_jack patch, that contains some major
changes.
- now multichannel works (before only 1 channel worked). i tested stereo,
and it works fine.
- i extended the configuration. the jack ports to connect to are now not
hard-coded anymore. instead, they will
../src/.libs/libasound.so: undefined reference to `snd_interval_set_minmax'
which is indeed not defined anyware in alsa-lib...
maarten
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Attached you find the patch with my latest changes. Both playback and
capture from jack work now, though not simultanously.
$ jackd -d alsa -p 4096 -d hw:0
$ aplay -Dmyplug /usr/share/sounds/KDE_Startup.wav
$ arecord -Dmyplug -d 4 foo.wav
(see my previous mail on how to define myplug)
Now, my
I wrote:
> The problem I described in my previous mail (no more calls to
> snd_pcm_jack_mmap_commit after start) still occurs though... Any
> idea what might be the problem, or where to look?
Okay, I fixed this. It was a missing
pcm->poll_events = POLLIN;
(after pcm->poll_fd = fd[1] ,
Hello,
I am experiencing lots of problems accessing cvs.alsa-project.org
bitone:~/alsa-cvs# cvs update alsa-lib
cvs [update aborted]: end of file from server (consult above messages if any)
bitone:~/alsa-cvs# cvs update alsa-lib
cvs [update aborted]: reading from server: Connection reset by peer
> I've updated a bit your code, but I cannot test it myself, because I
> cannot connect to a jack port - invalid destination port name - (I'll
> look what's wrong tomorrow).
Thanks a lot for your updates.
The problem I described in my previous mail (no more calls to
snd_pcm_jack_mmap_commit af
*sparams)
{
snd_pcm_plug_t *plug = pcm->private_data;
- _snd_pcm_hw_params_any(sparams);
int err;
+ _snd_pcm_hw_params_any(sparams);
if (plug->sformat >= 0) {
_snd_pcm_hw_params_set_format(sparams, plug->sformat);
/**
* \file p
> [...]
> Nope. The snd_pcm_mmap_appl_forward(pcm, size) is the appropriate.
> [...]
> I think that it should be opposite:
>
> appl_ptr should be increased when application writes samples (commit) and
> hw_ptr should be increased when jack callback processes samples
Okay, your mail made everythin
> There was a problem with refine code for pcm_plug, please, try again with
> latest CVS sources. Also, look to updated pcm_dmix plugin for implementing
> the "right" refine function.
Okay, this works fine now.
I am trying to do the following, using the mmap functionality. Let's
start with play
> Please, see to refine code in pcm_dmix.c. You cannot do it with your way.
> The refine means that it reduces given configuration and if no valid
> configuration for given parameter exists, then the result value has to be
> empty (or not set).
Okay, so, where I tried to do something like (not
Thanks for your reply.
> > As far as I understand, the easiest solution would be to have a pcm_plug
> > plugin inbetween the alsa application and the pcm_jack plugin, to take
> > care of sample rate and data format conversion. Then the pcm_jack plugin
> > simply restrict it configuration space to
Hello,
I am trying to write a pcm_jack plugin, which would allow existing alsa
applications to use jack as input/output, without changing any code. The
plugin will use some internal circular buffer for the data transfer
between the alsa read/write calls and the async jack process callback.
I have
sorry, just read your mail about the change in module option names.
problem solved.
maarten
---
This sf.net emial is sponsored by: Influence the future
of Java(TM) technology. Join the Java Community
Process(SM) (JCP(SM)) program now.
http:/
I just installed alsa-driver-0.9.0rc4, but alas i get invalid parameter
when modprobing...
$ uname -ra
Linux bitone 2.4.18-686 #1 Sun Apr 14 11:32:47 EST 2002 i686 unknown unknown GNU/Linux
(this is the Debian 2.4.18-686 kernel)
$ tar jxvf alsa-driver-0.9.0rc4.tar.bz2
[...]
$ cd alsa-drive
>> Is this happening with the CD player?
No, I am getting no sound at all. For example with xmms, aplay,
test/pcm.c etc.
Maarten
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
wouldn't it be easier to check for zerocrossings?
---
This sf.net email is sponsored by: Jabber - The world's fastest growing
real-time communications platform! Don't just IM. Build it in!
http://www.jabber.com/osdn/xim
__
i am going through the alsa-lib/test/pcm.c example, and i am
wondering about the different transfer methods available. are
there any guidelines or suggetions which method to use in
which particular situation?
maarten
---
This sf.net email is
add the flag -v to get verbose output and see what events you receive (this should be
default behaviour i guess...)
---
This sf.net email is sponsored by:ThinkGeek
Bringing you mounds of caffeinated joy.
http://thinkgeek.com/sf
___
> No, thats not the issue. It might be a CVS sync issue at sf.net, as
> well. The "anonymous" CVS repository is sometimes 6hrs behind the
> "login" CVS repository.
Wow! That is really very bad! Is this a known problem? Is sf working
on this? I wonder why the login and anonymous repositories are
> you can connect a port of aconnectgui to the system port.
> the system port will broadcast a notification with
> SND_SEQ_EVENT_CLIENT/PORT_START, and PORT_SUBSCRIBED/UNSUBSCRIBED
> events if the corresponding action occurs. checking events can be
> done just like others via poll or select.
> of
Hello,
I want to have aconnectgui automatically update when changes have
been mode in the alsa sequencer connections (for example by
aconnect, or new applications being launched, or an application
creating a new connection). What would be the correct way to do
this? Maybe a polling alsa sequence
current alsa-cvs compilations fails:
rme9652_mem.c:45: ../../alsa-kernel/pci/rme9652/rme9652_mem.c: No such file or
directory
maarten
___
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You ge
> Can anyone tell me if the Audigy support status has changed at all since:
Hmm. I have an Audigy. Works ok for me. wavetable, mpu401, audio i/o.
Drawbacks: the smallest blocksize is not that small (384 samples I think)
and behaviour under Windows (if you care about that) has been a bit
dubious.
Hello,
I just updated alsamixergui and aconnectgui. Changes: compilation on
Mandrake fixed (thanks to Thierry Vignaud <[EMAIL PROTECTED]>)
and a small though extremely annoying bug which stopped the alsamixergui
sliders from working (which I'd say is rather bad for a GUI mixer ;-) )
For downlo
Hello,
I just updated alsamixergui and aconnectgui. The code is now up to date
with alsa-utils 0.9.0rc1.
alsamixergui and aconnectgui are fltk front-ends for alsamixer
and aconnect. thet are written directly on top of the alsamixer and
aconnect source, leaving the original source intact, only a
Hello,
Updating my fltk alsamixer frontend, alsamixergui, I once again
found that alsamixer (and therefore alsamixergui) shows a lot
of sliders. With my Audigy, it's really too much. I think it
would be very nice to be able to configure alsamixer, to show
only a subset of sliders. I guess a .alsa
> > I was assuming that using poll (snd_pcm_wait), with the
> > alsa-lib/test/latency.c program would have snd_pcm_read
> > return period size samples at a time, but this is not
> > the case.
> > [..SNIP..]
> It's intended. It looks better in my eyes, if we can process some data
> ahead in low-l
Hello,
I was assuming that using poll (snd_pcm_wait), with the
alsa-lib/test/latency.c program would have snd_pcm_read
return period size samples at a time, but this is not
the case.
As far as I understand, the problem is that in the following
code:
val = !block ? 4 : snd_pcm_hw_params_
Hello Patrick,
Looks very nice.
Am I correctly assuming that you will be the maintainer of the ALSA pages
from now on?
Could you add the following alsa 0.9 applications I wrote:
http://www.iua.upf.es/~mdeboer/projects/tapiir/
http://www.iua.upf.es/~mdeboer/projects/aconnectgui/
http://www.i
On Mon, 8 Apr 2002 10:15:49 +0200 (CEST)
Jaroslav Kysela <[EMAIL PROTECTED]> wrote:
> The defines are in asound.h file - look for 'Timer section - /dev/snd/timer'.
>
> Usage (using defaults):
>
> options snd-seq snd_seq_default_timer_device=1
>
> or (full specification):
>
> optio
Hello,
Sorry for being such a pain, but I really want this to work, and I
really think this is something that has general interest: using a
higher accurate midi event timing. So: HOW DO I USE THE RTC TIMER?
I can find no up-to-date documentation about this.
The latest I find is a mail by Takashi
> so essentially you skip alsalib and interact with the driver only. i
> have found this to be the least painful way of dealing with raw MIDI
> streams.
Tim, I think this is very bad advice, especially on the alsa-dev
mailinglist!
Charles, you might want to have a look at the documentation:
htt
Hello,
I sent the following to the list, but did not get any answer, so I
repost, and will elaborate a bit on it.
> Hello, I noticed that the alsa rtctimer is not compiled when you have
> the RTC in your kernel as a module. The problem is in
> alsa-kernel/core/Makefile, where CONFIG_RTC is teste
Hi Richard,
Thanks for your fast reply. I will send this message to the ALSA development
list, maybe somebody else has some comments.
>> I was wondering if you are planning to implement native ALSA (0.9) sequencer
>> support in Rosegarden-4.
> This is a whole can of worms - have a look at the m
yes, that sounds like a layout problem. i will try to get my hands on
a SBLive, and also use some virtual midi ports. as you might have noticed,
this release is still rather beta: lot's of printf to be removed ;-)
maarten
___
Alsa-devel mailing list
[E
"aconnectgui is a FLTK based frontend for aconnect. It is written
directly on top of the aconnect source, leaving the original source
intact, only adding a couple of ifdefs, and some calls to the gui
part, so it provides exactly the same functionality, but with a
graphical userinterface."
http://
Hello,
An updated version of alsamixergui is available from
http://www.iua.upf.es/~mdeboer/projects/
alsamixergui is a FLTK based frontend for alsamixer. It is written
directly on top of the alsamixer source, leaving the original source
intact, only adding a couple of ifdefs, and some calls to
> I just completed version 0.1 of a very scrappy but functional gui midi
> patch bay for alsa's seq api. It's essentially just a graphical version
> of aconnect. It's available from:
I wrote one already a long time ago (though for alsa 0.5.x, but it should
be easy to port)
ftp://www.iua.upf.e
Kai Vehmanen <[EMAIL PROTECTED]> wrote:
> For fullduplex to work at 44.1kHz, you need to set sampling rate to 44100
> with ALSA's snd_pcm_hw_params_set_rate_near() function. The closest
> matching values are 44099.814 for capture and 44100.952 for playback.
Isn't this very strange? I thought that
I wrote tapiir, which is a realtime multi-tap delay. I am currently
cleaning up the code for a new release, which uses the alsa 0.9 api.
alsa, we are developing some realtime voice processing applications,
that really stress the system. we also use alsa here.
obviously, the use of a low latency
Hello,
I am trying to run the alsa-lib/test/latency test on an
ESS Maestro 2 (Dell Inspiron 3700), but it seems that
this card cannot do interleaved audio?
Jaroslav, could you update latency.c for these kind of
cards?
Maarten
___
Alsa-devel mailing
Andre Pang <[EMAIL PROTECTED]> wrote:
>> I am thinking of setting up a webpage, where people can post
>> their latencytest results, so we can keep an inventory of
>> the several combinations, categorising on:
>
> This is a great idea. I actually started re-writing the latency
> testing harness s
Hello,
I am thinking of setting up a webpage, where people can post
their latencytest results, so we can keep an inventory of
the several combinations, categorising on:
- processor
- SMP
- kernel version
- kernel patch
- kernel configuration
--- processor
--- SMP
--- ??
- tuning
--- vm
--- hdp
On Thu, 15 Nov 2001 21:47:02 +0100
Andy Lo-A-Foe <[EMAIL PROTECTED]> wrote:
> On Thu, Nov 15, 2001 at 07:54:41PM +0100, Maarten de Boer wrote:
>
> > Your results look good. For what processor did you compile your kernel?
>
> CONFIG_MK7=y
>
> Did I read correctl
Vincent Touquet <[EMAIL PROTECTED]> wrote:
> I have an Athlon too.
> Is it true that there are issues with the lowlatency patches
> (Andrew Morton's as well as the kernel pre-emption patches) and the
> optimizations used in the kernel for the Athlon processor ?
>
> If so, do I need to compile for
Takashi Iwai <[EMAIL PROTECTED]> wrote:
> I think 2.4.14 or 15pre are ok, too. The same LL patch should work.
I applied the 2.4.15pre1AA patch on 2.4.14 (with some very small
modifications), and the results are horrible.
http://www.iua.upf.es/~mdeboer/latency/2.4.14-15pre1AA/3x256.html
Maarten
On Thu, 15 Nov 2001 13:50:39 -0500
Paul Davis <[EMAIL PROTECTED]> wrote:
> >> Hmm sounds like h/w problem, then..
> >> It's interesting to know where the data is contaminated, whether on
> >> the driver level or transfer between capture and playback on
> >> user-space, or what else..
> >
> >I wou
> Okay, here's my setup:
>
> - kernel 2.4.15-pre4 + Robert Love's preempt patches
> (http://www.tech9.net/rml/linux/)
> - kernel HZ value set to 1000, default is 100
> (see /usr/src/linux/include/asm/param.h)
> - alsa 0.9.0beta9 + Trident 4DWave NX
> - SCSI hard disk with ReiserFS
> - Geforce
> Or, will you try AA patches? It's not a bad idea, since the current
> (vanilla) VM is based on Andrea's code. Linus still doesn't include
> all his patches.
Yes, I will try the AA patches, though I am not very sure which to use,
and on which kernel. The most recent one on a standard kernel (
On Thu, 15 Nov 2001 18:35:33 +0100
Andy Lo-A-Foe <[EMAIL PROTECTED]> wrote:
> On Thu, Nov 15, 2001 at 05:28:19PM +0100, Maarten de Boer wrote:
>
> > It would be really nice if somebody could repeat my tests on identical or
> > similar hardware (AMD Athlon, Trident 4
> I've used this setting:
>
> echo 6 > /proc/sys/vm/vm_scan_ratio
> echo 2 > /proc/sys/vm/vm_mapped_ratio
> echo 4 > /proc/sys/vm/vm_balance_ratio
Uuhh... I don't have these files...
$ ls /proc/sys/vm/
bdflush kswapd overcommit_memory page-cluster pagetable_cache
Did I miss something in my
> There are VM tuning parameters in /proc/sys/vm/vm_*_ratio files.
> Lowering these values tend to bring better latency results.
Any recommended reading about this?
I reinstalled my system (needed to do that for a while now anyway)
to be crispy clean. Look at the latest results.
http://www.iua.
> When I compile my kernel for i386 on an AMD Athlon, the
> alsa latency test is giving me weird distortion (knispering
> sound, like a dusty vinyl record)
> $ arecord -r 44100 -f S16_LE | aplay
> does not seem to have this problem.
I investigated this matter a bit further, and the crackling sou
I made a webpage with the several tests I did. Please have a look
at it. I ran tune_disk /dev/hda, and
do_tests none 3 256 0 2048
(indeed a really small size for the disk i/o test, but I was more
interested in the rest)
http://193.145.55.36/latencytest
The soundcard I use is a Trident 4DWave NX
Hi, I wrote this before, but I did not get any response.
When I compile my kernel for i386 on an AMD Athlon, the
alsa latency test is giving me weird distortion (knispering
sound, like a dusty vinyl record)
$ arecord -r 44100 -f S16_LE | aplay
does not seem to have this problem.
It really does
I am getting really disappointed and annoyed trying to obtain
low latency. I have been losing so much time by now, and it
still doesn't work as I expected.
I now have kernel 2.4.14 with Andrew Mortons LL patch, configured
and activated thorugh sysctl, compiled for 386 (even though I have
an AMD A
Not understanding why I could not get alsa-lib/test/latency.c to work
well, I decided to run Benno's latency test. It has been a long time
since I did... The results are surprising, and nothing like the excellent
results I have seen posted here.
$ ./do_tests none 3 128 0 256
http://193.145.55.36
> if you call poll(2) on the file descriptors returned by
> snd_pcm_poll_descriptors() (and there may be more than one for some
> kinds of PCM "devices"), then what you're actually doing is this:
Hmm, isn't this _exactly_ what the latency test does in poll mode?
(using snd_pcm_wait, which does po
Paul Davis wrote:
> Ah, OK. yes, i suppose this might not be clear.
> [...]
But you made it completely clear now! Thank you very much, Paul.
Paul Davis wrote also:
> but its basically fairly easy to get this performance out of
> any program that is engineered properly. latency.c is not the
> cor
I wrote:
> I don't think so, but I am probably completely missing the point.
> Let's start all over. I have a patched kernel, and I want to have
> low latency. I use latest alsa (cvs), and I run the latency test.
> (As you might have noticed, I submitted an filtersweep effect for
> the latency tes
Hello,
I am trying to get low latency with alsa.
I have kernel 2.4.13 with the preemptive patch and the
alsa-driver/utils/patches/rtc-2.4.9.dif patch applied.
In the kernel configuration, I turned on RTC and
Preemptive.
I run the alsa-lib/test/latency.c test in poll mode,
but the problem is the
On Tue, 06 Nov 2001 11:40:30 -0500
Paul Davis <[EMAIL PROTECTED]> wrote:
> >I run the alsa-lib/test/latency.c test in poll mode,
> >but the problem is the tick time, which is at 100 Hz:
> >
> >snd_pcm_hw_params_get_tick_time(params, NULL) = 1
> >
> >What am I doing wrong?
>
> using poll mode
Abramo Bagnara <[EMAIL PROTECTED]> wrote:
> This would not imply a "major" rewrite: the API and the kernel code has
> been thought for that.
> You need simply to have different snd_pcm_tick_set functions (see
> pcm_lib.c).
That's interesting. So you think that that would be the prefered way
to d
Hello,
I am using alsa 0.9.0beta8a, and I am having big difficulties
with synchronous I/O. I am using the latency.c test. When I
use it as it is, it eats all the CPU for 30 seconds (well, 3,
I changed to value the second time I tried). I can understand
why this happens, but it is certainly not wh
76 matches
Mail list logo
