Chris Cannam wrote:
Is there any documentation for the squillions of interesting-looking
event types defined in snd_seq_event_type?
The source.
I'm particularly intrigued by the SND_SEQ_EVENT_INSTR_* types which
look suspiciously like they might be intended for something useful
such as
Hi,
This patch defaults initial center/lfe jack to analog mode (now it is
initialized to digital mode). This solves problem with noise from
center on SB Live 5.1.
Peter Zubaj
http://www.logofun.pobox.sk - urobte radost svojmu telefonu
C:\\live_ad.diff
Juhana Sadeharju wrote:
From: Eckhard Jokisch [EMAIL PROTECTED]
Now we should look at why LiveDrive midi-in does not work.
As far as I remeber it worked half a year ago.. no?
Another person with LiveDrive said it does work, but
it does not work for me.
ALSA's emu10k1 entry says MIDI on
Hello all,
I am trying to understand the specifics of the mechanism
that JACK uses to perform audio duplexing
(simultaneous playback and capture of audio). I have downloaded the latest source from
CVS. Is the file alsa_driver.c a good place to start (i.e. is this
where the magic
On Tue, 9 Dec 2003, Maarten de Boer wrote:
Thanks!
Out of curiosity: how did you manage to keep binary compatibility?
Versioned symbols in the library. They are used for a long of time in
alsa-lib, so we can redefine functions in new libraries like libc-2.x.x
does, but symbols with old
On Wed, 10 Dec 2003, Patrick Shirkey wrote:
I'm using older alsa drivers so maybe this is fixed already.
Advanced Linux Sound Architecture Driver Version 0.9.3c.
Compiled on May 25 2003 for kernel 2.4.19 with versioned symbols.
I can sucessfully run two instances of arecord with the
Hello folks,
I'm starting work on a new midi sequencing app, but I'm a bit confused by
the different API options ALSA offers. I've been reading whatever snippets
I can find on the web, mostly mailing list archives, and if I understand
correctly my options are basically the rawmidi API and the
Jaroslav Kysela wrote:
'periods 0' and 'period_time 0' is missing here. You need to overwrite the
default values.
Thanks that works. I will update the .asoundrc page for the online docs.
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux
What is the use, in a programmer view, of alsa sequencer port type flags? How
this transcends to the 'user experience'?
(Context: Keep doing with the sequencer chapter of the Alsa user conceptual
model, an spanish documentation to be translated soon, at:
Clemens Ladisch wrote:
Denis de Leeuw Duarte wrote:
I'm starting work on a new midi sequencing app, but I'm a bit confused by
the different API options ALSA offers. I've been reading whatever snippets
I can find on the web, mostly mailing list archives, and if I understand
correctly my
On 08-Dec-2003 Arve Knudsen wrote:
Wether its done via the control or pcm interface, it'd be good to have a
loose coupling between configuration and streams, so one could could access
configuration space without locking a stream don't you think?
Yes, of course. Perhaps it can be done already
Tim Goetze wrote:
i found the sequencer API to be well-documented.
Internally right?
it's somewhat lacking
in code examples, but there are quite a few applications out there
that use it (pmidi for a start maybe, and then we have rosegarden,
muse etc).
I just spotted this older doc
David Garcia Garzon wrote:
(Context: Keep doing with the sequencer chapter of the Alsa user conceptual
model, an spanish documentation to be translated soon, at:
http://www.salleurl.edu/~is04069/Modders/Docs/alsadoc-sequencer.html)
Nice work. I have added a link to the docs page. Let us know if
Hi, Ryan
If you're interested in the mechanics of full duplex memory-mapped i/o
with ALSA-lib you could always check out PortAudio v19 CVS at
www.portaudio.com, which implements both a blocking and callback interface.
If you're interested specifically in JACK interfacing with ALSA-lib I
would
A Dimecres 10 Desembre 2003 12:44, Patrick Shirkey va escriure:
David Garcia Garzon wrote:
(Context: Keep doing with the sequencer chapter of the Alsa user
conceptual model, an spanish documentation to be translated soon, at:
On Wednesday 10 Dec 2003 12:35 pm, David Garcia Garzon wrote:
[...]
Each port has also the type bitmasks defined as follows:
SND_SEQ_PORT_TYPE_SPECIFIC Hardware specific port
SND_SEQ_PORT_TYPE_MIDI_GENERIC Generic MIDI device
SND_SEQ_PORT_TYPE_MIDI_GM General MIDI compatible device
[etc]
I
On Wednesday 10 Dec 2003 7:38 am, Clemens Ladisch wrote:
Chris Cannam wrote:
Is there any documentation for the squillions of
interesting-looking event types defined in snd_seq_event_type?
The source.
Ah.
I'm particularly intrigued by the SND_SEQ_EVENT_INSTR_* types
which look
Tim Goetze wrote:
* what kind(s) of sync-to-external will you need?
* do you want to receive/send MIDI sysex data?
last time i checked, the latter was impossible to do via the sequencer
API (please correct if things have changed).
Sending/receiving sysex has always been possible AFAIK. It's
Chris Cannam wrote:
On Wednesday 10 Dec 2003 7:38 am, Clemens Ladisch wrote:
Chris Cannam wrote:
I'm particularly intrigued by the SND_SEQ_EVENT_INSTR_* types
which look suspiciously like they might be intended for something
useful such as enabling soft-synths or samplers to report on
Tim Goetze wrote:
* what kind(s) of sync-to-external will you need?
* do you want to receive/send MIDI sysex data?
last time i checked, the latter was impossible to do via the sequencer
API (please correct if things have changed).
Sending/receiving sysex has always been possible AFAIK. It's
Maarten de Boer wrote:
Out of curiosity: how did you manage to keep binary compatibility?
With assembler magic (see alsa-symbols.h and pcm.h).
Regards,
Clemens
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does
On Wed, 10 Dec 2003 13:50:21 +0100
Midall [EMAIL PROTECTED] wrote:
Hi at all, i have abit nf7-s with nforce soundstorm mcp-t
I use the latest alsa lib, dev, tool (1rc2) all are ok but when i play
a dvd the channels are inverted and result effect is like ping-pong
channel to channel..
I have
alsa cvs 9th Dec 2003 (late at night):
hdsploader told me it could not find
/usr/local/share/alsa/firmware/
hdsploader/multiface_firmware_rev11.bin
I guess it didn't go to place with make install
for some reason.
# make install
make[1]: Entering directory
Sorry, my email was left out..
--
[EMAIL PROTECTED]
---
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 THE LOVE, and help us help
YOU!
On Wednesday 10 December 2003 20:06, Thomas Charbonnel wrote:
The firmware files are no more shipped with alsa-tools, but in the
alsa-firmware package. Did you install this one ?
Thomas
aha, ok, stupid me.. thanks :-)
---
This SF.net
Clemens Ladisch wrote:
Tim Goetze wrote:
* what kind(s) of sync-to-external will you need?
* do you want to receive/send MIDI sysex data?
last time i checked, the latter was impossible to do via the sequencer
API (please correct if things have changed).
Sending/receiving sysex has always
Hello all,
I wanted to check my knowledge of something: does an xrun necessarily
correspond to a drop-out in the audio stream? In other words, could
you have a drop-out WITHOUT an xrun, or an xrun WITHOUT a drop-out? Is
there a strict one-to-one correspondence between the two?
Any assistance,
Got a strange problem. My oss emulation drivers get auto loaded but not
my alsa driver. oss emulation depends on this driver.
I have to manual modprobe it to make my sound work.
And my volume control is broken but it seems this is because of ac97 if
I have read your mailing list correctly. When
I wanted to check my knowledge of something: does an xrun necessarily
correspond to a drop-out in the audio stream? In other words, could
you have a drop-out WITHOUT an xrun, or an xrun WITHOUT a drop-out? Is
there a strict one-to-one correspondence between the two?
a dropout occurs when the
29 matches
Mail list logo