So, I just bought the JST Toneforge Jason Richardson amp sim. Was super excited about it; started playing around with it and was thrilled. Until I started encountering issues...
Tried copying an instance of Toneforge to another track...parameters were obliterated (didn't copy over), and audio sounds really weird...thin and brittle and almost 8-bit-ish....even after fixing the parameters that were suddenly different.
Okay, whatever....just insert a whole new instance of Toneforge and tweak to taste. Sucks that I have to do that for every track, but whatever, right?
Except I then found that reopening the project does the same thing to all instances of Toneforge and I have to start all over. Every time.
So basically I just blew $50 on a plugin I can't really use.
Anybody had similar experiences with any plugins? I know that there were some random "plugin state recall" issues like this, particularly with VST3s, that were finally supposedly fixed recently. But here we are. Also, it does this with both the VST2 and VST3 versions of Toneforge. (Additional info: 64-bit W10; and I've confirmed I installed the 64-bit versions of the plugins.)
Also important to note that I do have other JST plugins (Gain Reduction deluxe and JST Clip) and have not had the same issues. I also have other, older amp sims (Peavey Revalver) that do not have this issue, and I haven't noticed it with any other plugins of mine at all. (Having said that, I haven't used all of my plugins since the last update, so there's that.)
I've sent support tickets to both JST and Cakwalk, but if anyone has any thoughts, they'd be appreciated.
TL;DR: Cakewalk doesn't recall Toneforge parameters/state when a) reopening project or b) when copying plugin to another track, and causes odd plugin behavior with regard to the audio (audio sounds really weird...thin and brittle and almost 8-bit-ish) even after settings are readjusted.
Question
AxlBrutality
So, I just bought the JST Toneforge Jason Richardson amp sim. Was super excited about it; started playing around with it and was thrilled. Until I started encountering issues...
Tried copying an instance of Toneforge to another track...parameters were obliterated (didn't copy over), and audio sounds really weird...thin and brittle and almost 8-bit-ish....even after fixing the parameters that were suddenly different.
Okay, whatever....just insert a whole new instance of Toneforge and tweak to taste. Sucks that I have to do that for every track, but whatever, right?
Except I then found that reopening the project does the same thing to all instances of Toneforge and I have to start all over. Every time.
So basically I just blew $50 on a plugin I can't really use.
Anybody had similar experiences with any plugins? I know that there were some random "plugin state recall" issues like this, particularly with VST3s, that were finally supposedly fixed recently. But here we are. Also, it does this with both the VST2 and VST3 versions of Toneforge. (Additional info: 64-bit W10; and I've confirmed I installed the 64-bit versions of the plugins.)
Also important to note that I do have other JST plugins (Gain Reduction deluxe and JST Clip) and have not had the same issues. I also have other, older amp sims (Peavey Revalver) that do not have this issue, and I haven't noticed it with any other plugins of mine at all. (Having said that, I haven't used all of my plugins since the last update, so there's that.)
I've sent support tickets to both JST and Cakwalk, but if anyone has any thoughts, they'd be appreciated.
TL;DR: Cakewalk doesn't recall Toneforge parameters/state when a) reopening project or b) when copying plugin to another track, and causes odd plugin behavior with regard to the audio (audio sounds really weird...thin and brittle and almost 8-bit-ish) even after settings are readjusted.
Link to comment
Share on other sites
9 answers to this question
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now