ValhallaRoom 1.5.1 Released. New Electric Blue GUI
-
- angelboy
- 4586 posts since 21 Aug, 2001 from Larnaca, Cyprus
- KVRAF
- 3432 posts since 28 Jan, 2006 from Phoenix, AZ
uhh, no.TristezaOrange wrote:The money! It's burning a hole in my pocket!
- KVRAF
- Topic Starter
- 3426 posts since 15 Nov, 2006 from Pacific NW
?Architeuthis wrote:uhh, no.TristezaOrange wrote:The money! It's burning a hole in my pocket!
-
- angelboy
- 4586 posts since 21 Aug, 2001 from Larnaca, Cyprus
Yeah, I didn't get that either!valhallasound wrote:?Architeuthis wrote:uhh, no.TristezaOrange wrote:The money! It's burning a hole in my pocket!
BTW when???!?!?!?
- KVRAF
- 3922 posts since 15 Dec, 2009
Lol, burning here too..
Demo sounds absolutely great.. This might well be one of those times where the increased expectations of a wait will be justified..
Demo sounds absolutely great.. This might well be one of those times where the increased expectations of a wait will be justified..
- KVRAF
- 1855 posts since 21 Sep, 2004 from Musician, Recording Engineer, Producer
- KVRAF
- Topic Starter
- 3426 posts since 15 Nov, 2006 from Pacific NW
My beta testers have let me know that the installer needs some refinement. Right now, the 32-bit and 64-bit VSTs are installed in the same folder, and my beta testers have said that this creates problems with Reaper. F***ing beta testers.
I'm setting the wayback machine to 1985, and learning enough Pascal to create an installer script to allow the user to specify different locations for the 32-bit and 64-bit VSTs. This won't be done today - at least not in time to get the installer posted to the website and be ready for orders.
The VSTs are working great for all beta testers, and work for me on my Win7 and XP machines. I would just put these out as raw DLLs, but the presets need to be installed in a very particular location, so an installer is a necessity for this release.
So...Monday.
I'm setting the wayback machine to 1985, and learning enough Pascal to create an installer script to allow the user to specify different locations for the 32-bit and 64-bit VSTs. This won't be done today - at least not in time to get the installer posted to the website and be ready for orders.
The VSTs are working great for all beta testers, and work for me on my Win7 and XP machines. I would just put these out as raw DLLs, but the presets need to be installed in a very particular location, so an installer is a necessity for this release.
So...Monday.
-
- KVRian
- 608 posts since 18 Apr, 2010
- KVRAF
- 3922 posts since 15 Dec, 2009
Exciting..
Shame to hear about the fixed preset path though, I really wish everything could be in the same folder. Remembering and/or hunting for paths here and there is so tiresome when loading and backing up.
Would be so nice if every manufacturer could just have things together with the dll. Can you share why there is a need for the fixed paths?
Shame to hear about the fixed preset path though, I really wish everything could be in the same folder. Remembering and/or hunting for paths here and there is so tiresome when loading and backing up.
Would be so nice if every manufacturer could just have things together with the dll. Can you share why there is a need for the fixed paths?
- KVRAF
- Topic Starter
- 3426 posts since 15 Nov, 2006 from Pacific NW
There aren't fixed paths - I'm trying to fix the path issues I am having with my installer. Which means allowing the user to choose the install directory or directories for the plugins. If you want to put both 32-bit and 64-bit VST .dlls in the same directory, you will be able to do so with the new installer. This is the behavior that my installer was defaulting to before, but the beta testers flagged this as causing some problems.V'ger wrote:Exciting..![]()
Shame to hear about the fixed preset path though, I really wish everything could be in the same folder. Remembering and/or hunting for paths here and there is so tiresome when loading and backing up.
Would be so nice if every manufacturer could just have things together with the dll. Can you share why there is a need for the fixed paths?
And the presets have to be in a particular place for the plugin to find them. Putting them in the same folder as the .dll would clog up that folder. I forget the actual path for the presets, so having these in an installer is the best solution.
On OSX, Apple has provided both user and system directories for all plugin formats (AU, VST, RTAS). So creating an installer is easier on the Mac - I just install things in the system directory.
Sean Costello
- KVRAF
- 3922 posts since 15 Dec, 2009
So I can put everything in the dll folder if I want to? (or as I prefer; a preset subfolder in the dll folder)valhallasound wrote:There aren't fixed paths
- KVRAF
- Topic Starter
- 3426 posts since 15 Nov, 2006 from Pacific NW
No, the presets go in their own folder, outside of the .dll folder. The plugin looks in a specific system directory for the presets.V'ger wrote:So I can put everything in the dll folder if I want to? (or as I prefer; a preset subfolder in the dll folder)valhallasound wrote:There aren't fixed paths
- KVRAF
- 3922 posts since 15 Dec, 2009
What's the difference between specific and fixed folder?
And why apart from the 'clogging' factor can't we have presets in the dll folder?
And why apart from the 'clogging' factor can't we have presets in the dll folder?
-
Funkybot's Evil Twin Funkybot's Evil Twin https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=116627
- KVRAF
- 12459 posts since 16 Aug, 2006
I'm guessing that UAC is the reason. Windows seems to want any user created files to only get written to certain folders.V'ger wrote:And why apart from the 'clogging' factor can't we have presets in the dll folder?
- KVRAF
- Topic Starter
- 3426 posts since 15 Nov, 2006 from Pacific NW
Because the plugin doesn't look for presets there. It looks in a system-specific folder. This is necessary for the cross-platform preset code to work properly.V'ger wrote:What's the difference between specific and fixed folder?
And why apart from the 'clogging' factor can't we have presets in the dll folder?

