HiI see a few guys on here have SU10s.Has anyone succesfully managed to get the System Exclusive dump / receive working to anything other than a Yamahs MDF2?I've been trying to get it to work with my laptop (I've tried 2 laptops, 2 different midi adaptors, at least 3 different software packages), and all the various settings on the SU10.Every time, I get a 'Wrong Data!' Error on the SU10 towards the end of the first block of data being dumped back in.I'm watching some MDF2s on ebay to see if I can get one cheap, but I bought the SU10 because it was small (and adding an MDF2 will double the size!)If anyone has got this working to a sequencer (or sysex app) then I'd be grateful to hear from you.(or if anyone has a cheap MDF2 they want to sell me )Cheers,Paul. Hi Paul,Welcome to the forum! I use MIDI-OX for sysex transfer, it allows for monitoring of MIDI data/events in great detail and in addition it has handy features to slow down/pause sysex transfer for those older machines that need more time to 'digest' the data. What I suspect is that your SU10 might need some breaks during the transfer (something the MDF2 no doubt does), so it would be worthwhile to check your preferred SW package for possible MIDI data buffer settings (buffer size, pause between buffers, etc.).If you specify the software you use we might be able to help better with the details. In case you try MIDI-OX you'll find these settings under 'View/Sysex.'

1. Send Midi System Exclusive Messages Data To Ensoniq Sd1 From A Pc Computer

1 / Run your sysex transfers program on your computer and load or open (depending on the program you are using) the sysex file you want to transfer. 2 / Choose 'Sysex send' (or the appropriate option) on your sysex transfers program. 5 / You must now see 'RECEIVING MIDI SYSEX' on your WS display. RECEIVING MIDI SYS^EX DATA ON THE SQ-1 The receiving of data dumps is initiated automatically by system exclusive messages sent from the transmitting unit, No front panel commands are necessary to receive dumps if the receiving of System Exclusive messages is enabled (Edit Sounds, Bank 9. MIDI data is a serial stream of bytes (31,250 baud, asynchronous, 1 start bit, 1 stop bit) representing MIDI commands. A MIDI command comprises a status byte followed by a variable number of data bytes (possibly none). Status bytes are identified due to their top bit being set.

Then 'Sysex/Configure.' In the resulting sysex window. OK, I did some testing of MIDI OX settings last night.Firstly I tried adjusting the Low Level Input Buffers and Low Level Output Buffers.I wasn't really sure what I was doing, so I just kept increasing them.

I got up to:Size 10240 BytesNum 512And still couldn't get the dump to workThen I started experimenting with the Output Timing sectionThe auto adjust option didn't seem to make any difference, and neither did the 'Delay Between Buffers' seting.However the 'Delay after F7' option was interesting:When this was off, the entire dump was sent quite quickly, and the SU10 gave the 'Wrong Data!' 3) When sending Sysex, some gear needs a break after the end of a SysEx message (signaled by F7) to process that message before it can handle another message. Since some messages, like loading an entire bank, frequently are composed of smaller messages, your gear might not be able to handle a composite message at full speed.

By checking the Delay After F7 box and specifying a time in milliseconds, any composite messages will wait the specified delay before sending the next message. Or, if you just want to break a large composite SysEx message into individual chunks and don't need the delay, you can check the box but specify a delay of 0.4) You can also optionally specify a delay after each buffer is sent. Some gear might have a small buffer to receive SysEx (say 256 bytes) and might not be able to process this data fast enough, so the bytes after the first 256 are ignored. In this case, you could set an output buffer size of 256 and then specify a delay of 100 milliseconds (or whatever is necessary). This delay will allow your gear enough time to process the buffer before the next 256 bytes are sent. You should be able to tailor the speed to fit any situation.

