Before responding in more detail to your requests for information on my graphics card, could you tell me where the standalone version of SCALER_EQ was installed by default. I can not find it !?
What is the file name?
I obviously left all the boxes checked during installation and I left the default paths that the installer offers.
And I don’t seem to have the same reaction as @Navado.
For me, after installation, I restart my PC then I open CUBASE Pro v13 and I put SCALER_EQ in an audio channel strip and there CUBASE hangs. I no longer have access to any menu and am therefore forced to close CUBASE by the task manager.
For informations :
Unlike with SCALER_EQ, the installation with SCALER_2 went well.
Hello @jchdejong
OK
I run scaler.exe and it has been running for 7 minutes with no results.
I found a possible clue to the problem:
In Task Manager, the “User Account Control Virtualization” column is “Disabled”
Is this the cause of my problems!?
I don’t know how to activate this virtualization…
Do you have an idea to activate this virtualization…
Video BIOS - Version: Version 84.04.84.00.89
OpenGL
Version: 10.0.19041.3636 (WinBuild.160101.0800)
Out of more than 700 plugins installed in my studio configuration, this is the first time that a standalone version does not present a personalized icon on the “.exe” executable file and does not present an icon on the desktop either. .
For me there was a problem during installation.
I have uninstalled SCALER_EQ cleanly and several times (at least 5 times).
Always the same result. Either a component is missing from my PC computer and which one? (until now I’ve never had this kind of problem, for at least fifteen years without having had a message warning me of a problem)
For me also only process in program manager with standalone version.
My videocard RTX4090. With all latest drivers. Interested that on virtual machine is work well.
We have taken some time to investigate this issue, but unfortunatly we haven’t been able to reproduce the issue in any way. This is unfortunate, because if we cannot reproduce the issue, we have no way of figuring out what is going on. This means we do not have a short term solution.
What we did do to solve this on the medium term, is implement a new way of drawing our GUI on Windows, directly utilizing the Windows OS. We are still running tests, but I am hopeful your issues will be resolved once we are able to add this to the plugin in an official update. We will keep you posted.
Of course, you not being able to use the product is a problem. Perhaps @davide can help you resolve this another way?
Very strange, today I created a new user account in Windows 11 and the Scaler EQ started working!
How can I make it work under my account? What we need to check?
I have the same problem: Just installed Scaler EQ, but it’s not opening any Windows. From digging through what the standalone executable does (with the SysInternals Process Monitor), it looks like it’s stuck in loop opening the preferences file (and all presets, for that matter) under the following path over and over:
C:\Users<username>\AppData\Roaming\Plugin Boutique\Scaler EQ\settings.pref
Maybe you could try to copy the preferences file from the working user account to your other account?
Okay, more digging, and I got it to work:
Scaler EQ does not start when the user TMPDIR environment variable is changed. I have moved mine to a separate drive, and by moving it back to the default location C:\Users<Username>\AppData\Local\Temp it started to work for me.
Looks like it wants to put a file called “Default Preset.seq” there, and it fails somewhere.
You’re doing fantastic stuff.
When I changed TEMP FOLDER Scaler EQ worked!
But I use RAM DISK and all the cache for programs is stored there.
What should I do?
Maybe SIMLINK can help?
The developer can now test it too.
Scaler EQ 1.1 fails when the temp dir is not on the system drive.
The proper way to handle this in code is to consult the environment,
rather than assume, however the issue may not be obvious if you are using a
development framework that fails to handle this properly but hides the
implementation details from you.
I hope you can fix this soon so that folks like me with temp dirs on alternate
drives can use the software.
