Miroslav standalone good --no go in Reaper!

[ObiK]

Originally Posted by chip mcdonald

I'm bumping this, since apparently I can't get past IKmultimedia's "support page" form.

It works standalone, and in Reaper X64; the path is indicated in x32 but I get an "executed invalid operation during scanning". I cannot make sense of this but would like to.

Hey just saw this. Whats wrong with our support page?

[chip mcdonald]

Originally Posted by ObiK

Hey just saw this. Whats wrong with our support page?

Instead of bothering your support, I tried posting in your forums. I was told to go to forward my question to "support" by a Mr. Brian Bane.

Upon finding your "support" page, I'm presented with a long form to fill out, without anywhere to actually write what my problem is.

After submitting this twice and not getting any response, I posted that I did not get a response. I suggested my question could be forwarded to tech support, or they could simply read my question in the forum. I was told to resubmit the form again.

I see today tech support was sent to follow up with any email from a Jason, which I did get and inquires about my system specs (basically what I already filled out on the form).

Sigh.

[ObiK]

PM me your Support Ticket number and I'll see what I can do to make this better for you.

[chip mcdonald]

I was contacted by a Jason Williams directly, without a support number, because you'll note *the support form didn't do anything*.

I'm thinking it's a problem with Reaper at this point though, actually. It would seem suddenly a lot of users here are having difficulties with one specific VST .dll not being recognized by Reaper.

[DarkStar]

As far as I remember, there are two pages to the Support Forum - the first collects all your details (a bit painful, each time) and the second is where the problem is described.

As for why a 32-bit VSTi runs OK in Reaper x64 but is not even found in Reaper 32-bit, I'm stumped.

[ObiK]

Originally Posted by DarkStar

As far as I remember, there are two pages to the Support Forum - the first collects all your details (a bit painful, each time) and the second is where the problem is described.

As for why a 32-bit VSTi runs OK in Reaper x64 but is not even found in Reaper 32-bit, I'm stumped.

Ya that is why I think Jason contacted him to finish out the ticket.

[karbomusic]

Originally Posted by chip mcdonald

I was contacted by a Jason Williams directly, without a support number, because you'll note *the support form didn't do anything*.

I'm thinking it's a problem with Reaper at this point though, actually. It would seem suddenly a lot of users here are having difficulties with one specific VST .dll not being recognized by Reaper.

Didn't read the entire thread but just an FYI that I didn't seem to have any issues with standalone or vsti.

Karbo

[chip mcdonald]

I was contacted, sent a reply but I've heard nothing back.

Half the time Reaper x64 finds it ran as administrator, I'll just have to use it that way, I've already spent too much time mucking about with settings/non-music things.

[Sambo Rouge]

Bumpety bump

[gunny]

Originally Posted by Sambo Rouge

IK Multimedia emailed me to say "Use Miroslav Philharmonik (under the Compatibility tab in Properties) as an administrator.

The problem with this error message...

Registry error
Please ensure this product has been installed properly

...is caused by the registry entry [HKEY_LOCAL_MACHINE\SOFTWARE\VPA].
On 64-bit machines it is created as [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VPA], but this registry path is accessible only for the administrator. The other users use their "safe" copies of this path located in their profiles.

I think that a "cleaner" solution is to copy the registry branch
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VPA]
to
[HKEY_CURRENT_USER\SOFTWARE\Classes\VirtualStore\MA CHINE\SOFTWARE\Wow6432Node\VPA]

The easiest way is to export it to a file, edit the paths in notepad and then reimport it back.