Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro How to do a 25 fps PAL DVD export from Premiere Pro with 24 fps source?

  • How to do a 25 fps PAL DVD export from Premiere Pro with 24 fps source?

    Posted by Tobias Andersen on January 8, 2013 at 11:54 am

    Hi,

    I have a Premiere Project where my source footage is 24p (1920*1080), but I would like to make a 25p MPEG2-DVD PAL Widescreen export (25 fps seems to be the only option when exporting).

    I tried to use frame blending to smooth out the result, since it was choppy on my PC without it. However, this also makes it quite a bit more blurry when the camera is moving, so it would be nice if I could avoid using frame interpolation – but I’m unsure what the best method is.

    I tried to create another sequence with 25 fps, and then I copied everything over from the old sequence – and I went to ‘interpret footage’ and set my clips to 25 fps. This renders smoothly, but it’s a bit of a mess to make since it messes up my timeline by inserting quite a few empty spaces – so I have to do a lot of small adjusments.

    I’m in doubt if I can just skip doing the new sequence and just do the second step with interpret footage and still use the old sequence – this causes less of a mess in my timeline, but I suspect it is of some importance that the sequence framerate is the same as the export framerate?

    Or are there any alternative way of doing it? It would be ideal if I could just tell Premiere to make the 25 fps export simply by playing through the sequence a little bit faster.

    I hope someone can help me, thanks 🙂

    Ivan Myles replied 13 years, 6 months ago 3 Members · 13 Replies
  • 13 Replies
  • Ivan Myles

    January 8, 2013 at 8:55 pm

    Please clarify which version of Premiere Pro, and whether you are exporting from Premiere Pro, Adobe Media Encoder, or After Effects. If you are using Premiere Pro CS6, the MPEG2-DVD codec allows frame rate to be set automatically based on source.

    In response to the question in your post, one method to reinterpret all footage simultaneously is to:

    – export the original sequence at 24fps, preferably with Key Frame Distance = 1; use either a lossless intermediate codec, or MPEG2 at equivalent settings to the final output
    – import the new file
    – interpret the new footage at 25fps
    – insert onto a 25fps timeline
    – export the new sequence at 25fps

    The other method was mentioned in the post: change the speed of each clip and adjust on a 25fps timeline accordingly. This is more work, but it allows other adjustments (e.g. extending clips or adding footage to fill the extra frames, and re-synchronizing the audio to play at normal speed).

  • Tobias Andersen

    January 8, 2013 at 9:22 pm

    Many thanks for your reply 🙂

    I am using Premiere Pro CS5, and I export from here by going File>Export>Media, it may be using the Media Encoder by doing this, I’m not sure?

    I did try with the automatic framerate based on source, but for some reason it still seems to be outputting at 25 fps (it does say 24 fps for source in the export settings – but in output it says ‘F Fps’ for some reason when I choose this framerate setting). I assume it’s best to go with 25 fps though for PAL.

    Regarding the method I posted, how important do you think it is to create a new sequence with 25 fps with a copy of my stuff in the 24 fps sequence (and with a change of framerate of the clips), as opposed to just using the 24 fps sequence (and also change framerate of the clips)? The problem is that I have many titles in my sequence and they are getting shortened too when pasting into the 25 fps sequence – so if I could just use my 24 fps sequence I wouldn’t have to change much.. but I’m unsure which effect this has on the export?

    Thanks again.

  • Ivan Myles

    January 8, 2013 at 9:52 pm

    The best method will depend on how much time you can devote to it, how many clips need to be adjusted, and whether the audio should be sped up or played at normal speed. If you have the time, I suggest adjusting each clip and reorganizing the 25fps timeline. In this way, you can decide on a clip-by-clip basis whether to speed up the footage, or just repeat every 24th frame (usually OK with low motion shots, and perfectly fine with non-scrolling titles). The down side is the time required, especially if dealing with hundreds of clips.

    You could also try a hybrid solution: use the method outlined in my previous post, and then combine the new file with some of the original footage (titles, for example) on a new 25fps timeline. That way you can pick and choose the places where you want to revert back to the original footage without having to speed up all of the other clips individually.

  • Tobias Andersen

    January 9, 2013 at 1:55 pm

    Thanks for your suggestions 🙂

    I just tried to export the clip in 24 fps to try your first suggestion – I wasn’t entirely sure on the format to choose, but I chose Microsoft AVI and set the codec to ‘None’, I ticked ‘Maximum Render Depth’ and chose 32 bit (probably not necessary).

    Apart from the large file size (it’s 20GB for 1min and 45 seconds) – are there any problems doing it this way?

    I’d asume I could use some losless compression for the same quality – but if there aren’t any problems with the way I did it, I don’t think I will change it for now 🙂

    It seems to be working fine (with the audio sped up to 104.1%).

  • Ivan Myles

    January 9, 2013 at 5:57 pm

    Good to hear it’s working.

    AVI-None is great if you can live with the file size. It is 8-bit RGB, so there might be a slight color shift if your workflow is YUV. Try exporting a short sample to MPEG-DVD to compare the final encode to the source footage.

    Good luck with the project.

  • Ivan Myles

    January 9, 2013 at 6:02 pm

    Good to hear it’s working.

    AVI-None is great if you can live with the file size. It is 8-bit RGB, so there might be a slight color shift if your workflow is YUV. Try exporting a short sample to MPEG-DVD to compare the final encode to the source footage.

    By the way, 32-bit depth denotes RGBA; if you don’t have an Alpha channel use 24-bit. It cuts the file size down by 25%.

  • Ivan Myles

    January 9, 2013 at 6:28 pm

    Sorry, one more thing: since the final output is MPEG-DVD, you can reduce file size greatly by creating the AVI-None in the final resolution and pixel aspect ratio (720×480 Widescreen, presumably). The 1:45 minute file in 24-bit depth would require 2.4GB.

  • Tobias Andersen

    January 9, 2013 at 6:50 pm

    I can’t really tell any differences between this export and with the other method (where I manipulate the timeline) – so that’s pretty nice 🙂

    I think I do have an alpha, though not intentionally, and I don’t need it – I got a title on top of nothing/black a few times in my project which I think causes this – in the .avi it looks a little strange at the edges of the text. I think it needs to be premultiplied – but when I import it in Premiere Pro it looks fine – and the final outcome also seems to be fine in this regard.

    So I suppose it’s not a problem I did 32 bit, apart from the increased file size (will do 24 bit in the future)?

    Many thanks for your help 🙂

  • Ivan Myles

    January 9, 2013 at 7:54 pm

    Glad to help!

    In an older version of Premiere Pro text would pixelate badly when titles were placed against an empty background. Out of habit now I just insert a large black rectangle under the titles.

  • Conrad Olson

    January 9, 2013 at 8:14 pm

    It sounds like you have a solution but…

    Why are you trying to make a 25fps DVD. From what I remember of the DVD format you can encode PAL res files at 24fps and the DVD players will do the 4% speed during playback to create the 25fps output. I’m pretty sure that most Hollywood DVDs are mastered at 24fps.

    I could be wrong, haven’t dealt with DVDs for a while.

    conradolson.com

Page 1 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy