Pro Tools LE 7.4cs10 Update for Mac OS X (Tiger)

• Universal installer for PowerPC and Intel-based Macs on Mac OS X 10.4 ("Tiger")
  
• Not supported on Mac OS X 10.5 ("Leopard")
  
• This update requires previous installation of Pro Tools LE 7.4
  

Who Should Use This Update?

• Playback
  
• File Management
  
• Time Shift Plug-in
  
• Core Audio
  
• Using original Mbox on Intel-based Macs
  

• Session/File Management
  
• Editing
  
• QuickTime Video
  
• Recording
  
• Reason Adapted
  
• DigiBase
  
• Fade files
  
• Automation
  
• Modification: Expand to New Tracks by Time Code Only
  
  • Requires DV Toolkit 2
    
• File Comments in WAV files
  
• MIDI
  
• Avid Video
  
• 003
  
• Plug-ins
  
• PAL/Mojo
  
• Scrubbing with Mojo
  
• User Interface
  
• Dynamics III
  
• Using Soundminer
  
• Avid Video Peripherals
  
• Elastic Time
  
• Digidesign Control Surfaces:
  
  • Command|8
    
  • C|24
    
  • Control|24
    
  • 003 Factory (console)
    
  • Digi 002 (console)
    

What’s Included in Pro Tools LE 7.4cs10 for Mac OS X?

• After a play command, the Play and Stop buttons may flash, however, Pro Tools does not playback. Subsequent tries would allow playback.
  

• Certain sessions cannot be opened due to the following error: "Could not complete your request because out_of_range: Cmn_PolyVectorImpl::At"
  

• 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.
  

• The operating system becomes unresponsive (spinning beach ball, freeze, or “kernel panic” message), requiring a restart of the computer.
  

• This problem does not occur on any Mbox 2 products or PowerPC-based Macs
  
• Please note that for Intel-based macs only, this fix will add approximately 3ms of monitoring latency when performing with virtual instruments
  
• This fix eliminates many, but not all instances of error -9136 during playback with the original Mbox on Intel-based Macs. For other possible causes of -9136 errors, see the following article: DAE error -9136 with an Mbox on Mac OS X.
  

• 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.
  

• If you selected several adjacent regions, clicking on one of them to move all selected regions will only move the region you clicked on.
  

• Multi-track QuickTime movies import into Pro Tools 7.4 with each audio track containing a mix of all tracks, rather than individual tracks.
  

• The audio was not affected, and the waveform could be restored by re-calculating it after the record pass
  

• Only occurs in Reason Adapted, and does not occur when Reason Adapted is operated without Pro Tools
  

• 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
  

• This could occur when trying to trim the breakpoints down a few dB.
  

• Typical Workflow
  
• Relinking the Original Unedited Guide Track
  
• Known Limitations with Expand to New Tracks by Time Code
  

• 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
  

• Window cannot be resized, scroll bar doesn't access other MIDI inputs
  

• This problem started in Pro Tools LE 7.4 for Mac OS X
  

• This would only occur if playback crossed 35min-45 seconds from the session start
  

• Although this is not likely to occur on 003 Rack, this update is recommended for both 003 Factory (console) and 003 Rack
  

• The thinning algorithm could mistakenly classify a breakpoint as redundant
  

• Celemony Melodyne and AudioEase Snapper would cause a crash with tick-based regions (introduced in Pro Tools 7.4)
  

• This resulted from Mojo getting "stuck" in NTSC mode even when Pro Tools was set to PAL
  

• Functionality is now the same as in Pro Tools 7.3.x
  

• This problem was intermittent
  

• 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)."
  

• This would occur after importing audio files from the Workspace Browser
  

• Transients could be placed either before or after grid lines
  

• 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
  

• This would usually occur when using extreme amounts of stretching
  

• Quantizing a selected area could cause markers outside that selection to move
  

• 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. Verify Pro Tools LE 7.4 is installed on your system.
2. Quit the Pro Tools application if it is open.
3. Locate the Pro Tools LE 7.4cs10 update installer and launch it.
4. Follow the onscreen instructions.
5. When installation is complete, restart your computer.

• Pro Tools LE.app (v7.4cs10)
  
• DAE.framework (v7.4cs10)
  
• DigidesignUSBDriver.framework (v7.4cs10)
  
• Time Shift.dpm (v7.4cs10)
  
• FFmt.framework (v7.4cs9)
  
• DigiReWire.dpm (v7.4cs8)
  
• DMC.framework (v7.4cs4)
  
• 003.bundle (v7.4cs3)
  
• DHS.framework (v7.4cs3)
  
• Dynamics III.dpm (v7.4cs2)