Jeff Pulera
Forum Replies Created
-
I’d guess it has to do with the blown whites/clipped highlights. Can you maybe bring the white levels down a bit?
Rather than going straight to .mp4, try exporting to a good intermediate codec like Cineform or DNxHD and see how it looks. If that works, then export that new clip to .mp4 and check results.
Thanks
Jeff Pulera
Safe Harbor Computers -
“I don’t believe that’s true. By necessity the previews must match the export (typically ProRes or DNX) and thus the rendered parts of the timeline become copies.”
Premiere can in certain circumstances do a “smart render” at export, but like you said the Preview and Export must match, which is not the case most of the time (maybe more common on Mac, ProRes to ProRes perhaps). For instance on a PC, the default preview render might be MPEG then exporting to H.264, so video is definitely getting transcoded twice then.
In any case, smart render would not “improve” the export, but only serve to keep the same quality as the preview was.
Thanks
Jeff Pulera
Safe Harbor Computers -
Jeff Pulera
January 4, 2018 at 8:58 pm in reply to: Timecode issue: Exported length not matching project length. Matches if I bring it back in23.976 frames per second x 60 seconds per minute x 65 minutes = 93506 frames of video
24 fps timecode x 60 x 65 = 93600 frames
93600 – 93506 = 94
94 / 23.976 = 3.92
The math adds up, accounting for 24fps timecode versus 23.976 actual frame rate as mentioned earlier
Thanks
Jeff
Jeff Pulera
Safe Harbor Computers -
No, if you are getting unwanted artifacts in the export, something is wrong.
Pre-rendering and then exporting with Use Previews checked is just going to add another generation of compression to the output, further degrading the quality.
Do you have any screenshots of the issue, or export settings that we can review?
Thanks
Jeff Pulera
Safe Harbor Computers -
Jeff Pulera
January 4, 2018 at 8:46 pm in reply to: Long video in HD but low quality output, need a handYou can have a small file, or a high-quality file…but not both, you decide.
What was the size of the original video file? You can’t expect to compress it 10 to 20x smaller and have it still look good.
2-Pass VBR will benefit the quality versus CBR when working with low bit rates, but the improvement would be slight, don’t expect miracles. You need bandwidth for quality and that means larger files unfortunately.
Thanks
Jeff Pulera
Safe Harbor Computers -
The GTX 1080 is great for Premiere, but since your CPU is not quite up to standards, the GTX 1070 might be a good match for price/performance. As the GPU is used for scaling in Premiere, the 1070 or 1080 card should help out when editing UHD in an HD sequence.
Make sure you have fast, dedicated storage also and are not editing media off the C: drive.
Thanks
Jeff Pulera
Safe Harbor Computers -
I agree with Tero – the VBR encoding is only going to use as much bandwidth as is necessary for the scenes being encoded. If you encode using Constant Bit Rate, then it would be a bigger file. However, I never see a SMALLER file as a being a “problem”. It saves space, downloads quicker, etc.
Thanks
Jeff Pulera
Safe Harbor Computers -
Jeff Pulera
December 29, 2017 at 9:37 pm in reply to: Encore CS6 and Windows 10 Fall Creators updateHi David,
Are you making DVD or Blu-ray?
Thanks
Jeff Pulera
Safe Harbor Computers -
Scale to Size has already diminished the image size down to match the sequence. You need to use Set to Frame Size instead.
And when moving clips to a new sequence, use Ctrl-A to Select All, then Ctrl-C to Copy, then open the “B” sequence and paste with Ctrl-V. Very quick and easy.
Thanks
Jeff Pulera
Safe Harbor Computers -
If you don’t hear the noise when listening to “live” output from VCR, then it stands to reason that the audio output from the VCR is fine then, and the noise is being introduced later at the capture stage (it does sound like digital noise to me).
Do you perhaps have a CD or DVD player with RCA audio outputs that you could use as a test, and “capture” the audio from that device and see if the same noise is present? That would tell you for sure it’s a capture issue.
Thanks
Jeff Pulera
Safe Harbor Computers