NDSP Misha X and Rabea X ..... very high Latency ??

TheTrueZoltan! said:
I was having such a lovely Saturday until you lot ruined my mood. ;)

Mood No GIF by Persona
Click to expand...
*black metal dissonance intensifies*
 
Unqualified remark from the Lurker's Corner:

What's with the tone around this place ATM?

Everybody on the edge because of forced time with the relatives ("bucklige Verwandschaft" in German)? Too much/not enough alcohol? Everyone calm the fuck down :cool:
 
Gojira reports 0.8ms on Studio One, the lowest of their plugins. Omega reports 0.1ms without OS and 1.1ms with OS, but supposedly, its actually component model and not parametric capture like the newer ones.
 
Thanks all.

I do get where everyoine is coming from and see all sides of the matter.

My primary interest was piqued when I saw that a full Genome 2 rack with all slots loaded with rev / delay etc.... and a full NAM Capture in Codex reports 0 Samples 0ms ..... I kind of expected the two X plugs I am demo'ing would be the same and was quite taken about by the [relative] sheer size of the added latency, especially compared to anything running NAM - which is a well established resource hog.
 
Orvillain said:
Not all plugins report the correct amount of latency anyway. Kind of notoriously difficult to get right. I wouldn't trust those figures at all.
Click to expand...

Hey Orv ... not for the first time looks like you are right :)

I ran an old school in / out real-world usage test - I feed my Laptop Interface Input a Click Track and ran it through an empty GP5 Rack with just the I/O's connected and then fed my Laptop Interface Input the same Click Track but now running it through a 20 Block Rack with the Rabea X Plugin open and running - tracks were aligned to zero in Audacity with Latency compensation off.

Test done at 96k as that is what I run my GP5 and Audio I/O at.

-> Compared to the Baseline Click Track Gig Perf 5 with a totally empty Rack added 20.2 Samples or 0.2103 ms
-> Compared to the Baseline Click Track Gig Perf Track with 20 Plugin Blocks plus the NDSP Rabea X Plugin VST3 on and working, added 23.5 Sample or 0.2448 ms

Did the test 4 times to get the worst results I could get - there were all within a few samples of each other

So the "load" or "added" latency of the NDSP Rabea X added only 3.3 Samples ms or 0.0344 ms at 96k ie: nothing.

So either Gig Perf 5 is reporting the wrong NDSP Latency -or- the NDSP Plugin is transmitting the wrong Latency figure

Either way, the NDSP Rabea X Plugin adds 0 latency - not the 175 Samples / 1.8ms as reported in Gig Perf 5.
 
Last edited:
newholland said:
thats equivalent to the delay time of moving your cabinet 2 feet further away.
Click to expand...
Given than the typical "playing through plugins" monitoring experience is headphones...yeah, moving the "cabinet" 2 feet further away would be noticeable.

Yes, there's a lot more going on in moving your headphones two feet away from your head than just latency. Which is...exactly the point and why this point of reference on latency is absolutely stupid.
 
Boudoir Guitar said:
Given than the typical "playing through plugins" monitoring experience is headphones...yeah, moving the "cabinet" 2 feet further away would be noticeable.

Yes, there's a lot more going on in moving your headphones two feet away from your head than just latency. Which is...exactly the point and why this point of reference on latency is absolutely stupid.
Click to expand...

I don't know about "stupid" but if you look at my post #33 just above, you will see that the impetus for this thread has now shown itself to be an error either in GP5's reporting of the NDSP latency or an error in what the NDSP plugins are reporting their latency to be.

From my view, with a fully digital set up, be it a Fractal or Stadium or QC or good Laptop and Plugin setup, anything in the range of 3 ms <-> 4 ms real world in to out, absolutely sounds and feels totally "real time" .... to me at least its imperceptibly different to a guitar plugged straight into an amp - although as others have noted, Steve Vai probalby would not agree :)

However as TheTrueZoltan! noted above, when running Amp Sim plugins, if you aren't careful about what you use, it is very easy to start stacking up the Latency - that's all.
 
Boudoir Guitar said:
yeah, we all knew the impetus for the thread was an error from the OP. One clue being the magical 0ms latency for everything else.
Click to expand...

As the OP .... I only reported what the App reported and queried it. Further testing - by me - has now shown either GP5 or the NDSP X Plugs are showing / reporting the wrong latency data - there is / was no "error" by the OP [me].

And yes - you are wrong - as I noted above, the difference between a fully empty GP5 Rack and one with 20 VST3's including NDSP Rabea X is only 3.3 Samples / 0.0344 ms at 96k - to me, and I suspect everyone else, for our purposes, 0.0344ms = 0 and it is well within the margin of error for different hardware guitar setups / software.

Nothing magical, just facts.

If you have Gig P5 and an NDSP X plugin, run the test yourself and you will get the same results ... otherwise, I'm not sure what points you are trying to make regarding this particular thread and what it is about.
 
You must log in or register to reply here.
Back
Top