Florin Andrei wrote:
> What's the max number of cards in a system that can be used by ALSA
> simultaneously?
8
> What's the max number of MIDI ports that's supported by ALSA?
There can be up to 8 rawmidi devices per card, but each device can
have an unlimited number of subdevices.
OSS emulation
Roc Wu wrote:
> > # ./aplay -t wav -f U8 -r 22050 alarm.wav
> > Playing WAVE 'alarm.wav' : Unsigned 8 bit, Rate 22050 Hz, Mono
> > ALSA lib pcm_plug.c:727:(snd_pcm_plug_hw_refine_schange)
> > Unable to find an usable access for 'default'
> > aplay: set_params:832: Sample format non available
> >
>
Cournapeau David wrote:
> My second problem is related to snd_card_next: If the card value
> returned by snd_card_next is different from -1, does that always mean
> than a alsa audio device is present on the system ?
It means that same kind of device with an ALSA driver is present.
This does n
Luke Yelavich wrote:
> usbcore: registered new driver snd-usb-audio
No other message? There should be at least an error message when the
driver fails to initialize. Please try to compile the kernel with
ALSA's "Debug detection" enabled, or --with-debug=detect when
configuring the package.
Rega
Måns Rullgård wrote:
> Is there a way to make alsa-lib stop spamming the terminal with error
> messages, for instance when a non-blocking open fails?
snd_lib_error_set_handler()
HTH
Clemens
---
This SF.Net email is sponsored by: Oracle 10g
Luke Yelavich wrote:
> below is the information I get when attempting to use this soundcard under
> a 2.6.6 kernel with alsa drivers 1.0.5rc1 and hotplug.
>
> dmes:
> usbaudio: device 3 audiocontrol interface 0 has 1 input and 1 output AudioStreaming
> interfaces
This is the OSS driver (audio).
Ed Wildgoose wrote:
> Can anyone suggest how to script the controls to default to some known
> values?
"alsactl store" saves the current values of all mixer control in
/etc/asound.state, "alsactl restore" restores them.
HTH
Clemens
---
This
Takashi Iwai wrote:
> I wrote:
> >
> > Clemens Ladisch wrote:
> > >
> > > depmod: *** Unresolved symbols in
> > > /lib/modules/2.4.26/kernel/sound/isa/wavefront/snd-wavefront.o
> > > depmod: errno
> > >
> > > The open/cl
IL PROTECTED]>
+ * Cleanups by Jaroslav Kysela <[EMAIL PROTECTED]>
* Ville Syrjala <[EMAIL PROTECTED]>
+ * Modified for ALSA 1.0.x by Clemens Ladisch <[EMAIL PROTECTED]>
*
- * You can use -a :...
- * For example: mpg123 -a 1:0 aaa.mpg
- * mpg123 -a gus
> Please, report (especially compilation) problems.
depmod: *** Unresolved symbols in
/lib/modules/2.4.26/kernel/sound/isa/wavefront/snd-wavefront.o
depmod: errno
The open/close/read system calls are implemented as inline functions
which change errno which isn't exported from the kernel.
Nicolas Hüppelshäuser wrote:
> I'm using alsa 1.0.4. How can I get a larger alsa buffer size?
PCM devices have a default maximum buffer size and a maximum maxmimum
buffer size. For example, in the snd-usb-audio driver, it's 64 KB and
128 KB.
The current value (in KB) can be seen in the file
/pr
Gilles Dégottex wrote:
> Why SND_SEQ_EVENT_NOTE event doesnt accept direct dispatching ?
> technicaly, there is surely a reason, but conceptualy, I dont see. Why do a
> difference ?
SND_SEQ_EVENT_NOTE isn't a 'real' event but gets split into two
events, SND_SEQ_EVENT_NOTE_ON and _OFF, and the latt
Gilles Dégottex wrote:
> > > but when I flush the output, I got an error: "Invalid argument"
>
> snd_seq_ev_set_direct(&ev);
> ev.type = SND_SEQ_EVENT_NOTE;
> ev.data.note.duration = 1000;
NOTE events must be sent through a queue because they need a timer so
that the NOTE_OFF event can
Gilles Dégottex wrote:
> I'm trying to dispatch midi event directly without queue.
> I did every thing I read in the alsa doc (for
> me: /usr/share/doc/libalsa2-docs-1.0.2/seq.html)
>
> but when I flush the output, I got an error: "Invalid argument"
> (when calling snd_seq_drain_output)
This may i
Luke Yelavich wrote:
> As above. The vendor and product IDs given are 0xa92 and 0x91 respectively.
>
> If there is any more information I can give, please let me know.
Output of "lsusb -v"?
And what exactly does "doesn't work" mean?
Regards,
Clemens
-
Patrick Shirkey wrote:
> >>Using the latest usb-audio code from cvs I get a kernel panic when
> >>loading the drivers.
> >>
> >>I'm running kernel-2.2.21 with gcc-2.95.4
>
> Unable to handle kernel paging request at virtual address 28302e63
> EIP:0010:[]Tainted: PF
>
> e08e7060 __insmod_snd
Ronald S. Bultje wrote:
> is it possible for me to get the cardnumber (and thereby the hw:N
> entry) for a given non-hw device (e.g. dspN, hw:N,M, dmix, ...)?
Try something like this:
/* Get the slave pcm of a pcm node. Caller must free the result. */
static snd_config_t *get_pcm_slave_pcm(snd_c
Sebastian Urbach wrote:
> I want to ask what happend with the following patch regarding the CMI
> 9739 ? :
>
> http://www.mail-archive.com/[EMAIL PROTECTED]/msg10804.html
>
> Are there any plans to fix the problem in the regular alsa release ?
Yes. There are plans to write a plugin that would imp
Rodrigo Severo wrote:
> With the Askey Magic I got only silence but with the Prolink PlayTV Pro
> revision 9D I got bad sound with btaudio. By bad I mean a slightly high
> pitch soundI got the sound of the TV with a slightly higher pitch than
> usual and with more than usual noise during silence. T
David McNab wrote:
> I'm trying to create and schedule outbound events, in realtime absolute
> mode.
>
> When sending these events directly, using SND_SEQ_QUEUE_DIRECT, the
> events get delivered fine to subscribers.
>
> But when adding realtime absolute timestamps, and marking the event to a
> que
Matt Flax wrote:
> The snd-usb-audio driver now doesn't hang my computer anymore during
> shutdown (it did with previous versions).
Just BTW: Does it still work if you unload and then reload the
snd-usb-audio module? >:->
Regards,
Clemens
Ronald S. Bultje wrote:
> for a given alsa device ("default", "dmix", "plughw:N", "hw:N,M",
> "dspN", etc.), how do I automatically obtain the right device to use as
> a audio mixer with that device?
Depends on your definition of "right device". In the general case
this isn't possible because man
Rodrigo Severo wrote:
> Clemens Ladisch wrote:
>
> >Rodrigo Severo wrote:
> >
> >>I have two Prolink PlayTV Pro capture cards (PV-BT878P+). One of them is
> >>revision 8E and tthe other is revision 9F.
> >>
> >>I tried to use both of them wit
Patrick Shirkey wrote:
> Using the latest usb-audio code from cvs I get a kernel panic when
> loading the drivers.
>
> I'm running kernel-2.2.21 with gcc-2.95.4
Works fine with my 2.2.19(?).
ALSA 1.0.4 fixed some horrible bugs in the USB compatibility code for
2.2.x kernels.
Where exactly does t
Rodrigo Severo wrote:
> I have two Prolink PlayTV Pro capture cards (PV-BT878P+). One of them is
> revision 8E and tthe other is revision 9F.
>
> I tried to use both of them with the snd-bt87x driver. Both of them
> returned only static.
Probably different mixer settings?
> I managed to get analo
Giuliano Pochini wrote:
> Some drivers use spin_lock_irq() a lot, while others always use
> spin_lock_irqsave(). I can't see the difference. When it's safe
> using the _irq() version ?
Only when you know that you are not in interrupt context.
Regards,
Clemens
Tom Watson wrote:
> Well, I've gone to another Compaq laptop. The previous one I had to
> resort to OSS (yuck) drivers and send it on its way. This laptop is
> one I'm going to use, so I'd like to get ALSA working on it.
>
> So... I've loaded ALSA and put the following in 'modules.conf':
> alias
Nico Schottelius wrote:
> anyone knows if there is the possibility to adjust sound volume or
> not.
CMI hardware doesn't have this capability.
It would be possible to write a plugin that scales sound data in
software before sending it to the device, but nobody has done this
yet.
Regards,
Clemen
James Courtier-Dutton wrote:
> Which section of code in alsa-lib is doing these conversions.
> I would like to see what code you use for the task of converting samples
> in float format to samples in int format.
Function snd_pcm_lfloat_convert_float_integer() in
alsa-lib/src/pcm/pcm_lfloat.c.
Re
Nikhil Deo wrote:
> When I read some captured data into a buffer by calling snd_pcm_plugin_read,
> how can I separate the left and right channels from that data?
In the most common case (interleaved stereo data), you have
alternating sample values for left and right.
HTH
Clemens
Erik Inge Bolsø wrote:
> I'm having trouble doing snd_pcm_hw_params_can_pause() on a certain pcm,
> even though it has already (hopefully?) been fixed to one config by
> snd_pcm_hw_params()... snd_pcm_hw_params has been called, at least. How
> can I check?
>
> fileja {
> type file
>
Caleb Crome wrote:
> Clemens Ladisch wrote:
> >However, Realplayer uses the OSS emulation through /dev/dsp0. To make
> >that work with your "file" device, add the following to the config
> >file:
> >
> > pcm.dsp0 = file
>
> Awesome! It works lik
Steve deRosier wrote:
> Is there any way for a program to query the alsa-lib to determine
> the version number?
The function snd_asoundlib_version() won't be available before 1.0.5.
For earlier versions, you can try to test if the symbols listed in
alsa-lib/src/Versions are available.
HTH
Clemen
ns wrote:
> I have WDM driver for our lab's own propertiary sound
> card(ADAT+SPDIF+DB...) and wanna write ALSA drv.
> I have linux w/kernel 2.4.20 (original).
>
> I know that I must patch kernel for ALSA and write ALSA driver.
> HOw to do it fastest?
look into alsa-kernel/Documentation/DocBook/wr
Caleb Crome wrote:
> >>>pcm.file {
> >>> type file
> >>> slave {
> >>> pcm "hw:0,0"
> >>> }
> >>> file "/tmp/file.raw"
> >>>}
>
> Alright, I did what you suggested, and real player comes up and connects
> to the dummy sound card (I had to do a modprobe snd-pcm-oss and
> snd-mixer-oss)
Lukas Degener wrote:
> Hi everybody and sorry for posting this to both, lad and alsa-dev,
> i was not sure which one fits better.
alsa-devel would be appropriate, but non-subscribers cannot post
there, so I'm keeping linux-audio-dev in the CCs.
> Concerning the issue with non-functional midi in o
Arek Korbik wrote:
> To summarise: hardware generates an interrupt when it should not - the
> driver should handle it (the simplest solution: ignore). The attached
> patch:
> - adds interrupt-on-FIFOE handling(/ignoring) to handler routine
IMNSHO it's better to check for the buffer completion int
Nikhil Deo wrote:
> It is to be done on QNX
By now, QNX's API is completely different.
> I need to capture input from the mic AND the line in.
This will work only if your hardware supports this. Many sound cards
can select exactly one input for recording.
> Then I need to output the mic input
Caleb Crome wrote:
> Arek Korbik wrote:
> >pcm.file {
> >type file
> >slave {
> >pcm "hw:0,0"
> >}
> >file "/tmp/file.raw"
> >}
>
> what do I do with that bit of configuration data? I found the
> /usr/share/alsa/alsa.conf, and there is a similar pcm.file entry
> in that, bu
Mathieu Rondonneau wrote:
> I have some problem writing an ALSA driver:
>
> When i use arecord:
> arecord -d 10 -r 8000 -f S16_LE -t wav -c 1 test.wav
>
> the data area of the wav file (test.wav) is filled with 0.
> I compared the data of the wav file and the data of the capture buffer:
> They are
Brian Furey wrote:
> i'm using an open source VoIP application with the
> alsa driver. My card is the onboard intel8x0.
>
>My problem is figuring out the patterns I am
> getting with the alsa driver when transmitting
> packets.
This depends more on how the VoIP application does things, not on
ian esten wrote:
> On Wed, 2004-04-14 at 10:00, Clemens Ladisch wrote:
> > What happens when you exchange the two 8x8 files in
> > /usr/share/usb/midisport?
>
> i get a working midisport 8x8! i can send it midi, and it shows up in
> /proc/asound/cards. thanks so much!
ian esten wrote:
> the midisport i have is reported as being hardware version 1.33 by the
> midisport control panel under windows xp (where it works fine). i looked
> in the midisport_fw loader, and it seems to only know about hardware
> versions 1.10 and 1.21. here are the entries in /var/log/mess
Perry Gilfillan wrote:
> I've a couple of people using my snd-tvmixer module with success now,
> and would appreciate comments/critcism/abuse (any thing is better than
> the deathly silence my first announcement yeilded) from people more
> experienced than myself.
Looks nice. (Not that I actually
Mathieu Rondonneau wrote:
> I'm writting an audio driver and i have some trouble.
>
> when i use:
> dd if=file.wav of=/dev/audio0
> the oss part of the ALSA driver seams to be used and some sound (not good
> sound but noise) are coming out. (the playback_pointer operator is called)
>
> but when i
Brian Furey wrote:
> with the ALSA driver, what do the OSS substream mean?
There are no "OSS substreams". ALSA PCM devices have substreams. A
device with more than one substream can be opened multiple times
simultaneously.
> If you have a 2 main capture channels, how many substream would
> you
[EMAIL PROTECTED] wrote:
> I have a home-bilt computer using an MSI 865PE Neo 2 motherboard.
> I've booted with xnoppix and it detects the sound card as
> intel8x0, so that's what I'm trying to get going using alsa.
>
> So lately I've been trying to use alsa and I'm stuck. I do not
> get any error
Patrick Boettcher wrote:
> I only applied the patch, loaded the module, pluged in the device
> ... result is attached.
> EIP is at __wake_up_common+0x13/0x50
> Call Trace:
> [] __wake_up+0x32/0x57
> [] pipe_readv+0x288/0x2d8
> [] pipe_read+0x37/0x3b
> [] vfs_read+0xd0/0x135
> [] sys_read+0x42
I wrote:
> I think I'll write a quirk for this ...
Please try the attached patch.
HTH
Clemens
diff -urN alsaold/alsa-kernel/usb/usbaudio.c alsa/alsa-kernel/usb/usbaudio.c
--- alsaold/alsa-kernel/usb/usbaudio.c Tue Mar 30 13:51:30 2004
+++ alsa/alsa-kernel/usb/usbaudio.c Tue Apr 6 13:20:36
Pavana Sharma wrote:
> ALSA lib pcm.c:1947:(snd_pcm_open_noupdate) Unknown PCM hw:0,0
Please show the output of "aplay -l" and "aplay -L".
Clemens
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by D
Patrick Boettcher wrote:
> On Mon, 5 Apr 2004, Clemens Ladisch wrote:
> > What sample rate/format uses 304000 bytes per second?
>
> I don't understand the question completely, what do you mean?
The descriptors say that the device can transfer up to 304000 bytes
per second in e
John H. wrote:
> the usb 2.0 hub was at fault,. thanks!
I have heard rumors that the latest 2.6.5 kernel is supposed to have
support for playing audio data through 2.0 hubs to 1.x devices.
HTH
Clemens
---
This SF.Net email is sponsored by:
Tom Browne wrote:
> Clemens Ladisch wrote:
> > Tom Browne wrote:
> >> Under certain conditions (yet to be established properly - it doesn't
> >> happen every single time) with this ICE1712 card (DSP24),
> >> snd_pcm_writei doesn't just block... it neve
Robert Rozman wrote:
> I've got advice how to use this 6 channel device as 3 stereo channels but
> there seems something not to be right (it could be my mistake).
>
> I have /etc/asound.conf :
>
> pcm.a {
> type plug
> slave.pcm ch12
> }
>
> pcm.b {
> type plug
> slave.pcm ch34
> }
>
> Now I do:
>
Pedro Lopez-Cabanillas wrote:
> This patch adds three new options to arecordmidi.
Committed, with some changes.
Thanks,
Clemens
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, Pres
John H. wrote:
> see, this is what is weird, it worked last week, now it doesn't
> work with exaudio or alsa! same errors!
Then it's not a problem of the sound driver.
> cannot submit datapipe for urb 0, err = -38
-38 means "not implemented". Probably some bug in the USB core in
your kernel.
H
Patrick Boettcher wrote:
> I'm using a usbsnoop program to do some basic sniffing. Logs are
> really big :/.
Try to play some 0.01-seconds wave file, and don't connect any other
USB devices.
> After plugging in, the device shows like this in /proc/bus/usb/devices:
>
> I: If#= 0 Alt= 0 #EPs= 0 Cl
Tom Browne wrote:
> Under certain conditions (yet to be established properly - it doesn't
> happen every single time) with this ICE1712 card (DSP24),
> snd_pcm_writei doesn't just block... it never comes back.
What is the state of the PCM device when this happens?
(see /proc/asound/cardX/pcm0p/*)
Ron Cococcia wrote:
> In a setup I'm working with, I have a motherboard (815 w/82801BA-ICH2) that
> has an onboard/primary (00) AC97 codec (AD1885). We've been playing around
> with adding a CNR card that would have a different/secondary (01) codec on
> it (CS4299). [...]
> The onboard chip is gen
John H. wrote:
> I get this error repeatedly
>
> ALSA /tmp/alsa-driver-1.0.4rc2/usb/usbaudio.c:811:
> cannot submit datapipe for urb 0, err = -38
>
> whenever i try to use /dev/dsp now, and i can only get sound from line in.
>
> i have kernel 2.6.4 and drivers 1.0.4rc2
What is in /proc/asound/card
I wrote:
> Now the modules load. However, loading snd-usb-audio doesn't do
> anything, and unloading and reloading it results in a crash or a hang.
Fixed. Apparently, snd-usb-audio has never been working on 2.2.x, and
nobody noticed ...
No remaining 2.2.x bugs AFAICS.
Clemens
Jaroslav Kysela wrote:
> On Wed, 31 Mar 2004, Clemens Ladisch wrote:
>
> > But now:
> >
> > # modprobe snd
> > modprobe: Too deep recursion in module dependencies!
> > modprobe: Circular dependency? snd-page-alloc snd
> >
> >
Jaroslav Kysela wrote:
> On Tue, 30 Mar 2004, Clemens Ladisch wrote:
> > On a 2.2.19 kernel:
> >
> > depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/snd-*
> > ...
>
> Missing inclusion of some header files?
Sorry, my error. Wrong kernel configuratio
Jaroslav Kysela wrote:
> 1.0.4rc1 packages are out. Please, report compilation problems.
On a 2.2.19 kernel:
depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/snd-*
depmod: synchronize_irq
depmod: tqueue_lock
depmod: waitqueue_lock
depmod: *** Unresolved symbols i
Pavana Sharma wrote:
> I am providing control interface for my driver to access from user space
> with functions get & put .
>
> * while creating new controls should I be allowed to create my hardware
> specific controls like gain, power, rate & other codec specific parameters.
All controls are h
Jaroslav Kysela wrote:
> On Tue, 23 Mar 2004, Clemens Ladisch wrote:
> > The following test program shows strange behaviour:
>
> Thanks. It's fixed in CVS now.
The second problem persists, i.e., snd_pcm_wait() returns although the
pcm isn't actually ready:
$ ./waitte
Jaroslav Kysela wrote:
> On Mon, 22 Mar 2004, James Courtier-Dutton wrote:
>
> > My current tests were not using the resampler. i.e. app using 48k, sound
> > card using 48k. I will try some tests that would use the resampler.
>
> Then I need more info how I can reproduce the bug.
The following te
James Courtier-Dutton wrote:
> I need more details on exactly what snd_pcm_wait() is supposed to do.
> The documentation on the www.alsa-project.org gives: -
> Wait for a PCM to become ready.
> ...
> So, when is a PCM ready?
When you can read/write some data without blocking, i.e.,
avail >= avail_
Hi all,
The latest version of the snd-usb-audio driver now supports USB 2.0
high speed devices. (The driver will be in the public SourceForge CVS
in a few hours.)
I couldn't test it much because I don't have a high speed device. If
you have an Audigy 2 NX, or an Edirol UA-1000, or some other hi
Hartmut Geissbauer wrote:
> I removed the quick hack from Mathieu and inserted snd_printk's in
> snd_usbmidi_disconnect.
>
> The new function:
> ...
> if (ep->out && ep->out->urb)
> usb_unlink_urb(ep->out->urb);
> snd_printk(KERN_INFO
Mathieu Geli wrote:
> Ok, I applied your second patch, and get this dmesg output:
>
> drivers/usb/core/usb.c: deregistering driver snd-usb-audio
> ALSA /home/mathieu/alsa-driver/usb/usbaudio.c:2944: snd_usb_audio_disconnect called,
> refcount = 1
> ALSA /home/mathieu/alsa-driver/usb/usbaudio.c:294
Lars Heineken wrote:
> Takashi Iwai wrote:
>
> | try strace with -r option and check which call takes too long time.
>
> When I use the application 'play' the delay is only around one second,
> the strace output is attached below.
It seems play is a shell script that calls sox to play the file.
Pl
Ove Kaaven wrote:
> - wavetable drops notes sometimes. (a good test example wanted.)
>
> I've encountered this randomly sometimes, but I think I also have an
> example of the opposite - a note that is never turned off - that
> manifests every single time for me. So I'm wondering if anyone else can
Mathieu Geli wrote:
> ok, what I did, is first to apply your patch to my source tree
> (1.0.3rc2), clean, compile, install, and even reboot. That doesn't
> output anymore the two lines "urb status -104", and
> "usb_submit_urb: -32" but still hang after printing:
> "drivers/usb/core/usb.c: deregiste
Mathieu Geli wrote:
> I'm trying to plug/unplug the midisport1x1 from M-Audio. The plug
> works like a charm, hotplug does its job, load the firmware
> (fxload) and snd-usb-audio, if not inserted, is auto-loaded. But
> just hang, trying to rmmoding snd-usb-audio or anything else usb
> related will
Clemens Ladisch wrote:
> Jaroslav Kysela wrote:
>
> > I don't know much about USB 2.0,
>
> Not too much differences for the driver.
Well, I should have read the specification before saying such things.
The format of synchronization information has changed, too; it
Karsten Wiese wrote:
> We can also vary the exact USB frame time.
> With UHCI 1.1 USB Hosts there is the SOF Register.
> ...
> It really works here already with the us428: The trick is:
> We first make the USB-Frame longer until we capture 1 Sample Frame more 45
> (for 44100). then the USB-Frame i
Takashi Iwai wrote:
> Clemens Ladisch wrote:
> >
> > > I don't know much about USB 2.0,
> >
> > Not too much differences for the driver. The main difference is that
> > there are now 8000 microframes per second. I have written a patch
> > (see b
Willie Sippel wrote:
> > But I'm not sure about, wether the NDA agrees in the basic alsa
> > principles. What are the developers of alsa are thinking about that
> > agreement?
AFAIK drivers for ATI hardware are developed in a similar way (ATI
gives specs under an NDA, the resulting driver is open
Jaroslav Kysela wrote:
> On Wed, 10 Mar 2004, Clemens Ladisch wrote:
>
> > Conceptually, USB devices have variable-sized periods. The question
> > is whether we actually want to allow this in the API. Probably not.
>
> What this does mean? I though that the period siz
Jaroslav Kysela wrote:
> On Tue, 9 Mar 2004, Takashi Iwai wrote:
>
> > BTW, the USB audio is another headache. the current ALSA PCM model isn't
> > perfectly suitable for the devices like USB audio.
>
> Unfortunately I don't see a better model.
Conceptually, USB devices have variable-sized period
Bauke Jan Douma wrote:
> I have two soundcards in my system, a cmipci(card) and
> an intel8x0 (on board).
>
> I have the audio cable of my CD/ROM drive wired onto the
> cmipci. Attached to line-out of the cmipci is just my
> headphones.
>
> I also have a TV-card.
> An audio cable runs from the TV-
Jack O'Quin wrote:
> Samuel S Chessman <[EMAIL PROTECTED]> writes:
>
> > This is caused by snd_pcm_hw_params_set_rate_near parameter val needing
> > to be a pointer, and alsa_driver passing in the frame rate instead.
> >
> > This occurs against current CVS of alsa. (2004-03-02)
>
> I think this is
[EMAIL PROTECTED] wrote:
> I wanted to get the tempo, so I did this:
>
> snd_seq_queue_tempo_t *qt;
> snd_seq_queue_tempo_alloca(&qt);
> snd_seq_get_queue_tempo(seq,id,qt);
> return qt->tempo;//line 91
>
> and the compiler told me this:
>
> alsa.cpp:91: invalid use of undefined type
@@ -0,0 +1,195 @@
+/*
+ * mpu401_acpi.c - driver for motherboard MPU-401 ports identified by ACPI PnP
+ * Copyright (c) 2004 Clemens Ladisch <[EMAIL PROTECTED]>
+ *
+ * based on 8250_acpi.c
+ * Copyright (c) 2002-2003 Matthew Wilcox for Hewlett-Packard
+ * Copyright (C) 2004 Hewlett-Packard Co
+ *
2.4.23 and .25 need new patches
diff -urN alsa-driver/utils/patches/rtc-2.4.23.patch
alsa-driver/utils/patches/rtc-2.4.23.patch
--- alsa-driver/utils/patches/rtc-2.4.23.patch 1970-01-01 01:00:00.0 +0100
+++ alsa-driver/utils/patches/rtc-2.4.23.patch 2004-03-02 15:50:48.901317000 +0100
Abramo Bagnara wrote:
> Jaroslav Kysela ha scritto:
> > Log Message:
> > Fixed return comment for *near() functions
> >
> > + * \return 0 otherwise a negative error code if configuration space would become
> > empty
>
> *near() functions semantic cannot return error by design.
>
> Taken for grante
- fix non-working control port on Roland U-8
- more port names
- new MIDI quirks for Roland MMP-2, V-SYNTH, VariOS, FP-*, GI-20,
BOSS GS-10, Edirol UR-80, PCR-A, PCR-1
Index: alsa-kernel/usb/usbmidi.c
===
RCS file: /cvsroot/alsa/a
fix alsa-lib doxygen errors
Index: alsa-lib/doc/doxygen.cfg
===
RCS file: /cvsroot/alsa/alsa-lib/doc/doxygen.cfg,v
retrieving revision 1.25
diff -u -r1.25 doxygen.cfg
--- alsa-lib/doc/doxygen.cfg8 Jan 2004 14:05:55 - 1
[EMAIL PROTECTED] wrote:
> I'm trying to set my ppq on my queue, so I do this:
>
> snd_seq_queue_tempo_t *qt;
> snd_seq_queue_tempo_alloca(&qt);
> snd_seq_queue_tempo_set_ppq(qt, ppq);
> return snd_seq_set_queue_tempo(seq, id, qt);
> that returns -22, what does that mean?
snd_stre
Manuel Jander wrote:
> AFAIK, it seems that when using a scatter gather buffer, not every
> period is located inside of a page. ...
> The problem is that a DMA transfer can not go accross 2 different pages.
> On Aureal hardware, even on contiguous buffers this causes all sort of
> odd problems. Eac
Jiang Jiang (HangZhou) wrote:
> I find that I can use alsamixer to adjust the volumn of line
> input. But how can I set the volumn of line input by program?
See the source of the amixer utility.
> And how to capture data from line input?
See the source of the arecord utility.
> What's more, whe
Mathieu Rondonneau wrote:
> Selon Clemens Ladisch <[EMAIL PROTECTED]>:
>
> > Mathieu Rondonneau wrote:
> > > I don't understand why count is 1024 ?
> > > why count is not equal to runtime->period_size (i.e. 16*1024)?
> >
> > If your fram
Hartmut Geissbauer wrote:
> That _has_ helped. Now the device is fully functional.
- search class-specific endpoint descriptor after the sync ep, too
Index: alsa-kernel/usb/usbaudio.c
===
RCS file: /cvsroot/alsa/alsa-kernel/usb/us
Mathieu Rondonneau wrote:
> I don't understand why count is 1024 ?
> why count is not equal to runtime->period_size (i.e. 16*1024)?
If your frame size is 4, this is the size of a memory page. I guess
ALSA wants to copy the data one page at a time, and this is required
if the buffer isn't contiguo
Hartmut Geissbauer wrote:
> Clemens Ladisch wrote:
> > Hartmut Geissbauer wrote:
> > > > > The only thing that's missing now are the two playback ports.
> > > >
> > > > Please show the output of "lsusb -v".
> >
> > The d
Will wrote:
> Clemens Ladisch <[EMAIL PROTECTED]> wrote:
> >
> >If you get correct output when you run "amidi -p virtual -d" and
> >aconnect your keyboard to that port, then it may be a bug in
> >arecordmidi. I'll test when I'm at home
Mathieu Rondonneau wrote:
> .period_bytes_min = 1092,
> .period_bytes_max = 32768,
> .periods_min = 8,
> .periods_max = 512,
>
> When i start to send a file, I Don't know why:
> runtime->period_size = 8192
> runtime->periods: 8
> and the ¨count¨ parameter in the co
snookertb wrote:
> SND_CTL_READONLY does not appear to be declared anywhere.
It's defined in alsa-lib/include/control.h. You have to install the
alsa-lib package before compiling alsa-utils and alsa-tools.
> Are you part of the alsa development team?
SourceForge says no, the bugtracker says yes
Will wrote:
> Clemens Ladisch <[EMAIL PROTECTED]> wrote:
> >> I'm getting empty MIDI files containing only the MIDI header.
> >
> >Are you using the latest CVS version of ALSA?
> >Some of the bugfixes I sent yesterday are needed by arecordmidi.
>
1 - 100 of 458 matches
Mail list logo
