MAGIX plug-ins: VST scanning error

[Mike@Ossarium]

Hello,
i have bought several plug-ins from MAGIX (essential FX; VANDAL and a few others).
All plug-ins work very well within the VSTHost V1.54 Application.

When i try to add the plugins to my reaper search path i got the following error for every plug-in:

"VST scanning error + note: Plug-in 'xxxxx.dll' executed invalid operation during scanning Note:if Reaper crashes as a result of this, simply run it again and it will continue on the next plug-in."

I am running Windows 10 32bit. So everything else is also 32bit :-)

I hope somebody can help me.

Michael

[Mike@Ossarium]

Hello again,

i have made some more tests.
I've tested the plug-ins on a friends computer (he also uses Reaper :-) )
On his machine everything works well.

The difference: 64bit OS and Reaper 64bit!

One the same machine the 32bit version of Reaper is installed. When we use that version the error occur again.

So it's seems that is a Reaper 32bit problem.
I hope that issure can be fixed till the next release.

Best regards,
Michael

[ivansc]

What made you decide to stay on 32bit windows when your system upgraded?

Might be worthwhile considering taking the plunge and going all 64bit with 32bit plugs bridged where you need to.

IIR you had the choice of 32 or 64 when Win10 invaded!

[EvilDragon]

It might also be an issue with Magix 32-bit plugins, too...

Either way, you should've gone 64-bit, really

[Mike@Ossarium]

Hi,

it's not possible to go for 64bit OS cause the CPU is 32bit.
I don't want to buy a new computer because of that issue.

I have tested an other DAW (Podium Free) and the Magix 32 bit plug-ins work there.

Mike

[EvilDragon]

What kind of a CPU is that, damn... Even ARM is 64-bit these days, AFAIK...

[Mike@Ossarium]

Its an AMD Athlon II X3 450 Processor.

I know that its not the newest one...

[ivansc]

According to everything I found online, that cpu IS 64bit enabled. Also you can try unlocking the 4th core which would up the performance quit a bit.
Worth a try.

[EvilDragon]

Yep, that IS a 64-bit CPU, through and through. Basically majority of consumer-grade AMD and Intel CPUs since 2003-2004 are 64-bit, ever since AMD's Opteron... And your CPU was released in Sep 2010, sooooo... time to format C: and put W10 x64 on!

[Mike@Ossarium]

Thanks a lot for your suggestion - i will check that.

But i cant do that until i have finished my actual project.... an therefore i want to use the plugins... :-(

But should'nt Reaper 32bit work with the plugins? I think this is a bug cause they will work in other DAW or VST host applications.

I prefer a fix of Reaper instead of seting up a new system.

[Mike@Ossarium]

My actual Audio interface also isn't capable to work under 64 bit.
If i upgrade my Windows i also need to buy a new Interface :-(

[VinodXAgent]

Please check the paths to your VST folder in Reaper preferences. Maybe you installed both flavors (64and32bit). If you have more than one VST folder make sure the folder with the 32 Bit vsts is last in your paths. BTW your interface will work with OS64.

[Mike@Ossarium]

Originally Posted by VinodXAgent

Please check the paths to your VST folder in Reaper preferences. Maybe you installed both flavors (64and32bit). If you have more than one VST folder make sure the folder with the 32 Bit vsts is last in your paths. BTW your interface will work with OS64.

The BCA2000 won't work under 64 bit.
I have only 32bit VSTs installed.

[VinodXAgent]

Originally Posted by Mike@Ossarium

The BCA2000 won't work under 64 bit.
I have only 32bit VSTs installed.

Ok, I just installed Reaper 32 Bit as a portable Install and Magix Vandal 32 Bit. Everything running fine. VariverbII running fine ,too.

[Mike@Ossarium]

Originally Posted by VinodXAgent

Ok, I just installed Reaper 32 Bit as a portable Install and Magix Vandal 32 Bit. Everything running fine.

oh - what's the difference to my installation? Any ideas?

[VinodXAgent]

Originally Posted by Mike@Ossarium

oh - what's the difference to my installation? Any ideas?

Did you manually delete the 64Bit VSt, cause the Magix-installer is installing both flavors?
Mal zwischen uns beiden Hübschen: Hast du über 500 € für diese Plugins ausgegeben?

[EvilDragon]

Originally Posted by Mike@Ossarium

The BCA2000 won't work under 64 bit.
I have only 32bit VSTs installed.

http://www.driverguide.com/driver/de...iverid=1689351

It will work under 64-bit. And it's not a problem simply installing 64-bit versions of plugins that you already have (if they do have 64-bit versions)...

[Mike@Ossarium]

Originally Posted by EvilDragon

http://www.driverguide.com/driver/de...iverid=1689351

It will work under 64-bit. And it's not a problem simply installing 64-bit versions of plugins that you already have (if they do have 64-bit versions)...

I am very impressed. I've searched also for the 64bit version of the BCA driver but didn't found some.
I will try it and let you know.

[Mike@Ossarium]

Originally Posted by VinodXAgent

Did you manually delete the 64Bit VSt, cause the Magix-installer is installing both flavors?
Mal zwischen uns beiden Hübschen: Hast du über 500 € für diese Plugins ausgegeben?

There are only the 32bit version of the plugins.

Ich habe natürlich nicht so viel bezahlt :-) War ein recht günstiges Bundle :-))

