Thanks, I tried this but still see no devices/synths in the Install window. I guess I'll have to use Midi Quest instead. For downloading Sounddiver, did you use the same Internet Archive link I posted above to download it or did you already have a copy of it?

Weird, depending on where that cracked version installs itself, check in the SoundDiver folder for a Diver folder. That should be full of all the dll's, ADA's, etc for all the synths.. Maybe that didn't get installed??

Just try launching the Sound Diver app you Ported again -- when it launches during the install the models window is blank. Close that so the install fully finishes then launch the app again and all your models should be there ready to be installed, along with your MIDI ports.

Has anyone here ever hooked up an Akai S1000 to SoundDiver? I have it hooked up over here and SD is communicating with the S1k and retrieves basic info like how much memory it has and program and sample names, but when I try to edit a program I get a lot of 'waiting for incoming midi data,' often followed by Sysex communication errors and 'S1000 didn't reply/respond' errors. It's weird that it can collect the basic stuff but the editing of programs seems a no go. Or maybe there's a setting in SD or on the S1k I'm missing? Afaik it's the only editor out there. It would be nice to do basic program editing via sw.

My E6400 Ultra is an odd one when it comes to SD. AFAIK, it will only work on the currently loaded programs in memory, at least for the EMU. I tried using it the first couple of times I had it setup in SD, and ended up wiping out some stuff because some command I hit loaded a bank and overwrote what I was working on (and I can't figure out how I did that either).

I wouldn't mind that 1st prog limit on the Akai because I'll only be editing that stuff via sw during sampling sessions. I plan on using it more like a module once I've got a nice library built up in there. Turn it on, load a prog or two and sequence from the DAW. For Emu samplers you should really check out ZoeOS. A lot more modern than SD, works great and you can edit multiple pros at once. Discontinued but still findable.

Have it installed on my 'media' drive but I haven't checked if it runs on the M2 Mac yet. I can't even remember the last time I used it, there were some things I couldn't quite figure out with it as far as loading and saving whatnot.

Even better though, go to the EMU.tools website with a browser that supports WebMIDI and edit it like you're on the front panel! If it's one or two things, I just reach over and do it on the sampler nowadays, but if it's patch making time, the web interface is great. It's super quick to move around once you learn the EMU's key commands. If I had the ASCII connection on mine, I'd probably just do everything with a keyboard in my lap.

Yeah there's quite a list of quirks using these things, but you get used to them after a while and learn which threads not to tug on and where to be gentle. I have the ASCII extension also and can confirm it is the absolute bomb diggy. Where Zo comes in handy is for stuff like the mod matrix. Super snappy. Tell you what though, even with graphic representation, I still can't figure out those damn Emu envelopes. So weird!

The answer to this was bad quality midi. Not sure if connection or cable, but it doesn't matter. Have since hooked it up with a Roland UM-One and am now editing the current program on the fly, all params and sample selection included. Also hooked it up with an ES USAMO, and at this point it feels almost on par with an itb sampler.

Shit is nuts

Hi

This is mostly working good here, macOS 13.6.2, install using Porting Kit (Windows XP). I'm able to open my old libraries etc.

I just can't get MIDI ports to show. For example, when I go to install a synth I get the "Scanning" window with 'Abort' and 'Skip' but all the fields are empty, suggesting that my installation does not see my osx midi setup.

Any suggestions where I should start looking? Thank you!

Click "New" -> "Install..."

Select the device from the install list and click the "Add" button.

Your device should now show in the Setup window.

Click the device in the setup window to set the parameters for that device.

You can select your Out Port and Input, which will give you the list of your MIDI ports.

Yes - unfortunately when I select a device and press "Add" nothing happens. No response.

The only buttons that cause any activity are "Scan" and "Scan All" which both bring up the scan dialog (with all parameters blank)

"Add" will not initiate any communication with your device. Check your Setup window. If your device already exists there then close the install window and proceed with the other steps I gave.

Thank you! My Setup window contains only 'Computer'

BTW I am an original SD user from 'back in the day!' so am familiar with it - just seems this issue over device install/midi ports seems to be eluding me.

Just a thought - the Porting Kit install I did used 'Windows XP'. Would you recommend a different windows version?

So, just to clarify, even if I click 'Add' my Setup window remains empty.

Hm I guess first double check that the executable being launched by your app is SoundDiver.exe. Open Porting Kit and then right click the app you ported and check the properties. If you're running SoundDiverAuthoriser.exe then SoundDiver will open but it won't function correctly, though the Install window would usually be empty in that case.

If you have a full list of devices in the Install window but clicking Add doesn't add them to your setup then something must be wrong with the install.

Did you do the install by choosing New Custom Port? Or did you click Add Application, or right click the Setup.exe in the SoundDiver install folder? Definitely only do New Custom Port. Windows XP is the OS that I chose.

Thank you -

Definitely appears to be some kind of graphics issue. After trying a few re-installs using XP I managed to get adaptations to add - but am getting strange graphic errors on the left of the setup window - see pic.

https://ibb.co/hLcq5CZ

Can I ask what version of Wine you installed under? I tried the latest (Wine12)

Huh, very strange. I left the Engine as my default, which for me is WS11WineCX21.2.0. I also left the Window driver as Mac Driver, also my default.

I wonder if it's a Ventura issue? I'm on 13.6.2, what do you use? Thanks

I'm on Sonoma 14.4, I think I did the install in December though, so been working to last few versions.

When I had issues using Wine Bottler and other non-Porting Kit solutions the last few years they were never graphics things like in your screenshot, and those would have been Ventura and older versions. Like I said, it's very strange to me.

Ok I’ve figured it out.

Peculiar one. I have multiple USB midi interfaces. A mioXL and a Komplete Kontrol.

If both are plugged in, I get the graphic errors, and the available MIDI ports in SD are incomplete (as well as not selectable even with arrows/shift&enter).

If I unplug either, everything works as expected!

So my solution is when I start SD I leave one of them unplugged (the Komplete Kontrol), then once the app is running I can plug it in again.

A bit of a workaround but frankly to have SD working again it’s worth it.

Thanks for your help

Glad to find this thread, still alive in 2024!

I have a stupid question on adaptation programming:
The manual is some 300 pages so before I might waste my time I might be better off asking since there seems to be quite a few adaptation programmers here.

How complicated is it to write/edit adaptations?
Which tools are necessary apart from the manual?

I've used Sounddiver so I basically know how it works, and also I know how midi works in general and some programming, although not a pro developer.

My starting project would be an Yamaha SPX990 adaptation (librarian only) I found where there's an error. The second last byte of each patch message (there are 100 sent) is lacking when Sounddiver uploads the patches back to the machine. So I though it might be possible to find this bug if it's not too complex to get started.

Also, are adaptations cross platform? I'm on Mac Intel.

I still think midi 2.0 and everything that is coming will adress this library program and what it can do with legacy midi 1.0 devices.

Hi, there are a lot of Midi 2.0 topics. Maybe you can post a link to where you posted?

MIDI 2.0 news

Here you go.

Decided to compile the step by step instructions of how to install SoundDiver using Porting Kit:

1. Download the files from archive.org
2. Install Porting Kit
3. In Porting Kit choose "New Custom Port" (don't "Add Application" or launch the exe with Porting Kit)
4. Select "Windows XP" as your Windows version, leave the Engine as default
5. SoundDiver will launch after the install, but it won't work yet. Quit this instance and then run the newly installed SoundDiver App from Porting Kit.
6. Click New -> Install, then select a device from the list and click Add
7. Your device will now show in your setup window, select it and then set the Out Port and Input to your MIDI device

Sorry, I'm jumping into this thread late. Is it possible to "share" a MIDI device or port used in SoundDiver running in a virtual Windows XP environment within (?) Porting Kit with your DAW running in macOS Sonoma, for instance?

That's been my problem in the past trying to use SoundDiver on my Mac running in Parallels. I can get the program to communicate with my MIDI devices. But only if I am not also using my Mac DAW to communicate with those hardware synths.

Try running sounddiver first before starting your DAW.

Porting Kit is a completely different type of emulation than Parallels or VMWare and should have far fewer issues like the one you were having.

Definitely worth the 15 minutes it takes to install to give it a try.

In case anyone is having authorisation issues, I was running 3.0.5 fine for a while until it started asking me to inset the install CD and wouldn't let me get into the program anymore. A simple reinstall of the 3.0.5.4 (last ever release) available on archive.org over the top of my already installed version seems to have fixed it. Also, for those who don't have anything in their adaptations box, if you're running win10, this post might be useful

Or maybe try installing 3.0.5, which definitely has all the adaptations. At least on my win7 machine.

You can re-authorize an existing install when it runs out -- open the properties and change the end of the Target from SoundDiver.exe to SoundDiverAuthoriser.exe, run it once but quit immediately, then change the Target back to SoundDiver.exe again.