On Tuesday 01 June 2004 10:40, Takashi Iwai wrote:
Pedro Lopez-Cabanillas wrote:
Anybody using the same hardware should avoid the 1.0.5 driver, IMO.
Relevant sources are ac97_codec.c and ac97_patch.c. The problem was
related to a mutex deadlock.
yep, sorry, my bad.
the bug hits AC97
On Monday 31 May 2004 03:07, I wrote:
My Gigabyte motherboard's integrated sound interface used to work with this
driver, but it doesn't with 1.0.5
Any program (amixer info, alsactl restore, alsamixer ...) trying to use the
control interface hardly hangs, and it is impossible to kill it at
Hi,
This patch adds three new options to arecordmidi.
-d,--dump
Shows the received events as text on standard output.
-m,--metronome=client:port
Plays a metronome signal on the specified sequencer port.
Metronome sounds are played on
Ryan Pavlik wrote:
Hrm, I've recently updated ALSA after a few weeks of inactivity, and
suddenly I'm not getting MIDI events from simple code that previously
worked. I don't see any alsa-devel messages about changes, but I
apparently missed the PCM API change notice. In addition to the more
Chris Cannam wrote:
While trying to track down the source of some poor timing in
sequencing, I've noticed that my ALSA sequencer queue timer has a
tendency to fall suddenly behind.
I have a little test program (available on request) that just starts a
queue and every second or so compares
El Martes, 28 de Octubre de 2003 17:30, Ryan Pavlik escribió:
Clemens Ladisch [EMAIL PROTECTED] wrote:
The event timestamps are set yo the current time of the queue. Your
queue isn't running, so its current time is zero.
Call snd_seq_start_queue(seq, queue, NULL) (and
El Lunes, 1 de Septiembre de 2003 15:25, Takashi Iwai escribió:
Martin Langer wrote:
But it fails in case of one device if you do a re-plugin! The first
plugin loads the firmware fine. Then you unplug your device and the
module still remains in a status of sleep. If you plug in your device
El Viernes, 29 de Agosto de 2003 20:12, Karsten Wiese escribió:
Just received an email from Takashi. He asks why not do it like he
did it before for the vx interfaces.
Another idea, after a closer look on the vxloader utility... Why not to forget
hotplug for rbtload? using modutils instead,
On Friday 04 April 2003 06:21, Ivica Bukvic wrote:
Yet, I still cannot get the second port of the Midisport 2x2 to become
available no matter what. /proc/asound/cards lists only one midisport
2x2 device (which is ok, I guess, since even Fernando's webpage mentions
that this is the case with
On Tuesday 11 March 2003 18:36, Clemens Ladisch wrote:
Jordi Mallach wrote:
any comment on the last stacatto bug I reported after the big
report?
I couldn't reproduce it on my machine (current CVS instead of 0.9.0beta8,
2.4.18 instead of 2.4.2, Roland Sound Canvas connected with USB
On Thursday 20 February 2003 15:14, Jaroslav Kysela wrote:
On Thu, 20 Feb 2003, Takashi Iwai wrote:
At Thu, 20 Feb 2003 09:55:18 +0100 (CET),
Jaroslav wrote:
On Thu, 20 Feb 2003, Pedro Lopez-Cabanillas wrote:
On Wednesday 19 February 2003 14:51, Takashi Iwai wrote
On Wednesday 19 February 2003 14:51, Takashi Iwai wrote:
there is the name field for each rawmidi substream, and the sequencer
looks up this string.
this reminds me the former patch by Clemens, and i've forgotten to
check this issue until now. sorry.
i modified the sequencer part (and
On Sunday 16 February 2003 19:53, Mark Knecht wrote:
2) In the screen shot with_2x2.png I've plugged in the MidiSport 2x2.
New devices show up in kaconnect. However, instead of showing 2 read
ports and 2 write ports, I am getting 4 read ports and no write ports.
Please explain why the
was introduced at 2003-01-10
So, you should use current CVS driver, or wait for a PlanetCCRMA update, or
use Midiman's firmware. For other USB MIDI fully compliant devices, like
Evolution's keyboards, a fixed driver is needed.
Regards,
Pedro
On Sun, 2003-02-16 at 11:43, Pedro Lopez
On Monday 17 February 2003 00:03, Mark Knecht wrote:
Pedro,
Is there any online information about how to use Midiman's firmware?
Thanks,
Mark
Yes. Clemens wrote an easy to use utility to extract and install Midiman's
firmware, see:
Hi,
Attached is a patch to solve a little mistake with output endpoints detection
for standard USB MIDI devices. Midisport devices are affected only if using
Lars Doelle firmware.
Typical syslog output was like this:
kernel: snd-usb-midi: MIDIStreaming version 01.00
kernel: snd-usb-midi: EP
On Thursday 16 January 2003 21:08, Brian Victor wrote:
I've removed all attachments to wxWindows, so anyone should be able to
compile my test program. So I don't have to keep sending snippits out
of context, the code is here:
http://www.personal.psu.edu/users/b/h/bhv1/nowx.cc or
On Friday 20 December 2002 21:09, Clemens Ladisch wrote:
Takashi Iwai wrote:
Mark Knecht wrote:
I was wondering what would happen in this process if someone had two r
three identical USB devices, like the MidiMan 2X2? OR also two
identical cards like the RME HDSP 9652?
when a
Hi,
The following lines are from my syslog after modprobe snd-ens1371 with
current CVS alsa drivers:
PCI: Found IRQ 9 for device 00:11.0
ALSA ../alsa-kernel/core/control.c:227: BUG? (!(kcontrol-access (11)) ||
kcontrol-put != ((void *)0)) (called from ca8f67a6)
Mixer works, though. (With too
On Thursday 14 November 2002 10:09, Jaroslav Kysela wrote:
Have you tried to create the virtual MIDI device (snd-virmidi.o) ? You can
connect any sequencer port to a rawmidi device (and first two rawmidi
devices are mapped to the OSS space as well). Note that virmidi module can
occupy up to 8
On Wednesday 13 November 2002 09:50, Clemens Ladisch wrote:
Pedro Lopez-Cabanillas wrote:
IMHO, mapping the card MIDI ports to subdevices may be OK, but only for
ALSA native rawmidi. After all, you can access some MIDI port with
hw:x,y,z instead of hw:x,y, but for OSS emulation a better
Hi,
Please, find attached a trivial patch for usbaudio.c (2.5.45) that fixes a
compilation problem triggered by CONFIG_SND_DEBUG_DETECT
Regards,
Pedro
--
ALSA Library Bindings for Pascal
http://alsapas.alturl.com
--- usbaudio.c.orig Fri Nov 1 02:09:38 2002
+++ usbaudio.c Thu Oct 31 22:10:30
El Jue 15 Ago 2002 10:56, Patrick Shirkey escribió:
Currently I am trying to maintain as few pages as possible so the
generic instructions access exactly the same data as ezusb devices.
However I have made the ezusb instructions more recognisable.
If this is still too confusing then I will
El Mar 13 Ago 2002 17:01, Patrick Shirkey escribió:
Clemens Ladisch wrote:
I didn't bother to report USB MIDI devices - until now:
Thanks. I'm collecting them for now until I or Dan get the energy to add
them to the matrix.
The usb generic instructions for USB-MIDI devices is a copy of the
El Sáb 03 Ago 2002 02:21, Martin Langer escribió:
Do we need an usb-midi device matrix? Up to now we have not much devices,
but the list is growing and alsa midi documents are rare. Perhaps we should
change this situation and start with a small midi-matrix or a general
usb-matrix.
In fact,
El Vie 02 Ago 2002 15:35, Michal Seta escribió:
On Fri, 02 Aug 2002 13:06:32 +0200
Clemens Ladisch [EMAIL PROTECTED] wrote:
I tested the snd-usb-midi driver with the ALSA rawmidi test programs
(rawmidi and midiloop in alsa-lib/test), and it worked.
It didn't work for me.
when called
El Vie 02 Ago 2002 21:03, Patrick Shirkey escribió:
Hey.
I am just about ready to release the new alsa docs to the general public .
Can you guys tell me what the differences are in installing the card
compared to the standard template. thx.
http://www.alsa-project.org/alsa-doc/
(just
El Mar 30 Jul 2002 15:09, Clemens Ladisch escribió:
- if (port 0)
+ if (port 0) {
+ snd_printk(KERN_ERR cannot create port (error code %d)\n,
err);
return port;
I think that you mean:
El Mar 30 Jul 2002 20:18, Martin Langer escribió:
The only strange thing I found are the unknown parts of the lsusb output
(broken descriptor?) and the impossible module reload = segfault.
These 'unknown descriptor' lines at lsusb output are jack descriptors and MS
endpoint descriptors, as
Hello!
I'm happy to see that I'm not the only MIDI guy at ALSA-USB world :)
El Dom 28 Jul 2002 23:39, Martin Langer escribió:
my new USB-MIDI-Keyboard has two USB subclasses usb-midi and usb-audio.
Evolution, the manufacturer, told me it's an Audio Class compliant
device, but I don't find a
In alsa-lib/src/rawmidi/rawmidi.c there are two functions :
snd_rawmidi_params, and snd_rawmidi_params_current. Both documented with
very similar brief descriptions: get parameters about rawmidi stream and
get current parameters about rawmidi stream.
I suppose that the first function
Hi,
I was trying to test rawmidi on snd-usb-midi with latest patches, with no
success :(
Then, as I have an sb 128 (snd-ens1371) I tryed the alsa-lib/test/rawmidi
program with only that card module loaded.
$ ./rawmidi -i hw:0,0
Read midi in
Press ctrl-c to stop
(With a MIDI keyboard
El Vie 05 Jul 2002 18:37, Takashi Iwai escribió:
I was trying to test rawmidi on snd-usb-midi with latest patches, with no
success :(
Then, as I have an sb 128 (snd-ens1371) I tryed the alsa-lib/test/rawmidi
program with only that card module loaded.
there might be still bugs on
- usb compatibility hack was moved to wrapper.h, so that it can be
shared with usbuadio.c
- newly added virmidi registrations.
that means, snd-usb-midi will have its own rawmidi devices
automatically as /dev/snd/midiCxDx.
this will be good for applications which speak only with
Me wrote:
I can't compile current CVS usb drivers:
Sorry, It had been fixed 4 hours ago.
I have compiled it succesfully now. And also works! (only preliminary tests).
$ cat /proc/asound/seq/clients
Client info
cur clients : 5
peak clients : 6
max clients : 192
Client 0 : System
35 matches
Mail list logo
