DSP56300Emu v1.2.25 - 8.1.2023 --> https://dsp56300.wordpress.com/downloads/

 

This synth ranks up there with Odin II, Vital and Surge as among the best free ones available.

 

OK- just send me a PM...
====================================
=] For my Virus Library, please PM to avoid spamming the thread [=

 

Last edited: Jan 13, 2023

Changes since 1.2.20 (looks like 21-24 builds were alpha):

DSP563xx Emulator 1.2.25 Change Log (2023.01.08):

Osirus:
- [Imp] DSP56300 plugins are now also available in CLAP plugin format
- [Imp] Faster startup time
- [Imp] LCD parameter changes are now also displayed for Dropdown Menus, Toggle Switches or when
modified via Midi or Automation
- [Imp] Parameter link toggle switches now work as intended
- [Imp] Prev/Next buttons now select preset browser patches instead of ROM patches if a preset
browser patch was selected last
- [Imp] More save options have been added, either save one Single, or the current arrangement (if
in Multi mode) or a whole bank
- [Imp] All save options now support saving as either .syx or as .mid

- [Fix] Preset export created incorrect preset if exported from any part but the first
- [Fix] Multi controls (part volume & pan) did not respond anymore after switching the active
part and displayed incorrect values
- [Fix] Performance issues when using automation
- [Fix] Controls may have displayed incorrect values if a preset was loaded from an
older Virus version
- [Fix] Do not attempt to process invalid Single Dump SysEx message the part number is invalid
- [Fix] Possible Audio Input crackling issues (Depending on the host sample rate)
- [Fix] Incorrect waveform labels for Oscillator 1 & 2 (Wave 2-63 => Wave 3-64)
- [Fix] Fix GUI scaling issues on various platforms / hosts
- [Fix] Fix weird sizes of popup menus
- [Fix] Do not open our own popup menu when right clicking while editing the patch name
- [Fix] Plugin may not emit any sound after the plugin state was restored (if part of a
previously saved project)
- [Fix] Some UI elements didn't update their state correctly
- [Fix] UI may send incorrect control changes back to DSP after changing patches
- [Fix] Loading multiple Singles via bank load (file with more than one Single) didn't load all
Singles but only the last one
- [Fix] GUI related crash after switching skins
- [Fix] Latency setting was not applied before editor opened

Test Console:
- Fix demo song couldn't be loaded from ROM

DSP:
- Performance improvements (5-10%)
- Stability improvements
- Large speedup of code (re)generation. Results in faster startup time, reduces hiccups
in Multi mode and when changing patches

 

You can run incoming audio through the filters? How? I know you can do it on the hardware but I didn't think it's possible with this. I mean I've got the basics down and have used delay, reverb, chorus and even EQ for incoming audio but I can't figure out how to use filters.

 

The Usual Suspects Osirus (DSP56300 Emulator) 1.2.29 MultiOS + ROM's [FREE]

DSP563xx Emulator 1.2.29 Change Log 1.2.29 (2023.02.13)

* DSP performance improvements 15%-20%
* Osirus can now boot from OS update .mid files. ROM binaries are no longer required if a pair of ``first....mid`` and ``...second...1024.mid `` files are found next to the plugin. The second file is optional. If Osirus is booted with the first file only, no ROM presets are available
* Patch Browser can now load presets from .vstpreset, .fxb and .fxp files, including those saved by the Access Virus TI Control Center and the Access Virus PowerCore
* File names of plugins have been modified to include Osirus in its name

* Fix plugin state not correctly restored if a Virus B ROM is used
* Fix swapped left/right channels and phase issues
* Fix UI didn't update play mode correctly in some circumstances when loading a .vstpreset / .fxb / .fxp
* DSP thread now runs at higher priority (Mac/Linux)

 

I posted a comment on sister site for the newest release, but figured i'd post a similar question here.
I wonder about the necessary .bin files. It seems (by HASH) there are duplicates.
LIKE THIS
When I began using this i was confused about the naming, and then found the same hashes and wondered even more...
If they are truly duplicates, why not remove them? Is there something I am not getting about them?

 

Copied to VST3. Ran command for Catalina. What am I doing wrong?

sudo xattr -cr /Library/Audio/Plug-Ins/VST3/DSP56300Emu.vst3

xattr: No such file: /Library/Audio/Plug-Ins/VST3/DSP56300Emu.vst3

 

"DSP563xx Emulator v1.2.9" the VST3 is now called differently: Osirus VST3
If you have problems delete the old one: DSP56300Emu.vst3

 

Last edited: Feb 17, 2023

Ah ok. Thank you

 

For those who've studied the DSP56300 Technical Info for reverse engineering (located here: https://dsp56300.wordpress.com/virus-c-technical-information/)...

Has anyone been able to locate the Spectral Waveshapes data in the "virus_c_650x352.bin" using IDA? If so, has anyone had any luck modifying & replacing the waveforms?

It would be nice to replace some of the factory waveshapes with some classic waveforms like the JP-8000 Supersaw, Virus TI Hypersaw, etc.

We just need to find the ROM data location for the waveshapes, convert our favorite single-cycle waveforms to the compatible data format, replace the waveforms we don't intend to use, and load up the modified ROM.

As many of us know, the Virus C has 64 spectral waveshapes available in the ROM. No. 1 is a sine wave; No. 2 a triangle; the remainder of the 62 waveshapes feature different combinations of frequencies. (It would probably be best to leave waves 1 & 2 alone, but replacing any of the other waves is fair game although it would have unexpected results when using pre-existing presets made from stock waveshapes.)

The 64 spectral waveshapes are static single-cycle waveforms that do not change over time. They are available in all versions of the Virus. (The Virus TI series added wavetables that can morph over time unlike the original spectral wave shapes.)

Here is what the 64 Virus C waveshapes look like:
http://www.waf80.de/virus/viruwaves/

And here's a downloadable .pdf of the 64 waveshapes (analyzed with Amadeus Pro):
http://www.vo1t.com/Euro/Illustrated/AccessVirusWaveforms.pdf

If you have any info, please share or PM me.

And remember... DO NOT discuss reversing on the discord!

 

Last edited: Feb 17, 2023

1.2.29 AU is not being validated in Logic Pro X. It Works fine in other DAWs. MacBook Pro M1 running Monterey. The mods over there are aware of the issue and are trying to fix it.

 

First versions on my i7-3770k were insanely heavy to play with, only one instance in a blank Reaper project, and only basses and simple tones, without effects, no sustain no release, they were good, but almost couldn't play pads, leads, chords, fast arps, were too glitchy system killas... Since earliest 1.2.0 it became better and better, and couple versions before 1.2.18 were almost non-glitchy. Since 1.2.18 and higher it is perfect.... Didn't test 2 or higher instances. Imho, it is good now)

 

