MOTUnation.com

Yukulele wrote:Something odd with Pro Tools 7.3.1cs4 though, MachFive 2 can't be instantiated on an Instrument track, but only with the old fashioned Aux track...
Not a big deal, but it's not very serious for a brand new virtual instrument...

Sure you're using a stereo (or surround) instrument track? If it's a mono instrument track, you won't see M52 because there is no mono version.

carrythebanner wrote:

Yukulele wrote:Something odd with Pro Tools 7.3.1cs4 though, MachFive 2 can't be instantiated on an Instrument track, but only with the old fashioned Aux track...
Not a big deal, but it's not very serious for a brand new virtual instrument...

Sure you're using a stereo (or surround) instrument track? If it's a mono instrument track, you won't see M52 because there is no mono version.

You're right, it was an a mono instrument track...
I ...

Bye.

Friend of mne has the same sluggish issue with HD 7.3.1 on g5 duel 2gig. He went back to mahc 5 v1 very dissapointed

Very slow and unusable for RTAS. So now what? How long before a fix?

Has anyone having trouble with RTAS M5v2 got FXpansion's VST-RTAS adapter?

Using M5v2 as a wrapped VST makes the plug-in stable and sample accurate. The RTAS version is an absolute nightmare.

I'd be really interested to know if I'm alone in this situation, and (as I'm on PC and PTLE 7.1) if it's similar over on the Mac.

[And no, I don't work for FXpansion...]

3over3 I'll let you know when I get my copy later on this week. I'm on a Mac Pro 1.8ghz and I have the fxpansion wrapper... It was tough for me to decide between MachFive2 and Kontakt 3 but the LoopLab feature seemed like it'd be perfect for what I do...I'll be pissed if it's not usable in Pro Tools...

I'm running PT 7.3.1 on my mac G5 and the new MachV plugin doesn't even show up..... I do see my old version ,1.2.3.....

phazor wrote:Very slow and unusable for RTAS. So now what? How long before a fix?

Not trying to be an a**, but... when it's done and tested ?

/B

3over3 wrote:Has anyone having trouble with RTAS M5v2 got FXpansion's VST-RTAS adapter?

Using M5v2 as a wrapped VST makes the plug-in stable and sample accurate. The RTAS version is an absolute nightmare.

I'd be really interested to know if I'm alone in this situation, and (as I'm on PC and PTLE 7.1) if it's similar over on the Mac.

[And no, I don't work for FXpansion...]

Hey 3over3, I've got FXpansion VST-RTAS adaptor, and you're right - MachFive 2 is much better as a VST plug, (at least in Pro Tools). One problem I'm having though (and I'm wondering if you or anybody else experienced this) is that whenever the MachFive window is open, my Pro Tools transport key commands don't work. So I have to close the M5 window in order to start and stop PT, or use the mouse... What a P.I.T.A.!

charlzj wrote:Hey 3over3, I've got FXpansion VST-RTAS adaptor, and you're right - MachFive 2 is much better as a VST plug, (at least in Pro Tools). One problem I'm having though (and I'm wondering if you or anybody else experienced this) is that whenever the MachFive window is open, my Pro Tools transport key commands don't work. So I have to close the M5 window in order to start and stop PT, or use the mouse... What a P.I.T.A.!

Great news - can I ask you to raise a MOTU TechLink simply asking why it works as a VSTW and not as RTAS? I've had nonsense responses like "it's normal, acceptable behaviour" to be 20+ ticks out (early) from where you've told it to play something. I get sample accuracy in the VSTW. And no stoopid crashing.

And you're on Mac, so it's not confined to PC - it's confined to RTAS!

As for the shift-of-focus problem (I think that's what they'd call it) I gather that's deliberate, due to all the new M5v2 key commands. Although you don't need to close the plug-in window to fix it - just click on free space in Pro Tools' mix or edit window and your key commands will be re-routed to Pro Tools.

I will submit a techlink today - But believe it or not, even if I click on a ProTools window, the transport key commands still don't work as long as the M5 window is open. Very boring, must use the mouse or keep closing the M5 window.

And although M5 does run more smoothly in VST, newly-created or edited loops and start/end times of samples still won't save. Bug city!

3over3, I should clarify - the VST version feels snappier overall in terms of launching the plug in and its window opening, saving, that sort of thing. Haven't used the VST version long enough to determine if it is significantly less crash-prone than the RTAS.
However, as far as MIDI timing per se, I'm not having any issues as you described. I loaded a sample of a click and did a test, recording the click and then zooming in and comparing performance on the grid. Both the RTAS and VST versions seemed fine as far as that goes on my system.

I have had other RTAS plugs like Ivory and BFD play early as you described. You probably already checked this, but just in case.. make sure your Pro Tools playback engine has delay compensation turned off.

charlzj wrote:3over3, I should clarify - the VST version feels snappier overall in terms of launching the plug in and its window opening, saving, that sort of thing. Haven't used the VST version long enough to determine if it is significantly less crash-prone than the RTAS.
However, as far as MIDI timing per se, I'm not having any issues as you described. I loaded a sample of a click and did a test, recording the click and then zooming in and comparing performance on the grid. Both the RTAS and VST versions seemed fine as far as that goes on my system.

I have had other RTAS plugs like Ivory and BFD play early as you described. You probably already checked this, but just in case.. make sure your Pro Tools playback engine has delay compensation turned off.

Oooh, so close! Ah well, maybe I am alone!

I'm in 7.1 LE - no compensation engine for me (although there is some form of compensation, otherwise there couldn't be early - or accurate - timing occurring).

So you get sample-accurate timing in both flavours? Could you fix Ivory or BFD?

I have an LE system as well- I will do the same test on that system...

With the HD system, there's only about 1/4 of a millisecond delay between a gridded quarter note click and Machfive2 playing quantized MIDI quarter notes of the same click sample. So it's not what you'd call sample accurate. But it's very short, and it's consistent enough that you could probably dial in a MIDI offset if it was ever an issue.

My LE rig is in transit, I will let you know how it performs on the same test.

Usually I was able to get around the early MIDI problem with BFD and Ivory by turning off delay compensation. If that didn't fix it, I would use MIDI track offsets. I haven't run into that since I updated my PT to 7.3.1 though...