cclarry
Max Output Level: 0 dBFS
- Total Posts : 20964
- Joined: 2012/02/07 09:42:07
- Status: offline
Saturation Knob bug
I have a situation now where, I will set the Saturation
Knob to a given setting (in this case 4) and then,
when I save the project, it resets itself to 0.
Yes I am using the latest version - 2.3.41
Anyone encountered this or have any insight
or can verify this issue? Thanx!
|
cclarry
Max Output Level: 0 dBFS
- Total Posts : 20964
- Joined: 2012/02/07 09:42:07
- Status: offline
Re: Saturation Knob bug
2016/09/03 16:05:26
(permalink)
25 views and not response...
That's scary!!!
|
Klaus
Max Output Level: -84 dBFS
- Total Posts : 320
- Joined: 2009/07/14 07:34:02
- Location: Cologne, Germany
- Status: offline
Re: Saturation Knob bug
2016/09/03 16:23:36
(permalink)
I just did a quick test, but the setting of the Saturation Knob persisted after saving and reopening the project (tried several times with different values).
Automation?
SONAR Platinum ∞RME HDSPe AIO - Windows 10 64bit - Intel i7 2600K - 16 GB RAM
|
Zargg
Max Output Level: 0 dBFS
- Total Posts : 10666
- Joined: 2014/09/28 04:20:14
- Location: Norway
- Status: offline
Re: Saturation Knob bug
2016/09/03 16:26:18
(permalink)
Hi, Larry. I am sorry to say that I cannot replicate on my laptop. It keeps the setting after saving and reopening the project. Does this happen in every project, or just this one?
Will check my studio pc tomorrow when I get home.
All the best.
Ken Nilsen ZarggBBZWin 10 Pro X64, Cakewalk by Bandlab, SPlat X64, AMD AM3+ fx-8320, 16Gb RAM, RME Ucx (+ ARC), Tascam FW 1884, M-Audio Keystation 61es, *AKAI MPK Pro 25, *Softube Console1, Alesis DM6 USB, Maschine MkII Laptop setup: Win 10 X64, i5 2.4ghz, 8gb RAM, 320gb 7200 RPM HD, Focusrite Solo, + *
|
cclarry
Max Output Level: 0 dBFS
- Total Posts : 20964
- Joined: 2012/02/07 09:42:07
- Status: offline
Re: Saturation Knob bug
2016/09/03 17:56:28
(permalink)
Only thing I have automated is the Volume envelope...so that
can't be it...I've only noticed it on the current project, but it's the only
one I've used the Saturaton Knob on so kind of a catch 22...
Kinda weird...
|
chuckebaby
Max Output Level: 0 dBFS
- Total Posts : 13146
- Joined: 2011/01/04 14:55:28
- Status: offline
Re: Saturation Knob bug
2016/09/03 19:39:45
(permalink)
Larry, might be just as important, what kind of track are you using it on ?
a midi track, Audio track ? if midi, what VST-I is it ?
Windows 8.1 X64 Sonar Platinum x64 Custom built: Asrock z97 1150 - Intel I7 4790k - 16GB corsair DDR3 1600 - PNY SSD 220GBFocusrite Saffire 18I8 - Mackie Control
|
cclarry
Max Output Level: 0 dBFS
- Total Posts : 20964
- Joined: 2012/02/07 09:42:07
- Status: offline
Re: Saturation Knob bug
2016/09/04 06:39:26
(permalink)
chuckebaby
Larry, might be just as important, what kind of track are you using it on ?
a midi track, Audio track ? if midi, what VST-I is it ?
It's on a Rock Vocal Track chuckebaby...recorded audio... I've never encountered anything like it...maybe I need to remove it and then put it back and see if the problem goes away...might have accidentally hit some setting that is causing it...
|
cclarry
Max Output Level: 0 dBFS
- Total Posts : 20964
- Joined: 2012/02/07 09:42:07
- Status: offline
Re: Saturation Knob bug
2016/09/04 07:16:22
(permalink)
Nope...removing it...and then putting it back did nothing.
And it does the same on every track...
|
Bristol_Jonesey
Max Output Level: 0 dBFS
- Total Posts : 16775
- Joined: 2007/10/08 15:41:17
- Location: Bristol, UK
- Status: offline
Re: Saturation Knob bug
2016/09/04 11:37:04
(permalink)
Just tried it on my laptop and the settings persist after saving/closing/re-opening.
CbB, Platinum, 64 bit throughoutCustom built i7 3930, 32Gb RAM, 2 x 1Tb Internal HDD, 1 x 1TB system SSD (Win 7), 1 x 500Gb system SSD (Win 10), 2 x 1Tb External HDD's, Dual boot Win 7 & Win 10 64 Bit, Saffire Pro 26, ISA One, Adam P11A,
|
gustabo
Max Output Level: -49.5 dBFS
- Total Posts : 2591
- Joined: 2009/01/05 17:32:38
- Status: offline
Re: Saturation Knob bug
2016/09/04 11:45:41
(permalink)
☄ Helpfulby cclarry 2016/09/04 11:46:35
My settings persist as well, both on track PC and buss PC
Cakewalk by Bandlab - Win10 Pro x64 - StudioCat Platinum Studio DAW - 32 GB Ram - MOTU UltraLite-mk3
M-Audio Keystation 88ES - Akai MPD26 (hot-rodded) - Alesis DM10 - a few guitars, a few amps
Novation Launch Control - Korg nanoKONTROL2 - PreSonus FaderPort - DAW Remote HD on iPad
Adam A7X - Behritone C50A
PreSonus Monitor Station v2 (controlling the mons)
https://www.facebook.com/groups/sonarusergroup/
|
cclarry
Max Output Level: 0 dBFS
- Total Posts : 20964
- Joined: 2012/02/07 09:42:07
- Status: offline
Re: Saturation Knob bug
2016/09/04 11:52:52
(permalink)
Ok...even in NEW project the same behavior.
If I put SK on the PC and change the settings,
the second I hit SAVE the settings revert to
the default...if I change ANYTHING, the second
I save the project everything reverts back to
the default settings....
|
gokidsmusic
Max Output Level: -89 dBFS
- Total Posts : 51
- Joined: 2010/11/09 16:29:40
- Location: NC
- Status: offline
Re: Saturation Knob bug
2016/09/04 11:55:57
(permalink)
☄ Helpfulby cclarry 2016/09/04 13:24:32
The Pro-Channel version I have is 1.3.8. There is no save issue on my machine.
I never install the saturation knob with my other Softube plugs since it was included with Sonar at some point in time.
In order to see if I could duplicate your issue, I installed the saturation knob by the Softube Plug-Ins Control app.
After the usual VST scan, the Sonar version was still 1.3.8 in the PC and Sonar crashed when I tried to play the small project.
I removed the saturation knob from the "C:\Program Files\Cakewalk\Shared Utilities\Internal" folder and rescanned.
The PC version was then 2.3.41 and Sonar played as is typical.
Tweaked the saturation knob settings and closed the file. I was prompted to save my changes. Reopened file. Settings was 0 on the saturation knob.
I can confirm that the action of hitting save moves the setting to 0 on the v2.3.41 of the PC instance.
I then replaced the 1.3.8 version in the internal folder and removed the VST2 saturation knob .dll. The VST3 and the older PC version coexist without issue and the older version keeps its setting as is usual.
I inserted the VST3 version of the saturation knob in the FX bin and in an FX chain in the PC both retain their setting on save and reopen.
Good luck.
Greg O
Greg OliverWindows 10 64bit, AMD FX-9590, 16 Gb ram, AMD Radeon HD 7450, ASUS M5A99FXPro R2.0, 240Gb SSD system drive, 2- 1Tb Int, 480Gb & 240Gb SSD sample drives.Cakewalk by Bandlab, Sony Sound Forge 11PreSonus AudioBox 1818VSL, Tascam FW-1884, Melda (All), Waves (All), Sound Toys (All), Eventide (All), Nomad Factory (All), Overloud (All), Softube (Most), Boz (All), XLN (All), Steven Slate Drums & Trigger2 (All)
|
cclarry
Max Output Level: 0 dBFS
- Total Posts : 20964
- Joined: 2012/02/07 09:42:07
- Status: offline
Re: Saturation Knob bug
2016/09/04 13:05:03
(permalink)
Thanx for the confirm Greg...I was pretty sure I wasn't completely crazy...LOL
|