Latest News: Kuassa Anniversary Sale
Issue when saving Vermilion as part of an FX Chain Reaper.
-
- KVRer
- Topic Starter
- 5 posts since 14 Feb, 2017
Hello All.
I was really glad to find this forum a few days ago. I've been using Vermilion 1.1.1 for a while now ( just upgraded to 1.1.3), and am really impressed with the range of sounds it produces, and how well it takes Impulse Responses too.
I have however come up against an issue with Vermilion that I can't seem to work around.
I use Reaper, and when I'm sorting my guitar sound, I sometimes use other vsts for tube screamers, reverb, etc etc, and when I have the sound I like, I save it all as an FX Chain so I can recall it at any time and get the same sound-or so I thought.
All my other Vsts retain the settings in the FX chain, but Vermilion always goes back to the Clean Reverb stock setting. If I make my own preset and save it in an FX chain, it does the same thing.
Now I know this is only a small point, but if you have a few guitar tracks in each song, having to go back and manually change Vermilion settings every time you go back to work on the song, gets to be a right pain after a while.
So, my question is, am I doing something wrong, am I missing something?
Thanks in advance for your help.
Joe
I was really glad to find this forum a few days ago. I've been using Vermilion 1.1.1 for a while now ( just upgraded to 1.1.3), and am really impressed with the range of sounds it produces, and how well it takes Impulse Responses too.
I have however come up against an issue with Vermilion that I can't seem to work around.
I use Reaper, and when I'm sorting my guitar sound, I sometimes use other vsts for tube screamers, reverb, etc etc, and when I have the sound I like, I save it all as an FX Chain so I can recall it at any time and get the same sound-or so I thought.
All my other Vsts retain the settings in the FX chain, but Vermilion always goes back to the Clean Reverb stock setting. If I make my own preset and save it in an FX chain, it does the same thing.
Now I know this is only a small point, but if you have a few guitar tracks in each song, having to go back and manually change Vermilion settings every time you go back to work on the song, gets to be a right pain after a while.
So, my question is, am I doing something wrong, am I missing something?
Thanks in advance for your help.
Joe
-
- KVRer
- Topic Starter
- 5 posts since 14 Feb, 2017
Hi Dimitar
Thanks for the replies.
This happens when I use verion 1.1.1 of Vermilion. I've just upgraded to 1.1.3 so I'll try it out and get back to you to see if the issue happens.
As for switching to VST2, on the Kuassa site I can only see downloads for VST and VST3 for 64 bit windows, should I go for VST, and will there be much difference, especially in the sounds?
Thanks
Joe
Thanks for the replies.
This happens when I use verion 1.1.1 of Vermilion. I've just upgraded to 1.1.3 so I'll try it out and get back to you to see if the issue happens.
As for switching to VST2, on the Kuassa site I can only see downloads for VST and VST3 for 64 bit windows, should I go for VST, and will there be much difference, especially in the sounds?
Thanks
Joe
-
- KVRer
- Topic Starter
- 5 posts since 14 Feb, 2017
Hi Dimi,
I've been able to do some testing of the versions of Vermilion and it's exactly as you expected.
I tried the up to date version (1.1.3) of VST3 last night, and the issue was still there.
I tried the up to date version of VST this morning, and everything worked fine. When I saved my preset sound in the FX Chain, and went back to it later on, it recalled it perfectly, so problem solved .
I'm wondering now if I should email Kuassa about the issue, to let them know, or are they already aware of it?
Thanks very much for your help Dimi.
I've been able to do some testing of the versions of Vermilion and it's exactly as you expected.
I tried the up to date version (1.1.3) of VST3 last night, and the issue was still there.
I tried the up to date version of VST this morning, and everything worked fine. When I saved my preset sound in the FX Chain, and went back to it later on, it recalled it perfectly, so problem solved .
I'm wondering now if I should email Kuassa about the issue, to let them know, or are they already aware of it?
Thanks very much for your help Dimi.
- KVRAF
- 23101 posts since 7 Jan, 2009 from Croatia
Hmmmm, this actually looks to be a bug with Kuassa's VST3 implementation, not Reaper's, as other VST3 plugins that I have recall properly when stored in an FX chain or a track template.dimitar wrote:There's still bug with VST3 in Reaper.
-
- KVRer
- Topic Starter
- 5 posts since 14 Feb, 2017
Hey Dimi
The fact that it's a known bug in VST3 and will be fixed is good news.
The fact that using VST instead of VST3 gets rid of the problem is really good news
No more having to remember what presets I used on what song, they'll be there when I open them now
Time to go play with Vermilion and make some presets
Thanks Guys
Joe
The fact that it's a known bug in VST3 and will be fixed is good news.
The fact that using VST instead of VST3 gets rid of the problem is really good news
No more having to remember what presets I used on what song, they'll be there when I open them now
Time to go play with Vermilion and make some presets
Thanks Guys
Joe
-
- KVRAF
- 2240 posts since 13 Dec, 2003
Hi Joe, glad it is working now for you!heyjoe73 wrote:Hey Dimi
The fact that it's a known bug in VST3 and will be fixed is good news.
The fact that using VST instead of VST3 gets rid of the problem is really good news
No more having to remember what presets I used on what song, they'll be there when I open them now
Time to go play with Vermilion and make some presets
Thanks Guys
Joe
Post some of your tones-music here
Cheers,
Dimi