Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Sorry that you two are running into issues. We've tested the latest release on multiple Win7/8/10 configurations, both clean installs and upgrades and haven't run into this issue. These machines only have STEAM and SONAR installed to them. We also make sure to run all updates and reboot the machines before install.
If the install is hanging on a certain process, it's being blocked, either by 1) Windows Update preventing the Steam from accessing built in Windows processes 2) Steam has insufficient admin rights 3) a 3rd party app is blocking the windows process.
If you can find and post your STEAM client logs that could help with finding the issue:
Logfiles: C:\Program Files (x86)\Steam\logs
Crashdumps: C:\Program Files (x86)\Steam\dumps
More info, like what version of Windows you run 32 or 64 and any antivirus software can help give us more info to see what's going on. Also, what version of SONAR?
If plug-ins aren't showing up after a reinstall, it sounds like the plug-in manager is not registering and and Dxi's are likely not getting registered either. This would point back to the Windows process being locked.
Make sure there are no pending updates to apply, and reboot the machine. Then run a re-verify application cache on SONAR in STEAM.
Step 122, is likely calling the Windows Reg.exe process. If the error is calling Cakewalk Plug-in Manager, we haven't touched this component in months, so It's unlikely to be related to just the last update.
I'd recommend checking Windows updates as well with this. Also, what version of Windows are you running on? What version of SONAR are you on?
But when I start Sonar from Steam that I normally do, it makes some errors and founds 93 plugins. But when I start that SONARPRO.EXE it founds only 55 plugins and no any errors.
I'll try figure out if there's some more problems with it. Atleast my old projects are working, and that's good.
Sounds like you're launching the 32 instead of 64 bit version of SONAR.
That lives in C:\Program Files (x86)\Steam\SteamApps\common\Cakewalk\x64\SONAR
What sounds are you attempting to use?
But after that I opened my another project and there was a plugin called Z3ta + 2. It didn't give any sound so I opened it and boom. It gives an error and it's not giving any sounds to my projects.
Sometimes it works for a little while, but soon there's another error. What's going on, or am I just really dump person :D ?
Studio Instruments get's automatically registered and activated on a successful install of SONAR. Every steam user has the exact same serial number and activation code, it's all hard coded and offline. It should never time out.
You were definitely getting that error because of a bad installation. The SI suite are installed/activated through us calling the Windows registry editor via the STEAM Client, the most common instances of this being blocked are STEAM/SONAR not having administrator privleges, malware/antivirus blocking the processes, or Windows Updates pending or a reset was not performed after an update. If this issue just popped up, it's likely a registry cleaner may have been used on the system and removed keys it should not have.
Z3ta + 2 is a separate plugin in the STEAM library that needs to be installed and run and activated through the STEAM client before you can use it in SONAR or another other DAW. I would.
It's okay. Depending on your driver mode, Windows sound manager and the sound device settings on the system devices could be impacting SONAR's settings. Most of the headphone devices become the default device when it's plugged in. If you're in the WDM/KS, WASAPI, or MME-32 driver modes these device changes could impact configuration and playback. That's why we strongly recommend ASIO compatible devices since SONAR talks to it exclusively outside of the Windows mixer.