Upgrades from 6.2 are, for the time being, free. All new purchases include access to this version. There is an upgrade price of $34.99 to upgrade any flavor of Metro from 6.x to 6.3.5.
Download it here:
http://www.sagantech.biz/downloads
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.2.
IMPORTANT: OS 9 support has been removed.
IMPORTANT: This is a pre-release, meaning it has some bug fixes (and possibly features) that were deemed important enough to be released before it could be rigorously tested.
We want our software to be bug free. If you find any bugs please report them here.
New to this version: 6.3.5.6
• New: Normalize Faders function in the special menu. This function mixes audio for all track for the current selection and based on the resultant peak sets the mixer faders so that the mix does not clip in most cases.
• New: View plug-ins by manufacturer or category. View all and view recently instantiated plug-ins. All this functionality in a simple menu and submenu interface directly from the graphic editor.
• New: Metro will interpret the enclosing folder name of any (Mach-O) VST plug-ins as the manufacturer name.
• New: When "manufacturer" is the selected plug-in sort field Metro will sort plug-ins by name if the manufacturer names are equal.
• New: Menu item for inserting a random chord progression.
• New: The Mouse Wheel can now be used for incrementing and decrementing numeric fields.
• New: Metro now receives MIDI data from VST plug-ins that send it.
• New: The jukebox now uses a triangle to indicate the currently playing song.
• New: Humanize and Extract Data have been added to the LX version.
Fixes in this version:
• On Intel Macs, strange errors or crashes could occur after opening a Metro document saved prior to version 6.2 that contains audio.
• Intel Mac could crash after cueing an empty audio track.
• Intel Mac could crash after clearing an audio track while playing.
• Turning the power off in the effects window did not work consistently.
• Software audio through was not working properly in some cases where there was no audio data on the track.
• Certain Virtual Instruments (VI) would become quiet if a Metro output was reassigned during playback.
• A problem with pitch-preserving fast forward on multi-output audio devices was corrected.
• If a core audio aggregate device was created and named 'built-in' a problem could result with subsequent recording.
• Using an arrow on a note of Bb in the key of Ab minor would stick at Bb, instead of going to Cb.
• Dragging a sample, when zoomed all the way in the graphic editor, now displays the sample value in the upper left.
• After saving a .ins file the currently selected bank name is no longer replaced with the name of the .ins file.
• Trim outputs was not preserving audio outputs that were the destinations for Virtual Instruments.
• In certain cases the availability status of menus were not being set properly.
• A new fatal error message was added if the user attempts to run a version of Metro that requires a G4 processor on a G3 or earlier processor.
• A possible crash could result if the jukebox was empty and remote control was active.
• The jukebox slider now indicates the time within the currently playing song as it is dragged.
• Typing the name of the song in a long list of jukebox entries now works more reliably.
• Copying track data and pasting it to a new section could result in a erroneously auto-muted aux buss virtual instrument.
• Mixing down to 24 bits on an Intel Mac could create pops and clicks in certain scenarios.
• Pasting note data or adding data to a VI track while cueing would not set the playback position for that track correctly.
• Port change dialog no longer defaults the destination to a non existent core-audio port.
• Better enabling and disabling of menus when the offline effects or progress dialogs are in front.
• A problem whereby making changes to section events could affect track effect automation data detrimentally.
• It was possible that a newly opened Metro document set to show effects automation using a AudioUnit plug-in would not initially show the correct information because the scale of the displayed parameter can not be determined until after the plug-in is loaded.
• Dragging files into the tracks window would occasionally leave ugly blue lines.
• Expand By Drum was not setting the correct resultant track type to MIDI.