[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | * * Computer Music, MIDI, and Related Topics * * |
Notice: | Conference has been write-locked. Use new version. |
Moderator: | DYPSS1::SCHAFER |
|
Created: | Thu Feb 20 1986 |
Last Modified: | Mon Aug 29 1994 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 2852 |
Total number of notes: | 33157 |
2569.0. "Saving/Restoring Memory Dumps using C-Lab Creator" by MAJORS::SPENCE (Bugs? You mean insects?) Tue Feb 05 1991 13:14
I've been using an Atari-based sequencing package called Creator for over a
year now, with Korg M1 and DS-8 synthesizers, a P3 piano module and (on
occasions) an Alesis HR-16 drum machine. I much prefer to keep backups of the
memory (sounds etc) from the synthesizers on a floppy disk costing 2 pounds
instead of a RAM card costing probably 80 pounds. So, I have a song for each
synthesizer, generated as follows:
1. Start Creator recording a track
2. Start the synthesizer dumping its memory out via MIDI
3. Wait for the synthesizer to say that it's finished
4. Wait for Creator to finish processing the data (ie the cursor is unlocked)
5. Stop the recording
In theory, you could now play back that track onto the synthesizer that it
was generated from, and restore it undamaged. Unfortunately, that does not
always work. I've found in practice that to get the data saved and restored
without errors (judged to have worked if none of the program/sound names
are garbled), you need to set the Tempo in Creator to a value which is different
for every synthesizer I own, and then play it back at a slower speed. Even
then it doesn't always work.
Does anyone else use C-Lab Creator (or Notator) for saving/restoring memory
dumps for their synthesizers? If so, I'd be interested to know how you have
fared so far, what pitfalls and/or useful tricks you've discovered. I've just
about managed to sort out saving and restoring the M1 and HR-16 - the DS-8 I'm
still working on; about six of my sounds are currently garbage as a result
of restoring a duff backup!
Cameron
P.S. For actually playing music, I think Creator is superb - very easy and
logical to use, and extremely reliable.
T.R | Title | User | Personal Name | Date | Lines |
---|
2569.1 | Generic Sys-Ex Utilities Right Here On The E-net | AQUA::ROST | In search of the lost biscuit drop | Tue Feb 05 1991 13:45 | 9 |
| As an alternative, you could use a generic sys-ex librarian, a few of
which can be had right here on the net. This would run separate from
your sequencer, but let you archive your sounds more reliably.
Check the note on MIDI software on the Enet (it's down in the first 20
notes somewhere). I've pulled a few useful MIDI utilities for the ST
off the net.
Brian
|
2569.2 | Tempo, handshaking & channel. | EICMFG::BURKE | Jim Burke, @UFC | Thu Feb 07 1991 05:19 | 15 |
| [shouldn't this be under the CREATOR note ?]
I have achieved this without too much fuss. As I remember, I had to
crank the tempo down to about 50 (BpM) or so.
Also note that some SGU's require a handshake when SYSEX
dumping/loading - use Notator's 'Pseudo Events' to react to these
handshakes. It may be that the dump sequence is slightly different than
what's required for a load sequence. You'll have to study the SYSEX
implementation for your synths.
I think that I had to switch my synths down to MIDI channel 1. In fact,
this was necessary for the CZ and also the FB01.
Jim Burke
|
2569.3 | No Dump Problems with DX11. | JGODCL::SUIJDAM | Roel van Suijdam JGO::SUIJDAM | Fri Feb 08 1991 12:56 | 16 |
| No Problem.
I've been using Notator/Creator for the past 2 Years now. I'm Using version
3.0 now but I've never had any problems with garbled dumps from my DX11.
I don't even bother to turn down the tempo if I record a dump.
I usually save Voice and Performance dumps in a separate track (99).
Roel.
NB. I've found some minor bugs in V 3.0. One alert box which overwrites one
of the buttons inside and a difficult to reproduce phenomenum. It becomes
obvious in the Score display as numerous 1/16 rests displayed in a peace
that previously looked OK.
Reloading the piece from disk resolves it.
|