Paul Budline
Forum Replies Created
-
Nevertheless, I may have some bad setting because I can almost not see the blue numbers and there’s no way this release would have been approved. I wonder if I might change some monitor setting or something like that.
Thanks again
-
Either my computer maker is a genius or I’ve been getting very lucky. He had me go into BIOS and turn up one voltage parameter by some small amount … encoding has gone very smoothly since then. Definitely hardware.
-
Apparently CS6 has a known issue with these files.
-
One more interesting wrinkle – I have PP CS5 on my old computer and ran a test. The files listed as “damaged” in CS6 imported perfectly. So it could be a PP issue.
-
Thank you very much – your suggestion gave me the idea to get the .AVI files onto my hard drive in a different way. So instead of using the computer’s built-in CF reader, I transferred from the Sony MRC-1 CF unit via Firewire. Put the files on the hard drive, tried to import into Premiere Pro, but the same thing happened – 8 of the 9 files were “damaged or unsupported.” And since I also have tried three different CF cards, I am wondering whether it could be that I’m using the 400x rather than the 133x that I usually use.
-
I have been working in a project that is serious HD – 1920 x 1080 – and the encoding time is lengthy. One or two times it finished and then I spotted an error in the encoding – it was really having problem with a still photo that was too large.
I suggest that you just check the encoded file, even if you do it in fast forward, to make sure there are no black holes in it.
I’m getting back to a regular 720 x 480 DV project today and I think the encoding will be much easier.
Paul
-
Two suggestions that seem to help: 1, even after the error message pops up and you click “don’t send,” wait for a couple of minutes. The encoder often starts again and may even make it to completion. 2, it seems a little better to start AME CS4 on its own, without Premiere even running. Then go to “add premiere pro project,” click on the one you wish to add, give AME a minute to find the project and its associated files, then go ahead and do the settings.
Regardless, this is a very annoying bug.
Paul
-
Thanks for your help. I should advise folks that encoder seems to work better when Premiere Pro is not running … I’m not sure if people know that you can add a project to encoder under CS4 without PP being active.
-
If I can call on your expertise one more time:
I took your advice and made a high quality, uncompressed 1920×1080 AVI from the 8 minute timeline … final size was about 73 GB. Using Adobe media encoder, I did a 2-pass VBR encode of that AVI, winding up with a 1.6 MB .m2v file. Do you think that will be superior to the 1-pass H.264 encode that resulted in a 1.3 MB .m4v file? The H.264 came directly from the timeline, while the MPEG-2 came from the intermediary .AVI file.
Lots of numbers.
Thank you again,
Paul Budline -
Thanks for that suggestion. I won’t often be working with material shot at full 1920 like this, but it still shouldn’t be happening.
And one question – what is the best way to export to a master-quality HD movie?
Thanks
Paul