From: Martin Tarenskeen Subject: Re: [v7 PATCH] amidi: add sysex-interval option Date: Wed, 14 Sep 2016 07:43:37 +0200 (CEST) Message-ID: References: <20160830160248.4595-1-eu@felipetonello.com> <84e1a053-73bc-392b-4348-73ed26734ab4@sakamocchi.jp> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from cpsmtpb-ews09.kpnxchange.com (cpsmtpb-ews09.kpnxchange.com [213.75.39.14]) by alsa0.perex.cz (Postfix) with ESMTP id 11FE0261740 for ; Wed, 14 Sep 2016 07:43:44 +0200 (CEST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: Takashi Sakamoto Cc: alsa-devel@alsa-project.org, Felipe Ferreri Tonello List-Id: alsa-devel@alsa-project.org >>>>> + "-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