As an extreme example, you can select one buffer, one byte in size and specify a delay of 1000. This means you would be sending data at the astounding rate of 1 byte per second!Reports are that there is also a problem with some cheap MIDI class compliant devices under WinXP, being only able to send a sysex chunk (data between two F7 bytes) at once, not per byte or interrupted anywhere between the two F7 bytes (meaning that your buffer size must be equal or larger than the largest sysex chunk your're trying to send). While I'm not sure why this problem occurs and have not experienced it myself, in such cases it might be a good idea to try another MIDI interface for a test.

OK - I've done a bit more testing.The entire dump is 479415 bytes. It looks like most of the data packets are the same length - 400ish bytes.So I've set the input and output buffers to 512 in MIDI OXI'm not sure how many packets there are in the string - I counted up to 100 F7's in the text file (before I got bored!) and I was less than a quarter of the way through the file. So I'm guessing there's well over 500 packets.So do I need to set the 'Num' setting to more than 500??Changing these settings has made no real difference to the problems with speeds. I've managed to work out I can get the delay between F7s down to 5150 milliseconds, but any lower and it gives an error.I can't believe that data dumps from the MFD2 would be this slow (or maybe because it is reading data from floppy, the delays from the drive slow it down to this level?)It's eally frustrating that this process isn't easier - it's a serious disadvantage to what could be a great little unit!Thanks for all you help and thoughts - if anyone has any other suggestions (or experience of success with this) then please do let me know.CheersPaul.

MIDI-OX.GIF (13.7 KiB) Viewed 1794 timesLow level input buffers you should not worry about - just leave them alone. But if running out of options and you want to play it safe, set the size to some large value (1k, 8k, 32k or something similar), number of buffers should be a few (between 2 and 32, go for the higher, if you lose incoming data to MIDI-OX - not likely your problem).Low level output buffer size, number and delay are the parameters you want to tweak. The values on the screenshot should be fine for many older synths. Keep the number of buffers low (e.g. 1), size of the buffer low as well (between 16 and 512 bytes - but just for a try you might want to give it a shot with a large value, like 32k, if all other options fail). Delay between buffers should not go above 500 or 1000 msec, but these are already enormously high values - remember, total transfer time will be a function of this delay, multiplied by the number of packets (the smaller the buffer size, the higher the number of packets for the whole file).

Delay between messages (F7) should not be much more than doube or quadruple of this value, at most - but you should be able to lower it to the same value as the delay between buffers or pretty close, once you've found the ideal inter-buffer delay.A golden rule when troubleshooting: always change only one parameter between attempts. I can't believe that data dumps from the MFD2 would be this slow (or maybe because it is reading data from floppy, the delays from the drive slow it down to this level?)Yes, it is slow, and floppy reads likely help with the gaps. Floppy MIDI data filers should work around 1k buffer size and up to 500 ms delay between buffers. Plus, it seems that the SU10 relies on receiving data at the same speed as it has sent it (hence the SEQ mode requirement on the MDF/QS/QY, as highlighted in the manual), so it might be that you'll never get acceptable results with MIDI-OX.

In such case you'll need a realtime sysex recorder (mostly HW sequencers are capable of this - probably DAW SW can be tricked into it, too, but you'll need to dive into the manual for that).On the other hand, 479415 bytes over MIDI take around 3 minutes even at the highest speed without breaks, so with the necessary gaps, processing, etc. You're likely to need about 10 minutes at least to transfer such a file - just so as to manage your expectation. Try to create smaller dumps, if you can.Hope this helps. Thanks - really helpfulTried the settings (and the suggested variations) mentioned above, but it still refuses to accept the transfer until the delay (either between buffers or after F7) is over 5 seconds.I did try recording the sysex dumps into Sonar when I first started testing this, but maybe I'll go back to that idea and see if I can make that work.The dump from the SU10 is relatively quick (probablay around the 10 mins mentioned in your post) - and I'd be very happy if I could get it to receive dumps at that sort of speed.I'll keep trying ideas. Yep, just tried Sonar again - the inbuilt Sysex editor won't transmit the packets (presumably 'cos I can't set the delay settings like MidiOX)Tried recording to a track (I've enabled SysEx recording which is disabled by default) - it records the first packet (which is a short on - about 14 bytes), but then although I can see the subsequent packets being transmitted through the midi interface, Sonar does not record them - must be a size issues (the majority of the packets are much larger).I'll have a look to see what other software I can find that might cope with this better.

