Is the sequence where you test the title by itself, is it the same settings DSLR 1080p 30fps?
the screen shot you show is confusing, because you say that you blur and come into focus. that must be your in focus position.
TThanks for responding.
yes the sequence is the same. Dslr 1080p 30fps.
The screen shot is still in the blurred stage...I was hoping to show the blockyness of it. Not necessarily the blur vs in focus. The original video with titles, all of the video is blocky so it reduces the entire projects resolution.
its like the fast blur is effecting the layer underneath?
Did you start with a large Title or a small Title before you scaled it?
Titles in PPRO are not vector graphics...so start large or use a vector graphic
good. I thought they were vectors.
do as shooternz mentions
Letters are big to start. So the key frame starts with it shrunk, and moves to the default size...does that make sense?
I don't think the blur has anything to do with it. If I remove it still does the same thing.
Nto sure if this helps....but in yet another project, I have a title crawling right to left....and it does the same thing with pixelation. It seems that motion is what it triggers it.
Also, it looks good in the preview. But when I export it, it looks terrible. Exporting it with max render, for 2 vbr pass, and max quality 1080p .mp4. I use this preset for all my videos and never have an issue.
Another thing to note. When I have video with this, it badly pixelates the video, without any titlle over the video. It's like because it's in there, it reduces the resolution of the entire sequence.
All points noted. I have returned to my machine, but in SpeedGrade.
Will be back in Premiere soon to simulate.
Thanks for your help!
To make things a little easier, I have posted a video to vimeo to give you an idea of the pixelation on the title and the accompanying video. Vimeo Password = adobehelp
Also, here is a picture of how I have the scale and blur in the timeline.
looks like CS6
I am unable to watch video from this current location
i am also unfamiliar with fast blur - mine defaults to quick fast blur in and then clear, then ramp to default blur out. I see you ramp yours down to zero
your position looks like a 29.5 blur, so nothing wrong with that view - its how it effects the rest of your video
one solution I read this morning was to do the effect in After Effects, render, then import into Premiere
Woops, me bad, my CS6 and CC have same fast blur as you. I must have hit something, so I now see the same effect graph as you
there is a member on here that renders using the Media Encoder rather then exporting through Premiere, but that is with codec mpeg-2. Says better quality through AME queuing through Premiere export because AME does not use GPU to render, uses only CPU. Says takes longer, but better quality.
or, what about using an adjustment layer over yout Title track and applying the effects to the adjustment layer rather then all on the title?
sorry, just throwing thoughts out there
DOes anyone else have anymore thoughts on this? I am using cs6. Does cc perhaps fix it? Can anyone try it and duplicate the issue in cs6.
Alright, I have been doing the process of elimination. I tried a different export mode, and it worked! It's not exactly the export I wanted, so I tried the one I am used to doing. a custom preset that I have made based on the h.264 1080p preset. I have always done, max render, max depth, and 2 pass vbr. Well it turns out that choosing 2 pass vbr is what is causing it to happen. If I turn that to 1 pass, and export. The resolution is what it should be along with the file size....Which is obvisously strange, as I was under the impression 2 pass would give me a better picture.
Can anyone explain why this would happen?
My thoughts doesn't make sense because you used to be able to export that way before
When you say the file size is what it should be,,, Does the vbr1 pass give you a larger file size then the vbr2?
SInce the vbr2 should be a larger file size, does it have to do with the bit rate? Where on the second pass, it tries to make the file bigger, but the first pass has reached max file size according to set bit rate, so during the second pass, instead of adding to the file size, data is trashed because the bit rate has already max'd out the file size. During the second pass the data fills in the first pass, but trashes the best part.
In this instance, yes vb1 does a much larger size than vb2. We are talking 1 GB for a 5 minute video with vb1. Vs. vb2 is like 3 MB....
Interesting thought on the bit rate. I will have to try and experiement a little. Although the bit rate is set to 30-40...so its pretty high to begin with. I had to reformat my machine so it may be a couple of days before I can try it again. Will keep it updated.
i am looking for exact Export Setting you are using
I am making a guess at
preset Vimeo HD 1080p29.97
and not looking into it too much until I zero in on your export setting
Does the Estimated file size change? Or I assume the estimated file size does not indicate the drop in file size when changing the bitrate VBR 1 to VBR 2.
Looks to me in that Export Setting there is no change from CS6 to CC where target and maximum are set at 5. My thoughts were Vimeo needs that max bitrate and don't know what your output was.
Hi Oceanshutter, did you try both export with media encoder and directly from premiere? With some Graphics I noticed some strange difference between this two ways. Maybe worth a try?