Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Steve Netting <steve@moonfoundation.co.uk>
To: linux-sound@vger.kernel.org
Subject: Re: Midi / SysEx - Dump / Linux?
Date: Sat, 15 Jul 2000 14:52:27 +0000	[thread overview]
Message-ID: <marc-linux-sound-96367272709995@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-96349816311777@msgid-missing>

<Benno - if this doesn't make it out to the list - could
 you forward it?   I've been having email noghtmares recently!>

 < snip >

> > Could anyone confirm that? I've got an Elektron
> > SIDStation and there is no other way to save custom
> > programs than via MIDI/sysex. So if this does not
> > work, I'll lose all my carefully crafted custom
> > programs.
> > Thanks a lot in advance.
> >  - eric -

 <snip?

> I am sorry that I can not try the reverse cat dumpfile >/dev/midi00
> because of the lack of HW here.
> 
> it should work, but wait for someone confirming this.

 Yes, does indeed work - tested using an Alesis MMT-8 sequencer
 dumping it's memory via midi ... and a Korg N1 synth dumping all
 it's programs settings etc.  All restores without any problems.

 Thanks to all who replied!   I should have though of that myself,
 but well... I really didn't think it was that easy.

 I'll probably knock up a script to make the whole process more
 user-friendly, and provide some sort of menus for dumping/
 restoring data...


Thanks again!


Steve
--
http://www.moonfoundation.co.uk
--
- Steve Netting - Logica Aldiscon, Bristol, UK

      parent reply	other threads:[~2000-07-15 14:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-13 14:22 Midi / SysEx - Dump / Linux? Steve Netting
2000-07-13 14:42 ` Eric Brunel
2000-07-13 15:14 ` Dave Phillips
2000-07-13 15:33 ` Andrew Ryan
2000-07-13 22:54 ` Benno Senoner
2000-07-14 14:48 ` Dave Phillips
2000-07-14 15:23 ` Andrew Ryan
2000-07-14 16:46 ` Benno Senoner
2000-07-14 17:03 ` Eric Brunel
2000-07-15 14:52 ` Steve Netting [this message]

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=marc-linux-sound-96367272709995@msgid-missing \
    --to=steve@moonfoundation.co.uk \
    --cc=linux-sound@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