Metro Now Available

General announcements appear here.

Metro Now Available

Postby Jerm » Tue Jan 23, 2007 1:01 pm

6.x to 6.2 upgrades are free. All new purchases include access to the latest version. There is an upgrade price of $34.99 to upgrade any flavor of Metro 6.x to

Download the latest version here:

IMPORTANT: The official system requirements have changed as of 6.1.

IMPORTANT: Metro Documents written with this version will NOT be readable in any version prior to Metro/Metro SE version 6.3.6.

IMPORTANT: OS 9 support has been removed.

IMPORTANT: This is a release candidate, meaning it has been fairly well tested and will most like be the final 6.3 version.

We want our software to be bug free. If you find any bugs please report them here.

New in this version:
• Holding control while closing an effects edit window will now close the editor completely. This works around a problem with Arturia's Moog Modular whereby the editor uses up much of the processor time even when the edit window was hidden.
• Recording MIDI from a plug-in is now disabled unless the user explicitly selects 'Record MIDI' from the effects window's contextual menu popup accessed by control-clicking on the name of the plug-in. Previously, since recording was always enabled, this could cause seemingly spurious MIDI events to be sent in MIDI through.
• A new option in the plug-ins window contextual menu, adds support for AudioUnit plug-ins which do not support sample accurate automation (namely PSP's).

Fixed in this version:
• Better VST 2.4 compatibility.
• Metro was not reading/converting old Metro 4 data files correctly on Intel Macintoshes.
• In very rare cases it was possible that an operation on section events (time/key sigs or master volume) could cause automation on other tracks to become messed up.
• Importing a MIDI file was leaving the file open in some cases.
• Inserting Master volume events via the continuous data dialog during playback would likely fail.
• Audio scrubbing was not working correctly.
• Setting the selection filter to the first n of m notes, could cause a crash.
• In rare cases, when working with an aggregate audio device, it was possible that the device would stop responding requiring an audio reset to get the device back.
• Transpose was changing the selected notes in some rare cases.
• Entering text via the keyboard was causing crashes in older carbon based VST plug-ins (PPC only).
• Software audio through was broken on Intel Macs when the recording bit depth was set to 32.
• Software audio through would not restart after clearing an entire record-enabled track.
• If audio glitches occurred, the play bar would be out of sync with the audio.
• If a key signature event occurred at the same exact time as a Tempo change event, the tempo could be messed up for virtual instruments.
• Selecting a new folder or adding files to the existing Jukebox while the Jukebox was playing could have failed.
• Selecting a new track output would not mark the document as changed.
Posts: 2665
Joined: Tue Feb 11, 2003 12:50 pm
Location: Massachusetts

Return to Announcements

Who is online

Users browsing this forum: No registered users and 1 guest