Ensoniq DP/4 Emulation Incoming!

[jens]

Why would i disable suspend ? Works fine.

Unbelievable!

You shared a screenshot here showing how little CPU the plugin uses withotu audio input. But if you have "Suspend VST 3 plug-in processing when no audio signals are received" enabled, then the plugin is literally auto-bypassed in Cubase i.e the CPU load will be exactly zero regardless of both the type and number of loaded fx-plugins.

i.e. your screenshot shows no actual information at all except - sorry to be so blunt - that you do not actually understand what it is that you were trying to do.

If you wanted to test how much CPU the plugin uses without doing any processing you would instead have to disable the processors within the plugin itself - either while sending audio through it or while having suspend disabled.

And that's the kind of support the developer is getting here - cultish stupidity, which the more regular users wouldn't want to touch with a bargepole.

Or to say it more drastically: you sort of help branding the developer as someone who's solely for the nutters and the hopelessly incompetent. And I'm not sure he'd be to happy with that kind of stigma.

And from what I read from him so far it neither didn't seem at all like the deserves this. He seemed rather reasonable, competent and down to earth to me - none of which applies to you.

[budweiser]

Unbelievable ! Hair splitting jerk at his best. Carry on.

[c_voltage]

Zero cpu consuption here when noting inputs in the plug, works perfectly fine. Windows 11, cubase 14, i7 8700k.

You forced me to install demo again lol
Curiously i has the same CPU (i7 8700), just without "K" in name.

I just wanted to check again how it actually will do with no any effects in slots at all.
So, this is state not only with no any effects, but i even make "Bypassed" each of 4 sections.

Sorry at my side it still eat 14%. Just shell, no any effect are active here.

Untitled.jpg

Win10 \ Studio One 6

[jens]

Unbelievable ! Hair splitting jerk at his best. Carry on.

At this point there's nothing you could say that makes you look less incompetent.

If explaining to you how you posted a screenshot that shows absolutely nothing in regards to what you assumed and claimed it would show, is splitting hairs for you that illustrates your level of competence and intelligence even more.

Sad, just sad...

[c_voltage]

