MOTUnation.com

I'm fairly sure most of the users of this excellent forum are DP and Mac based. I'm having mild issues using MachFive 2.01 in PC Pro Tools LE (the standalone's not too bad though). Is there anyone in the same boat for me to compare notes with? I'd be interested in the opinions of any PC users working with the plug-in in any host, too.

"Come out of the shadows my brethren! Mwah-ha-hah, where's Bill Gates' PayPal details?" ... and so on.

Be warned: we're in the definte minority here, things might get nasty

Anyway, we could make this a Windows bug thread for other Windows users to check first.

Here's one I'd like to know if it has been fixed in 2.01.

Start the stand alone and load up any preset
Click on a sample and then expand the sample editor to full screen
Close the full screen.
For me, part of the full screen image will overlay the main M5 GUI (i.e. the main GUI does not refresh correctly).

Simple minimizing and maximising M5 will clear the problem.
(Also happens with the plugin dll)

Just had a bit of tech support which points out that I'm using a Sempron processor rather than the Pentium4 on the spec. M5v1 demands a Pentium III and I haven't got one of those either, yet M5v1 works fine.

Also M5v2 actually works as a standalone - it's only when hosted in Pro Tools that I have issues. The program exits suddenly while M5v2's polyphony meter reads 2000-plus.

I don't see a high processor load when running the plug-in (though maybe there are very short spikes?) and I'm not using virtual memory (so I haven't run out of RAM).

Anyone know anything about Sempron vs Pentium architecture? I'm fairly sure it's not quite the old DX/SX issue... or is it?!

Hi. I'm new to this so I'm going to post this on several threads that have problems similar to mine. I noticed that some of these threads just stopped, so I wonder if people just gave up.

I am running Protools 7.4cs2 and MachFive 2. I have had the same problems with all Protools 7 versions I have used. I bought MachFive in August and basically put it aside because it bombed and I didn't have time to deal with it. Over the last week I have put countless hours trying to make it work. If I run stand alone it seems to work finds - I add filters as I like.

In Protools, sounds cut in and out, clicks, pops, bombs. If I start anywhere other than measure 1 it goes silent and I have to reinstantiate. I spent the $99 and put the Fxpansion "envelope" around it. There is a definite improvement - it goes from useless to better-than useless. I can actually start in other measures - the sound cuts out less frequently, and it tends not to completely bomb. The filters- forget it - I found a couple of simple ones that work but that's it.

I am running on a 2.4GHz Pentium 4 with 4GB memory - I don't expect the world but I expect something. I have tried every Windows optimization imagineable. I am plain sick of it and yet plan to find some way to make it work or burn the software in a bonfire.

By the way, I have no trouble with running multiple plugins from Waves, Digidesign, whatever. Any help, comments, would be appreciated.

Thanks, Craig

bizzbag wrote:Hi. I'm new to this so I'm going to post this on several threads that have problems similar to mine. I noticed that some of these threads just stopped, so I wonder if people just gave up.

I am running Protools 7.4cs2 and MachFive 2. I have had the same problems with all Protools 7 versions I have used. I bought MachFive in August and basically put it aside because it bombed and I didn't have time to deal with it. Over the last week I have put countless hours trying to make it work. If I run stand alone it seems to work finds - I add filters as I like.

In Protools, sounds cut in and out, clicks, pops, bombs. If I start anywhere other than measure 1 it goes silent and I have to reinstantiate. I spent the $99 and put the Fxpansion "envelope" around it. There is a definite improvement - it goes from useless to better-than useless. I can actually start in other measures - the sound cuts out less frequently, and it tends not to completely bomb. The filters- forget it - I found a couple of simple ones that work but that's it.

I am running on a 2.4GHz Pentium 4 with 4GB memory - I don't expect the world but I expect something. I have tried every Windows optimization imagineable. I am plain sick of it and yet plan to find some way to make it work or burn the software in a bonfire.

By the way, I have no trouble with running multiple plugins from Waves, Digidesign, whatever. Any help, comments, would be appreciated.

Thanks, Craig

TDM or LE ?
What version of windows ?
What motherboard are you using ?
How are your drives hooked up?
Do you have a separate drive for the samples ?
What sounds are you trying to load ?
What soundcard ?
Have you tried to run M5v2 standalone (assuming you can on the windows version) ?

/B

Thanks for the quick response.
Protools LE - Digi002
XP Home
Dell 02Y832 Mama
Use 1 7200 RPM internal for programs
1 7200 internal for recording
1 firewire 7200 external for samples
Creative SB Live soundcard

Seems fine in standalone

As an example, in Protools with MachFive, just trying to run the MachFive tutorial using the tutorial sounds and adding the ping-pong delay to the drums fails - quickly and always.

Thanks,
Craig

K. I don't have Protools, but I'm curious why you mention SB Live, as that should definitely NOT be in your audio chain.

Secondly, I'd try downloading a demo of another host and see if you still have the same problem. Try SONAR or Ableton's Live (both great hosts). If they fail as well, then you'll know that Protools is not the problem.

Thirdly, try streaming the samples in Mach V

Hope that helps

Hi, thanks
1) mentioned Sb because I wasn't thinking clearly at the time and the phrase "sound card" was mentioned - I actually have it disabled.
2) use ez drummer - no problem
3) the sound used in the tutorial is so small it works with or without without streaming and it bombs either way.

