Manuel Jander wrote:
Hi,
Since there is almost nothing else to do to support the Aureal Vortex
3D processor on Linux, just as i announced some time ago i started
designing a OpenAL interface for ALSA. The design is meant to be
applicable to other hardware too.
I made a preliminary description, f
>Since there is almost nothing else to do to support the Aureal Vortex
>3D processor on Linux, just as i announced some time ago i started
>designing a OpenAL interface for ALSA. The design is meant to be
>applicable to other hardware too.
<
>I made a preliminary description, from what i have done
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 compar
On Mon, 15 Dec 2003 02:03:53 +0100
Pedro Lopez-Cabanillas <[EMAIL PROTECTED]> wrote:
> > The problem isn't getting 0's for time (got that one sorted awhile
> > back, but never integrated the fix)---the problem is I'm not
> > getting anything.
> >
> > Anyhow, just wondering what's new or different,
Hi,
Since there is almost nothing else to do to support the Aureal Vortex
3D processor on Linux, just as i announced some time ago i started
designing a OpenAL interface for ALSA. The design is meant to be
applicable to other hardware too.
I made a preliminary description, from what i have done
On Sun, 2003-12-14 at 06:48, Chris Cannam wrote:
> On Sunday 14 Dec 2003 2:34 pm, Chris Cannam wrote:
> > On Sunday 14 Dec 2003 2:02 pm, Jan Depner wrote:
> > > If I'm not mistaken the timing for your audio is coming from your
> > > sound card not your system clock.
> >
> > [...]
> > I mentally rul
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 mo
Kristof vansant <[EMAIL PROTECTED]> writes:
> alsa won't compile on kernel 2.6
> removing sndversions.h in vxp440.c and vxpocket.c does the trick.
>
> /home/lupus/alsa-driver-1.0.0rc2/pcmcia/vx/vxp440.c:6:31:
> linux/modversions.h: Onbekend bestand of map
> /home/lupus/alsa-driver-1.0.0rc2/pcmci
alsa won't compile on kernel 2.6
removing sndversions.h in vxp440.c and vxpocket.c does the trick.
/home/lupus/alsa-driver-1.0.0rc2/pcmcia/vx/vxp440.c:6:31:
linux/modversions.h: Onbekend bestand of map
/home/lupus/alsa-driver-1.0.0rc2/pcmcia/vx/vxp440.c:7:25: sndversions.h:
Onbekend bestand of m
On Sunday 14 Dec 2003 2:34 pm, Chris Cannam wrote:
> On Sunday 14 Dec 2003 2:02 pm, Jan Depner wrote:
> > If I'm not mistaken the timing for your audio is coming from your
> > sound card not your system clock.
>
> [...] what if you have more
> than one soundcard or no soundcard at all
And of cours
Hi,
While writing a advanced capabilities (positional audio) interface for
ALSA, i encountered this same problem.
So far i have "architected" the thing like this:
- The ALSA driver loads as usual.
- When OpenAL or whatever fires up, it queries the device for
capabilties, using a well defined con
On Mon, 15 Dec 2003 01:17:26 +0900, Patrick Shirkey
<[EMAIL PROTECTED]> wrote:
If we have a DB of info how would we define the abilities of each device?
I assume this info is available in the driver layer because there is a
point where ALSA will return false eg. if a card is not able to run at
>My opinion is that a simple function could be included in alsactl which
>scans for available devices, makes a list of their abilities. Everyone
>uses "post-insert alsactl restore" in the modules.conf file so it would
>be essentially a non issue from a user perspective.
i think it needs to be s
Hi
I know it's no big news for a USB Midi device to be working but I
thought I may as well announce this anyway.
The Edirol PCR-30 Midi Keyboard Controller (with sliders, knobs, buttons
e.t.c..) works perfectly the USB audio module (snd-usb-audio).
This most likely means the PCR-50 and PCR-80
If we have a DB of info how would we define the abilities of each device?
I assume this info is available in the driver layer because there is a
point where ALSA will return false eg. if a card is not able to run at
48000Hz
My opinion is that a simple function could be included in alsactl which
Patrick Shirkey wrote:
I'm looking but I can't find a way to get the list of all available
devices including virtual devices defined in the .asoundrc
Is there any function that provides this?
If not has there been any thought put into how it can be accomplished?
Sorry missed the thread on "quer
I'm looking but I can't find a way to get the list of all available
devices including virtual devices defined in the .asoundrc
Is there any function that provides this?
If not has there been any thought put into how it can be accomplished?
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boo
Multiple soundcards usually have to use word clock or some proprietary
method of syncing the cards. Usually one card will be the master and
the others slaves. I know you can put up to 4 ST Audio DSP24 cards in
one system and set one up as master. I believe the same is true for the
M-Audio Delta
On Sunday 14 Dec 2003 2:34 pm, Chris Cannam wrote:
> On Sunday 14 Dec 2003 2:02 pm, Jan Depner wrote:
> > If I'm not mistaken the timing for your audio is coming from your
> > sound card not your system clock.
>
> [...]
> I mentally ruled out a hardware problem quite early on because I
> wasn't see
On Sunday 14 Dec 2003 2:02 pm, Jan Depner wrote:
> If I'm not mistaken the timing for your audio is coming from your
> sound card not your system clock.
Is that so? Obvious though it is, that simply hadn't occurred to me.
I mentally ruled out a hardware problem quite early on because I
wasn't s
Jan Depner <[EMAIL PROTECTED]> writes:
> On Sun, 2003-12-14 at 08:07, 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 prog
If I'm not mistaken the timing for your audio is coming from your sound
card not your system clock. The gettimeofday is from the system clock.
They probably won't match. Of course, I could be totally in the dark
;-)
Jan
On Sun, 2003-12-14 at 08:07, Chris Cannam wrote:
>
> While trying to tra
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 the queue timer against
Hallo,
Noel Bush hat gesagt: // Noel Bush wrote:
> I am using the planetccrma-core distribution. Recently I tried
> upgrading, via that distro, to the alsa 1.0.0 packages. I found that
> after this upgrade, I was unable to hear any sound when using any app
> (simplest test, using aplay on a wav
You should buy the O'Reilly book "Linux Device Drivers". It's
excellent.
Jan
On Sun, 2003-12-14 at 04:08, Patrick Shirkey wrote:
> Coen Leermakers wrote:
> > Hi all,
> >
> > Does anyone here know where to find some good manuals and howto's on
> > driver programming? I myself have some programm
On Sun, Dec 14, 2003 at 06:32:58PM +0900, Patrick Shirkey wrote:
> Could someone send me a list of all the usbmidi devices that require
> firmware to be inserted. I am redesigning the docs for these cards.
>
snd-usb-audio with MidiSport firmware loader:
MidiSport 1x1, 2x2, 4x4, 8x8, KeyStation,
Coen Leermakers wrote:
Hi all,
Does anyone here know where to find some good manuals and howto's on
driver programming? I myself have some programming experience, and want
to take this some further. Since I have a sound card which is not (yet)
compatible with ALSA, I decided the ALSA-Dev mailing l
On Sun, 14 Dec 2003, Frank Barknecht wrote:
> Hallo,
> Amaury Jacquot hat gesagt: // Amaury Jacquot wrote:
>
> > I am using a Creative Labs MP3+ usb sound device.
> > mobo is VIA EPIA 800, USB is UHCI
> > Alsa is 1.0rc2
> >
> > The things works great, it's not even muted on startup (huh ?)
>
>
On Sat, 13 Dec 2003, Dirk Vornheder wrote:
> Hi !
>
> Is the creative soundcard Audigy LS supported by the alsa driver ?
No. This chip is different from emu10k1 (Live) and emu10k2 (Audigy) and we
have no information about it. Ask Creative for help (documentation).
Could someone send me a list of all the usbmidi devices that require
firmware to be inserted. I am redesigning the docs for these cards.
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
30 matches
Mail list logo
