Pro Tools M-Powered 7.4.2cs4 Update for Mac OS X (Leopard)
Pro Tools M-Powered 7.4.2cs4 Read Me for Mac OS X July 29, 2009 For M-Audio Systems with Pro Tools M-Powered 7.4.2 for Mac OS X "Leopard" Only Universal installer for PowerPC and Intel-based Macs on Mac OS X 10.5.3 and 10.5.4 This update requires previous installation of Pro Tools M-Powered 7.4.2: Pro Tools 7.4.2 Information
Who Should Use This Update?
This update contains fixes in the following areas: Playback File Management Time Shift Plug-in Plus previous fixes in the following areas: Session/File Management Editing QuickTime Video Automation Reason Adapted DigiBase Fade files File Comments in WAV files MIDI ProFire 2626 I/O Setup Pro Tools M-Powered 7.4.2cs4 is provided as an interim "customer support (CS)" release to address the issues described. While our testing has not shown these changes to introduce other problems, this version has not been fully qualified by Digidesign.
What's Included in Pro Tools M-Powered 7.4.2cs4 for Mac OS X?
Fixed: A play command in Pro Tools may not always engage playback on the first attempt (Item #114517) After a play command, the Play and Stop buttons may flash, however, Pro Tools does not playback. Subsequent tries would allow playback. Fixed: Cannot open sessions due to PolyVector error (Item #114287) Certain sessions cannot be opened due to the following error: "Could not complete your request because out_of_range: Cmn_PolyVectorImpl::At" Fixed: Audible drift when using PAL to Film TCE conversion on long audio files (Item #113490) Using the Time Shift Varispeed preset (PAL to Film -4%) will result in a file that drifts over time and runs out of sync with picture.
Included from 7.4.2cs3: Fixed: Converting sample rate during Save Copy In or Import Session Data adversely affects volume automation (Item #111930) Saving a session copy with sample rate conversion to a rate different from the session's may result in erroneous automation ramps between breakpoints. This is mostly evident in scenarios where a static automation level had been changed over the duration of a single region.
Included from 7.4.2cs3: Fixed: Converting sample rate during Save Copy In or Import Session Data adversely affects volume automation (Item #111930) Saving a session copy with sample rate conversion to a rate different from the session's may result in erroneous automation ramps between breakpoints. This is mostly evident in scenarios where a static automation level had been changed over the duration of a single region. Fixed: Problems moving multiple selected regions (Item #99538) If you selected several adjacent regions, clicking on one of them to move all selected regions will only move the region you clicked on. Fixed: Incorrect multi-track audio import from QuickTime movies (Item #102279) Multi-track QuickTime movies import into Pro Tools 7.4 with each audio track containing a mix of all tracks, rather than individual tracks.
Included from 7.4.2cs2: Fixed: Volume Breakpoints at "- inf" Could Change to Full Volume When Manually Trimming Automation (Item #104551) This could occur when trying to trim breakpoints at minus infinity down a few dB Fixed: Pro Tools and Reason Crash When Loading "Machine" Patches on Reason Adapted Combinator (Item #106627) Only occurs in Reason Adapted, and does not occur when Reason Adapted is operated without Pro Tools

Included from 7.4.2cs1: Fixed: The following error is generated when selecting a 256 + comment in the Workspace: "The value contained too many characters; previous value substituted". (Item #100604) Fixed: Attempting to Drag and Drop Files Containing iXML metadata from the Workspace Browser Would Result in No Import, and Assertion Errors (Item #100723) The assertion errors would occur when attempting to subsequently save the session Previous workaround was to use File > Import > Audio instead of drag and drop from the Workspace Fixed: Despite Changing the Fade Shapes in the Fade Dialog, Fade-ins and Fade-outs Always Conformed to the Last Created Fade In and Out (Item #100913) Fixed: WAV Files Containing Non-English Characters Are Not Visible In Pro Tools 7.4.2, and Can Be Corrupted if Edited (Item #100502) Although the file comments are invisible in the DigiBase comments field, clicking in that field will delete all of the comments This only affects non-BWF WAV files This CS version restores the visibility of WAV file comments, as long as the field wasn't clicked in using earlier versions of Pro Tools 7.4.2 Fixed: Only the First 16 MIDI Inputs Are Available In The MIDI Input Enable Window (Item #76712) Window cannot be resized, scroll bar doesn't access other MIDI inputs Fixed: The ProFire 2626 is not displaying I/O properly in the I/O Setup window. (Item #101255) Note: If the I/O Setup does not show all Analog, Optical, and S/PDIF input labels after updating to 7.4.2cs4, launch the ProFire 2626 Setup Application via Hardware Setup to refresh the I/O Setup.
#76712) Window cannot be resized, scroll bar doesn't access other MIDI inputs Fixed: The ProFire 2626 is not displaying I/O properly in the I/O Setup window. (Item #101255) Note: If the I/O Setup does not show all Analog, Optical, and S/PDIF input labels after updating to 7.4.2cs4, launch the ProFire 2626 Setup Application via Hardware Setup to refresh the I/O Setup.
Installation Instructions
1. 2. 3. 4. 5. Verify Pro Tools M-Powered 7.4.2 is installed on your system. Quit the Pro Tools application if it is open. Locate the Pro Tools M-Powered 7.4.2cs4 update installer and launch it. Follow the onscreen instructions. When installation is complete, restart your computer.

If you have installed previous updates, some file versions may not change. This update installs the following files: Pro Tools M-Powered.app (v7.4.2cs4) DAE.framework (v7.4.2cs4) Time Shift.dpm (v7.4.2cs4) FFmt.framework (v7.4.2cs3) DigiReWire.dpm (v7.4.2cs2)
Pro Tools M-Powered 7.4.2cs4 Read Me for Mac OS X July 29, 2009

Pro Tools M-Powered 7.4cs10 Update for Windows
Pro Tools M-Powered 7.4cs10 Read Me for Windows July 29, 2009 For M-Audio Systems with Pro Tools M-Powered 7.4 Only Single installer for Windows XP and Vista This update requires previous installation of Pro Tools M-Powered 7.4
Who Should Use This Update?
This update contains fixes in the following areas: Playback File Management Time Shift Plug-in RTAS Processing Plus previous fixes in the following areas: Session/File Management Editing QuickTime Video Reason Adapted Importing Audio DigiBase Fade files Automation M-Audio ProFire 2626 M-Audio Fast Track Ultra File Comments in WAV files MIDI Plug-ins User Interface RTAS processing on AMD-based computers Dynamics III Elastic Time Using Soundminer Control Surfaces Plus Support for M-Audio Fast Track Ultra Series & ProFire 2626 In addition to the fixes above for M-Powered 7.4 users with all M-Audio interfaces supported with M-Powered 7.4, Pro Tools M-Powered 7.4cs3 or higher is required for M-Powered support of the M-Audio Fast Track Ultra, Fast Track Ultra 8R, and ProFire 2626. Pro Tools M-Powered 7.4cs10 is provided as an interim "customer support (CS)" release to address the issues described. While our testing has not shown these changes to introduce other problems, this version has not been fully qualified by Digidesign.
What's Included in Pro Tools M-Powered 7.4cs10?
Fixed: A play command in Pro Tools may not always engage playback on the first attempt (Item #114517) After a play command, the Play and Stop buttons may flash, however, Pro Tools does not playback. Subsequent tries would allow playback. Fixed: Cannot open sessions due to PolyVector error (Item #114287) Certain sessions cannot be opened due to the following error: "Could not complete your request because out_of_range: Cmn_PolyVectorImpl::At"
Fixed: A play command in Pro Tools may not always engage playback on the first attempt (Item #114517) After a play command, the Play and Stop buttons may flash, however, Pro Tools does not playback. Subsequent tries would allow playback. Fixed: Cannot open sessions due to PolyVector error (Item #114287) Certain sessions cannot be opened due to the following error: "Could not complete your request because out_of_range: Cmn_PolyVectorImpl::At" Fixed: Audible drift when using PAL to Film TCE conversion on long audio files (Item #113490) Using the Time Shift Varispeed preset (PAL to Film -4%) will result in a file that drifts over time and runs out of sync with picture. Fixed: Cannot select the number of RTAS processors on a hyperthreading-enabled CPU (Item #114048) When working with a hyperthreading-enabled processor, Pro Tools does not allow selection of the number of RTAS processors in the Playback Engine dialog.
Included from 7.4cs9: Fixed: Converting sample rate during Save Copy In or Import Session Data adversely affects volume automation (Item #111930) Saving a session copy with sample rate conversion to a rate different from the session's may result in erroneous automation ramps between breakpoints. This is mostly evident in scenarios where a static automation level had been changed over the duration of a single region. Fixed: Problems moving multiple selected regions (Item #99538) If you selected several adjacent regions, clicking on one of them to move all selected regions will only move the region you clicked on. Fixed: Incorrect multi-track audio import from QuickTime movies (Item #102279) Multi-track QuickTime movies import into Pro Tools 7.4 with each audio track containing a mix of all tracks, rather than individual tracks.
Included from 7.4cs8: Fixed: Pro Tools and Reason Crash When Loading "Machine" Patches on Reason Adapted Combinator (Item #106627) Only occurs in Reason Adapted, and does not occur when Reason Adapted is operated without Pro Tools Fixed: When Importing More than 100 Audio Files, Pro Tools could Close with no Warning (Item #100595) This would occur when importing all of the files at the same time
Included from 7.4cs7: Fixed: Attempting to Drag and Drop Files Containing iXML metadata from the Workspace Browser Would Result in No Import, and Assertion Errors (Item #100723) The assertion errors would occur when attempting to subsequently save the session Previous workaround was to use File > Import > Audio instead of drag and drop from the Workspace Fixed: Despite Changing the Fade Shapes in the Fade Dialog, Fade-ins and Fade-outs Always Conformed to the Last Created Fade In and Out (Item #100913) Fixed: Volume Breakpoints at "- inf" Could Change to Full Volume When Manually Trimming

The assertion errors would occur when attempting to subsequently save the session Previous workaround was to use File > Import > Audio instead of drag and drop from the Workspace Fixed: Despite Changing the Fade Shapes in the Fade Dialog, Fade-ins and Fade-outs Always Conformed to the Last Created Fade In and Out (Item #100913) Fixed: Volume Breakpoints at "- inf" Could Change to Full Volume When Manually Trimming Automation (Item #104551) This could occur when trying to trim the breakpoints down a few dB.
Note: There was no Pro Tools M-Powered 7.4cs6 release Included from 7.4cs5: Fixed: Cannot Launch Pro Tools M-Powered with M-Audio ProFire 2626 or Fast Track Ultra on Non-English Windows Vista or Windows XP OS (Item #103928) Attempting to launch would result in a "0 Length String" error message
Included from 7.4cs4: Fixed: The following error is generated when selecting a 256 + comment in the Workspace: "The value contained too many characters; previous value substituted". (Item# 100604) Fixed: WAV File Metadata Containing Non-English Characters Are Not Visible In Pro Tools 7.4, and Comments Can Be Lost if Edited (Item #100502) Although the file comments are invisible in the DigiBase comments field, clicking in that field will delete all of the comments This only affects non-BWF WAV files This CS version restores the visibility of WAV file comments, as long as the field wasn't clicked in using earlier versions of Pro Tools 7.4 Fixed: Only the First 16 MIDI Inputs Are Available In The MIDI Input Enable Window (Item #76712) Window cannot be resized, scroll bar doesn't access other MIDI inputs
Included from 7.4cs3: Fixed: Pro Tools Automation Thinning Could Sometimes Remove Non-Redundant Breakpoints (Item #100794) The thinning algorithm could mistakenly classify a breakpoint as redundant Fixed: Certain Third Party Products Could Cause Pro Tools to crash (Item #100661) Celemony Melodyne and AudioEase Snapper would cause a crash with tick-based regions (introduced in Pro Tools 7.4)
Included from 7.4cs2: Fixed: Track Color Coding Saturation Was Not Adjustable (Item #94474) Functionality is now the same as in Pro Tools 7.3.x Fixed: RTAS Processor Selection in Playback Engine Dialog Was Greyed Out With MultiProcessor AMD-based Computers (Item #99545) Note that this condition should only occur when HyperThreading is enabled on Intel-based computers Fixed: Opening a Session with an RTAS Version of Dynamics III Could Result in a Burst of Noise (Item #99562)
Functionality is now the same as in Pro Tools 7.3.x Fixed: RTAS Processor Selection in Playback Engine Dialog Was Greyed Out With MultiProcessor AMD-based Computers (Item #99545) Note that this condition should only occur when HyperThreading is enabled on Intel-based computers Fixed: Opening a Session with an RTAS Version of Dynamics III Could Result in a Burst of Noise (Item #99562) This problem was intermittent Fixed: Quantizing Grouped Elastic Audio Tracks Produces Some Inaccurate Transient Placement (Item #100013) Transients could be placed either before or after grid lines Fixed: User Can Only Promote the Confidence of an Event Marker by Moving it (Item #100378) Clicking on any Event marker will now raise its internal confidence rating to 100%, thus preventing the marker from being removed when the Event Sensitivity setting is lowered within the Elastic Properties window Fixed: Using Render or Commit With "Rhythmic" Algorithm Can Produce Artifacts at End of Files (Item #100420) This would usually occur when using extreme amounts of stretching Fixed: Elastic Time Warp Markers Could Move After Quantizing (Item #100423) Quantizing a selected area could cause markers outside that selection to move Fixed: Errors Resulting From Importing Certain Files Using Soundminer (Item #100028) File names using an ellipsis (.) would cause the error, "Unable to create a new audio file on drive "xxx" for track "xxx" because I/O error (-36)." Fixed: Pro Tools May Crash While Setting Up MIDI When Administrator Account Name Contains a Non-English OS and/or a Non-ASCII Character (Item #100142) Known to have occurred with Norwegian, Czech, Japanese and Korean Operating Systems

Included from 7.4cs1: Fixed: Pro Tools quits unexpectedly when moving a plug-in window while closing it from a control surface (Item #99442) If a plug-in window was closed from a control surface while the plug-in window was being dragged across the screen, Pro Tools would quit unexpectedly.
Installation Instructions
1. 2. 3. 4. 5. Verify Pro Tools M-Powered 7.4 is installed on your system. Quit the Pro Tools application if it is open. Locate the Pro Tools M-Powered 7.4cs10 update installer and launch it. Follow the onscreen instructions. When installation is complete, restart your computer.
If you have installed previous updates, some file versions may not change. This update installs the following files: ProTools M-Powered.exe (v7.4cs10) DAE.dll (v7.4cs10) DirectIO.dll (v7.4cs10) Time Shift.dpm (v7.4cs10) FFmt.dll (v7.4cs9) DigiReWire.dpm (v7.4cs8) CFnd.dll (v7.4cs8)
If you have installed previous updates, some file versions may not change. This update installs the following files: ProTools M-Powered.exe (v7.4cs10) DAE.dll (v7.4cs10) DirectIO.dll (v7.4cs10) Time Shift.dpm (v7.4cs10) FFmt.dll (v7.4cs9) DigiReWire.dpm (v7.4cs8) CFnd.dll (v7.4cs8) DHS_Resource404.dll (v7.4cs5) DHS_Resource411.dll (v7.4cs5) DHS_Resource412.dll (v7.4cs5) DHS_Resource804.dll (v7.4cs5) ProTools_Resource404.dll (v7.4cs5) ProTools_Resource411.dll (v7.4cs5) ProTools_Resource412.dll (v7.4cs5) ProTools_Resource804.dll (v7.4cs5) DHS.dll (v7.4cs3) DigiMIDIServices.dll (v7.4cs2) Dynamics III.dpm (v7.4cs2)
Pro Tools M-Powered 7.4cs10 Read Me for Windows July 29, 2009