If I turn off errors in the RTAS engine in ProTools I do better - but, why should I have to turn that off with a light load?

My intuition says ProTools and MachFive are just fighting each other for CPU time and the fighting eats up more resources than the actual task.

Craig

At least you know it's not a M5 problem......

( if it's OK in Another one )

Your system should easily be able to cope with PT and Mach5v2.

I'm using an Athlon 1.6GHz processor with 1.25Gb RAM, XPSP2 and PT7.1. RTAS M5v2 is unusable, but the wrapped VST is solid. Plenty of polyphony and processing available. Well, maybe not as much as an 8-core...

I'm not sure whether this applies, but it's worth pointing out that it's best to avoid putting effects on with the effect slot near the filter section - this uses one effect instance per voice as opposed to the right-side effect section which uses up less CPU power as it makes one instance per preset.

I appreciate the filter tip. I've made some progress with ProTools 'buffer too big', 'buffer too small', 'held off interrupts' etc. I haden't seen these issues in years until I got MachFive. I think graphics has a lot to do with these problems, but disentangling the specifics is difficult - there seems to be some wacky balance with what level of hardware acceleration you use. ProTools recommends turning it off, but that's a bomb for me. The other issue is that every time I think I've made progress, it changes again. There's a few folks on the ProTools DUC that allude to changeability regarding the ProTools buffer stuff and CPU usage - I think they're right - it sometimes borders on the random.

Thanks,
Craig

bizzbag wrote:I appreciate the filter tip.

... nah I'm a non-smoker

It's interesting you mention the graphics. I had big problems until finding the latest drivers which improved the OpenGL 2.0 compatibility (even though my card was listed as 2.0 compatible, it wasn't that compatible until the upgrade).

ouch - thanks for the driver tip, although I'm not a golfer.

I just downloaded the latest drivers - maybe it will be even better.

Thanks,
Craig

[lame-arsed pun]... hope it's not a rubbish tip... [/lame-arsed pun]

I'm jumping in just to show my sympathy. I can't really help solving your problems as I haven't figured what to do with my own.

I run M5v2.1 inside Cubase 4.
Computer: Dell Dimension 9150, cpu Intel D930, mobo Intel 945P.

This will run smoothely for a while, untill it suddenly poofs and I'm left with my desktop. I left M5 unused since last fall because of the problems, but now wish to pick it up and give it a second chance. I intend to do some testing to find what is triggering my problems.

Whirly