New features v2.1
In the development to make custom E-MU SIMMs, prodatum will be the tool that will help get there.
With respect to the preset and sample rom portions of the custom SIMM, the sample rom creation is pretty straightforward and the preset rom is not. The most natural thing to do is work inside the box, and then export sysex data where it could be converted into a writable SIMM file object. This development was one of the major pieces that helps to realize a custom SIMM.
My main development, and works for me. If you run into problems, please share.
I have started the user interface on a VM and if the exe doesn't work, you may have to download and build from source. Hey it's linux! If this is your preferred platform, the build instructions will get you there. Might be missing some dependencies which should be easy enough to sort out.
Update 12/30/22: I was able to verify the github agent build works on Big Sur 11.x and Monterey 12.x OS - with a couple tweaks:
- The prodatum-macos-x64 executable needs the .app extension added
- Moved the executable to the Applications folder
If clicking gives you an error after that:
- The security features may prevent the app from running (unknown company, etc.), so you will need to give the executable permission to run.
- Run the following line from a terminal:
sudo chmod -R 755 /Applications/prodatum-macos-x64.app - Then System Preferences -> Security & Privacy -> General tab look for a Allow button specific for an unknown application (s/b prodatum-macos-x64.app).
NOTE: Apple M1/M2 chips are not supported by Github currently, with no ETA. The builds in this release are specific to Intel Macs only.
The Command Station and Proteus 2000 were tested throughout, but alas I do not own an Audity 2000. There was a lot of existing functionality in the code to support it already. I did have preset dumps available to check the Audity sysex was unscathed in the conversions.
There were limitations in the previous versions that only work for a single preset at a time. This was File->Export for a single preset export or dragging and dropping a sysex file which would only import to the edit buffer (and then require a manual save). In addition to that, mixing and matching sysex dumps from the various hardware families could cause crashes.
This should all be fixed now.
- Export one or many presets for any given rom or user banks
- Import one or many presets into user banks (automatically handling the conversion between command station, proteus, and audity 2000)
- Export one or many arp patterns for any given rom
- Import one or many arp patterns into user arp pattern storage
- Export current user setup
- Import a specified user setup
File menu has changed. Export has been changed to "Preset - Export", because that is what it did.
If you make a prodatum-config folder where you run the executable, you will get a portable config. The other folders are up to the user.
The following pictures illustrate the sysex differences between the E-MU synths. Before 2.1.0, you would not be able to share with someone that has a different device than you. The sysex wrangling is handled under the hood, and now you can mix and match freely.
NOTE: When converting from a smaller file to a larger one, default values are inserted to make the transition work. Vice versa, if a Command Station patch uses the additional "M N O P" controllers, those controller values will be removed when importing to an Audity or Proteus.
Audity 2000 is 2 bytes smaller than Proteus 2000, and 10 bytes smaller than Command Station
Proeteus 2000 is 2 bytes larger than Proteus 2000, and 8 bytes smaller than Command Station
Command Station is 10 bytes larger than Audity 2000, and 8 bytes larger than Proteus 2000
Choose destination folder, and the ROM (or user flash), the preset bank and preset start and stop range.
Choose source folder, and you can multi-select the files within. This imports to user flash (4 banks of 128 presets each).
Choose destination folder, and the ROM (or user flash), the arp bank and arp start and stop range.
Choose source folder, and you can multi-select the files within. This imports to user arp bank (1 bank of 100 patterns only). There is a quirk with this step, please read on.
The E-MU operating system doesn't seem to save the loaded arp patterns across power cycles by just loading alone.
After prodatum import completes a banner will popup reminding you to complete extra steps. Close the popup.
Navigate to the MULTI menu, and scroll to EDIT_USER_PATTERN setting. I don't think it matters which pattern you do this on. Set cursor on the ID of the arp pattern showing, and hit enter. This will take you to the edit arp menu, and now every arp you have loaded should be committed to the user area now. The same thing occurs with the COPY_ARP_PAT in the SAVE menu if you try to do it manually without prodatum.
Using example above, this was my machine's state before importing:
After import, my machine's state. The arps can be used at this point, however if you power cycle - nothing is stored and we would be back to the first image (LILY).
Hit MULTI button, and scroll to EDIT USER PATTERN. Place cursor on arp pattern ID and press enter.
The edit arp menu is showed and all the arp patterns should be stored at this point. Only need to do this step once per arp import.
Can double check after a power cycle. Voila!
Choose destination folder and the current setup will be downloaded.
Choose source folder, the chosen setup will be uploaded to the setup specified. Can store up to 63 user setups (+1 factory that cannot be modified).