OK, one last suggestion, then: try to set the output buffer size to something like 4096 or 8192 (number of buffers still 1) and keep inter-buffer delay at 5000 ms (or whatever you've found working), HOWEVER, switch delay after messages (F7) off (untick). This should give you a faster transfer and hopefully no errors.If this does not solve the problem, then it means that the SU10 needs the 5 seconds pause exactly at a specific point during the transfer and this will be impossible to automate. In this case your best bet will be to go back to Sonar, but you'll have to make sure that syx data will be paced out at the same rate (5 sec pause included at the critical place) as it has been received from the SU10 when dumping.Good luck and keep us posted for the benefit of others!P.S.: some useful reading about Sonar and realtime sysex. Another alternative (if you fail to find a 'realtimer' and SU10 remains) would be to split up the SYX into two chunks (you'll figure it out how, I guess) and send the two parts manually with the break between.

I'd go the 'binary search' way, cut the SYX at the half, if the first half goes OK then add the half of the second half again, etc. if does not work, cut the first half into two again, etc.Of course slicing will have to be done at F7 bytes, as otherwise you get an incomplete message. Probably some header information will have to be added to the 'new' chunks.Logic and other sequencer soft seems to work fine, Sonar is a bit of a b.ch for this, it seems -that's why I suggested the link.Yeah, upgrading the SU10 looks like a reasonable idea, if you're into sampling.

⇝ ⇝ Ensoniq ESQ-1The ESQ-1 is a 'hybrid synthesizer' in that it has digital oscillators, but analog filters. Other synths with similar architecture are the, (and DW6000), and (and K3m).The ESQ-1 has three digitally-controlled oscillators available per patch and its analog filters use Curtis CEM 3379 chips.The Ensoniq ESQ-1 is known to have been used by Skinny Puppy, Jean-Michel Jarre, Front Line Assembly, John Carpenter, and Depeche Mode. Sequencer ExpansionsThere are two sequencer expansions that have been produced for the Ensoniq ESQ-1.

The SQX-10 expands the sequencer to a 10,000-note capacity, while the SQX-20 expands the sequencer to a 20,000-note capacity. Both are cartridges that plug into the mainboard via a slot in the back of the ESQ-1. Sound CartridgesA handful of manufacturers released sound cartridges for the ESQ-1.

Among the most popular were Ensoniq's Voice 80 series, Eye & I's Voice Crystal series, and Syntaur's Soundset series.How can I tell what operating system version I have?When you first turn on your ESQ1 the display will show the version number in the lower right just before it displays the patches.The firmware is stored on two EEPROM chips, one containing the 'high' and one containing the 'low' ROM image. The low ROM chip is in the chip socket labeled 'U18' on the main board, while the high ROM chip is in the socket labeled 'U17' on the main board. Operating System HistoryKnown bugs in Version 1.7:1. Selecting a different song while a sequence is running can cause a system crash.2. Performing any of the following sequencer functions when there is very little sequencer memory remaining can cause a system crash:a. Saving or merging a trackb. Erasing a trackc.

Recording a track3. The system will occasionally lock up after loading data from MIDI. The data transferred intact, but the ESQ-1 never returns from flashing PLEASE WAIT. Turning the unit off and on again cures the problem.4. The first time that MIDI data is loaded after powering up the unit, the unit has a tendency to fail to load; the display will read TARGET SYSTEM NOT RESPONDING, even though all connections are correct.

The data load will be successful if tried again.5. Due to 'jitter' on the part of the Data Entry Slider, parameters on Programming pages and Tempo on Sequence pages will sometimes jump to the present value of the slider.Known bugs in Version 2.0:1. It is possible to set the pitch bend range outside the legal limit (49 to 63).

It is necessary to re-initialize the unit to reset the pitch bend to the proper range of 0 to 12.2. The sequencer sometimes fails to accurately record SUSTAIN pedal information.3. The sequencer will sometimes play back key down events with velocity of 0 if the key had been recorded with a low velocity value.4. In MIDI MONO mode, the ESQ-1 may not properly receive program changes on all channels.5. When syncing to tape, the sequencer will sometimes play the first note of the sequence as soon as the user presses play, putting the rest of the sequence out of sync.Version 2.2 fixes/adds the following:1. A parameter was added to allow the CV Pedal to be used as a volume pedal as well as a MOD Pedal.2.

Allowed data dumps to disk drives capable of accepting generic system exclusive messages.3. Allowed compatibility with MIDI Guitar controller.4.

Keygen-Lz0Author: 26 January 2011 Views: 7008. Yamicsoft Windows 7 Manager v2.0.8 Incl. Keymaker-CORE 15.55 MbWindows 7 Manager is a system utility that helps you optimize, tweak, and clean up Windows 7. Last xp v20 iso key. Boot Disk v.5.1.3 Windows Edition 2011 143 MBOriginal title: Active @ Boot DiskOperating System: Windows AllRozdache version: 5.1.3Year: 2011Language: EnglishActive @ Boot Disk - a bootable CD based on Windows PE 3 ( Windows 7), which contains a powerful set of tools to recover lost data, reset passwords, user.s Windows, system backups, securely erase data beyond recovery and much more.Comments (0)#6:: WOAT v3.1 - Windows 7 / Office 2010 VL Activation Tool (OEM/KMS Activator)Author: 28 January 2011 Views: 8835.

Ability to output a tape sync clock when syncing to MIDI clocks as well as when syncing to tape.Version 2.3 fixes/adds the following:1. 40 internal patches are loaded from the OS rom's after initialization.2. Fixed a bug which caused erratic operation when using the LOCATE function by more than 16 bars.Version 3.0 fixes/adds the following:1. Added sequence editing features which allows addition and deletion of variable bars at any boundary within a sequence.2. Ability to rename songs by pressing the soft button above the song name on the SONG EDIT page.3. Allowed startup screen to automatically switch to last selected internal page.4.

VELOCITY parameter renamed to TOUCH.Version 3.0 adds the following:1. Ability to remain in SONG mode even after unit was turned off.Version 3.4 fixes the following:1. Corrected a sequencer problem which prevented the ESQ-1 from recording correctly with synchronized (SYNC=MIDI CLOCK) with units which send clocks continuously.Version 3.5 includes the following:1. Corrected waveform pointer in EPNO2 waveform.2. Restored the values of the TOUCH parameters to their original and correct order, HARD, MEDIUM, SOFT.

How do I perform a Hard Reset?If you are unable to re-initialize the unit due to scrambled software (i.e. The keyboard not responding), you can clear the RAM by following this procedure:Make sure the power is off and the power cable is disconnected!For METAL UNITS: short the right side lead of CR1 to C1.For PLASTIC UNITS: short the right side lead of C18 to the left side of CR3. How do I know if I have a 'Metal' or 'Plastic' ESQ1?The metal versions of the ESQ-1 don't have a heat sink on the back and have a serial number from 9 with a main board assembly number of 1.The plastic versions of the ESQ-1 have a heat sink on the back and have a serial number of 25000 and higher with a main board assembly number of.There are no interchangeable parts between the metal and plastic ESQ1's.

Send Midi System Exclusive Messages Data To Ensoniq Sd1 From A Pc Computer

SpecificationsYear Released: 1986MSRP: $1295Keyboard: 61 keys with velocityPolyphony: 8 notesMultitimbral: 8 partsUser Patches: 40ROM: 64 KB (32 8-bit waveforms)Sequencer Memory: 2,400 notesScreen: 40 x 2 character fluorescent displayPatches: 40 (40 User-Programmable, Expandable to 120 With Memory Card)Newest OS Version: 3.50 User Demo VideosRating.