linuxaudio.org

--_0e054774-07ce-4911-9d10-faf08c87df81_

Content-Type: text/plain; charset="iso-8859-1"

Content-Transfer-Encoding: quoted-printable
> > The bristol B3 is perhaps not the most popular example of hammond emula=

tors

quoted text
> > but has anybody seen this?

>=20

> i have some extremely limited and utterly circumstantial evidence that

> the ALSA sequencer can cause this. Check the comparative versions of

> his and yours. I stress: I can't prove this either=2C I've just seen

> vaguely similar behaviour that given a brief debugging seems to be

> caused by the sequencer at some level. Relevant?

I would be more than happy to finger ALSA here but from the debugging done =

so far the problem happens with no evident lost note_off events=2C just one=

 spurious duplicated note_off debug message from bristol that definitely di=

d not result from an event delivered by the Seq interface. Debuging is an a=

wkward operation since each time I want to concentrate on selected code sec=

tions I have to provide updates and wait for the output - its a bit like pr=

ogramming with punchcards.
The difference in ALSA versions could naturally be relevant and will review=

 it.
Regards=2C Nick.
_________________________________________________________________

Show them the way! Add maps and directions to your party invites.=20

http://www.microsoft.com/windows/windowslive/products/events.aspx=
--_0e054774-07ce-4911-9d10-faf08c87df81_

Content-Type: text/html; charset="iso-8859-1"

Content-Transfer-Encoding: quoted-printable
.hmmessage P

{

margin:0px=3B

padding:0px

}

body.hmmessage

{

font-size: 10pt=3B

font-family:Verdana

}
&gt=3B &gt=3B The bristol B3 is perhaps not the most popular example of=

 hammond emulators&gt=3B &gt=3B but has anybody seen this?&gt=3B &gt=3B i have some extremely limited and utterly circumstantial evidence =

that&gt=3B the ALSA sequencer can cause this. Check the comparative ver=

sions of&gt=3B his and yours. I stress: I can't prove this either=2C I'=

ve just seen&gt=3B vaguely similar behaviour that given a brief debuggi=

ng seems to be&gt=3B caused by the sequencer at some level. Relevant?I would be more than happy to finger ALSA here but from the debugging=

 done so far the problem happens with no evident lost note_off events=2C ju=

st one spurious duplicated note_off debug message from bristol that definit=

ely did not result from an event delivered by the Seq interface. Debuging i=

s an awkward operation since each time I want to concentrate on selected co=

de sections I have to provide updates and wait for the output - its a bit l=

ike programming with punchcards.The difference in ALSA versions cou=

ld naturally be relevant and will review it.Regards=2C Nick.See all the ways you can stay connected to friends and =

family

=
--_0e054774-07ce-4911-9d10-faf08c87df81_--