[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
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
Hi,
I have two soundcards in my system, a cmipci(card) and
an intel8x0 (on board).
cmicpi is /dev/dsp0, intel8x0 is /dev/dsp1.
In .asoundrc I have:
pcm.cmipci { type hw ; card 0 ; device 0 }
ctl.cmipci { type hw ; card 0 ; device 0 }
pcm.intel8x0 { type hw ; card 1 ; device 0 }
ctl.intel8x0 {
Hi,
I have two soundcards in my system, a cmipci(card) and
an intel8x0 (on board).
cmicpi is /dev/dsp0, intel8x0 is /dev/dsp1.
In .asoundrc I have:
pcm.cmipci { type hw ; card 0 ; device 0 }
ctl.cmipci { type hw ; card 0 ; device 0 }
pcm.intel8x0 { type hw ; card 1 ; device 0 }
ctl.intel8x0 {
[Sorry about those earlier mails; something went wrong with
permissions on my mail-editor; the editor failed, but mail
was still sent out to some bogus (and some not so bogus)
addresses]
Hi,
I have two soundcards in my system, a cmipci(card) and
an intel8x0 (on board).
cmicpi is /dev/dsp0, inte
Takashi Iwai <[EMAIL PROTECTED]> wrote:
>William wrote:
>> This is very important information. How about explaining this on the
>> alsa-project.org website where the current sentence reads "simply copy ..." ?
>
>maybe. the statement is a bit old.
And a bit confusing too...
>> I probably want th
Hi,
it seems that some mobo with ALC650 uses GPIO 0 as the mic bias +5V.
in ac97_patch.c, the GPIO 0 is turned on/off in conjunction with
the mic/center sharing switch, but this handling appears only for the
old ALC650 revision (D or older).
interestingly, there is a report that even a mobo with
James Courtier-Dutton <[EMAIL PROTECTED]> wrote:
>
>The point of option 1 is to explain how to upgrade alsa if you need to.
>Not everyone needs to upgrade.
My point was that the explanation given in option is actually confusing.
I guess it's the wiki problem of many different people collaborative
Takashi Iwai wrote:
Hi,
it seems that some mobo with ALC650 uses GPIO 0 as the mic bias +5V.
in ac97_patch.c, the GPIO 0 is turned on/off in conjunction with
the mic/center sharing switch, but this handling appears only for the
old ALC650 revision (D or older).
interestingly, there is a report th
Hi,
My fault.
This is what is in datasheets:
>There are two option circuits for MIC to disable bias voltage. For
>ALC650 ver.E or later, there is Vrefout-disabled function, so
>bias voltage from Vrefout(pin28) is recommended as option2 circuit.
>When MIC is shared with Center/LFE, software sho
Hi,
My fault.
This is what is in datasheets:
>There are two option circuits for MIC to disable bias voltage. For
>ALC650 ver.E or later, there is Vrefout-disabled function, so
>bias voltage from Vrefout(pin28) is recommended as option2 circuit.
>When MIC is shared with Center/LFE, software sho
Hi,
My fault.
This is what is in datasheets:
>There are two option circuits for MIC to disable bias voltage. For
>ALC650 ver.E or later, there is Vrefout-disabled function, so
>bias voltage from Vrefout(pin28) is recommended as option2 circuit.
>When MIC is shared with Center/LFE, software sho
hi,
Can someone please explain me what is the difference between
runtime->dma_addr and runtime->dma_area
where runtime = substream->runtime
I am getting a very strange problem where I am getting a rumtime->dma_addr
value as 0 while runtime->dma_area is a proper value.
Any hints will be
On Wed, 3 Mar 2004, Gupta, Kshitij wrote:
> hi,
> Can someone please explain me what is the difference between
> runtime->dma_addr and runtime->dma_area
>
> where runtime = substream->runtime
>
> I am getting a very strange problem where I am getting a rumtime->dma_addr
> value as 0 while
I have the AD1888 on the P4P800S working to some degree. I have the alsa drivers and
it reads the card as: SIS SI7012 and Chip as obviously AD1888. All sound seems to
come out the headphone port no problem, however the optical out is a bit more flaky.
I seem to have mplayer working via optic
At Wed, 3 Mar 2004 18:13:17 +0100,
p z wrote:
>
> Hi,
>
> My fault.
>
> This is what is in datasheets:
>
> >There are two option circuits for MIC to disable bias voltage. For
> >ALC650 ver.E or later, there is Vrefout-disabled function, so
> >bias voltage from Vrefout(pin28) is recommende
Hi
I have been having som problems with mixer settings on my Sound Blaster
Extigy.
I am using the alsa from the linux 2.6.3 kernel. White alsa's usbaudio.
When starting it wood fail. When i set #define IGNORE_CTL_ERROR in
usbmixer.c it wood load but when alsamixer came to the settings for the
At Wed, 3 Mar 2004 23:47:10 +0530,
Gupta, Kshitij wrote:
>
> hi,
> Can someone please explain me what is the difference between
> runtime->dma_addr and runtime->dma_area
>
> where runtime = substream->runtime
dma_addr is the physical address of the buffer.
this is valid for PCI, ISA and S
Hello,
Am Mittwoch, 3. März 2004 20:17 schrieb Tim Blechmann:
> are you planing to use this machine with a hdsp?
I'm afraid not, but I'd kindly test it for you if you sent me a hdsp (cardbus
iface, this is a laptop).
Gabriel.
---
Thi
Hullo,
I can't seem to find how to create MIDI channel mode messages (like "reset all
controllers" or "all notes off"), nor can I find out how to create many MIDI meta
events (like "text event" or "copyright notice" or "sequence name"), I've been able to
find out how to create some events at
ht
[Linux 2.6.3-SMP, single 933 MHz PIII, 1 GB RAM,
devfs, gcc-3.2.3]
Hi,
I have just installed the latest ALSA from CVS and
discovered that it has broken PCM playback. This is
what aplay gives me now:
$ aplay /usr/lib/sounds/jungle_exit.wav
Playing WAVE '/usr/lib/sounds/jungle_exit.wav' :
Signed
[EMAIL PROTECTED]
>Hullo, I can't seem to find how to create MIDI channel mode messages
>(like "reset all controllers" or "all notes off"), nor can I find out
>how to create many MIDI meta events (like "text event" or "copyright
>notice" or "sequence name"), I've been able to find out how to creat
On Wed, Mar 03, 2004 at 07:29:19PM +0100, Jaroslav Kysela wrote:
> On Wed, 3 Mar 2004, Gupta, Kshitij wrote:
> > hi,
> > Can someone please explain me what is the difference between
> > runtime->dma_addr and runtime->dma_area
> >
> > where runtime = substream->runtime
> >
> > I am getting a
Hi
I'm a bit of a newbie here. I'm trying to write a PCM application
using alsa 1.x. Firstly, is there an up to date howto or tutorial on
this? I am currently using the ALSA 0.9.0 HOWTO from the ALSA dev
page:
http://www.suse.de/~mana/alsa090_howto.html
*nothing* works. The header files m
On Thu, 2004-03-04 at 02:11, Tim Hollingsworth wrote:
>
> alsa-base 1.0.2c-3
> alsa-headers 1.0.2c-3
> alsa-source 1.0.2c-3
Looks like you're missing libasound2-dev?
--
Earthling Michel DÃnzer | Debian (powerpc), X and DRI developer
Libre software enthusiast| http
On 04/03/2004, at 9:54 AM, Michel Dänzer wrote:
On Thu, 2004-03-04 at 02:11, Tim Hollingsworth wrote:
alsa-base 1.0.2c-3
alsa-headers1.0.2c-3
alsa-source 1.0.2c-3
Looks like you're missing libasound2-dev?
aha!
---
This SF.Net e
26 matches
Mail list logo
