Some questions about Machfive 3

AudioSoundzz · Post by **AudioSoundzz** » Sun Sep 11, 2011 4:11 pm

Congratulation first are in order to Motu for this serious upgrade! I have been loyal to Motu from way back when it was only a MIDI program.

I have 3 questions:

1. Can this new version be bounced to disk? Version 2 cannot do this which has been a problem for me.

2. Will this new version import version 2 setups perfectly?

3. Are any of version 2 operations or power lost?

FutureLegends · Post by **FutureLegends** » Mon Sep 12, 2011 5:52 am

I don't think anyone here has recieved their copy of M5v3 yet to answer your questions.

AudioSoundzz · Post by **AudioSoundzz** » Mon Sep 12, 2011 7:30 am

Then maybe Motu could answer the questions?

MIDI Life Crisis · Post by **MIDI Life Crisis** » Mon Sep 12, 2011 7:57 am

This is not an official MOTU site so you'll have to contact them.

FWIW:

• My M5-1 patches work fine in M5-2 so I don't anticipate a problem with them working in ver 3 - but you never know.

• Search the board for answers on how you can bounce VIs. There is a way and it has to do with whether pre-rendering is on or off and if you are using the MAS or AU version of the VI.

• I doubt MOTU will reduce the capabilities - but again, you never know.

You're welcome!

gjensse · Post by **gjensse** » Tue Sep 13, 2011 2:07 pm

From MOTU: "MachFive 3 performances are not directly compatible with MachFive 2. MachFive 3 can access MachFive 2 patches, however, it does not directly convert them into the new plug-in. Effectively, MachFive 3 is a new product. The installation does not wipe out MachFive 2, so if a user created projects with MachFive 2, they will not be overwritten. Both MachFive 2 and MachFive 3 can co-exist on a single system until a user has fully converted over to MachFive 3. I hope this helps."

MIDI Life Crisis · Post by **MIDI Life Crisis** » Tue Sep 13, 2011 2:20 pm

I believe that was also the kind of thing they said about M5-1 when -2 was released, yet I was able to load my patches just fine. I do recall some workaround that I did but it escapes me at the moment. Perhaps it was a file renaming kind of thing. I'll try to figure it out when the app arrives but not until at least Sept 23...

Then again, this may be such a different bird, it may not be possible to port them over easily.

scooter · Post by **scooter** » Tue Sep 13, 2011 8:39 pm

MachFive 3 performances are not directly compatible with MachFive 2. MachFive 3 can access MachFive 2 patches, however, it does not directly convert them into the new plug-in. Effectively, MachFive 3 is a new product.

Well that's just terrific news!
Maybe my good news for tomorrow will be that I need a root canal.

There goes all my days of work, creating my own patches for M5 2.
If it's a whole new and different product, then do they have to name it MachFive??
I think they're afraid of using the "d" word.

Discontinued

scooter

MIDI Life Crisis · Post by **MIDI Life Crisis** » Tue Sep 13, 2011 8:47 pm

There is often a way around such things. Let's just wait and see what that might be.

hugy · Post by **hugy** » Wed Sep 14, 2011 1:24 am

scooter wrote:
MachFive 3 performances are not directly compatible with MachFive 2. MachFive 3 can access MachFive 2 patches, however, it does not directly convert them into the new plug-in. Effectively, MachFive 3 is a new product.
Well that's just terrific news!
Maybe my good news for tomorrow will be that I need a root canal.

There goes all my days of work, creating my own patches for M5 2.
If it's a whole new and different product, then do they have to name it MachFive??

I think you have misunderstand what they means.
M5v3 won't replace M5v2 if you reload an old song after installing M5v3.

Both plugins will be listed in the available ones.

Still M5v3 will be able to read M5v2 presets and multi.

This is the same thing for Kontakt.

Henry Warner · Post by **Henry Warner** » Thu Sep 29, 2011 7:04 am

To Bounce MachFive [plugin] to Disk, one can Bus the MF output to an Audio Track which can then be Bounced to disk [or Recorded directly].

MF3 'setups' are Saved as Multis which can be used in either Plugins or stand-alone.

To move audio files to Digital Performer [DP] from a stand-alone MachFive3, one can use SoundFlower {SF]. But if one Selects SoundFlower in the MOTU Audio Setup there will be no Output from DP other than SF. To access analog [or digital] Outputs for DP one must Open Apple's Audio MIDI Setup.app {Utilities folder] and create an Aggregate Device consisting of both SF and the usual Output … for Example, SF and Ultralite. Then both SF and Ultralite show up in DP's Bundles. An Audio track can then be set up using a SF input and an Ultralite [or whatever] Output.

YouTube · Post by **James Steele** » Thu Sep 29, 2011 10:04 am

gjensse wrote:From MOTU: "MachFive 3 performances are not directly compatible with MachFive 2. MachFive 3 can access MachFive 2 patches, however, it does not directly convert them into the new plug-in. Effectively, MachFive 3 is a new product. The installation does not wipe out MachFive 2, so if a user created projects with MachFive 2, they will not be overwritten. Both MachFive 2 and MachFive 3 can co-exist on a single system until a user has fully converted over to MachFive 3. I hope this helps."

Not correct actually. MachFive 3 DOES load MachFive 2 performances just fine. Or it is supposed to, at least. Just use the 'Load Multi' command in MachFive 3's File menu.

MIDI Life Crisis · Post by **MIDI Life Crisis** » Thu Sep 29, 2011 11:19 am

I just loaded them in and they worked. So did MachFive -1. I must be doing something wrong...

Oh darn! Forgot to

There's my problem right there...

MOTUnation.com