Seeing as several folks have come back to this thread I thought I'd just update my position.

found some major problems in ProChannel with settings not persisting after reopening projects and some settings reversed from actual. Apparently confirmed by Noel so Pro Channel is dead for me.

Still finding numerous annoying things not fixed and totally fed up at this stage.

I'll continue to use SONAR 8.5.3 for work while I examine options. I'll dabble in X1 from time to time to get to know the program with the hope that a future update will bring the fixes and stability I need but its far too unreliable for my work. Truly wished it could have been better.

mudgel


Seeing as several folks have come back to this thread I thought I'd just update my position.

found some major problems in ProChannel with settings not persisting after reopening projects and some settings reversed from actual. Apparently confirmed by Noel so Pro Channel is dead for me.

Still finding numerous annoying things not fixed and totally fed up at this stage.

I'll continue to use SONAR 8.5.3 for work while I examine options. I'll dabble in X1 from time to time to get to know the program with the hope that a future update will bring the fixes and stability I need but its far too unreliable for my work. Truly wished it could have been better.

Wow sorry to hear you are having so many problems. It is weird how different the experiences of X1 users have been. I hope you get it sorted. I've been lucky for whatever reason. I am not going to suggest any fixes, as I wouldn't know where to start, but good luck with it. I can say that for me, X1b works mostly as advertised, and I'm happy with it. But if I had half the things go wrong that you've had, I would have given up by now. Let's hope there's an X1c real soon for your sake.

riojazz, right click and show all option restores the dock.

I also use audition, and i get this bug everyday.

It's not till you come back to SONAR that you notice (I'm working with 8.5 but it's the same in X1) that there's always a little gap when you try to change fx modules or synths etc on the fly and spometimes it can even trigger a dropout of the audio engine.

But on the other hand, there's always the thrill of exictment knowing that you might just crash Sonar instead.

It's just like coffee but cheaper (well unless you are counting the costs of your time of course)

aurelien33


riojazz, right click and show all option restores the dock.

I also use audition, and i get this bug everyday.

Thank you!  Yes, I saw this later in the thread. 

Hey Mudgel, hope this quickfix might work out for you. I won't be able to download it until later tonight. Good luck.

Wow Mike. I'm stil not getting the differences in different set-ups. Did you check for demons? Just sayin'

Did not mean to sound flippant. Sucks. Did you see the other thread re: Pro Channel not working? I think the symptoms were similar - not sure of the fix. May have been a vst scan - yeah I know - I can understand your frustration. I'm a hobbyist at best so I don't stress X1 but I just don't see ANY of the things you're seeing - just not understanding that.

I was just making general comments not directed at you Larry. I didn't think you were being flippant.

As for VST Scan I have SONAR set to scan at start up which technically means it just reeads the inventory which happens very quickly unless a new plugin is detected. I might just force a rescan but I don't think that ProChannel is VST based. The only specific prochannel file/s I've been able to find other than the presets are in:
 
C:\Program Files\Cakewalk\Shared Utilities\Internal -- these aren't in the scanner path same as BitBridge and other SONAR Utilities

spec'd for me by DAW builders.

Not only affecting me. Several others have reported it as well. I do however acknowledge that there are only a some of us that are affected by this.

The recipe is pretty straight forward.

Start SONAR
Load project (can be a new one or an existing one)
Select track
Open the ProChannel gui
Activate all modules ie compressor, EQ & saturation
Play project
Adjust settings in any or all modules

What I expect is to see and hear the audio being processed by the 3 modules and see the meters and eq plot respond with changes to settings.

What actually happens is that

No meters move at all
the compressor and Saturation indicators do not activate
there is no eq plot
no audio is audibly changed by adjusting any parameters.

conclusion is:

ProChannel does not process any audio.

repeat recipe and 100% of the time same result.
 
Change the recipe by starting a clean project import or record some audio choose a preset for ProChannel.
Same result.

Whether I use only one instance of ProChannel and only one module active or 2 or all 3 modules active or whether I have multiple Prochannels active or ProChannel active on every track the results are always the same.

Makes sense as Pro Channel doesn't process any audio in the first place.

From further testing this afternoon as far as I can tell SONAR only sees the gui for Prochannel but doesn't see the .dll files associated with it. In effect meaning that the ProChannel code isn't really running.

How do I know this?

The 4 .dlls that I  think are part of ProChannel are stored in

Program Files\cakewalk\Shared Utilities\Internal.

I can remove those files and the whole folder. Take them off my system completely and it makes no difference to how ProChannel runs at all. It doesn't even make a difference to SONAR I would have thought that SONAR would crash as soon as I tried to activate ProChannel but the gui for it still appears and runs the same as usual. ie it doesn't process any audio at all. Even rebooting things work as before. Still see the PC gui but no activity.
 
I'm now more sure than ever that something catastrophioc has happened during one or more update installations after X1A that is causing all this.

When I get some more time I will do a complete delete and reinstall of X1 and all patches to see if this makes a difference to ProChannel and or my whole X1 experience. I did this twice previously with the original install of X1 but it didn't change anything at that time to make it run any better and because things only got worse after that I haven't done another complete reinstall.
 
At last I may be onto something that I can do to make this work. Cross every appendage you have.

mudgel


As for VST Scan I have SONAR set to scan at start up which technically means it just reeads the inventory which happens very quickly unless a new plugin is detected. I might just force a rescan but I don't think that ProChannel is VST based. The only specific prochannel file/s I've been able to find other than the presets are in:
 
C:\Program Files\Cakewalk\Shared Utilities\Internal -- these aren't in the scanner path same as BitBridge and other SONAR Utilities

Mike, 

I think it's worth a shot to rescan existing plug-ins (and maybe rescan failed plugins as well).


The PC DLL names in C:\Program Files\Cakewalk\Shared Utilities\Internal are in the Cakewalk VST X64\Inventory registry keys on my system. It doesn't make sense to me unless the internal file path is hard-wired into the VST scan, but seeing that they are listed in the inventory suggests that they have been scanned. 

[EDIT: I found the path. If you click on the VST Configuration "Options" button in the Cakewalk Plug-in Manager, you should see that folder path included in the scan paths.]


I did a quick look back but didn't notice, do you have both versions of X1 installed (x86 and x64)? I ask because I have only ever installed the 64 bit version and wondered if maybe there could be an issue with a dual install getting into each others business.

~Don

Hi Don,
you posted while I was doing the same.

I have done several rescan for failed plugins as I had an ornery plugin that wouldn't scan.

So maybe my problem could have been with the VST Scanner.

I didn't see (nor did I look for it) the path for the ProChannel modules listed in theVST x64  inventory
 but I did see a path to the "Internal" folder in another key.

I've done the big uninstall now so it's too late for further hunting down of things.

I'm actually quite hopeful of a resolution doing just a basic and completely default reinstallation.
Because I had problems right from the very start I never bothered doing a 32 bit install.
Wish me luck.

Here's something weird: the Internal folder exists in the Plug-in Manager/VST config/Options, but it doesn't show up in the Preferences/VST Settings dialogue. Every other folder is identical. I wonder what the consequences of this are?

Mike, I'm as Antipodean as possible in Oz - Hobart :)

Cheers, Peter.

Is Tassie part of Oz again is it? sorry i couldn't resist.

Actually vice versa - welcome back North Islander :)