[Alex Ezorsky]

Hi, thanks for responding.

However, I kind of figured you might say that. I know mpeg2 is not a happy medium for AE but whats really frustrating me is that I had NO problems before the update, even with the exact same files. I guess I was really wondering if anyone here knew the internal structure of the AE program on a mac and if so how to re-install codecs.

Your help is highly appreciated.

[Alex Ezorsky]

AH! I LOVE YOU!

Seriously I was about to completely lose it with Premiere and seriously considered FCP. My situation is still quite stupid but you have hit the nail mostly on the head.

first I tried setting up a sequence as (progressive). The result was a much clearer image during little motion, but low and behold when the character moved warbly ghosting would appear.

Then I tried going back to the normal 640×480 sequence and changed the field to “always de-interlace” on the clip settings which sadly had no effect.

Finally I went back to my progressive sequence, changed the clip to “always de-interlace” and voila! Finally the full crispness the video was intended to be!

Strange notes: My camera (admittedly lower end) the JVC HD7, supposedly creates files that are 1920×1080 square, interlaced. When I did some research however, I found out that the camera apparently first captures 1080p then somehow converts it to interlaced https://en.wikipedia.org/wiki/JVC_GZ-HD7. This seems ridiculous to me.

I am also still a bit confused why even in the timeline and timeline monitor my raw files 1920x1080i square scaled down into a 640x480i square timeline look low quality, but the same file looks fine in a 1920x1080i timeline OR when scaling down looks fine in a 640×480 square but only if DE-interlaced in a progressive timeline.

This is some heady video science that I am trying to wrap my head around but only getting halfway.

Whether I totally get it or not, I have found the solution and owe it all to you Tim Kolb.

Thank you, and thanks CCF

[Alex Ezorsky]

Ok you are right and I am sorry to let my frustration show.

However in my second post I mentioned how I made changes to the settings in response to your post about size differences.

At the time of my first post I was not aware that the “desktop” setting in premiere meant “custom” (strange to me) which is why I settled for the DV NTSC preset. However since then what I did was make sure my AE comp and Premiere sequence had the same settings.

AE: 640×480 square 29.9fps
Premiere: 640×480 square 29.9fps

Then I opened AME and imported both the comp and the sequence. Then I exported both with the same settings.

AME export: FLV 640×480 500kbps

After reviewing, the premiere file was still less sharp than the AE one.

Thanks again for all your help.

[Alex Ezorsky]

Well AE isn’t so good at long projects (15min), doesnt do live-preview, and sucks at audio editing. The project is quite simple so I figured premiere would be fine. Why is premiere exporting the same dimensions, same aspect, same, pixel ratio, same compression, at LOWER QUALITY!?

[Alex Ezorsky]

Ok thanks for all your help, however here’s what I’ve done since to no avail.

I made a premiere timeline that was 640×480 square with source shrunk to fit, rendered 640×480 square
(still not sharp)
I made a premiere timeline that was 1920×1080 square and rendered it shrunk and cropped in AME
(still not sharp)
I made a premiere timeline that was 1440×1080 square and rendered it simply shrunk in AME
(still not sharp)

I go back, check my render from AE and though the files are roughly the same size the difference in image quality is obvious. If it will help I will find a way to post these videos for reference.

I really want to trust premiere, but now I don’t know what to think, are all of my square pixel premiere projects better off done in AE?

Any other ideas?

Again thanks a bunch.

[Alex Ezorsky]

I just bought an HVX200 and imported an MXF file into premiere from the VIDEO folder on my firestore FS-100. Premiere played the file fine and let me use it freely on the timeline. However when I disconnected the firestore the file went offline. Is there a way to have Premiere automatically transfer the necessary files (audio video XML etc) to a scratch folder so the video becomes native to my computer the way FCP does? What do you suggest?

Thanks

[Alex Ezorsky]

Thanks for the quick reply.

I tried cropping 1 or 2 pixels off the top and now I get even thicker black lines on the top and bottom. Any other ideas?

Thanks

[Alex Ezorsky]

Thanks for your reply,

However I am now sure its not due to time remapping and pretty convinced my Premiere is bugged.

Reasons:

It still does this with time remapping off.
It does it in a new project.
It does it somewhat randomly. If I trim the beginning of the clip then scroll back and forth a couple times then the entire clip will suddenly switch to having the attribute of the last keyframe.

Sometimes instead of having the entire clip solidly take the brightness value of the second keyframe it will flicker on and off and then stay on.

Does this sound like anything you’ve heard? Do you think a premiere re-install will help?

thanks

[Alex Ezorsky]

Arrgh, I too am getting this message. It seems that it’s only when I try to import H.264 files. The files play fine in QT whats the deal?????

[Alex Ezorsky]

For some reason when I try to import H.264 clips into compressor I too get this error message. Here is the info on the files which play fine in QT.

Dimensions: 640 x 480
Codecs: H.264, AAC, Timecode
Duration: 02:22
Total Bitrate: 1,148

H.264 was a problem for FCP and Compressor was supposed to be my solution, so any idea how I go about solving this problem?

Thanks.