Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Will <walsac2@liam2.demon.co.uk>
Cc: alsa-devel@lists.sourceforge.net, clemens@ladisch.de
Subject: Re: [PATCH] add aplaymidi & arecordmidi utils
Date: Wed, 25 Feb 2004 15:26:16 +0100	[thread overview]
Message-ID: <s5hd683nsl3.wl@alsa2.suse.de> (raw)
In-Reply-To: <200402251419.OAA13155@liam2.demon.co.uk>

At Wed, 25 Feb 2004 14:19:36 GMT,
Will wrote:
> 
> Takashi Iwai wrote:
> >>Will wrote:
> >> I wonder whether drvmidi actually does correctly restore controller and sysex
> >> when you move during MIDI playback.  I haven't studied the drvmidi code in
> >> detail.  I know the sound quality always seems to be correct
> >> even when you move forwards and backwards very often in a piece with
> >> lots of sysex and controller settings.
> >
> >it does.  when skipping forward/backward, it will send all necessary
> >ctl/sysex messages from the beginning.  i implemented in this way
> >because it's designed only for the internal MIDI wavetable, which can
> >handle many events immediately.  that's not for general MIDI devices.
> 
> That's great.  How easy would it be to port drvmidi to the ALSA sequencer?

a bit touch.  it's a quite old code.

> It's a fantastic little player.  It has the very useful functionality of
> a GUI player (moving forwards and backwards during playback).
> The only problem is it's for the OSS sequencer...

sorry, i have no time for that...
patches are always welcome, though :)

--
Takashi Iwai <tiwai@suse.de>		ALSA Developer - www.alsa-project.org


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click

  reply	other threads:[~2004-02-25 14:26 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-23  9:18 [PATCH] add aplaymidi & arecordmidi utils Clemens Ladisch
2004-02-23  9:41 ` Jaroslav Kysela
2004-02-24 17:12 ` Will
2004-02-24 17:36   ` Clemens Ladisch
2004-02-24 17:51     ` Will
2004-02-24 17:58       ` Clemens Ladisch
2004-02-25  0:10         ` Will
2004-02-25  8:23           ` Clemens Ladisch
2004-02-25 13:22             ` Will
2004-02-25 13:58               ` James Courtier-Dutton
2004-02-25 14:11                 ` Will
2004-02-24 17:26 ` Will
2004-02-24 17:43   ` Clemens Ladisch
2004-02-25 13:02     ` Will
2004-02-25 14:04       ` Takashi Iwai
2004-02-25 14:19         ` Will
2004-02-25 14:26           ` Takashi Iwai [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-03-02 15:20 CVS ALSA failed upgrade in Linux 2.6.3 William
2004-03-02 15:36 ` Takashi Iwai
2004-03-02 15:52   ` William
2004-03-02 16:39     ` Takashi Iwai
2004-03-02 17:28       ` William
2004-03-02 17:33         ` Takashi Iwai
2004-03-02 17:59           ` William
2004-03-02 18:04             ` Takashi Iwai
2004-03-03 14:50               ` William
2004-03-02 21:08 ` James Courtier-Dutton
2004-03-02 23:35   ` William
2004-03-03  1:07     ` James Courtier-Dutton
2004-03-03 15:54       ` William

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=s5hd683nsl3.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=clemens@ladisch.de \
    --cc=walsac2@liam2.demon.co.uk \
    /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