public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Phillips <dlphilp@bright.net>
To: steve.home@cox.net
Cc: linux-msdos@vger.kernel.org, ametts@mindspring.com
Subject: Re: no MIDI input with dosemu ?
Date: Fri, 16 Jan 2004 08:27:29 -0500	[thread overview]
Message-ID: <4007E6C1.4040806@bright.net> (raw)
In-Reply-To: <20040116062115.BYPV11223.fed1mtao06.cox.net@smtp.west.cox.net>

Greetings:

  Before anyone gets disturbed over all this, I must let you know that 
Stas has sent me a patch to test for adding MIDI input to the CVS 
DOSemu. I have compiled the sources and have slightly tested for MIDI 
input. It didn't work, but that doesn't mean Stas's code is wrong. I'm 
currently in the middle of a very heavy writing project (12,000 words 
and I'm only about 2/3 finished, so I've been stalled for a while 
(Sorry, Stas!). I'll try to make some time for more testing today.

  So, thanks to Stas we're getting there. When Seq+ gets MIDI input 
it'll be just fantastic. I agree with Steve, Linux MIDI just hasn't "got 
there" yet, though it's certainly moving right along (so far MusE has 
the most appeal for me, but I haven't had time to test the latest 
Rosegarden release).

  Little by little, the doing gets it done... ;)

Best,

== dp




steve.home@cox.net wrote:

>The problem is that MIDI is not just for games. I haven't used a better all-around MIDI sequencer than seq+ in the last 10 years. And I know other people who feel the same. I hate to say it but from a user's perspective, even a user with a strong pro-linux bias, Linux MIDI hasn't hit the mark, Jazz and Rosegarden included. If dosemu and Linux are to live up to their promise there's no reason not to have a full MIDI implementation. Some of us would really appreciate it.
>  
>
>>From: Dave Phillips <dlphilp@bright.net>
>>Date: 2004/01/08 Thu AM 10:16:00 EST
>>To: linux-msdos@vger.kernel.org
>>CC: Stas Sergeev <stsp@aknet.ru>,  steve.home@cox.net,  ametts@mindspring.com
>>Subject: Re: no MIDI input with dosemu ?
>>
>>Stas Sergeev wrote:
>>
>>    
>>
>>>Why? Implementing midi input is trivial,
>>>but I'm puzzled as of what's the use.
>>>Dosemu needs a MIDI output as otherwise
>>>you can't play games. But as for midi
>>>recording, you can use the native Linux
>>>programs just fine. And it will actually
>>>work better, because under dosemu the
>>>timing is not always accurate. So why
>>>would anyone ever need that? 
>>>      
>>>
>>No, Stas, I can't use the native Linux sequencers "just fine" and their 
>>developers know it. Unfortunately there is no easy way for them to 
>>accomodate my working method (which results from amenities of the 
>>particular DOS sequencer I like to use). I put about nine years into 
>>working with a particular program (Sequencer Plus, or Seq+ for short) 
>>whose working method is far more amenable to me than that of any native 
>>Linux sequencer. I'm not much of a keyboard player, I'm a guitarist, so 
>>I prefer a MIDI sequencer with exceptional QWERTY keyboard data entry 
>>features, and none of the native Linux sequencers approach the usability 
>>of Seq+ in this regard. Actually I can use Seq+ under DOSemu to meet my 
>>needs, but a few other users have written to me about wanting MIDI input 
>>with Seq+ under DOSemu. Apparently they're not comfortable with the 
>>native Linux MIDI sequencers either.
>>
>>The developers of the native Linux sequencers know of my needs quite 
>>well (I've been corresponding with all of them since their projects 
>>began). The problem lies in some of their own assumptions and some of 
>>the restrictions forced on them by X11. Also, Seq+ includes many MIDI 
>>features not found in Rosegarden-4, MusE, Jazz++, or seq24. Timing is in 
>>fact very good, especially when run with a Linux kernel patched for 
>>low-latency (I use the Planet CCRMA system). MusE and Rosegarden both 
>>have trouble playing some of my MIDI sequences that Seq+ handles 
>>perfectly under DOSemu. The plain fact is that for my working methods 
>>Seq+ is superior to any native Linux MIDI sequencer. I say this not to 
>>criticize the Linux sequencers, but merely to indicate how far they have 
>>to go before they reach the maturity of an application like Seq+ (which 
>>by 1995 had almost ten years of development).
>>
>>Btw, I'm uninterested in integrated audio/MIDI sequencing, which is the 
>>design philosophy behind the Jazz++, MusE, and Rosegarden-4 (seq24 is 
>>designed more like a hardware sequencer such as the old Alesis MT8 and 
>>again has little value to my work methods). I'm strictly interested in 
>>MIDI, and it seems to me that the Linux developers are putting more time 
>>into audio-oriented features than into MIDI-specific features. As I 
>>said, they know my opinions about these matters (and we're still 
>>friends, incredible as it seems).
>>
>>If adding MIDI input capability in DOSemu is trivial, hopefully these 
>>reasons will convince you that it would still be greatly appreciated by 
>>some of us.
>>
>>Best regards,
>>
>>Dave Phillips
>>
>>
>>
>>
>>    
>>
>
>
>  
>



  reply	other threads:[~2004-01-16 13:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-16  6:21 Re: no MIDI input with dosemu ? steve.home
2004-01-16 13:27 ` Dave Phillips [this message]
2004-01-16 17:32 ` Stas Sergeev
2004-01-16 22:25   ` Ged Haywood
2004-01-16 23:47     ` Robert Komar
2004-01-20 14:16       ` Dave Phillips
2004-01-20 15:50         ` Bart Oldeman
2004-01-20 20:45           ` Dave Phillips
2004-01-21  4:42           ` Justin Zygmont
  -- strict thread matches above, loose matches on Subject: below --
2004-01-16 17:18 Stas Sergeev
2004-01-08 13:53 Stas Sergeev
2004-01-08 15:16 ` Dave Phillips
     [not found]   ` <3FFD9C0D.90804@aknet.ru>
     [not found]     ` <3FFDA3E1.5070508@bright.net>
2004-01-09  1:18       ` Stas Sergeev
2004-01-09  8:31 ` Ryan Underwood
2003-12-26 20:17 Is sound in dosemu a myth? JLB
2004-01-08 13:22 ` no MIDI input with dosemu ? Dave Phillips

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=4007E6C1.4040806@bright.net \
    --to=dlphilp@bright.net \
    --cc=ametts@mindspring.com \
    --cc=linux-msdos@vger.kernel.org \
    --cc=steve.home@cox.net \
    /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