![]() ![]() I've tried "save session copy in" and removing and re-importing the QuickTime but with no success. Hopefully I haven't confused the crap out of anyone reading this post, I know it can be difficult to explain things only in writing when you can't actually see the issue in person. The video will remain this way until I close the session and re-open it. In this example, the magic "glitch" point in the Pro Tools timeline is at 02:05:46:15 where the video loops back to the beginning of the file and continues playing while the playhead continues on from 02:05:46:15. Then it will hit the "glitch" point and the Quicktime will loop back to the beginning of the film and continue playing. When I scrub through the video earlier than where the QuickTime glitch occurs on my timeline it plays fine. let's say I'm adding some sounds at 02:28:14:06, when I drag files in from workspace the video will glitch and start playing back at 01:22:28:08 even though the playhead will be at 02:28:14:06 and the QuickTime File hasn't moved on the timeline either. I realize that probably sounds confusing when you read it so I'll explain using an example. I can import audio form the "Import Audio" window and it doesn't affect the QuickTime but I prefer to use the workspace for speed and efficiency in my workflow. Basically the issue occurs when I import audio by dragging files from the workspace, the video will get screwed up and play the QuickTime from a completely different point in the film. In both cases it's happened when I've been working in the later parts of the films (past the one hour point of each film). the last 2 feature films I've worked on). ![]() I seem to be encountering the bug with my QuickTime playback when working on longer video files (i.e. When I edit sound fx for post audio projects I like to use the workspace window to audition sounds and drag the files to my timeline. ![]() I didn't have this issue on my old system so I'm wondering if it's a bug that is specific to Pro Tools 10 and Lion (I'm also running PT 10.2.0). I recently upgraded to a newer MacBook Pro and am now using Lion 10.7.3 coming from Snow Leopard. Hopefully someone out there might be able to shed some light on an annoying bug that I can't seem to figure out. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |