Activity › Forums › Adobe Premiere Pro › 29,97 fps and adding black messing up the framerate
-
29,97 fps and adding black messing up the framerate
Posted by Tero Ahlfors on March 20, 2013 at 7:28 amSo I got a bunch of files back from a broadcasting company because the frame rates were weird and I checked them again. Premiere shows them as 29,97 but QT player says 28,95. The problem is that I added some black video in the front and back, If I render it out straight without the black it works great. The thing is they want the black because it is in their specs. If I generate black video from Premiere it renders out as 28,95 and if I add a black still (or leave the track empty) it comes out as 23,54.
What is going on?
I can render black video from AE and it seems to work, but this feature should really work inside Premiere.
Tero Ahlfors replied 13 years, 1 month ago 3 Members · 8 Replies -
8 Replies
-
Jeff Pulera
March 20, 2013 at 1:54 pmThat’s really bizarre. Rather than using the “Black Video” function in Premiere, try creating a black Matte in Premiere or just a black video-sized still from Photoshop, some other type of placeholder and see
Thanks
Jeff Pulera
Safe Harbor Computers -
Tero Ahlfors
March 20, 2013 at 3:44 pm[Jeff Pulera] “Rather than using the “Black Video” function in Premiere, try creating a black Matte in Premiere or just a black video-sized still from Photoshop”
I tried and it does the same weird frame rate change. I don’t know if it’s a Prores thing or frame rate thing or what. I’ll have to test more.
-
Tim Kolb
March 21, 2013 at 11:18 pmAre you creating the sequence from the media itself?
Maybe if you create a solid sequence with the correct settings (it sounds like 29.97 fps) and then go into your project panel and right click on the weird video clips…go to “modify” and under interpret, force the clip to play at 29.97.
Then the black clip you make when working in that sequence should play nice…and export properly.
TimK,
Director, Consultant
Kolb Productions,Adobe Certified Instructor
-
Tero Ahlfors
March 23, 2013 at 7:12 amIt doesn’t matter if I create the sequence from the clip or if I create it separately. If I have empty space or use the black video generator the frame rate will show up wrong.
-
Tim Kolb
March 23, 2013 at 12:43 pmYou forced the video clip to the right framerate with “modify”?
TimK,
Director, Consultant
Kolb Productions,Adobe Certified Instructor
-
Tero Ahlfors
March 24, 2013 at 3:28 pmI’m not forcing anything to any frame rate because that is not the problem. The export works correctly if I export the timeline that only has the file in it. The file is 29.97 and the sequence is 29.97 and when I add black video or a still or leave a track empty the export is messed up.
-
Tim Kolb
March 24, 2013 at 5:04 pmI can’t help but think there is some additional piece of information here…something that makes some of this connect somehow…
You said that the clip’s framerate is interpreted by QT player incorrectly…but that Premiere Pro interprets it as 29.97. You know this because Premiere Pro displays that framerate in the project panel header, or shows the clip properties someplace specific?
You said that the sequence is set for 29.97, but the black video “renders out” as 28.95?
Do you mean that the media is created at that framerate in the new asset dialog?…that dialog sets the framerate based on the sequence, so that would point to the sequence being the same (incorrect) framerate…which could happen if you create a sequence by dragging a clip that has that framerate over the “new item” widget to create a sequence based on that clip…
…or that the exported clip shows that framerate (in QT?…in PPro?) after you export the timeline?
Have you analyzed either the source files or the exported files in anything else?
I think more details are necessary to troubleshoot this.
TimK,
Director, Consultant
Kolb Productions,Adobe Certified Instructor
-
Tero Ahlfors
March 25, 2013 at 5:08 amI think that there’s some weird Quicktime frame rate flag bug going on. The rendered file shows up in the Premiere project panel as 29,97 and the length is the same as it’s supposed to be and I can render it out again at 29,97 and the frame rate is correct in QT player but that’s a generation loss right there. I do not know what the broadcaster uses to check these files but if it’s messed up at their end it’s my problem and not theirs.
Reply to this Discussion! Login or Sign Up