public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Phillips <dlphilp@bright.net>
To: Clarence Dang <clarencedang@yahoo.com>
Cc: linux-msdos@vger.kernel.org
Subject: Re: some comments re: dosemu 1.1.99 (fwd)
Date: Sat, 18 Oct 2003 17:21:41 -0400	[thread overview]
Message-ID: <3F91AEE5.7080309@bright.net> (raw)
In-Reply-To: <200310172128.24344.clarencedang@yahoo.com>

Clarence Dang wrote:

[re: Sound Globs opening noise]

>>I'm now able to open and run the program, but something happens when it
>>opens that kills its MIDI activity. The program appears to be working, it
>>just doesn't send any MIDI data. Upon opening it sends a big MIDI reset to
>>my synths (including a big chord with no apparent note-off), then I get no
>>joy. :(  I'm still working with it though, trying to at least create some
>>MIDI files for later use.
>>
>>    
>>
>Are you using midid?  If so, is ~/.dosemu/run/dosemu-midi a pipe?  If it's 
>only a file, MIDI events will just accumulate in there; that might explain 
>why you get a single note at startup but no MIDI after that.
>
Hi Clarence:

  Actually it's a bunch of notes sounding at once (i.e. a chord). I 
remember beta testing a version of Sequencer Plus that did exactly the 
same thing, and the programmers at Voyetra fixed it. They told me that 
the sequencer did a complete MIDI reset upon opening, which makes sense, 
but they also realized it was an error to send a bunch of MIDI note-on 
messages. Btw, when I run Sound Globs on a dedicated DOS machine this 
effect does not occur.

  No, I'm not using midid. ~/.dosemu/run/dosemu-midi is linked to 
/dev/snd/midiC1D0, ALSA's virtual MIDI card. In the past I've found that 
method to be much les latency-prone than midid, though I recall Stas 
mentioning that the daemon had been much improved lately. I might try it 
again someday, but truthfully the link works so well I'm not inclined to 
change it.

  Thanks for the suggestion, I appreciate any & all input on this matter.

Best regards,

Dave Phillips




  parent reply	other threads:[~2003-10-18 21:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-16 20:17 some comments re: dosemu 1.1.99 (fwd) Bart Oldeman
2003-10-17 11:28 ` Clarence Dang
2003-10-17 14:41   ` ye olde vga fonts problem redux Dave Phillips
2003-10-17 21:23     ` Ralph Alvy
2003-10-18 21:21   ` Dave Phillips [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-18 21:14 some comments re: dosemu 1.1.99 (fwd) Stas Sergeev
2003-10-18 21:54 ` Dave Phillips
2003-10-18 22:31 Stas Sergeev
2003-10-20 12:40 ` Dave Phillips
2003-10-20 18:39 Stas Sergeev
2003-10-24 17:16 ` Ryan Underwood

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=3F91AEE5.7080309@bright.net \
    --to=dlphilp@bright.net \
    --cc=clarencedang@yahoo.com \
    --cc=linux-msdos@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox