From: Martin Tarenskeen <m.tarenskeen@zonnet.nl>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: alsa-devel@alsa-project.org,
Felipe Ferreri Tonello <eu@felipetonello.com>
Subject: Re: [v7 PATCH] amidi: add sysex-interval option
Date: Wed, 14 Sep 2016 07:43:37 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.20.1609140730140.7857@192.168.2.4> (raw)
In-Reply-To: <bd1656a5-cb69-02d9-d449-0f93897b8124@sakamocchi.jp>
>>>>> + "-i, --sysex-interval=mseconds delay in between each SysEx
I really appreciate this new option. It's by no means useful only for
firmware upgrades that's often mentioned in this thread. IMO that's a
special case.
More common is that (older) synths expect a delay between SyxEx blocks to
prevent "MIDI buffer full" type of messages on the synth's display. I have
read in the manual of some Yamaha synths (can't remember which) a
recommendation to use an interval of 10 ms. When I programmed YSEDITOR, a
Yamaha synth editor/librarian in the old Atari days, I often used series
of sysex messages simulating button presses to put the synth in a certain
mode, before sending bulkdumps and parameter change messages. Some
messages took more time inside the synth to be processed and I had to
insert time intervals before I could send another message.
If I combine such a sequence of sysex messages in a single .syx file and
use amidi to send the message, I will surely need the new -i parameter.
Apart from that, every sysex dump utility I have seen has a similar
feature. MIDI-OX for Windows is probably the best known example.
So, thanks guys.
--
MT
next prev parent reply other threads:[~2016-09-14 5:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 16:02 [v7 PATCH] amidi: add sysex-interval option Felipe F. Tonello
2016-09-12 16:41 ` Felipe Ferreri Tonello
2016-09-12 23:32 ` Takashi Sakamoto
2016-09-13 13:53 ` Felipe Ferreri Tonello
2016-09-13 17:44 ` Takashi Sakamoto
2016-09-14 5:43 ` Martin Tarenskeen [this message]
2016-09-13 15:37 ` Clemens Ladisch
2016-09-13 16:20 ` Takashi Iwai
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=alpine.LFD.2.20.1609140730140.7857@192.168.2.4 \
--to=m.tarenskeen@zonnet.nl \
--cc=alsa-devel@alsa-project.org \
--cc=eu@felipetonello.com \
--cc=o-takashi@sakamocchi.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.