The Dreaded .ini file

[richswit]

Hello,
For almost 20 years, i've never been able to get .ini files to work...I always installed VST plugs directly into the Saw VST folder....
But now that I have SawStudio V2, I have to get .ini files to work.

Here's what I've done so far..in Windows 11 I right click on the VST3 plug and choose copy file path, and I get this:

"C:\Program Files\Common Files\VST3\SINE Player.vst3"
I then remove the quotes, correct? and get this:
C:\Program Files\Common Files\VST3\SINE Player.vst3

I save the file from notepad into Saw Vst plugins folder as Sine.ini

The pretty green "sine" shows up in Saw Plugins, but when I try to load, the old "trouble loading Plugin" jumps up...

I then tried this:
C:\Program_Files\Common_Files\VST3\SINE_Player.vst3 ( and yes I hit return at the end.
Still no go...


Anyone notice what the hell I'm doing wrong????
Thanks very much
Rich

[ivanoff]

Hi, Bob answers here :
https://www.sawstudiouser.com/forums/sh ... 2-Released

[richswit]

Hi, Bob answers here :
https://www.sawstudiouser.com/forums/sh ... 2-Released

Been over that 10 times. I

[richswit]

OK...I downloaded Notepad++ and now things are working....
Good day

[Todd R]

what were you using? wordpad? I have always used notepad :-)

[Bob L]

Remember... notepad in Win 11 no longer outputs ASCII Text files... you must use something like NotePadd++.

Bob L

[richswit]

Remember... notepad in Win 11 no longer outputs ASCII Text files... you must use something like NotePadd++.

Bob L

I know that now!***129322;

[Todd R]

Remember... notepad in Win 11 no longer outputs ASCII Text files... you must use something like NotePadd++.

Bob L

Thanks...I'll stay with 10 as long as I can... I have been using Notepad++ for years mainly for sysex/ midi conversion named ticks files

[mr_es335]

Hello,

Why not just employ metapad...works absolutely wonderful for many, many operations!!! [Click_me]
* And...by-the-way, it is portable as well...and only 190kb!
* Make sure you place the exe in the root of the Windows folder!!
* I employ metapad for .txt, ini and cmd edits.

WordPad does NOT do ASCII!!!

[jmh]

Just a heads up, rather than do it the hard way, making defective inis with typos, I'm putting the time into writing a tool to make vst3 inis for v2 quick and easy. Is anybody interested?

Stay tuned, it will take a couple of days to make it presentable (alas, I'm not on linux, otherwise it would have been hours - and done).

[Dave Labrecque]

Is anybody interested?

Be assured that everyone is interested.

[mr_es335]

Hello!

Sorry Dave...I for one am NOT interested...as I do not have issues with .ini files.

I really do not understand why anyone has issues with this feature set of RML Labs software?

[cgrafx]

Hello!

Sorry Dave...I for one am NOT interested...as I do not have issues with .ini files.

I really do not understand why anyone has issues with this feature set of RML Labs software?

Hey Dell, the issue is with the new version of SAW studio, because VSTs need to be installed in their native location and pointed to by the .ini file.

You can no longer move the VSTs into the SAW VST directory. So this makes things a little more complicated (not hard, but for some getting the correct directory path can be more difficult).

[mr_es335]

cgrafx,

You stated 1st, "...because VSTs need to be installed in their native location and pointed to by the .ini file..."

Okay, this feature is not something NEW as this feature has been the case with many plug-ins!

You stated 2nd, "...You can no longer move the VSTs into the SAW VST directory. So this makes things a little more complicated (not hard, but for some getting the correct directory path can be more difficult)..."

Okay, but I am always surprised as to how it is that some find getting the path difficult!

In some cases, the "mklink" command can come in handy!

[Dave Labrecque]

Hello!

Sorry Dave...I for one am NOT interested...as I do not have issues with .ini files.

I really do not understand why anyone has issues with this feature set of RML Labs software?

Dell,

I'm not sure what you mean my "issues," but I think the intention is to automate the INI file creation process, which can be a huge time saver for anyone with lots of VSTs or VST3s.

You're welcome to create each INI file in any way you like, of course. To create my dozens, I'd prefer pushing a button. YMMV.

[jmh]

My ini builder is coming along fine. I'm going away till the new year, so I'll be taking a week off from this.

Ridiculously I decided to process licensed waves plugins also - which has thrown obstacles to the left and right, and basically made it 10 times more difficult. I imagine SAC64 also will support VST3? If so, what is the standard name for its folder and its vst3's? Not being a SAC user, I assume you may use a different collection of plugins (like low or no latency) than you would on Saw. Anyway since I'm doing this, I may as well make it ambidextrous.

Can I expect powershell to already be installed on any windows installation that will run SS64?