Hi guys,
I installed Massive X from V.R. , I can see Massive X.dll in vst folder, but, Reaper x64 dont see it....
My system is Win7x64 Sp1

Any help is welcome.

 

Last edited: Jul 24, 2019

I just tried (thanks to our pirate and zippy).

Same setup, everything's fine. You didn't by chance wrote something in the search filter (happened to me once or twice)?

 

go to preferences CTRL + P
vst
and make sure the folder is in plugin paths location
exit reaper and enter reaper again

 

MASSIVE X requires an AVX-compatible CPU to run.

 

Works not so fine in reaper 5.981, win7 x64, after several minutes of testing it crashed with showing warning of video drivers or so. It was shown on the windows panel, lower right corner. Never used again.
i7-3770k, 16 GB RAM. I think this is why my old computer from 2012 vs newer software technologies. I think newer software are made for future use, win 10 and further, newer cpus etc

 

Check out the permission of massive file.

 

Thank you for your answers.

It is in the scanned location, as it's my default vst folder.

No I didn't wrote anything in search box at first. Then I wrote Massive x and I see only the old massive.
Which name have the plugin in your setup?

I know, but I should at list see the plugin listed anyway, or not?

Permissions are normal, not hidden, nor read only, and I'm admin so it shouldn't be the problem.

Just in case there could be a conflict, I took off the other version of massive from my vst folder, but still I cant see MassiveX.

I suppose that it may be due to my computer specs then? My CPU is Bloomfield i7 950

 

Last edited: Jul 24, 2019

VSTi: Massive X (Native Instruments GmbH)

 

So it cannot conflict with old version.

Well I guess I have to assume that this is a compatibility problem...

Never mind , there are so many good synth out there ...

Thank you all for your help.

 

@Olymoon I remember it showing in the plugin scan, then disappeaing in the program, same in studio one
my cpu came out in 2010 lol

for anyone who cares:
CPUs with AVX

• Sandy Bridge processors, Q1 2011[10]
• Sandy Bridge E processors, Q4 2011[11]
• Ivy Bridge processors, Q1 2012
• Ivy Bridge E processors, Q3 2013
• Haswell processors, Q2 2013
• Haswell E processors, Q3 2014
• Broadwell processors, Q4 2014
• Broadwell E processors, Q2 2016
• Skylake processors, Q3 2015
• Kaby Lake processors, Q3 2016(ULV mobile)/Q1 2017(desktop/mobile)
• Skylake-X processors, Q2 2017
• Coffee Lake processors, Q4 2017
• Cannon Lake processors, Q2 2018
• Whiskey Lake processors, Q3 2018
• Cascade Lake processors, Q4 2018
• Ice Lake processors, expected in 2019

 

Yes I saw this list and my i7 is from 2010 too ...
But we'll, there are a lot of other wave table synth nowaday, so, that's not such a problem.
Given that Massive X is the only program I may use that needs this technology to work, I certainly won't change my computer only for that reason.

 

sorry for resurrecting this old thread but I have this issue now...
massive x 1.4.4 bob dule works fine; updating to 1.5.0 VR version (sister site) fails to scan in reaper
tried these options:
Re-scan VST paths for new/modified plug-ins
Clear cache and re-scan VST paths for all plug-ins
tried in a sandbox and works fine... please, anybody have any ideas?

windows 10 pro (up-to-date) 22H2(19045.5608),
2.90 gig Intel 7-7500u Lenovo x64,
16GB ram

 

Presuming your CPU supports AVX?
Have you tried installing the 1.5.0 bobdule version?

 

I tried 1.5.0 in a sandbox (same computer) and it worked fine.
Since the 1.4.4 bob dule version I have not had success installing any other bob dule massive x version.
also, I swapped the 1.5.0 dll & vst3 with the 1.4.4 version and it worked as expected, so it seems to be something about the 1.5 0 dll and vst3 files... but remember the 1.5.0 works in sandbox

 

Latest versions (VR and R2R) do not show up here either (Ableton, Reaper, Vsthost). It must be the AVX thing (was it introduced in recent updates? Just curious).

 

Yes, but 1.5.0 does work in a sandbox on the same computer so it can't be the AVX thing, right?