I’ve been using Gig Performer for quite some time as a system-wide solution for VSX, room correction, and analyzer tools in the studio.
And it’s the best and cleanest solution I’ve used in 30 years. Many other users share my opinion.
Unfortunately, something currently doesn’t seem to be working as smoothly with VSX as I’m used to. There are sound discrepancies when I use the VSX plugin through a DAW like Cubase versus loading it as an AU/VST2/VST3 plugin in GigPerformer. I’ve run several null tests and keep getting different results. It also makes a difference whether Cubase or Gig Performer is running at 44.1 or 48 kHz.
For testing purposes, I tried other plugins as well - and those work perfectly fine. One might immediately assume that VSX is to blame (which does seem likely).
The problem is that the CEO of VSX (Steven Slate) has officially stated that he cannot support third-party system-wide apps.
Since Deskew Technologies has surely gained quite a few new users in recent months - and especially in recent weeks - it would be a shame if Gig Performer suddenly became unusable in combination with VSX.
I simply don’t understand how VSX, as a VST3 or AU, can deliver two different results on two different platforms. If someone with technical expertise can help here, I’d really appreciate it.
@Development:
I think it might be in your interest to take a look at this. It mainly concerns VSX v6.0.5.
You are allowed to post links, but the system flagged your repeated posts with only containing links to the same site as a possible spam… i restored your posts and “un-flagged” them.
You probably should avoid that in future.
If the problem is only with version v6.0.5 and all other variables are the same (the same OS, interface, Gig Performer version, etc.) then the problem is in the plugin.
For everyone who has already updated to 6.0.5, caution is advised.
Because what you hear unfortunately does not reflect the actual result of how the plugin is supposed to work.
AGAIN: right now we are only talking about 6.0.5 (and maybe 6.0.4).
Exactly - nevertheless, there are certainly some users here from GigPerformer who are currently using VSX v6.x.x and are not aware that the VSX plugin and GigPerformer are not communicating correctly.
What I have never experienced, however, is a plugin running cleanly via the DAW (Cubase) and VST3, yet producing different results when used through GigPerformer with VST3.
That is a mystery to me.
And at that point, I wouldn’t care whether the diagnosis comes from Dr. House or Dr. Doug Ross - right now, we’re dealing with Frankenstein!
You don’t mention whether you were on Mac or Windows - if the latter, the fact that a reinstall solved the problem would suggest that something else you installed along the way replaced a library/DLL and consequently screwed things up.
Just mentioning this as, if this is what happened, you’re probably going to run into it again.
If you were on Mac, then I don’t understand how a reinstall would have made any difference.
Yes, I’m working on a Mac.
I spent many hours trying to find a plausible solution to the problem and repeated all the tests several times yesterday and today. Unfortunately, the only information I can provide is that a complete uninstall truly worked wonders in my case.
Of course, I’m more than happy about that. Still, it makes me somewhat uneasy that I don’t have a clear answer as to what exactly caused the issue. I haven’t experienced anything comparable in the past 30 years.
The only explanation that seems plausible to me is that some kind of file corruption must have occurred somewhere, ultimately leading to all these problems. I had also installed several beta versions of VSX v5 and v6 recently. At this point, I can’t think of any other explanation.