[ivansc]

Originally Posted by Mike@Ossarium

oh - what's the difference to my installation? Any ideas?

Actually, why don`t you teach yourself something and have a look at the two installs yourself?
Having someone else do all the work will fix the problem, but you will surely benefit more from learning it yourself.
None of this is rocket science and think opf the feeling of accomplishment you will have from sorting it out yourself now we have pointed you in the right direction.

P.S. I sold my BCF2000 in 2011 and it was 64bit capable even back then.

Good luck and have fun!

[Mike@Ossarium]

Originally Posted by ivansc

Actually, why don`t you teach yourself something and have a look at the two installs yourself?
Having someone else do all the work will fix the problem, but you will surely benefit more from learning it yourself.
None of this is rocket science and think opf the feeling of accomplishment you will have from sorting it out yourself now we have pointed you in the right direction.

P.S. I sold my BCF2000 in 2011 and it was 64bit capable even back then.

Good luck and have fun!

Hi -
the BCF2000 is no Audio interface - the BCA200 is one!

I don't understand at what installations i shall have a look. I only have one 32bit installtion which don't work...

[Mike@Ossarium]

Originally Posted by ivansc

... now we have pointed you in the right direction.

Installing a 64bit OS is only a workaround. It don't solve the 32bit problem itself!

The question is why is VinodXAgent 32bit installation working and not my?

[ivansc]

Quoting you: "the BCF2000 is no Audio interface - the BCA200 is one!"

In your sig, you are showing that you have a BCA2000, which also isn`t an audio interface, it is another controller like the bcf2000.
And it has nothing to do with audio. That is your FCA1616 unit, which IS an audio interface.

Scratching my head a little here.

[Mike@Ossarium]

Originally Posted by ivansc

You are showing that you have a BCA2000 which isnt an audio interface, it is another controller like the bcf2000. Scratching my head a little here.
And it has nothing to do with audio. That is your FCA1616 unit, which IS an audio interface.

You are not right. Take a look here:
http://www.musiciansfriend.com/pro-a...-control-audio
http://www.zzounds.com/item--BEHBCA2000

Let me help you scratch your head :-)

[Mike@Ossarium]

Originally Posted by Mike@Ossarium

I am very impressed. I've searched also for the 64bit version of the BCA driver but didn't found some.
I will try it and let you know.

Now i have tested the driver on two computers, but it don't work on both machines.
That matches what i have seeon during my search for an 64bit driver for the BCA2000.

[ivansc]

Ah - Silly me! I was thinking of the bcR2000! Wasnt aware of the bcA2000.
Sorry for the red herring.