Motorola DSP563xx Emulator (BETA) (Access Virus, Nord Lead, Waldorf MW...)

[rasmusklump]

Is there a change log for the beta versions somewhere?

yes,
on the discord server
but hasn't been updated since the x.x.12 release as far as i can see...
current rel is x.x.17

Thanks

[todd_r]

Anyone have this working in Reaper, the vst3 doesnt scan at all for me

*Edit, vst2 working

[Funkybot's Evil Twin]

Anyone have this working in Reaper, the vst3 doesnt scan at all for me

VST2 works here in Reaper. Did you put the ROM in the same folder as the plugin? If not, maybe it got blacklisted when it scanned the plugin and found the missing file.

[todd_r]

Anyone have this working in Reaper, the vst3 doesnt scan at all for me

VST2 works here in Reaper. Did you put the ROM in the same folder as the plugin? If not, maybe it got blacklisted when it scanned the plugin and found the missing file.

Git it thanks, yeah VST2 works, VST3 doesn't even show up in the blacklist

[gentleclockdivider]

Latest one is super buggy
Can't load sysex presets anymore (made with rom b )
Also pressing load (from top menu ) -then cancel freezes the gui and a hard shutdown of host is necessary

[hurricaneaudiolab]

I would really like this to work well, however, it doesn't - at least on 2 of my Macs. Loads fine, can browse presets without an issue, and when I first play a preset it goes well and the CPU barely registers. But as soon as I load a 2nd instance and start playing, I get CPU spikes like crazy and Logic spits out error messages. Keeping them loaded but not doing anything, makes my CPU go nuts. Then my system becomes unstable and the emulator is unusable. Happens both on my 2012 Mac mini running Catalina (which can handle practically everything), and a 2018 MacBook Air running Monterrey.

[Tj Shredder]

Deal with it as if it were hardware. You rarely buy two Viruses… There might be a clash between two instances if they share resources…

[rasmusklump]

I did a test on windows 10 with cubase 11 where I used 6 or 7 instances of the plugin without any problems.

[muki]

[…] But as soon as I load a 2nd instance and start playing, I get CPU spikes like crazy […]

no problems here
mac mini 2012, i7, 16GB ram that is
logic 10.5.1, mojave

running 3 instances of latest dsp v1.2.17 in loop
cpu at about less than 10% with occational cpu-spikes at about 75%

that's 1 instance per core
-> i should be able to add another 3 or 4...

here's a screenshot:



the 3 on the left are the 3 dsp instances
the big one on the right is the input

p.s.:
in logic it's better to have the input not focused on the dsp instance (when not necessary)

pps.:
but, yes, admittedly, logic acts up massively when switching programs
or when there are other synth doing something etc...
...so...well...

[muki]

and more:
actually works quite fluently win 2 instances
beginning with the 3rd, programm switching and other stuff might get problematic

and another ps.:
that's with virus_b rom
i find b more stable and less problematic...
whereas c has a higher polyphony count (if i'm not mistaken) which will cause troubles
b is lmited to 24 afaik...

[hurricaneaudiolab]

Here - this is what happens to me:

[muki]

Here - this is what happens to me:

wow! cool! with video

yes, i can see
that's frustrating

edited:

i now see, that you're using the same rom as i do

well,
all your questionmarks are cpu overloads
and from what i *think* polycount problems

tipp nr1:
i'd give the whole song more preroll (4-8 bars)
reason:
i might be wrong, but afaik the virus needs some time to
calculate DAW tempo
so maybe with all those poly i might get too much (for poor old virus)
so maybe, when you start playing and old-virus ist still calculating bpm-daw-speed
it might get a cpu peak with overload

just a thought...

...and if i understand the devs correctly,
a speciality in kemper's dsp code is, that it dynamically scales up
meaning that suddenly there are tons more of calculations
therefore the sudden peaks and spikes in a normally calm cpu-load
...again: i don't know if i understand this correctly...

tipp nr2:
(on jx8p preset) reduce release even more

it kind of looks like your mac can't handle the increasing polyphony

make some tests of how much poly you'll get until the sound gets gritty

for example, in the first incarnations of DSP
i was able to get only up to 20 or so
since no rom has the ability to reduce the poly-voice-count, afaik,
i was pretty much out of luck quite easily
but there was one version, that improved cpu immensely,
so that i was able to handle the 24polycount of b
c never worked well enough on my oldie...

there's a comparison chart, that says c has 32
but i seem to remember that a newer updated version even gets much higher (50s or so...)
but can't find that chart anymore...
...i *think* it was an official access chart, but they'vemoved it and have no search
on their site...

so:
using different roms might also be critical...


tipp nr3:
try the newest version 1.2.17
(from what i see, you're using 1.2.12)
this thing improves more and more...

[hurricaneaudiolab]

I have the same Mac as you - 2012 Mac mini, i7, 16gb ram, but I'm running Logic 10.6 on Catalina. Also using the B ROM. Guess I'll try 1.2.17 next.

EDIT: Playing that Jupiter patch on v .17 worked flawlessly for like the first minute - no cpu spikes, no stoppages - thought it was fixed (yay) but then I got a weird spike flipping between sections, and all of a sudden it seemed like things became unstable. Recorded an 8-bar section successfully and with minimal CPU action, but then the INTERESTING part is that when I keep the track active and in focus (that means having the track selected as it plays for all you non-Logic people) it plays without any hiccups. It spikes and crashes on me when I don't have it in focus, which is the opposite of what you'd expect. It's repeatable, happens like this every time. Highlight the track as it plays, and it plays fine. Highlight an empty track and hit play, it vomits.

[muki]

yes
can confirm (contrary to my expetations)
very interesting...

[muki]

so...some findings as to what *seems* to help (a little bit)

putting all audio/instrument tracks 1-2 bars later - letting dsp "breathe" a little...

1 instance works, 2 also more or less, 3 becomes critical

what dsp does not like is sudden changes in the timeline, jumping around
as soon as you jump in the timeline, the cpu load spikes
the more and often the faster there's a cpu overload

changing the i/o buffersize to something bigger like 512 seems also to help...maybe...

what i did:
letting logic run (akaplayback)
hit return - jump to start
multiple times
or jump around in the timeline to various parts while logic is running

works good with 1 instance, quite ok with 2, problematic to not with 3

hmm...