PlanetZ forums - scopeusers.com

I plan on re-installing Mod IV, but thought I'd share my experience lately anyway.

Recently my Mod IV seems corrupted. It first started acting strange with presets, or the top menu bar wouldn't be seen. Now, it loads (even in an empty project, with an empty Mod IV) and my native CPU usage uses a full core, and I also get DSP SAT connection overloads.

I don't use the "auto-save" feature, and haven't done anything too crazy in the patches, just some simple effects processing really (nothing that uses samples or any inserts that would need native RAM, or even access to the native hardware). So I'm confused about how it started, and why the symptoms I have exist.

Hello

Couldn't it be some antivirus scanning mod files when used by Scope?
Can you check after excluding the scope directories from scanning?

I never use Anti-Virus on my music machines, but it's a good thought.

The only thing I can think of is that the .dev was overwritten by accident, but that still doesn't explain the odd behavior.

Ive had ModIV crash issues when using the tape delays - are you using those ?

I'm not using the tape delay, but I am aware of those issues, and have added the patch that is available. I still need to find time to re-install MOD IV and get things stable again, just been busy here.

JK, did you solve this problem? i've reinstalled Modular IV now 3 times and I'm still getting errors like this..

I can't test it yet, but seeing somebody else does have the same pb and if you did not report to S|C, maybe it's now time.

I got a new laptop, and since then I reinstalled and haven't had any issues. All seems well. I will start to mess with the Tape delay again soon, and that's the only thing I haven't explored.

I think what had happened is that I had "saved" a Mod IV patch as a .dev, but had overwritten the normal Modular4.dev. I don't know what that means under the skin, if there's implications to the registry, the cset.ini file, or whatever (ie, just replacing the .dev and .pre (preset) file might not be enough). But a clean install was the trick for me.

Interesting about Modular4.dev - added to troubleshooting guide thanks.