AWESOME

 

It looks as though it works. Feel free to test it on your own systems. You can copy and rename this virtual floppy disk, and then format it in EnsoniqMame VST using the synthesiser’s storage functions, etc.
It is a virtual 3.5-inch floppy disk with 1.44 MB of high-density storage.
It makes sense to save this ‘disk’ in the same ‘Documents’ folder as the firmware, but any other location should work just as well.
I suspect that the TUS version will offer a more convenient storage solution for your own presets. It should also work on Windows – but I still need to test that.
Have Fun
Edit:
I forgot to mention that I’ve saved the default sounds on this disc. So, as I described... just copy, rename and format it to create a blank Ensoniq SD1 floppy.

 

Last edited: Mar 22, 2026

Which floppy emulator are you using, I need a windows version? Thanks

 

HxCFloppyEmulator

 

Thanks, do you have to mount the image so that it shows up as a floppy on the OS to then get the plugin to load/save from that location? I've got some syx files so how would you load those?

 

No, I'm not there yet.

 

It's gonna include MIDIOX I am pretty confident. May try today.

 

Last edited: Mar 22, 2026

I hesitate to comment because in the next millisecond my computer will blow up.

I am on a Dell laptop Inspiron 7706 2n1
I uninstalled and reinstalled ASIO4ALL to current
I uninstalled and reinstalled the Realtek Audio available on the Dell website to current.



I can't tell you which of the two did it, or the combination. But my experience has come up to pro level.
No DAW shutdowns.

I'm getting GOOD performance with zero dropouts or crackles of any kind.

1024 MAME Buffer is a hard lower limit in the VST for me.

I've taken my DAW down to 128. To me - unbelievable. I've not run 128 for a number of years.



I am running 44.1k 16bit system wide at the moment.

I am concluding my conflicts were audio driver related. I've now got low latency and so far no shutdowns or operational glitches of any kind.

Oh and FFS ASIO4ALL is sending audio to my headphones for the first time.

All of a sudden this thing's become reliable. Anyone have any no start or unexpected shutdowns --> maybe reinstall your audio driver and ASIO4ALL (if using) and try at 44.1k 16bit systemwide to start. I guess.

P.S. I made sure all system audio enhancements were off. When the new Realtek driver installed, it had turned them back on.

 

Last edited: Mar 22, 2026

Thanks - I tried this, verified the changes, checked the frameworks were there in the bundle, and resigned (as terminal said the above changes will invalidate the code signature), and it still doesn't work here on Apple silicon.

Leaving this for now, will check back in with the TUS stuff...

 

No Problems here with Mac M1 cpu.

 

Trying to send SYX. Gonna have to be on another session. I can barely keep one plate spinning. MIDIOX is sending the data out like a madman. I haven't routed it properly once yet.

 

Last edited: Mar 22, 2026

I think the only solution will be to use a SysEx program to transfer data to the virtual SD1. If that works, I’ll be able to save the sounds to my virtual disk. It doesn’t seem possible to mount an Ensoniq-formatted disk and save SysEx data directly to it – I’ve tried several times today to open the Ensoniq disk on my computer... but I haven’t managed it yet.

 

Understood Headroom . I am going to try here after a full sleep too.

Here are some grfx

 

I hope there’ll also be a virtual F.I.Z.M.O. which I used to have many years ago.

 

No success on my side neither

 

Hello everyone! There’s a new build with tons of bugfixes and new features!
https://github.com/sojusrecords/Ensoniq-SD-1-32-Voice-VST-emulation/releases/tag/v0.9.7b

What's new in v0.9.7 beta?

• Full VST Automation for EVERY button (All keys, sliders and buttons. Now you can save presets: Saving requires holding down PRESETS button and pressing a BANK button)
• Heavy CPU and GPU optimizations
• Reworked GUI rendering and modified UI font
• Global settings saving
• Lowered macOS deployment target to 10.14 (Mojave)
• SHA256 checking for rom files inside sd132.zip
• Switched Windows graphics engine to Direct2D
• Updated build.md

Bug fixes

• UTF8 for Windows paths
• refined ANTI-SMART-DISABLE Protection
• Deadlock fixed at shutdownmame
• DAW blacklisting workarounds
• Updated macOS Jucer with frameworks flags and with no webbrowser, updated Windows Jucer with no webbrowser and plugins.zip

 

As a test, I converted a SysEX VFX bank into a *.mid file. In Cubase, I placed this file on the SD1 track and, using ‘Storage > Midi Record’, I managed to read this file (at a very slow Cubase speed, e.g. 20 BPM) as shown on the SD1 display... however, it then also displays ‘incomplete’. I’m getting closer, but it’s not working yet.

 

0.9.7 brings an ENORMOUS improvement in CPU efficiency.

 

I think I got MIDI-OX sysex data into Studio One, and to a midi track. Is it normal for a SYX transmission to happen in a fraction of a second? MIDI-OX takes awhile to 'send' and then I see evidence of the transmission in studio one extremely briefly as MIDI-OX's progress bar completes. Both in the MIDI Monitor and the MIDI activity band of the track. Just a blip.

Also, does this hex data look like a SD-1 bank? It must be because I have no other data moving around. I transmitted something called soundfx.syx

No data into SD-1 VST yet, it's not even loaded. I have to downshift and look over the manual to get SD-1 prepared to receive data.

 

Last edited: Mar 23, 2026

stupid

 

Last edited: Mar 23, 2026