On Tue 18 Feb 2025 at 09:53:18 (-0500), Laura Conrad wrote:
> >>>>> "David" == David Wright writes:
> 
>     >> "aplaymidi -p 14:0 score.midi" doesn't crash but hangs and doesn't play
>     >> anything.
> 
>     David> It "hung" here for the exact length of the MIDI file (about 4 
> seconds
>     David> for the output from your attached .ly file, 46 seconds for 
> tenor.midi),
>     David> and I heard nothing. Then I got the prompt.
> 
> Yes, you're correct.  The MIDI file I was originally  using was a couple
> of minutes long.  When I do i t on test.midi, it hangs for only a few
> notes time.
> 
>     David> However, I then set up a MIDI listener—on one xterm, I typed:
> 
>     David>   $ timidity -iA
>     David>   Requested buffer size 32768, fragment size 8192
>     David>   ALSA pcm 'default' set buffer size 33868, period size 3760 bytes
>     David>   TiMidity starting in ALSA server mode
>     David>   Opening sequencer port: 128:0 128:1 128:2 128:3
> 
>     David> and on another, observing the above, I typed:
> 
>     David>   $ aplaymidi -p 128:0 /tmp/tenor.midi
> 
>     David> and heard part of "Sumer is icumen in" played very slowly.
> 
> Yes, "aplaymidi -l" lists the "midi through" port, so I'm sure if I'd
> done what you did, it would have worked for me, too.

Wouldn't that need testing, as you just posted that timidity dumps core.

>     >> This worked fine for years.  It seems to be a problem not only with
>     >> current MIDI files but with (all?) the others on my website that were
>     >> generated years or decades ago.
> 
>     David> Peter Chubb appears to be running timidity 2.14.0-8.3 from Debian
>     David> testing/trixie, three versions newer than my June 2018 version.
>     David> I've had no problems with 2.14.0-8, but that said, I don't run
>     David> it as a client or server for other processes. I always just type:
> 
>     David>   timidity [options] <MIDI-filename>   (or a script does).
> 
> That's all I was doing either.

Sorry, I was just explaining that whereas you appeared to be familiar
with aplaymidi in your first post, it was new to me, and I had to
work out that it needed another program to make the computer emit sound.
So I was mystified as to why you thought aplaymidi just hung. Is port
14 normally meant to produce sounds without help? There's obviously
something special about 14, because every other number ≤127 is an
"invalid argument", except for 0, which is "not permitted".

> But my version is only one behind
> Peter's.  I suppose linux mint should be nudged to update.

Without actual version numbers, it's not clear what's meant by
"one behind" and "before the last update". It depends what you're
tracking and how closely.

Cheers,
David.

Reply via email to