Pro Tools and Pro Tools HD 10.0 on Mac OS X 10.6.x (“Snow Leopard”) and Mac OS X 10.7.x (“Lion”) — 10/13/11 13
QuickTime Clips with “Clean Aperture” Settings Do Not Play Back in Pro Tools 10 on OS X 10.7 (PTSW-150342)
Pro Tools 10 on Mac OS X 10.7 is unable to playback QuickTime video clips with “Clean Aperture” settings. The session plays
back, but these clips appear black in the Video window. These clips do play back in Pro Tools 10 on Mac OS X 10.6.
Standard Definition QuickTime Movies Are Rendered as 16:9 Anamorphic Play Back in Pro Tools at 4:3 (PTSW-23020)
Standard Definition QuickTime movies rendered with 16:9 an anamorphic Scaled Size of 853x480 play back in Pro Tools at 4:3 or
720x486 resolution. The Scaled Size attribute of QuickTime movies is ignored by Pro Tools. To work around this problem, render
the movie letterbox natively within the 720x486 pixel dimension.
MPEG-1 and MPEG-2 Video Freezes at Edit Points (PTSW-55185)
Editing MPEG-1 & MPEG-2 video is not officially supported. If you experience this problem, try switching playback to the Video
window, or convert the movie to a supported format using a 3rd party application. Removing the audio from an MPEG-1 or
MPEG-2 movie with a 3rd party application may also fix the problem.
Audio from “Muxed” MPEG-1 and MPEG-2 Movies Cannot Be Imported and Will Be Heard in a Bounced Movie (PTSW-53625)
Unlike other QuickTime formats, MPEG-1 and MPEG-2 movies store audio and video in a single multiplexed track, called a
“muxed.” track. Pro Tools cannot separate the audio from video for these types of movies. As a result, you will not be able to im-
port the audio from an MPEG-1 or MPEG-2 movie. Also, if you Bounce to QuickTime using an MPEG-1 or MPEG-2 movie as a
source movie, the original audio from the movie will be present in the bounced movie (even though it will not be heard while
working with the movie in Pro Tools). To import audio from an MPEG-1 or MPEG-2 file, use a third party application to “demux”
the MPEG stream.
Dragging from Mac Finder in Shuffle Mode Does Not Work Correctly with Video (PTSW-28041)
Dragging a Video file from the desktop to the Edit window while in Shuffle mode will always place the video at session start, over-
writing existing video clips in that location.
System Instability when Running Multiple Applications Using Blackmagic Design Hardware for QuickTime Video Output
(PTSW-19486)
When Pro Tools is running with a Blackmagic DeckLink II Extreme or Intensity video capture and playback PCI-e card installed,
launching Blackmagic Design’s Deck Capture utility, Final Cut Studio, or any other application which supports Black Magic hard-
ware for video output, can result in system instability. To avoid any potential system instability only use one Blackmagic Deck-
Link–aware application at a time.
Clip names appear incorrect after selecting Field Recorder channel matches, or expanding to new tracks.
(PTSW-136012)
This can occur if the file name of a Field Recorder channel match contains a hyphen followed by a number greater than zero. Pro
Tools names new clips by incrementing the number after the hyphen. If a field recorder file is already named in this way (such
as “Filename-01”), then new clips created by selecting a Field Recorder channel match or by expanding a track may have names
different from the parent file. To avoid this situation, avoid using hyphens in Field Recorder file names.
Importing a File Directly to a Field Recorder Guide Track Disables the Field Recorder Guide Track Setting (PTSW-152913)
Importing an audio file directly to a Field Recorder Guide track, either by dragging from the Workspace browser or dragging from
the desktop, will disable the Field Recorder Guide track setting for that track. Once this has occurred, you must re-enable the
track as a Field Recorder Guide track. To avoid this issue, import the file to the Clip List first, then drag it to the track. Alter-
nately, you can use the Import Audio command (File > Import Audio) to import the file to a new track or the Clip List, and then
drag it to the desired track.
Field Recorder Matches Appear Offset After AudioSuite Rendering if the Session Timecode Rate Does not Match the File
Timecode Rate (PTSW-152147)
If a portion of a file has been rendered with an AudioSuite plug-in, an offset can occur when expanding field recorder matches
in cases where the session timecode rate does not match the timecode rate of the audio file. To avoid this issue, you can either ren-
der the whole file with AudioSuite (rather than only a portion of the file), or use Whole File mode when rendering AudioSuite pro-
cessing.
Comentarios a estos manuales