VSTI scan freezes up in Vista/lap top

MoBeach · 01-31-2012, 01:17 PM

I installed Reaper on my lap top, Toshiba Satellite with Windows Vista, the program installed okay, when I right click then add a virtual instrument track it scans for the programs I have installed but it always freezes up very quickly. Anyone experience this? When I click cancel I always get that "not responding" error.

Fex · 01-31-2012, 03:45 PM

It might be getting stuck on one particular VST. See if you can figure out which one it's scanning when it freezes. It might be corrupted.

Quote:

Originally Posted by MoBeach

when I right click then add a virtual instrument track

Curious - I don't understand what you're right clicking on. I know two ways to add put a virtual instrument on a track, and neither of them involve right clicking anything.

Try going to Options > Preferences > Plugins > VST, and scanning the VST folder from there. I think you'll have the same problem, but it's worth a try.

DarkStar · 01-31-2012, 03:51 PM

Just double-checking - what path(s) did you select in the Reaper Preferences >> VST plugins?

@Fex
Right-click below any existing TCPs, select "Insert virtual instrument on new track"

Fex · 01-31-2012, 04:26 PM

And now I know three ways.... thanks.

MoBeach · 01-31-2012, 04:58 PM

Quote:

Originally Posted by DarkStar

Just double-checking - what path(s) did you select in the Reaper Preferences >> VST plugins?

@Fex
Right-click below any existing TCPs, select "Insert virtual instrument on new track"

I'm taking a look right now...

It hung up on FM8

Just tried again and it made it further and hung up on Absynth 4

The scan completed and made it through but it skipped over those two and successfully scanned 4 other NI programs.

RJHollins · 01-31-2012, 06:52 PM

This seems to be an issue with many of the DAW's the first time scanning VST's.

The program appears to lock up ... or sometimes, just crash to the desktop! [PC].

If you then re-run the DAW, and continue scanning, it usually ignores the 'troubled' plug and continues to the next. It could crash again ... just re-run till it does a complete scan.

SOME plug-ins can take FOREVER to initialize ... which also looks as if the DAW has locked up.

Fex · 01-31-2012, 07:59 PM

What's the registration status of the troublesome plugs? Are they demo versions? Recently registered?

A plug querying its registration status could cause a minor hiccup the first time it's run. A whole bunch of them doing it.... well....

DarkStar · 02-01-2012, 03:09 AM

If everything else is OK:
-- find your reaper-vstplugins.ini (click [Options], select "Show Reaper resource path ...." to open the folder)
-- close Reaper,
-- make a back-up copy of the .ini file and open the original in a text
-- look at the entries for FM8 and Absynth
-- are they noticeably shorter than the other lines?

If so, then Reaper ran into a problem during scanning. Try removing those 2 lines and starting up Reaper again - it should detect those VSTis again.

MoBeach · 02-01-2012, 04:46 AM

Quote:

Originally Posted by Fex

What's the registration status of the troublesome plugs? Are they demo versions? Recently registered?

A plug querying its registration status could cause a minor hiccup the first time it's run. A whole bunch of them doing it.... well....

They're full registered programs, I registered them a few weeks ago. Everything went smoothly on my desk top PC with Windows XP and I've been using that system for a while now. I wanted to put everything on my Lap top for band practice.

Fex · 02-01-2012, 08:50 AM

Try removing the dlls for the problem plugins from your VST folder, let Reaper scan the others, and when it has successfully completed a scan, add the others, one at a time, rescanning each time.