@budweiser
For instance (so you don't think that I have some kind of weird config), i did check to loading in row (at single track) together next plugs:

Liquidsonics Cinematic Rooms Pro
Fabfilter Saturn
Devious Machines Infiltrator
Relab LX480 Complete
UHE MFM2
Eventide H3000 Factory MKII

Result: 12%. All that plugs together (!) \ in single calculation stream. Moreover during active audio input processing.

Untitled.jpg

Upd (VS 14% of empty inactive shell)

[budweiser]

@c_voltage : it's probably the same here, the only difference is i don't see it as a problem as it's vastly outweighted by the convenience of having a DP4 clone in the box. The plug is two weeks old, at best, when i have so much other vsts from big players that face the same buggy behaviour for years...

@jens : Apart the fact you're uterly boring, i have to confess i skim over your endless posts, considering you argue on things you're not even interested in (your own word).
But i'm pretty confident you can hit the 30k kvr posts mark in this thread, then find some room to get a life, so you won't have to interfere anymore.
You don't like it ? Fine. Next one.

[rafa1981]

If the algorithms are actually black-box reversed and reimplemented there is no way that allpass-loop reverbs, phasers and those kind of DSP effects from the 90s take that CPU amount. Even on fixed point and emulating saturating arithmetic (had the device saturating arithmetic?).

My educated guess is that this is either a very big bug or this is an actual emulator. Because the other explanation I can come up with, which is NaNs, wouldn't happen when the effect is bypassed.

EDIT: and NaNs don't happen in fixed point.

[c_voltage]

@c_voltage : it's probably the same here, the only difference is i don't see it as a problem as it's vastly outweighted by the convenience of having a DP4 clone in the box. The plug is two weeks old, at best, when i have so much other vsts from big players that face the same buggy behaviour for years...

Ok i see.
(Although for the sace of justice can correct my 12% statement regarding 6 mentioned plugs, actually it 17% (did reassembled right now), because in some of them i did not select something preset after load, so in initial state they had sort of non processing, like in Saturn and Infiltrator. That's all now.)

[idoru97214]

It does use a fair amount of CPU. That (obviously) will matter to some more than others. I am in the 'I don't care too much, but I do care a little' camp. I really like the sound this little guy makes. Heck - I BOUGHT IT! If I could drop these indiscriminately, that would be great. But - whatever. My understanding is that this is basically a circuit level emulator like Relab 176 or Korneff Sitral (both of which eat more CPU than this one does, btw). I use both of those because they sound so great. But for some, due to workflow or other issues, sound is not the only major variable, and that is fine.

[c_voltage]

My understanding is that this is basically a circuit level emulator like Relab 176 or Korneff Sitral (both of which eat more CPU than this one does, btw).

Lol i thought you're exaggerating.
(But nope)
Ok, not exactly more, but can say curiously the same as 4U preset of DP/4.

Untitled.jpg

Ok, now i saw all. No more questions.
I really didn't think that this was possible from one compressor. And from Relab.

[jens]

My understanding is that this is basically a circuit level emulator like Relab 176 or Korneff Sitral

Nope - these are totally diferent things. Both are emulations of (highly non-linear) analog gear.

The DP/4 on the other hand is a completely digital unit (the AD/DA is not part of the emulation - it's just the pure digital algorithms.)

[TemeculaDSP]

Hey everyone,

A massive thank you to all the early adopters who have picked up DEEP/4 over the last few weeks. The response has been incredible, and I've been hard at work taking your feedback and building it directly into the plugin.

Version 0.2.5 is now live and available to download. This is a major workflow and engine update.

What’s New in v0.2.5:

Major Features & Routing

Per-Unit MIDI Tempo Sync: You can now lock delay times and LFO rates directly to your DAW's tempo on a per-unit basis.

Drag-and-Drop Routing: Reorder your effect units (A/B/C/D) simply by dragging the tabs to completely customize your signal chain.

Hardware-Compatible Preset Banks: Full SysEx format support. You can now create, rename, delete, import, and export custom banks to share between sessions (fully compatible with the original hardware). Please note, any prior presets you may have created will not load. You will have to recreate them.

Mono Track Support: The plugin can now be loaded directly onto mono channels in all DAWs.

Audio Engine & UI Improvements

Artifact-Free Preset Switching: Completely rebuilt the switching engine. Delay RAM now clears instantly when loading a new algorithm, combined with a custom crossfade. Zero flanging, zero transients, just clean preset changes.

Hardware-Accurate Values: Knobs now display the exact 0–99 (and -99 to 99) values matching the original front panel, rather than internal 0-127 MIDI ranges. Delay times now properly display the "ms" suffix.

Precision Control: Double-click any knob to type in exact values. Added keyboard shortcut hints (Alt/Opt+click for fine adjust, Shift+drag for snapped increments).

UI Cleanup: Improved knob notch visibility, eliminated the algorithm panel scroll bar for a cleaner fit, simplified the bypass to a clean two-state toggle, and corrected internal parameter ranges across 8 different algorithms to perfectly match the hardware specs.

You can download the v0.2.5, or grab the free trial if you haven't checked it out yet, right here: https://www.temeculadsp.com/release-notes/deep4

Join the official Temecula DSP Discord! If you want to talk production, show off your mixes, or chat about what hardware is going on the test bench next, come hang out with us here:

https://discord.gg/mFpHfQJPfm

Thanks again for the support, and happy mixing!

- John
Temecula DSP

[DrGonzo]

Version 0.2.5 is now live and available to download. This is a major workflow and engine update.

Long-time Ensoniq fan here with an almost mint condition DP/4 sitting next to me. Question - are you only focusing on replication of the effects or are you diving deeper into the sound when overdriving the inputs?

/Carl

[jens]

@jens : Apart the fact you're uterly boring, i have to confess i skim over your endless posts, considering you argue on things you're not even interested in (your own word).
But i'm pretty confident you can hit the 30k kvr posts mark in this thread, then find some room to get a life, so you won't have to interfere anymore.
You don't like it ? Fine. Next one.

Ah yes?


Look, the problem is clearly and simply that you most obviously completely lack the backspine to admit if you were wrong - regardless of how overwhelming the evidence may ever be. Instead you keep side-tracking and resorting to absolutely uncalled-for ad-hominen attacks.


But no amount of that will be able to take away the fact that you:

- attacked me for me stating a perfectly valid fact

- tried to prove me wrong with an absolutely meaning- and pointless screenshot

- you did this because you don't even know properly know how your own DAW functions and needed me to explain it to you (even that's neither my main, nor even my secondary DAW of choice)

- attacked and insulted me since then instead of admiting that you were WRONG - which you totally were.

And it's all here in this thread for everyone to see.

[jens]

Hey everyone,

[...]

Thanks again for the support, and happy mixing!

uhm... so no word from you at all regarding the most excessive CPU consumption?