Helpful ReplyLittle nagging Prochannel issue

Author
RookOSU
Max Output Level: -90 dBFS
  • Total Posts : 14
  • Joined: 2013/06/18 15:35:33
  • Status: offline
2016/08/24 23:24:48 (permalink)

Little nagging Prochannel issue

I logged a customer support request over a month ago and not one response (which I'm guessing by my initial forum review is common) so I thought I'd give this a go here.
 
Every time I load a project in Sonar Platinum (only on the first instance of loading a program upon opening Sonar), I get a pop up window that shows as below.  I click OK, and it pops up again and does the same for 5 more various Prochannel Modules (Gloss EQ, Tube Saturation, Console Emulator, another compressor etc).  Then everything works fine, but I must do this, every single time I load any project.  Click ok 6 times then get to work.  Because prochannel modules aren't really something I can 'point to a location' in settings it's not like I can go change a path.  Any ideas?  It'd be greatly appreciated!  Thanks!
 
- Shaun
 

#1
scook
Forum Host
  • Total Posts : 24146
  • Joined: 2005/07/27 13:43:57
  • Location: TX
  • Status: offline
Re: Little nagging Prochannel issue 2016/08/24 23:49:21 (permalink) ☄ Helpfulby RookOSU 2016/08/25 12:48:09
This looks like a custom installation. Make sure all instances of SONAR are installed on the same drive. Then run a vst reset.
#2
RookOSU
Max Output Level: -90 dBFS
  • Total Posts : 14
  • Joined: 2013/06/18 15:35:33
  • Status: offline
Re: Little nagging Prochannel issue 2016/08/24 23:54:14 (permalink)
Hmm. I only have one instance of Sonar. But because I have two hard drives (one SSD for program files and an HDD for big data) I do have paths pointed to each for various settings in Sonar. Perhaps that has something to do with it?
#3
scook
Forum Host
  • Total Posts : 24146
  • Joined: 2005/07/27 13:43:57
  • Location: TX
  • Status: offline
Re: Little nagging Prochannel issue 2016/08/25 00:00:22 (permalink)
Looking at the error closer the location reported for the ProChannel module is unusual even for a custom installation. You might want to try a more conventional installation.
#4
Kev999
Max Output Level: -36 dBFS
  • Total Posts : 3922
  • Joined: 2007/05/01 14:22:54
  • Location: Victoria, Australia
  • Status: offline
Re: Little nagging Prochannel issue 2016/08/25 03:18:57 (permalink) ☄ Helpfulby RookOSU 2016/08/25 12:47:59
I was getting the same messages, except that in my case they referred to ordinary plugins, not ProChannel modules. This started after I set up a custom Plugin Layout and they appeared whenever I opened a project in 32-bit Sonar (X3 or Platinum). I presume that they referred to 64-bit plugins that were not available in 32-bit Sonar. Reverting the the default Plugin Layout made them stop appearing.

SonarPlatinum(22.11.0.111)|Mixbus32C(4.3.19)|DigitalPerformer(9.5.1)|Reaper(5.77)
FractalDesign:DefineR5|i7-6850k@4.1GHz|16GB@2666MHz-DDR4|MSI:GamingProCarbonX99a|Matrox:M9148(x2)|UAD2solo(6.5.2)|W7Ult-x64-SP1
Audient:iD22+ASP800|KRK:VXT6|+various-outboard-gear|+guitars&basses, etc.
Having fun at work lately
#5
RookOSU
Max Output Level: -90 dBFS
  • Total Posts : 14
  • Joined: 2013/06/18 15:35:33
  • Status: offline
Re: Little nagging Prochannel issue 2016/08/25 12:13:36 (permalink)
Thanks Kev.  Unfortunately I haven't messed with Plugin Layouts at all.  I'm wondering though if there's remnants of older versions of Sonar hanging out on my computer though.  I'll do a registry search for them.
#6
KPerry
Max Output Level: -44 dBFS
  • Total Posts : 3120
  • Joined: 2011/04/26 15:13:15
  • Location: London, UK
  • Status: offline
Re: Little nagging Prochannel issue 2016/08/25 12:25:56 (permalink) ☄ Helpfulby RookOSU 2016/08/25 12:47:50
My guess would be that the "hard-coded" (but in the registry) link to the folder where PC modules are installed has got lost.

Windows 7 x64 SP1
SONAR x86/x64
 
Intel Q6600/8GB
MOTU UltraliteMk3 (USB/ASIO)
Edirol PCR300
#7
Jump to:
© 2025 APG vNext Commercial Version 5.1