

- SOFTUBE FREE SATURATION KNOB WONT WORK INSTALL
- SOFTUBE FREE SATURATION KNOB WONT WORK UPDATE
- SOFTUBE FREE SATURATION KNOB WONT WORK PC
There was a step in there that required the deletion of the Saturation Knob dll as it was updated with the X1D Expanded update patch". "Did you correctly folllow the procedure when updating to X1D. I was able to access the plugin by clicking the +button at the top right of the FX module. You notice these VST instances are on busses. "It is not available as an fx insert on any channel or buss".
SOFTUBE FREE SATURATION KNOB WONT WORK PC
Right click anywhere in the PC window to open up the selections". "The saturation knob is only accessible via the ProChannel interface. I always use Administrator access if that matters.Īny other option I haven't thought off? Any help appreciated. Is 1- the Sat Knob installed to the correct folder, maybe the reason it's not available as a PC module?Ģ- do I need to manually reinstall or move (carefully!) the Sat Knob folder to the VST Plugin folder & rescan? The recently purchased PC4K S-Type Comp & PC4K Gate/Exp modules installed to the same folder with no problems (they show up & are available as plugins for the audio tracks. I have run the Plugin Manager VST scanner several times with no change, that is, it's not available in any audio track. When I installed X1Expanded following the detailed instructions, Sat Knob.dll installed (as I recall by default)to C:\Program Files\Cakewalk\Shared Utilities\Internal\Softube & C:\Program Files (x86)\Cakewalk\Shared Utilities\Internal\Softube folders. My SofTube Sat Knob is only coming up as an audio FX option for the buss(Master, Preview, etc.) FX modules. No problem for me.I just overwrite it and carry on with the newer bug fixed version.Another Can't Find Softube, Sort of (continued from Can't Find Softube thread, message #12 ), Sorry my original post was probably not clear on this.įor me, the latest update worked fine but I have a very recent beta version of the Softube Saturation Knob which fixes a bug that still exists in the X1d version of it. I was just wondering how it ever got that way in the first place. After blowing away the directory obviously this is not NOW a problem. That should not have happened cause it meant that any time he would ever update he would never see whatever got fixed. My "woaaa" was more directed at the fact that he was pointed at the backup version of the Softube Saturation Knob in the first place. The X1d installer will create a new Saturation Knob.dll file for you. In most cases this is C:\Program Files\Cakewalk\Shared Utilities\Internal\Softube or C:\Program Files (x86)\Cakewalk\Shared Utilities\Internal\Softubeĭelete all of the contents of the "Softube" folder (including both the "Saturation Knob.dll" as well as the "Backup" folder). Navigate to the location where your Softube Saturation Knob is installed.
SOFTUBE FREE SATURATION KNOB WONT WORK INSTALL
This is described in the install instructions: In David's case, it sounds like he removed the Backup but hasn't done a re-scan so the VST scanner cannot locate the missing component. If you really want to keep it around, you can definitely do as you suggest though. To install the updated Saturation Knob.dll, on the other hand, you do not need the previous.

If you delete your backup of that, you're out of luck. The difference is that to install X1d over a Quickfix, you need the previous. The backup folder in the Softube folder is redundant at this point, unlike the backup folder in the SONAR directory. Renaming, as you suggested, or removing should do the trick. Softube told me that this was an issue with the Cakewalk installer and they were supposedly going to talk to Cakewalk about this. I had this very same issue while beta testing some fixes Softube gave me for the Saturation Knob and this is what I had to do. It will say it is not found and then you can reinstantiate the plug in your project and it will find it in the correct directory and NOT the backup directory. Rename that VST extension to dll.backup and then rescan and it won't try to load that.

Woaaaa.The bigger problem is that the VST it is trying to find is in the backup directory.
