MIRx Not Running Properly After Running Normally Before [SOLVED]

[DaddyO]

Never had this happen before.

Cubase 8.0.3 (single computer, see specs in signature if helpful)

VE Pro 5 current version

VI Pro 2 current version

MIRx current version

VI Pro instances in VE Pro show MIRx continually loading in Reverb tab even when progress bar on top shows all samples loaded. Any attempt to remedy it crashes all four listed programs.

Any ideas? If I need to do a complete reinstall of course I will, but I'm hoping someone has run into this before and there is an easier solution.

[Paul]

Hello DaddyO, 

What is your attempt to remedy it? Do you want to send us some crash-dumps (location is shown after the crash occured), directly to support@vsl.co.at. Maybe you can also include a VE PRO viframe file for us to check. 

Best, 
Paul

[DaddyO]

First attempt this morning unable to reproduce the kind of "whiteout screen" crash that affected all including Cubase yesterday, I still have a non-responsive (i.e., frozen) instance of VE Pro. See attached screen print.

On this occasion while the MIRx load progress circle was in a constant loop of reloading I tried clicking "None" for the Reverb selection. As you can see, now both "None" and "MIRx" remain highlighted in this frozen state.

I am going to try a few more things today, and if nobody recognizes this problem and I can't resolve it myself I'll submit everything I can to Support.

Thanks, Paul.

 

edited to add: It turns out that once I attempt to close the non-responding windows of VE Pro and Cubase, then I get the "whiteout" screen and am prompted by Windows to force closure of the windows. I never get a crash dump notification.

[DaddyO]

I have an idea what might be behind this, though I"m not sure.

Recently I for the first time created a "Startup" Preset as outlined in the VI Pro manual page 14.  That Startup included MIRx as the selected Reverb, and I'm not sure but the problem I'm having may have started right afterwards. The Startup Preset is shown in my screen print.

The problem is now that any time I initiate a new VI Pro instance I am faced with this endless MIRx loading loop, and VI Pro doesn't respond. My cursor has become the dreaded "hourglass." Thus there is no way for me to delete the Startup Preset and go back to a "blank" initial state.

If there is a user-available folder where this custom Startup Preset can be deleted I believe it might solve my problem. Any ideas where to find it?

[kenneth.newby]

I reported something to this effect a while back.  As far as I can tell it was a conflict between two MIRx venues trying to load alternately.  I re-edited the project, making sure all the venues were the same and all was well again.

Kenneth.

[DaddyO]

@kenneth.newby said:

I reported something to this effect a while back.  As far as I can tell it was a conflict between two MIRx venues trying to load alternately.  I re-edited the project, making sure all the venues were the same and all was well again.

Kenneth.

Thanks for the suggestion, Kenneth. Interesting.

I have "Synchronize" checked, which should be making all venue selections the same. The screen shot verifies this. But what you suggest is still possible that somehow VI Pro is making the attempt to do this in error.

Prior to freezing if I could capture the screen over time it would show the progress circle completing and then starting over.

At this point I have no way to fix it, since every newly initiated instance exhibits this behavior.

[Paul]

Hi DaddyO, 

Please start the Directory Manager, remove all folders and add them again. Make sure that the right MIRx Impulses are installed, and that there are no double impulses. 

To erase the STARTUP preset, find the CUSTOM DATA FOLDER (referenced in the Directory Manager) and erase the preset manually. 

Does that help?

Best,
Paul

[DaddyO]

Thanks, Paul. Just the info I needed.

edited to add:

Was able to find and delete Startup VI Preset, but I also found I had somehow failed to notice a Feb 2015 MIRx update (despite having checked last week that all my software was current!), so I also downloaded and installed that. That could have been part of the problem, but I had been running fine until recently.

Anyway, in the immortal worlds of Inspector Clouseau from Pink Panther fame, problem SOLV-ed!