[BRLTTY] alert tones

[Mario Lang]

Dave Mielke <dave at mielke.cc> writes:

>>Maybe the check in configure should be replaced with a fallback?  Check for
>>ALSA first, if no libasound2 can be found, fallback to OSS?
>>This should cover the case where someone tries to get brltty running
>>on an older distro.
>
> That's what we'll do. We should get ALSA MIDI working first, though. I've 
> verified that ALSA PCM does work, but, like you, I also get no sound when doing 
> ALSA MIDI via timitidy.
>
> I'm wondering, though, if timidity might be part of the problem. When I run it 
> with -iA (act as ALSA client), and then play a regular MIDI file through it via 
> aplaymidi, the sound is quite broken up. If I add the timitidy option 
> --realtime-priority=50, it's better, but still quite broken up. Do you get the 
> same thing?
No.  I happened to test on a pretty fast machine, and
normal playback of midi files via aplaymidi through timidity worked fine.
In fact, that was the first reference test I did do see if something
else was broken.

Note that the ALSA sequencer API has two ways of delivering events,
either directly timed, or timestamped via a queue.  Maybe we are mixing
these two approaches up a bit?  Another thing we should look at
is port subscription.  I dont remember, but there was a event
dumping application we could use to see what actually comes out of the brltty
alsa midi port.

-- 
CYa,
  ⡍⠁⠗⠊⠕ | Debian Developer <URL:http://debian.org/>
  .''`. | Get my public key via finger mlang/key at db.debian.org
 : :' : | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44
 `. `'
   `-      <URL:http://delysid.org/>  <URL:http://www.staff.tugraz.at/mlang/>