From: "Ville Syrjälä" <syrjala@sci.fi>
To: alsa-devel@lists.sourceforge.net
Cc: perex@suse.cz, tiwai@suse.de
Subject: Question on sequencer synth driver
Date: Fri, 10 May 2002 05:06:10 +0300 [thread overview]
Message-ID: <20020510050610.C8147@sci.fi> (raw)
I'm still struggling with my MikMod driver, and since no one has answered
my previous mails, I've been trying to figure it out myself. Maybe I'm in
Jaroslav's procmailrc or something :( Takashi can you take a look?
My problem is that events get delivered but I don't get any sound. I've
concluded that snd_gus_synth_event_input() get's called and it in turn
calls snd_gus_sample_event(). And in that function the problem arises. The
for-loop tests for v->use for each voice. And in my case v->use is never
set. The 'use' field is set in snd_gf1_alloc_voice() which is called from
snd_gus_synth_use(). Is's called for as many voices as the subscriber has
requested. But the voices field in snd_seq_port_subscribe_t can't be set
because there is no function to do so. So I think I need
snd_seq_port_subscribe_set_voices(). To continue my testing I added that
function to my local copy of alsa-lib. But I was disappointed again. Now
it seems that snd_gus_synth_use() doesn't even get called when I
connect my client to the synth. It's registered as the 'use' port
callback, and if I'm not mistaken it should get called whenever a client
connects.
Summary:
I think snd_subscribe_{set,get}_voices() are needed.
Why doesn't snd_gus_synth_use() get called when my client connects to it?
The latest verions of the MikMod driver is at
"http://www.saunalahti.fi/~syrjala/alsa/"
--
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net
reply other threads:[~2002-05-10 2:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020510050610.C8147@sci.fi \
--to=syrjala@sci.fi \
--cc=alsa-devel@lists.sourceforge.net \
--cc=perex@suse.cz \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.