Yes, maybe. I tried to install the windows version under Wine, but there is doesn't work.
Can you tell me where these two directories are installed in windows? Maybe I can check then where Linux is trying to put them and failed for some reason.
But hey, it's great that you thought about Linux users!

 

These folders are created by MAME and contain the SD-1's memory and cfg files. Where it save it depends on which OS or DAW you're using: For example on macOS/FL Studio: FL Studio 2025.app/Contents/Resources/FL/ on Windows: %localappdata%\Temp I think
I've never heard anyone say that these files are on the Desktop.

 

I tried placing the sd132.zip file in other places and locate them with the program, but no luck. It keeps placing the two directories on my desktop. Well, sometimes it is just what it is. Thanks anyway for your good work!

 

Spoiler: Perplexity KI - Maybe it Helps!

On Linux, temporary files are usually in folders like /tmp, /var/tmp, or a user session temp area such as /run/user/<uid>, rather than on the Desktop. In FL Studio, the user data and related files are normally stored in the configured data folder, not the Desktop.

For your SD-1 / MAME case, the fact that it keeps creating the two directories on the Desktop usually means the program is using the Desktop as its current working folder or a fallback path, instead of a proper temp directory. On Linux, the next place to check is whether the app is honoring TMPDIR, TEMP, or TMP, or whether the wrapper/launcher is forcing the Desktop as the working directory.

A practical Linux temp-file target is:

• /tmp
  
  
• /var/tmp
  
  
• /run/user/<uid>/
  
  
• possibly a per-app cache under ~/.cache/
  

If you want, I can help you figure out the exact Linux path that your SD-1 build is using and how to redirect it away from the Desktop.

On Linux, MAME’s default config and output folders are typically under ~/.mame/, including cfg, nvram, sta, diff, and related files like mame.ini and ui.ini.
For your specific question about SD-1 cfg files, the usual path is:
~/.mame/cfg
If you are using a custom mame.ini, that file can override the default and point cfg_directory somewhere else, but the standard Linux setup still uses ~/.mame/cfg. If files are ending up on the Desktop, that usually means the emulator was launched with the Desktop as its current working directory, or the path was not set explicitly and it fell back there.

 

Thanks for helping PulseWave!

I created a ~/.mame/cfg but still no luck. Also no mame.ini found.

I have no idea how to change that? I use Reaper to start the plugin.

 

I have Linux Mint and I have tried the Linux version of this plugin as soon as it was released. However, until you pointed the case here, I haven't noticed that I also have those two directiories on my desktop.

 

So can you look where these two directories are located in Mint?

 

Both are in /home/mint/Desktop.

 

That is weird? Is your userid "mint"? My userid is paul and the two directories are in home/paul/Desktop, so that's on my desktop.

 

Actually, I have a "live" (portable) Mint on USB. (For testing/learning purposes.) Not a full installation on disk. That may be the reason.

 

A live USB? Ahh....yeah, that may be the reason.

 

Spoiler: Grok KI

Yes — that sounds like MAME is using the config location for your account, not “mint.” Since your userid is paul, the default per-user MAME folders would normally be under /home/paul/.mame/, not ~/Desktop. MAME’s default setup expects mame.ini and related files in ~/.mame/, and one common way to create mame.ini is by running mame -cc or using MAME’s own “Save Configuration” option.

A couple of important points:

• ~/.mame/cfg is only one piece of the setup; MAME still needs to know where to look for its main config file and search paths.
  
  
• If no mame.ini exists, MAME may just fall back to defaults unless it is started with the right config path or the config file is created first.
  
  
• If your plugin is being launched from Reaper, it may be inheriting a different working directory or user environment than you expect, which can make MAME place files somewhere surprising.
  

The practical fix is usually:

1. Create mame.ini in /home/paul/.mame/ by running MAME once with config creation enabled, or by using the UI to save configuration.
   
   
2. Make sure Reaper launches the same MAME/plugin binary every time.
   
   
3. Check whether the plugin is configured to use a custom config path instead of the default home-directory path.
   
   
4. If you want, explicitly point MAME to the directory in your home folder rather than relying on defaults.
   

So yes, those two directories ending up in /home/paul/Desktop is a clue that the program is using your user context, not mint’s. The bigger issue is that it is probably not finding a proper mame.ini, so it keeps reverting to defaults or creating files in the current working location instead.

A good next step is to check whether Reaper is launching MAME with a custom command line or sandboxed path, because that often decides where MAME reads and writes its config files.

 

When we investigate the core heart of the Ensoniq series - from Mirage ESQ1, SQ80, ESP, ASR, FIZMO, VFXxx..... they all have the core DNA of the DOC chip.
- which was usually commanded by the Motorola 68000 CPU.

Which was also the core of wave table (blaster) sound cards in PC's and the Apple Mac IIGS.

A great legacy !
Cheers Ensoniq ^_^

 

A manager (with custom folders, like The Usual Suspects is doing) will appear in upcoming v1.0 (I've seen a - closed - issue from GitHub, today).

https://github.com/sojusrecords/Ensoniq-SD-1-32-Voice-VST-emulation/issues/20

 

I have no idea how to do that?

Also, I have no idea how to check that either.

If it takes so much time to understand something, it is obviously above my paygrade...

 

The MAME SD-1 emulator writes these files to the current working directory. On Linux, most DAWs launch from the directory specified by the `Path=` setting in their .desktop launcher - on MX25, this likely points to ~/Desktop (or it is launched manually from there).

Modifying the Path= in the DAW .desktop file
You can find the DAW .desktop file in the /usr/share/applications/ or ~/.local/share/applications/ directory:
ini
[Desktop Entry]
...
Exec=/usr/bin/reaper
Path=/tmp ← this is what you need to add or overwrite

The Path= parameter specifies the current working directory at startup, and you have to modify it to Path=/tmp

 

That was it. Thanks! I started Reaper with a desktop shortcut without a working directory. Obviously Reaper then considers the desktop to be the working directory. Now I put /tmp and it puts the two directories there.Well done sir!!!!