Izotope Neutron compatibility

[Bob L]

Sometimes this idea will not work because the installation uses that setting you enter as a base path and then also creates a folder or folders within that path entry... this will cause the plugin link to fail in SAWStudio because the dll must end up in the VST folder itself... so... again... I say... let the plugin install where it wants... then just place the .ini link file in the SAWStudio VST folder and have it point exactlty to where the dll files ended up.

Bob L

[Naturally Digital]

I hear audio, the plugin says, "Track assistant is listening" but nothing ever happens and the spinning ball the the plugin displays just keeps spinning forever even if playback is stopped.

My buffer settings are:

Out preload buffers 4

Out buffer size 512 samples.

No stalling but no action either.

Have you tried 1024?

[demodoc]

Could someone please tell me EXACTLY how to create the .ini file needed to make this work correctly?

The Neutron .dll files (32 bit version) are installed here.

Drive C

Program files (x86)

vst plugins

How does the file look, how is it created? The explanation in the manual confuses me, sorry.

[mr_es335]

Hello.

If the path is [C:\Program Files (x86)\VST Plugins] - then the contents of the .ini file would be:

[full path]\[plug-in name].dll
[space]

For example:

C:\Program Files (x86)\VST Plugins\Neutron.dll
[space]

Note: Ensure that the actual path name and the file name is precise. Also, ensure sure that there is a space following the path statement - as noted.

Hope this helps?

[demodoc]

Hello.

If the path is [C:\Program Files (x86)\VST Plugins] - then the contents of the .ini file would be:

[full path]\[plug-in name].dll
[space]

For example:

C:\Program Files (x86)\VST Plugins\Neutron.dll
[space]

Note: Ensure that the actual path name and the file name is precise. Also, ensure sure that there is a space following the path statement - as noted.

Hope this helps?

There are 2 .dll's

iZNeutron.dll

and

Neutron.dll

It seems both have to be present for it to work. Do I create two files?

[cgrafx]

There are 2 .dll's

iZNeutron.dll

and

Neutron.dll

It seems both have to be present for it to work. Do I create two files?

One file with two lines in it, one for each dll

[mr_es335]

Hello,

No, you just need to use the Neutron.dll I the .ini file - at least this has worked for me.

[demodoc]

Hello,

No, you just need to use the Neutron.dll I the .ini file - at least this has worked for me.

I must be doing something wrong.

I created an ini file using Notepad that read:


C:\Program Files(x86)\Vstplugins\Neutron.dll

with a space at the end. I called the file Neutron.ini.


Sorry to be so dense about this. I just use the software, I don't write files as a rule.

Saw does not recognize it and the plugin doesn't show up.

And when I use the method of copying the plugin .dlls to the SAW vst plugins folder, I must have both Neutron.dll and iZNeutron.dll in the folder for the plugin to show up.

All features of Neutron work except Track Assistant. If I have to live with this to have everything else work, so be it.

[cgrafx]

I must be doing something wrong.

I created an ini file using Notepad that read:


C:\Program Files(x86)\Vstplugins\Neutron.dll

with a space at the end. I called the file Neutron.ini.

I believe there has to be a return at the end of the line not a space

[Bob L]

I suggest reading the helpfile section on plugins... it pretty simply states how to do this. From the helpfile: Some VST Plug-In installations will hardcode or otherwise force their plug-in path to remain intact as installed and will not allow the .dlls to be moved into the SAW VST_PlugIns folder. SAWStudio will allow VST Plugins to reside in any folder on any drive by placing an .ini file substitute in the VST_Plugins folder pointing to the full path of the dll file itself. Open the Notepad (or any other ascii text editor) to create a new text file. Inside the file, type the full drive and path and original .dll filename on the first line of the file. Make sure to finish the line with a carriage return by pressing the [Enter] key to return the cursor to the start of the next line. Then save the file as an .ini file using the same name as the plugin itself. For example, if a VST Plugin called TestPlug.dll is installed to D:\VST\Work, then create an .ini file called TestPlug.ini and inside the file type the line D:\VST\Work\TestPlug.dll followed by a carriage return. This .ini file, placed in the VST_PlugIns folder under SAWStudio, will now link SAWStudio to find the VST plug-in in its originally installed path. This can help solve compatibility issues with hardwired path plug-ins and their various copy protection schemes.

Bob L