More free VSTs needing an .ini file lately

[Angie]

There has been a lot of praise for the Valhalla Room reverb here. A few days ago, I finally had a chance to check out all of the Valhalla plugins. Most are demos with installers, but the FreqEQ is free. All the demos installed and worked just fine in SAWStudio. The free one gave me a little trouble. Moving the dll to the VST folder caused an instant crash when opening SS. This was frustrating because it looks like a cool effect. I decided to try something. I created a folder within the VST_Plugin folder and moving the dll to it, created an .ini file for it. SS didn't crash on opening and I was able to load the plugin without a problem. Remembering some other free plugins that were causing crashes, I did the same for them with success.

Now, I don't know if it is just my system. But I've only had to do this one other time. It seems more and more common to me. I thought I'd throw it out there if it hasn't been discussed before.

BTW, I really like the Vintage.

[Dave Labrecque]

I decided to try something. I created a folder within the VST_Plugin folder and moving the dll to it, created an .ini file for it. SS didn't crash on opening and I was able to load the plugin without a problem. Remembering some other free plugins that were causing crashes, I did the same for them with success.

Cool find, Angie. One wonders how many other such DLL placement issues for SAW (including non-free ones) would be fixed by this approach, when all along we thought it was placement in C:\Program Files (x86)\Steinberg\Vstplugins or C:\Program Files (x86)\Vstplugins that was the key.

[mr_es335]

Hello,

A question: Are you referring to the Valhalla FreqEcho vst? I am not finding a FreqEQ, but I do see the ValhallaFreqEcho vst?

Personally, I have never had any problems with the Valhalla DSP products. I just tested the FreqEcho and it works just fine via drag 'n drop.
Generally most vst's like these do not care where they are placed - especially those that do not use an actual installer - like the FreqEcho. So, you just might have a glitch somewhere in your system.

Given that, I still prefer Bob's method of organizing vst's - which I do find pretty slick. As much as is possible, I try to save all of the vst's in the VST_PlugIns folder. With that done, I will then put all of the same type of vst's in a separate folder inside the VST_PlugIns folder and create .ini files pointing to those vst's. This not only keeps the VST_PlugIns folder really clean and organized, but it also allows for renaming the vst's to anything that you would want.

For example, I will create a Delay folder and have all of the Delay vst's in that folder. Then I will create a separate .ini file for each vst in that folder. For the FreqEcho - the actual name is "ValhallaFreqEchoMkI.dll" - so I can rename the .ini file as "FreqEcho". Much more readable than "ValhallaFreqEchoMkI.dll". Also, when testing vst's, you can easily see the .dll's from the .ini's - as the icon graphics are different. Way to go, Bob!

Hope this helps, or is useful.

[Angie]

Hello,

A question: Are you referring to the Valhalla FreqEcho vst? I am not finding a FreqEQ, but I do see the ValhallaFreqEcho vst?

Yep. Sorry, the FreqEcho is the one.

Generally most vst's like these do not care where they are placed - especially those that do not use an actual installer - like the FreqEcho. So, you just might have a glitch somewhere in your system.

I've not had this problem in the past either. Maybe it is my system. Don't know what exactly would change the behavior. Just thought I'd mention it and my solution.

[TotalSonic]

Angie -
I don't know if this helps dealing with these types of issues any easier for you - but there are two small utility apps that are designed to streamline the steps of creating .ini files for linking VST plugins placed in various other folders into SAWStudio.

They are:

http://www.richmccoy.com/SAWStudioSACVSTINITool/
(Windows 7 compatible)

http://www.efofex.net/software.html
(Windows XP only)

Best regards,
Steve Berson

[Angie]

Angie -
I don't know if this helps dealing with these types of issues any easier for you - but there are two small utility apps that are designed to streamline the steps of creating .ini files for linking VST plugins placed in various other folders into SAWStudio.

They are:

http://www.richmccoy.com/SAWStudioSACVSTINITool/
(Windows 7 compatible)

http://www.efofex.net/software.html
(Windows XP only)

Best regards,
Steve Berson

Thanks Steve,
I'm aware of those. There is this one too. http://www.avocadoproductions.com/VS...ive_paths).zip

[Sean McCoy]

BTW, I really like the Vintage.

Not to hijack the thread, but I'm interested in whether you hear a distinct difference between the Valhalla Vintage and Room reverbs. I love and use the room, but I'm pretty happy with my UAD Lexicon 224 and wonder if I really need another Lexi-type plugin. Of course, for fifty bucks it's not much of a risk, but I'm already suffering from plugin overload.

[Angie]

Not to hijack the thread, but I'm interested in whether you hear a distinct difference between the Valhalla Vintage and Room reverbs. I love and use the room, but I'm pretty happy with my UAD Lexicon 224 and wonder if I really need another Lexi-type plugin. Of course, for fifty bucks it's not much of a risk, but I'm already suffering from plugin overload.

I can't say I hear a difference exactly. I was happier with what I was dialing in on the Vintage with the material I was using to demo them at the time.

[Sean McCoy]

I can't say I hear a difference exactly. I was happier with what I was dialing in on the Vintage with the material I was using to demo them at the time.

Cool, thanks, Angie. I'll get the Vintage demo and check it out.

[Dave Labrecque]

Watched Thor for the first time tonight. There was a brief reference to Thor's people's 'heaven', if I understood correctly. They called it 'Valhalla'. Kooky, huh? ...which lead me to this.

So... which came first -- the plug-in or... ?