Hello again,
Quoting Jaroslav Kysela <[EMAIL PROTECTED]>:
> The 32-bit mixing code is not debugged. Please, could you try to change
> one line in pcm_dmix.c (alsa-lib/src/pcm/pcm_dmix.c) from
> '#ifdef __i386__' to '#ifdef __i386XX__' and recompile library?
> We'll see then if it's a problem with
Takashi Iwai wrote:
> (i also don't know any pci (or other bus) cards with opl4, though...)
The marketing for the ALS4000 claims it's "compatible with the Yamaha OPL4
wavetable synthesizer", but, judging from the manual, this is a lie. :(
Clemens
-
On 24-Mar-2003 Takashi Iwai wrote:
>> Ok, PAUSE_PUSH-->stop() and TRIGGER_STOP-->stop()-and-reset dma
>> pointer. In my case RELEASE and START are the same thing.
>
> note that resetting the dma pointer wouldn't be necessary in STOP
> trigger (although it may be safer), since the dma pointer will
At Mon, 24 Mar 2003 11:48:50 +0100 (CET),
Giuliano Pochini wrote:
>
>
> >> What are PUSH, RELEASE, SUSPEND, RESUME trigger commands supposed to do
> >> ?
> >
> > * pcm stream pausing
> > imagine the pause-button is pushed and released.
> > these commands are issued only when SNDRV_PCM_INFO_PAUSE
On Mon, 24 Mar 2003, Kristof Pelckmans wrote:
> Hi all,
>
> I tried to use the dmix plugin, as mentioned :
> > pcm.dmix_analog {
> > type dmix
> > ipc_key 5678293
> > ipc_key_add_uid yes
> > slave {
> > pcm "hw:0,0"
> > }
> > binding
>> What are PUSH, RELEASE, SUSPEND, RESUME trigger commands supposed to do
>> ?
>
> * pcm stream pausing
> imagine the pause-button is pushed and released.
> these commands are issued only when SNDRV_PCM_INFO_PAUSE is set to
> info field of snd_pcm_hardware_t.
>
> - PAUSE_PUSH
> pause the st
Hi all,
I tried to use the dmix plugin, as mentioned :
> pcm.dmix_analog {
> type dmix
> ipc_key 5678293
> ipc_key_add_uid yes
> slave {
> pcm "hw:0,0"
> }
> bindings {
> 0 0
> 1 1
> }
> }
When
At 23 Mar 2003 18:31:04 +,
Giuliano Pochini wrote:
>
> What are PUSH, RELEASE, SUSPEND, RESUME trigger commands supposed to do
> ?
* pcm stream pausing
imagine the pause-button is pushed and released.
these commands are issued only when SNDRV_PCM_INFO_PAUSE is set to
info field of snd_pcm_har
At Mon, 24 Mar 2003 10:33:12 +0100 (MET),
Clemens Ladisch wrote:
>
> Jaroslav Kysela wrote:
> > On Mon, 24 Mar 2003, Clemens Ladisch wrote:
> > > This adds support for the mixer and wavetable synthesizer of OPL4 chips.
> > >
> > > The OPL4 can be used with OPTi 82C928/Mozart, 82C929 and 82C924 car
Jaroslav Kysela wrote:
> On Mon, 24 Mar 2003, Clemens Ladisch wrote:
> > This adds support for the mixer and wavetable synthesizer of OPL4 chips.
> >
> > The OPL4 can be used with OPTi 82C928/Mozart, 82C929 and 82C924 cards
> > (82C925 and 82C93x have an integrated OPL3 and don't support an externa
On Mon, 24 Mar 2003, Clemens Ladisch wrote:
>
> This adds support for the mixer and wavetable synthesizer of OPL4 chips.
>
> The OPL4 can be used with OPTi 82C928/Mozart, 82C929 and 82C924 cards
> (82C925 and 82C93x have an integrated OPL3 and don't support an external
> OPLx chip).
Is there an
fix typo
Index: alsa-kernel/core/seq/seq_midi_emul.c
===
RCS file: /cvsroot/alsa/alsa-kernel/core/seq/seq_midi_emul.c,v
retrieving revision 1.9
diff -u -r1.9 seq_midi_emul.c
--- alsa-kernel/core/seq/seq_midi_emul.c25 Feb 200
This adds support for the mixer and wavetable synthesizer of OPL4 chips.
The OPL4 can be used with OPTi 82C928/Mozart, 82C929 and 82C924 cards
(82C925 and 82C93x have an integrated OPL3 and don't support an external
OPLx chip).
Added/changed files:
+++ new/alsa-driver/include/amagic.hSun Mar
The first version of this quirk was based on some obscure entry in the
Quattro driver's .inf file. The Audiophile .inf file actually knows the
right number.
(There still isn't a firmware loader for the Audiophile.)
Index: alsa-kernel/usb/usbquirks.h
=
When a seq-midi device is used multiple times, it doesn't reset the parser
when opening/closing the underlying rawmidi device, so it is possible that
the first command to the newly opened rawmidi device uses running status.
This may not work because the device may have been reset by the 0xff sent
Fernando Pablo Lopez-Lezcano wrote:
> [...]
> Apparently having active sensing midi bytes coming in to the Quattro
> while the driver is being loaded kills input. I was not able to make
> things work if the keyboard is connected to the interface when alsa
> starts.
>
> A MidiSport2x2 works fine und
16 matches
Mail list logo
