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

[muki]

fyi
i just found, that dsp56k with B/C will quite happily load TI banks
tons of those banks can be found on the official virus.info site
also within the TI software installer there are all the TI/TI2 factory banks
just as info for those who are searching for presets...

[muki]

btw,
there's a comparison-video, comparing betweens TI hardware and dsp-C



question:
in re the access hardware-TI-controller-window on the left side.
this will be installed with the downloadable software as AU/VST plugins ?

so this is an official editor/librarian for the hardware ?

and this only works if the systemextensions are also installed (kext and mididriver) ?

p.s.:
i don't want to run the nstaller thingies since it also installs a kext and special mididrivers
and i don't want to spoil my system with (for me) unneccessary systemextensions...

[Scotty]

fyi
i just found, that dsp56k with B/C will quite happily load TI banks
tons of those banks can be found on the official virus.info site
also within the TI software installer there are all the TI/TI2 factory banks
just as info for those who are searching for presets...

The actual hardware Virus C will load them too but inaccurately just like the emulator.

[Syngularity]

The new update is fantastic. The arpeggiator bug (when playing the recorded notes) has gone here!

[Syngularity]

Unfortunately the arpeggiator does not sync perfectly to host.

[arkmabat]

But you can set the bpm, right?

[Scotty]

Unfortunately the arpeggiator does not sync perfectly to host.

At least here on Cubase 11 on Windows 10, the arpeggiator will eventually pickup the host BMP and sync . It it takes a bar or two. It is working very well. There is s discord where you can read the commentary and bug reports and there is a DAW specific beta group although it seems we are all using the same build.

This versions is not designed to load the TI banks and play them properly ... so far it remains the Virus B and Virus C that this is intended to replicate. I believe the TI has different DSP requirements and I expect they will move on to another synth before going after the TI. One that only uses 1 DSP chip and requires less work to get going. There are a few candidates that the developers mention.

[Syngularity]

You can‘t set the bpm, and in Cubase 11 Pro it picks up „close“ to the bpm, so after some bars the arp runs out of sync. No, I didn‘t join a beta forum, because here‘s a forum too. As I already mentioned, the emu is close to perfect.

[Scotty]

You can‘t set the bpm, and in Cubase 11 Pro it picks up „close“ to the bpm, so after some bars the arp runs out of sync. No, I didn‘t join a beta forum, because here‘s a forum too. As I already mentioned, the emu is close to perfect.

Interesting. I didn't mean to be argumentative. I didn't pick up the arpeggiator drift with the latest build. Perhaps I wasn't listening close enough.

[PAK]

Unfortunately the arpeggiator does not sync perfectly to host.

At least here on Cubase 11 on Windows 10, the arpeggiator will eventually pickup the host BMP and sync . It it takes a bar or two.

FWIW Even the official ProTools TDM / Powercore plugin versions (Which are ~19 years old now I think about it.. ) never had 100% rock solid timing when it came to the arp either.

The timing would also tend to "go off" more often when a DSP core was under heavier load. It's one of those things which potentially might not ever be "100%" without directly changing the way the original DSP code handles event timing.. IE The problem might well be with the original Access code..

[Scotty]

Unfortunately the arpeggiator does not sync perfectly to host.

At least here on Cubase 11 on Windows 10, the arpeggiator will eventually pickup the host BMP and sync . It it takes a bar or two.

FWIW Even the official ProTools TDM / Powercore plugin versions (Which are ~19 years old now I think about it.. ) never had 100% rock solid timing when it came to the arp either.

The timing would also tend to "go off" more often when a DSP core was under heavier load. It's one of those things which potentially might not ever be "100%" without directly changing the way the original DSP code handles event timing.. IE The problem might well be with the original Access code..

I have an actual Virus C on my desk that I sync with external midi clock. I have had it since 2009 - 2010. It also chases clock a bit and settles. I don't doubt your comments. I usually just record the audio and don't use it in real time jams. I am probably not as sensitive to it.

[arkmabat]

Interesting that it's so exact that it has the same flaws. Can you not use ghost notes to align it before it comes in?

[Funkybot's Evil Twin]

Interesting that it's so exact that it has the same flaws.

Remember: they're not emulating the synth...they're emulating the chip it runs on. So issues that exist in the hardware should be expected here too.

[Syngularity]

Seems logical to me… solution for the emulator vst could be to allow manual setting of the bpm. In the meantime one can import those arp presets in Adam Szabo‘s Viper or simply turn off the internal arp and use an arpeggiator plugin instead.

[rasmusklump]

The arp presets are already hard-coded in viper.