Yeah, i'm still on 1.2.25
Have no Internet, laptop is dead. I do massive updates of software once or twice a month, using my grandma's PC ahahaha. So week later or two will try, if nobody uploads 1.2.29 beta)

EDIT: Found it)

 

Last edited: Feb 24, 2023

Runs well enough I am starting a project that will be full of Osirus...
The ones highlighted in the performance meter are Osirus..
Not the most CPU intensive, as I was going for sounds but now I will tweak the unison& etc and search for more CPU heavy patches...
Forgot to say : i7-7700 3.6Ghz non-K (no OC)

 

Last edited: Feb 22, 2023

So I figured out why I can't view the ROM properly in IDA... in their documentation they say to:

"Remember to use our tool `be2le.py` in the `dsp56k` directory to convert
it to little endian so that you can load it up into IDA Pro."

I have Python. I've navigated to "dsp56k" in Terminal. I drag and drop the be2le.py command and drag and drop the .bin (which is also in the dsp56k folder). Then when I run the command, all I get in Terminal is "<input_binary> <output_binary>". It's not converting the file.

Can someone please explain to me like I'm 5 how to do this properly, so I can properly convert the ROM and view it in IDA?

 

it look just like a simple case of incomplete syntax to me. you should be doing in your terminal: be2le.py <drag your binary><enter a name for new file to be created, in correct format>

 

Well, I think that got me a little closer. Instead the Input/Output brackets, I get this error:

ERROR:__main__:Expected a multiple of 24-bit words, size=524288

I tried putting in the same file name, different name, with and without extension, random letters and numbers. There must be something specific I'm missing.