![]() |
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#1
|
|||
|
|||
![]()
Just upgraded to Sonoma and PT 2024.10.2 and now experiencing a problem with Pro Tools when bouncing audio for video (post-production). The 0.1% pull down engages automatically for both audio and video, and the Video frame rate indicator turns red. This issue persists regardless of whether I'm working with h264, DNx, or ProRes video formats. When I change it back to None (frame rate indicator matches) and try to bounce again, it will do it again anyway.
The only way to Bounce correctly is to remove the QT. Has anyone encountered this problem or know how to resolve it? |
#2
|
|||
|
|||
![]()
Why are you trying to bounce with a pulldown? How are you converting the video?
|
#3
|
|||
|
|||
![]()
Here's my process and I've been doing this for a very long time without issues:
-import h264 mpeg4-avc part 10 1920x1080, 23.976 QT into PT -have a Session Setup window open, if Pro Tools adds a 0.1% pull down on QT import, correct it to None -on a video track, frame rate indicator goes from red to white after correction -mix and bounce offline After the update, as soon as I press opt+cmnd+b to Bounce, I can see in a Session Setup window that 0.1% pull down gets added automatically and no way to change it. Could it be a codec missing? |
#4
|
|||
|
|||
![]()
Interestingly, I've noticed that if I import two 23.98 QuickTime files, Pro Tools adds the pull down for the first import.
After correcting it to "None," importing a second QT file doesn't trigger the automatic pull down. This behavior is consistent regardless of the order of file imports. |
#5
|
|||
|
|||
![]()
What frame rate is your session? Are you using a Sync peripheral?
A 23.98 QT should import into a 23.98 session just fine.
__________________
~Will |
#6
|
|||
|
|||
![]()
Session frame rate is 23.98. No sync peripheral.
|
#7
|
|||
|
|||
![]()
After extensive testing over the weekend, I discovered that turning off "Auto Match Pull Factors" setting, tucked away at the bottom of Timecode Rate settings in the Session Setup window revolves the issue. When the setting is turned off, everything goes back to normal. Interestingly, turning it back on doesn't resurface the problem.
For context, this "Auto Match Pull Factors" setting (Reference Guide p.1351) is designed to automatically adjust audio and video playback rates when you change the session's timecode rate. It's a feature that's supposed to help maintain sync, but in this case, it's causing more trouble than it's worth. This definitely points to a potential bug in how this feature is implemented in the current version of Pro Tools, in my case 2024.10.2 |
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Pull Up/Pull Down and digital transfers | dmfisher1 | Post - Surround - Video | 8 | 10-28-2004 11:45 PM |
Pull-ups / Pull-Downs (which is which?) | rdolmat | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 3 | 04-15-2004 01:51 PM |
Time code pull up pull down? | Digipics | Tips & Tricks | 1 | 08-07-2003 09:23 PM |
Pull-ups / Pull down question | georgia | Tips & Tricks | 4 | 06-01-2001 05:21 PM |
Pull up/pull down question | Olav Celius | Pro Tools TDM Systems (Mac) | 1 | 02-15-2001 10:17 AM |