Jump to content

Wikipedia:Reference desk/Archives/Computing/2018 August 11

From Wikipedia, the free encyclopedia
Computing desk
< August 10 << Jul | August | Sep >> Current desk >
Welcome to the Wikipedia Computing Reference Desk Archives
The page you are currently viewing is a transcluded archive page. While you can leave answers for any questions shown below, please ask new questions on one of the current reference desk pages.


August 11

[edit]

Adobe Premiere Pro CS6

[edit]

I possess the entitled software. I am unable to retrieve the same .mp4 quality thereafter creating a whole file. The following steps I've taken in order to modify an .mp4 file i.e.:

After opening "Adobe Premiere Pro CS6", click/select "New Project" option, "New Project" window appears, pass through the window(s) to "New Sequence" window – I believe the problem rest in this window…

Issues found, disturbance in image/video quality and slow frame rate.

How do I get exact quality and the exact frame rate?

119.30.35.10 (talk) 15:52, 11 August 2018 (UTC)[reply]

First off, does this problem only seem to occur during playback within Premiere Pro, or also with your exports? If it's just the former, your playback resolution may be set inappropriately—you can adjust it using the dropdown meny below the bottom-right corner of the program monitor
If you're noticing a big difference between your source material and your exports, check the file—what is its resolution, frame rate etc.? If they all seem to be what you'd expect (probably nothing lower than 1280x720 and ~24fps) then try changing your sequence settings to one of the presets—you may find that what you have been using is giving you a low resolution and low frame rate. As an example, the AVCHD 1080p50 preset is 1920x1080 and 50fps. The second step to checks is your export settings. Again, you can use a preset for exporting—as it happens, my latest PPro project is set up using the H.264 format, with the "Match Source - High bitrate" preset. Give that a try.
MIDI (talk) 14:14, 12 August 2018 (UTC)[reply]