Pierpaolo Ferlaino
Forum Replies Created
-
I can export 5.1 AAC on CC2014 both audio only and h264… I don’t know if the previous version had some sort of limitation…
-
If you’re talking about burned in subtitles you can only blur, cover them with a black matte or something like that…
-
You can fit your footage right clicking your clips and selecting “scale to frame size” from the contextual menu… You can also set this behaviour as default in you preferences but it will work on your newly created sequences…
It’s obviously better to downscale rather than upscale but it depends on your workflow and delivery format…
-
To check the fields metadata you can use imedia hud (mac only) or media info . You can also import the file back to premiere and look at the native fields interpretation using “interpret footage”…
-
I’m on a tablet at a the moment and for some reason I can’t see the video header on you website but according to what you are writing you’re starting from wrong assumptions…
Data rate is measured in bps which is byte per seconds: that means duration really cares… It doesn’t matter if you’re using a static or a moving image…
If you’re using cbr compression 30 seconds of static image will be equal to 30 seconds of moving image.
If you use vbr compression 30 seconds of a static image will be smaller than 30 seconds of a moving image but 35 seconds of a static image will be greater than 30 seconds of the same static image.In a movie with mixed static and moving images vbr compressioon will result in frames which are more or less compressed according to the complexity of the scene.
That said, it’s weird you see visual difference in the static image (the tv) and it’s probably a matter of compression settings… maybe you’re using a data rate which is too low…
-
That sounds weird… what are your export settings?
-
You should keep your footage interpretation (project window) as native… If premiere is misinterpreting the native field scan set it manually to interlaced (upper field)… Then edit in a progressive sequence…
-
If your project is well organised you can copy everything to the new machine and relink…never had a issue on a well organised project…
You can also use the project manager but I usually copy projects by hand and use the project manager only for archiving purposes…
Keep the old project on the old machine until you verify everything works fine… -
It can be both a faulty graphic card (apple is replacing my laptop’s motherboard right now because of a similar problem) or a Cuda issue…
In that case try upgrading Cuda at first and if the problem persists the workaround is to uninstall cuda and use opencl. ..
If you google “premiere Yosemite cuda” you’ll find a lot on that…
I know you’re not on Yosemite but, as far as I know, some user experienced the problem on the last release of mavericks too… -
Hi, I’m not sure I understand well…
Your movie is 23.976… you had your mix done at 23.976 so audio and video have the exact same duration, right?
Why don’t you just drop the 23.976 movie to the dcp facility and ask them to do the conversion?