public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: "John R. Sowden" <jsowden@americansentry.net>
To: linux-msdos@vger.kernel.org
Subject: Re: Sound support (2), using hardware directly
Date: Sat, 23 Jul 2005 05:19:52 -0700	[thread overview]
Message-ID: <200507230519.52704.jsowden@americansentry.net> (raw)
In-Reply-To: <42E226FD.3080008@zgod.cjb.net>

On Saturday 23 July 2005 04:16, Julius Schwartzenberg wrote:
> Stas Sergeev wrote:
> > Julius Schwartzenberg wrote:
> >> I have ran it succesfully on my AMD Athlon @ 1GHz, and I know there
> >> are softsynths that need much less, although not for Linux.
> >
> > As I said, you can tune timidity++
> > to work even on 386, just disable
> > some effects processing.
>
> Ah, OK. I was more thinking of i386 and compiling Timidity without
> special instructions for P4.
>
> > There are also the alternative
> > synthesizers, like fluidsynth,
> > as someone pointed out to me, but
> > I am not sure if they work as an
> > alsa sequencer backend, or have
> > the server interface for midid.
>
> I think I'll just try Timidity :)
>
> >> running a softsynth inside Dosemu...
> >
> > That is possible for FM synth, but
> > you really don't want to distribute
> > the instrument patchsets with dosemu.
>
> This wasn't meant for distribution with Dosemu. I also do not know any
> FM synths that run in Dos. I've just tried WinGroove in Dosemu (which I
> haven't been able to run for a long time) and it didn't seem to run that
> bad!
> I still haven't been able to install the SB16 drivers for MS Windows
> though. (I'll probably have to get them of a real machine, since those
> annoying Creative installers think too much.) Those might improve the
> quality even more.
>
> >> Well, the problem seemed to be at the time that the (OPL3) driver from
> >> ALSA was conflicting with the OPL3 being accessed directly.
> >
> > In this case simply not loading the
> > OPL3 driver from ALSA would help,
> > but IIRC it doesn't.
>
> Yes, but it would be nice to still have sequencer support for other
> Linux apps too similar to how MS Windows seems to be able to do it.
> Also not loading the OPL3 driver doesn't seem to be possible, since the
> plain sounddriver seems to have a dependency on the OPL3 driver. At
> least on snd_opl3_lib. I do not know how serious this is though. Also
> what snd_opl3_synth does and what snd_opl3_lib does and why they're not
> combined, is not clear to me.
> I was thinking myself of some sort of special interface for applications
> like Dosemu, but if there already is full hardware access that doesn't
> really sound like an improvement.
> Maybe the OPL3 would just need some initialization first before it would
> work with most games, so it gets in the state where it is also when no
> driver has loaded. Then it might be possible to have some sort of Dos
> program that runs inside Dosemu before running the game to do it .

Since this thread has worked it way to "Dosemu talking directly to hardware", 
I am interested in using my linux/dosemu box to connect to a local area 
network that runs DOS only (we don't do windows).  Now I have to either boot 
into DOS on my linux box via grub or, using a kvm, switch to a different 
computer.  Neither of these options allow me to share data to/from 
Linux/Dosemu and DOS.  My net is "Little Big Lan".  It have served me well 
for about 10 years, but I will grudgingly let it go if I have to.

tia,

-- 
John R. Sowden
AMERICAN SENTRY SYSTEMS, INC.
Residential & Commercial Alarm Service
UL Listed Central Station
Serving the San Francisco Bay Area Since 1967
mail@americansentry.net
www.americansentry.net

  reply	other threads:[~2005-07-23 12:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-23  9:45 Sound support (2), using hardware directly Stas Sergeev
2005-07-23 11:16 ` Julius Schwartzenberg
2005-07-23 12:19   ` John R. Sowden [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-07-23 19:18 Stas Sergeev
2005-07-24 15:13 ` Julius Schwartzenberg
2005-07-23 12:30 Stas Sergeev
2005-07-23 12:27 Stas Sergeev
2005-07-23 18:16 ` Julius Schwartzenberg
2005-07-22 17:56 Stas Sergeev
2005-07-22 18:20 ` Julius Schwartzenberg
2005-07-22  4:03 Stas Sergeev
2005-07-22 13:11 ` Julius Schwartzenberg
2005-07-19 12:54 Stas Sergeev
2005-07-21 20:17 ` Julius Schwartzenberg
2005-07-19  4:18 Stas Sergeev
2005-07-19 11:11 ` Julius Schwartzenberg
2005-07-18 19:25 Julius Schwartzenberg

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=200507230519.52704.jsowden@americansentry.net \
    --to=jsowden@americansentry.net \
    --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