Big problem in MachFive 2 on my system

Shooshie · Post by **Shooshie** » Wed Aug 15, 2007 3:22 pm

1nput0utput wrote:
Shooshie wrote:Version 2.0.1 has fixed my problem in Mach Five 2, but now the problem has spread to MSI, and it is still not fixed. What on earth has happened to these things?

Anyway, if you have the same problem, download the update for version 2.01. That's got me up and running again.

Thanks, MOTU!

Shooshie
You probably just need to uninstall/reinstall MSI. Mucking around in the application package probably didn't help much. Use the MSI installation disc to uninstall, then reinstall; then download and install the latest MSI update from motu.com.

Nope, that doesn't do it. This is something I'm calling the "Standalone Flu," and the MSI app is acting exactly like the MachFive2 app did. It's going to require the same fix that M5.2 required, and MOTU is going to have to release the update for it.

I have uninstalled and re-installed MSI twice, and one of those times I started from the original disk and upgraded it, rather than just starting with the 1.1.3 updater. In other words, I've tried it both ways -- starting with the 1.1.3 updater, and starting with 1.0 and upgrading incrementally. Neither method worked.

The problem seems to come from a UNIX executable file called "PluginhooksSA" in the package contents.

I've left MOTU a technote about this, using my original MachFive2 technote as reference, since the symptoms are exactly the same. I sure hope we get all this resolved soon. Others are reporting that Ethno also fails to open in standalone mode. All of these are based on the same engine, same installation methods, and same Finder files. Whatever MOTU did for M5.2, now needs to be done for MSI and probably Ethno as well.

Shooshie

homebilly · Post by **homebilly** » Wed Aug 15, 2007 4:06 pm

did 2.01 kill the spectrasonics thing?

stephentayler · Post by **stephentayler** » Wed Aug 15, 2007 4:18 pm

homebilly wrote:did 2.01 kill the spectrasonics thing?

It seems to have killed it on my G5, I have not yet run the update on my MBP.

Stephen

Shooshie · Post by **Shooshie** » Wed Aug 15, 2007 7:03 pm

Remember, MOTU didn't kill Spectrasonics. Spectrasonics opted out. That was his bad decision, not MOTU's. Call him up, write him, tell him what a fool he is for doing that. That's just bad business. MOTU tried to help by making MachFive2 compatible with his samples. He apparently nixed it, since they WERE working! Don't blame it all on MOTU.

I'm thrilled to have MachFive2, and it makes me sad that anyone would actually want to withdraw their products from its reach. Sad for THEM, not me. I'll just use something else, and my dollars will go to those who cooperate.

Shooshie

RCory · Post by **RCory** » Wed Aug 15, 2007 9:35 pm

yep - 2.01 killed the spectrasonics thing...

Even if you go back and replace the component plug-in to 2.0, it won't let you load the .dat files... so...

It must change something in a preference file/extension too.

RCory · Post by **RCory** » Wed Aug 15, 2007 9:37 pm

well - good thing I converted my fav patches before I updated...

abinning · Post by **abinning** » Thu Aug 16, 2007 1:21 am

Chipping in again, then I'll leave this post: v2.0.1 appears to be the medicine for my particular strain of Standalone Flu. MachFive now launches as a standalone app, although I can't comment on any other MOTU VI's 'cos I don't have them!!

As a returnewbie I'll probably post elsewhere on these boards. Hopefully all you nice folks can help me find my way.....

technomorph · Post by **technomorph** » Fri Aug 17, 2007 3:29 pm

This sounds like a pre-binding issue.

I found this crops up when you update your Mac OSX system.

Like going to 10.4.10
or QT 7.2

Many folks suggest downloading the 10.4.10 combined update and installing that rather than using the Software UPdate function....which does not complete the pre-binding (whatever that is).

The is a command line in Terminal you can run.

Or better yet is to just download the YASU application for free.
It will do some housecleaning on your Mac for you.
Make sure you click on the REPAIR PREBINDING as it's not defaulted.

Run Yasu and things should come back.

This happened to me recently on upgrading to QT 7.2
Then my ProTools wouldn't open.
Just do the bounce a few times then done.

Give that a shot.

Technomorph

Shooshie · Post by **Shooshie** » Fri Aug 17, 2007 5:26 pm

Prebinding is exactly the word I was looking for, but could not remember. And yes, that's what it was. Someone else suggested Onyx. I'm glad to know of another utility that will fix prebinding issues. We're making some good progress here.

Shooshie