Just wondering if anyone else has graphic issues when inserting a module, usually Softube Saturation, where it results in it being inserted, but only "over" another module, so that the knob is invisible (though you can see from the module bar at the top that it is there).

This has happened with prior X versions as well, where inserting a module screws up the whole PC graphic interface.

Anyone else experiencing this or have any fixes?

Thanks in advance


EditQuoteReply

Try doing a reset and rescan. 

This is a bug, that has gotten a few threads already on this subject. There are a few of us that has this issue, especially with the saturation knob. I am not sure whether or not this is a prioritized issue for the bakers. Been through a teamviewer session with Joey Adams from Cakewalk (cool guy), and did not find any faults with my setup. I know other people has the same issue, so we can only hope for a solution to an otherwise "minor issue" (for us with issue), so that we can continue to enjoy a very good / nice / stable DAW. 

Ken if its a bug then why are many not seeing it?

Who knows John. Perhaps the problem is tied to a particular chipset. If a number of people see it, it's an issue.

The problem mainly arises when using multiple monitors with different resolutions...in particular having one monitor over the top over another, and it is definitely a bug since the only module affected is the Soft Tube saturation knob...resetting and rescanning will not help if it is a bug in the monitor resolution...I can drop the Pro Channel modules onto my primary monitor and get it to populate and work correctly but if it is loaded into the secondary monitor first the glitch happens...
 
Probably low priority for the bakers since it's an eye-candy issue and you can work around it...for me I just ditch the Soft tube channel since it is a cheap way to add distortion that you can get away with and should have done in your signal chain to begin with...if you like that sort of stuff...lots of ways to get the same effect without using it...but it's a cheap and quick way to pretend like you have an analog path somewhere...

Technically though it's not a cakewalk product, it was developed by softube. It would be up to their developers to address any graphics issues the plugin has. I'd hazard to guess that because their saturation knob is a free product it wouldn't be a high priority.

ampfixer
Who knows John. Perhaps the problem is tied to a particular chipset. If a number of people see it, it's an issue.

No question its an issue. Its been reported enough. However I don't have the problem and thus it doesn't seem to be a bug for everybody.
 
Lately we have seem a few people reporting "bugs" when it was user error.  
 
In this case it maybe a bug but as reported by others here it may not have anything to do with CW. 

John

ampfixer
Who knows John. Perhaps the problem is tied to a particular chipset. If a number of people see it, it's an issue.

No question its an issue. Its been reported enough. However I don't have the problem and thus it doesn't seem to be a bug for everybody.
 
Lately we have seem a few people reporting "bugs" when it was user error.  
 
In this case it maybe a bug but as reported by others here it may not have anything to do with CW. 

Except that Soft tube is firmly planted as a Cakewalk ProChannel module, it is not a separate vst, it has been wrapped up by the bakers and the wrapping has come undone for some of us...

Actually that's not correct.

There is an SDK that Cakewalk provide for developers to make their plugins PC compatible as they are basically VSTs dressed differently and locked to ProChannel.