My neighborout maybe are thinking I'm gonna mad ..... I mad a big scream of victory. :D Thank you mr Lentini for your help. Finally with the use of the app notepad++ whit your suggest of return key I have the VST3 working. Sorry, this is my first experience with ini file. A big thank you for you precious work in Saw Studio, the only DAW I enjoy to use. The best daw period.

JMH, thank you for your suggest. In the next day I try to use it.

[quote="VANDERGRAAF"]Please can someone help me ?[/QUOTE]

[URL]https://www.sawstudiouser.com/forums/showthread.php?20201-INI_Builder-for-SAWStudio64-V2-has-been-added-to-Control2Tempo-(SSC2T)[/URL]

Follow the install instructions (the first few lines of the 2nd post). You can have your ini in 10 minutes.

...after that, with a few adjustments, you can have them install directly into VST_Plugins (making a zip of your old inis). It doesn't do one ini - it does them all, effortlessly. Waves (if you got them) everything.
Oh yeah, it makes them for SAC64 too.

what else, you can have renames (I prepend all of my waves plugins with w_ ) ***
you can filter them, so only some inis get built - and differently for sac.

BTW, (since everyone seems squeamish about trying this) that SETUP was built on my machine with iexpress, and the install script and contents written entirely by me. Also I should note that the script doesn't do anything 'to' studio. It mimics running it by a sequence of pulling down menues, mouse clicks, etc... If you don't load the script, it is not there. If you do, it does nothing. But in the 2nd case, if you press one of the defined hotkey combos (nearly all use the backtick plus another key), it will call an autohotkey function. In the case of INI_Builder, backtick + x

Also I just tried the download link, on my test machine, defender popped up and challenged me - which I have to admit is quite ominous. I had to navigate and click 'run anyway' (this wasn't happening when I tested it off the flash drive - it gets tagged when an internet origin). This happens because it is an unsigned file - and I'm not shelling out a couple of hundred to buy a code signing certificate for something I'm giving away.

Note; the inis are built with 8.3 short filenames. It doesn't matter unless you have a registry entry to disable that - very unlikely. I had done that before I realized Bob had a long-filename fix. If I re-build I'll probably remove that.

*** This done by changing one line in [font=system]"C:\SAWStudio64\VST_PlugIns\INI_BUILDER\CONFIGS\VS T3_filter.SAWStudio64" (which was automatically generated)[/font]
[font=system]
vendor='waves'
[/font][font=system]to
vendor='waves', prefix='w_'[/font]

Make sure you end the path line in the .ini file with a Return key... just one... so the cursor in the file ends up on the 2nd line and goes down no further.... if you press the doen arrow key, there should be no blank extra lines.

See if that helps.

Bob L

Good morning. I have a problem with ini file in Saw Studio V2 in Windows 11

I have read every post in this forum about VST3 and in file, trying to find a solution.


SAW V 2.4 installed. I have installed different VST3 in r: C: Program File, Common File, VST3.

Now I have try to use different editor like metapad, notepad ++, have also download the old Windows notepad. No succes.

The pat I use for example whith Valhalla shimmer is: C:\Program Files\Common Files\VST3\ValhallaShimmer.vst3

I copy it in the editor an save the ini file directly in Saw studio VST Plugin folder. After the creation of the ini file I have try to open Saw Studio. Different editor and try. different results:

sometimes SS not open at all, sometimes it try to open, the message: "initialize plugin" appear but stay for a long time without stop processing.

When Saw Studio open the VST3 is not visible in Saw Studio.

Please can someone help me ?