HD output codec

What's the recommended output codec to play a digital animation directly from computer to a 1366 x 768 plasma TV. The animation will be in "animation" codec and edited in FCP HD 4.5. The final video will play to the public as a continuous 3.5 minute loop and must be of the highest reasonable quality.

The animation codec is not an HD codec...it is SD. To play out your footage, you need to either convert it to DV (yuck) and output it via firewire, or purchase a capture card (Aja, Decklink) and convert it to one of their codecs for output. 10-bit uncompressed is the best SD resolution.
But now you are talking high speed drives and capture cards. Big bucks.
You could also convert that to an HD codec... DVCPRO 720p, and have the ability to output via firewire, but then you need to rent the 1200HD deck that Panasonic makes.
Shane
"There's no need to fear, UNDERDOG is here!"

Similar Messages

Output codec

using premiere pro 6 what would be an equivalent output codec as Pro res 442? I want to output my video with a similar quality codec.

Stan, what is the ultimate purpose of the export? To be edited in another program? Graded?
You could export it to a visually lossless codec like Lagarith but the files would be HUGE!! Which might be fine if you are handing off a hard drive.
Or you could merely export it to something of the same approximate quality of the original footage. That might be less of a problem for you.
My choice for such things has always been to use the Cineform codec. It is a very high quality codec that uses a different method of compression than any of the other codecs. But the more info you provide, the more we could help you narrow it down.

Best PPCS5 output codec for import to FCE

Got a friend who's had trouble capturing from my XHA1 into Final Cut Express on his Macbook Pro. So I'm capturing using PProCS5 and I'm going to export the clips for him to edit on his FCE. I don't have any special codec packages installed, just the basics that come with PPro. What's the best output to give him for editing in FCE on his Mac?

...but all he needs is the sound.
You could have exported AIFFs then, and forgone the unnecessary bulk of even the DV MOVs.
You're probably a little limited with the built-in codecs for HD source when going from PPro the FCE. Yeah, you could do something like uncompressed/None, but those would be huge. I'm not positive, but a DVCPROHD MOV might work, even in FCE--yes, you do have that as an export option from Premiere Pro, and I'm not talking about P2 MXF. Those would keep the file sizes reasonable, and not apply too much additional, visible compression.
Another choice would be the Avid DNxHD QuickTime codecs; they're cross-platform, free, and look great. That involves an install on both machines (get 'em here), but that's pretty painless and offers great flexibility.

Media Encoder CS5 is missing a bunch of output codecs

I recently upgraded all my CS4 products to CS5. I'm currently running on XP64 and cannot install Premiere or AfterEffects. I guess Flash installs the ME CS5. When I open ME CS5 the only output options I get are FLV/F4V and h.264. I can input any file type. When I open ME CS4 all of the output options are available. Does anyone have any idea what is going on? Thanks.

I just ran into the same issue - all I need to do is batch convert wavs to mp3, and the only two options I get are FLV and H.264.
Does anyone know a workaround/way to get this added, so that I can at least output my audio? Should I download something like the "lame" codec for mp3? Would that even work?
I'm on a 32-bit system running XP with Adobe Design Premium installed (Flash, PS, DW, Illustrator, FW, Indesign, etc.) and Captivate. It's a new machine that has no other multimedia software installed...I would assume that a codec for mp3 audio would be included with this, but I know there are some legal issues with codecs.
What is the purpose of the ExporterMP3.prm file under C:\Program Files\Adobe\Adobe Media Encoder CS5\Plug-ins\common?
Thanks!

Video Converter Compatibilty Output Codec?

Hi Gang
Yes unfortunately I'm still in 10.4 which eliminates the capability to download any type of MTS converter software which I'll need to convert PAL to NTSC.
'ClipWrap2' and others are all designed for 10.5 or 10.6
Work Around: I also use a Dell PC with Windows 7. I found a program called 'Wondershare Video Converter Ultimate' which during the trail period successfully converted a piece, (watermarked), into a QT file. I then brought it over to my G5 and was able to open and play it in QT 7.6.4
Soon as I legally paid for and registered 'Wondershare Video Converter Ultimate', the newly converted files would cause QT and Streamclip in my G5 to Crash.
I tried converting to straight up QT as well as MPEG-4, same result ....
QT Inspector Window shows:
H.264
1440X1080
AAC Stereo 48kHz
FPS: 50
Data Rate: 8.84 mbits/s
Ummmm?
Any ideas?

Solution:
Fortunately, 'Wondershare Video Converter Ultimate' also provides a setting for converting HD to SD 720X480, and a nice feature of converting to 24P, (which matches my current project).
When I exported using these settings, I was able to get QT 7.6.4 to play the files without issue, and edit in FC6.
Thank you
Mike

I would like to know the list of possible output (export) file codec from FCP X. For example, can I export in F4V or FLV format?

I would like to know the list of possible output (export) file codec from FCP X. For example, can I export in FLV format? Where do I find the list, which gives me all the details about it? Or is there only one output codec? Thanks

That's an excellent analogy. While FCP cannot export FLV. It is possible to do a very simple substitution. If you export a QuickTime movie using the .mov suffix with the H.264 codec, you can change it to FLV simply by changing the suffix to .flv. This is an acceptable format for Flash movies on most web sites, if that's where you're trying to go.

How do I output the smoothest video when changing or mixing frame rates from the original footage?

I have been experimenting with various Media Encoder settings, and wondered if there was anything else I can try to get the smoothest video output possible, especially when changing frame rate and possibly resolution. For clarification, let me start from the beginning and explain what I'm doing and what I've tried so far. I'll try to be as brief as possible, but if I do go into too much detail, I apologize.
My original footage is AVCHD 1080p - 60fps. (my camera only does 60fps...specifically 59.94fps) We're not talking interlaced video here, I'm staying away from that. This is definitely full frame, progressive video at 60 frames (not fields) per second. My output will ultimately be for the web. I have been keeping my output codec (H.264) and bit-rate (VBR 2-pass, relatively high-bitrate) consistent, and have been trying numerous output options and even sequence settings to see what would yield the best results. I am using Premiere Pro CS5.5 along with Media Encoder. Here's what I've done and the results I've observed:
1. I created a sequence with 1080p - 59.94fps settings to match my original footage. I then output both 1080p and 720p versions at 59.94fps, and at 29.97fps. The 59.94fps output files looked absolutely great, as would be expected. Extremely smooth. The 29.97fps output files were generally smooth, but not near as smooth as the 59.94fps. This is expected since it's half the frame rate as my original footage. However, my question is this: What exactly is Media Encoder doing when "down converting" from 60p to 30p? From a technical stand point, is it dropping every other frame? I'm just curious to understand exactly what it does. I tried the Frame Blending option as well, and that only yielded a bit more blur to the images which wasn't desirable for any of the output files.
2. Just to see what would happen, I created a sequence with 1080p - 29.97 settings. I then output both 1080p and 720p versions at 29.97fps. The video was much more choppy in these cases, even with Frame Blending on. Now, I know not matching my sequence settings with my original media isn't ideal, but I again just want to understand why this yields less smooth video than the 29.97fps options above. Why does cutting the sequence settings frame rate in half from the original, then outputting the same frame rate as the sequence yield video that is not as smooth?
3. Next, I wanted to try mixing frame rates to see how Premiere and Media Encoder handled the footage and output files. Premiere handled it great, no issues there. However, I had some interesting things happen when I output the files. Here's what I did: I created a sequence with 1080p - 59.94fps to match my original footage. Then I took the same exact footage that was in my sequence, copied it in my project panel and interpreted it at both 23.976 and 29.97 fps, yielding slow motion video. The slow motion video looked great in Premiere, so I went ahead and just added it to my sequences, along with the original 59.94 footage. I also created separate sequences for the 29.97 and 23.976 footage respectively, each with matching sequence settings, then added a nested sequence to another original footage sequence (with 59.94fps sequence settings) to see which yielded the best results. Basically, I'm trying to output 59.94fps that match my original footage, but also throw in some slow motion footage at different framerates. I'll explain my results in a moment as they are a bit convoluted, however, here is my question: When mixing frame rates and trying to output the smoothest video, am I going about this the right way? I would assume you would use your sequence settings that match the original footage (which is what the majority of the footage will be), then bring in a nested sequence for the slow motion (as oppose to just dropping the slow motion video directly into my main sequence), and then output to the same frame rate of the majority of the footage, in this case 59.94fps. Is there a better workflow for this?
The results to #3 above were as follows. Initially, it looked like it didn't matter if I nested the slow motion sequence into my main sequence, or simply dropped the actual slow motion video into my original 59.94fps sequence. It seemed to produce smooth results either way. Frame Blending blurred the video a bit, but didn't seem to make much difference, and quite honestly I like the footage without Frame Blending in general. However, when I closed down Premiere, and opened the output files later (opening in Quicktime), the footage looked choppy. In fact, it would go from choppy to smooth and back, almost like it had an irregular cadence (don't know if I'm using "cadence" in the right context here). I would then open up Premiere again, import the output footage into my project panel, and play the footage in Premiere, and it would play back smooth again. Is this a Quicktime issue? I was playing 1080p 59.94fps files when this happened, so maybe it's just because it's a large file. Doesn't seem to have issues with the 720p files I created. But it sure threw me off with my testing because I then started second guessing the settings I was using. My iMac is the latest 2011 model with plenty of RAM, so I wouldn't think it's the computer. Thoughts?
4. Next, I noticed on ALL my output files (again, using the H.264 codec from Media Encoder) that the color of my video seemed to flatten quite a bit. It seems that the original footage has more contrast and saturation than the output files. I figured maybe this was just how it was, but when I re-imported the output files back into Premiere, they looked IDENTICAL to the original footage. And in Media Encoder's Source/Output windows, I don't see any difference there either. Is Quicktime again the culprit here, doing some odd things to the color of my videos?
5. Regarding Frame Blending, when is the best situation to enable this option in Media Encoder? I've read it is when mixing frame rates, but I honestly didn't see too much of a change except for a bit more blur, which I didn't care for.
6. Lastly, my conclusion is that 60fps yields the smoothest video, which is an obvious conclusion. However, I know that 60fps isn't the best or easiet frame rate for web delivery. It seems 30p is more the standard. Are there any integrated web players that would play 60fps? Can you get 60fps video on YouTube/Vimeo? If yes to any of these questions, can they do 720p and 1080p at 60fps?
Those are all my questions. I hope I am clear enough without being overly wordy and hopefully I didn't put too many questions into one post. Thanks in advance for any insight, I really appreciate it.

Did you ever figure out which output worked the best? I have the same original footage; trying to determine the best output settings to make a dvd for tv.
thanks!

Selecting codecs for HD

I was working on an HD project the other day. When I imported the first video into FCP It automatically changed my sequence settings to 1280x720 and the aspect ratio(dropdown) defaulted to 720p which was all good. However when I selected my output codec from the dropdown, I selected DV/DVC Pro NTSC. Is this what I should have selected or should I have selected an HD codec, possibly 720p to coincide with the aspect ratio. It looked fine. I saved this out as a 1280x720 HD Quicktime.
My questions are is FCP intuitive enough to pick up 720p and highlight it in the dropdown menu for codec selection?or if this is not the case how do you select the proper codec?
Has anyone found anything in a google search or a book that lists codecs and what and when to use?
Thanks
Jeff

Bookmark and download Flash from here, DO NOT trust any website telling you to install anything or follow their links.
Flash update
http://get.adobe.com/flashplayer/
Silverlight update
http://www.microsoft.com/silverlight/get-started/install/default.aspx
There is a FlashBack trojan making the rounds which tries to con people into installing it by looking like it's the real thing.
Make sure your Flash (and Silverlight) is current by running these checks
http://flashbuilder.eu/flash-player-version.html
https://www.mozilla.org/en-US/plugincheck/
You Mac likely will come across sites and content that won't play in Quicktime or in your web browser unless you install additonal codecs
You can get them here
Perian
http://perian.org/
VLC
http://www.videolan.org/vlc/download-macosx.html
Flip4Mac $29
http://www.telestream.net/flip4mac-wmv/overview.htm
How to install
When you click a link, a download of the installer file occurs to your Downloads Folder usually located next to your Trash Can or in your Users Folder.
Open the folder and double click (or File: Open) the download and icon can appear on your desktop which you open and inside is a installer package which you double click on to launch the installer.
OS X will check the download to make sure you intended to start it and that it's not malware it knows about.
Follow the installer instructions to install the software onto your computer and quit when finished.
Some require the browsers to be closed first, others require the machine to be restarted to enable the software.
Once the install is completed, remove any and all downloads from your Download folder, it's safer to keep this folder empty so you can keep track of what appears in there.
Drive by downloads of malware can occur and reside in the Downloads folder, mixing in with files residing there and await your click to install.
For backup, restore, performance and other tips I've got, read here
https://discussions.apple.com/message/16276201#16276201

How to set codec for Quicktime 7 export with AppleScript

Hello everyone,
I'm new to applescript and I'm having some trouble with a batch export of video files.
I'm trying to transcode several image sequences into .mov using QT 7, via Automator.
I found this code that works:
on run {input, parameters}
          repeat with theFolder in input
                    tell application "Finder" to set theSequence to first item of folder theFolder as alias
                    tell application "QuickTime Player 7"
activate
open image sequence theSequence frames per second 24
                              set nameSequence to (theSequence as string) & ".mov"
                              tell document 1
                                        with timeout of 500 seconds
save self contained in nameSequence with replacing
                                        end timeout
                              end tell
                    end tell
          end repeat
end run
The problem is that QT automatically sets the output codec as Photo - JPEG, but in this case I need Prores 422. Is it possible to set a different codec?
One other question: I'd like to set a name pattern for the file name. Right now, it picks the name of the image sequence (imag_seq_001.jpg.mov), but i would like to keep only the first part of the name (imag_seq.mov). And i'd need to do this for different sequences (imag_seq_002, 003, ...), using the same script. Is this feasible?
Thank you for your help.

I have a similar question as well. I tried this for you and nothing happened.
on received file transfer invitation theFileTransfer
end received file transfer invitation
I think "completed file transfer" is regarding to the file being transfered to Apple's Server from your computer when a file is sent, but I'm not sure about "received file transfer invitation." Regarding it being an inline file, maybe try using the attachment class.
attachment n [inh. rich text] : Represents an inline text attachment. This class is used mainly for make commands.
elements
contained by rich text, characters, paragraphs, words, attribute runs.
properties
file (file, r/o) : The path to the file for the attachment syn file name

AME takes a long time to start

Also, and maybe not super important to Adobe, because it IS only my time after all, but Media Encoder takes a blasted long time to load - like longer than AE. ya...

Actually, I just discovered it doesn't seem to have anything to do with OpenCL. I just put the rendering back to software only and it is doing the same thing. hangs for a long time before it starts to run. Activity monitor shows it running 85-95% CPU, 17 threads and about 615 MB of memory. Activity Monitor doesn't say its not responding, it just seems kind of idle. It took almost 7 minutes for it to start rendering.
1- Running version 7.2.2.29 of Media Encoder,
version 7.2.2 (33) of Premiere.
2- Yes, a premiere project of HD 1080 source shot with Canon 60D, output to H.264 YouTube 720, fps 23.976
not sure what you are referring to by native rendering. The rendering setting i tried now is Mercury Playback Engine Software Only if that is what you are referring to. But OpenCL gives me the same issue now.
3- H.264 YouTube 720, 23,976 - seems to happen on multiple output types
4- In Premiere, I have my project timeline window selected. Command-M, selected the output location I wanted and what output codec, selected submit to Queue. Media Encoder comes up, the project loads and I select the run icon. It preps and shows the encoding process setup in the "Encoding" window, then just sits there with no "Elapsed" time occurring until almost 5-6 minutes later, then it kicks in.

AME takes a long time to start encoding when using GPU Acceleration (OpenCL)

Have had this issue for a while not (current update as well as at least the previous one).
I switched to using GPU Hardware Acceleration over Software Only rendering. The speed for the actual encoding on my Mac is much faster that software only rendering. However, more often than not, the encoding process seems to stick at 0% waiting to start for a long time, say anywhere from 1 minute to several minutes. Then it will eventually start.
Can't seem to find what is causing this. Doesn't seem related to any particular project, codec, output format or anything else I can see. I'd like to keep using GPU Acceleration but it's pointless if it takes 5 times as long to even start as rendering by software-only would. It doesn't even pass any elapsed time while it's hanging or waiting. Says at 0 until it starts. Like I said, once it starts, it's a much faster render than what the software would take. Any suggestions? Thanks.
using an iMac, 3.4Ghz, 24GB RAM, AMD Radeon HD 6970M 2048 MB

Actually, I just discovered it doesn't seem to have anything to do with OpenCL. I just put the rendering back to software only and it is doing the same thing. hangs for a long time before it starts to run. Activity monitor shows it running 85-95% CPU, 17 threads and about 615 MB of memory. Activity Monitor doesn't say its not responding, it just seems kind of idle. It took almost 7 minutes for it to start rendering.
1- Running version 7.2.2.29 of Media Encoder,
version 7.2.2 (33) of Premiere.
2- Yes, a premiere project of HD 1080 source shot with Canon 60D, output to H.264 YouTube 720, fps 23.976
not sure what you are referring to by native rendering. The rendering setting i tried now is Mercury Playback Engine Software Only if that is what you are referring to. But OpenCL gives me the same issue now.
3- H.264 YouTube 720, 23,976 - seems to happen on multiple output types
4- In Premiere, I have my project timeline window selected. Command-M, selected the output location I wanted and what output codec, selected submit to Queue. Media Encoder comes up, the project loads and I select the run icon. It preps and shows the encoding process setup in the "Encoding" window, then just sits there with no "Elapsed" time occurring until almost 5-6 minutes later, then it kicks in.

Adobe MEdia Encoder Crashes with big files inputed

Hello,
There isn't a forum for the Adobe Media Encoder, so I thought this would be a good spot. I am an after effects and Premiere user who likes the idea Adobe seems to have of using the media encoder to cover all my encoding needs.
My typical workflow, especially since these days I'm doing more shorter form animations, is to render out to a Quicktime Animation codec file as my main archive file. From there, output all the various different web versions, flv, etc from that core archive file. Since my projects usually aren't running more than 5 minutes, this leaves me with a nice 3 - 7gig file.
Problem: I'm running CS4 and the media encoder crashes when I input files that are in this file size range. The program locks up when I push start que, and then eventually crashes. Works fine with smaller size files that are about under a gig.
I can run a render out of after effects, which seems to be more stable. But I'd love to be able to use this great new tool.
Here's my machine specs if it helps:
PC
Intel Quad Core Q9550 @ 2.83 ghz
4gB RAM
Windows Vista 64 bit ultimate
All updates current for CS4 apps as of 01/30/08
Running Adobe Media Encoder V 4.01.078
Hard drives are nothing special. 7200 rpm western digital internal and external. I've tried all sorts of hard drive configurations, where the input is coming from, where it's going, etc. No difference.
I have been experimenting with using Lossless AVI's as my "uncompressed" archive file. Works well, but same crashing with the Media Encoder.
Also tried experimenting with frame size alterations during encoding, no difference there. Also, whatever the output codec is, be it FLV, H264, etc. no difference.
Anyone have any thoughts or have experienced similar issues? I hope all my MAC friends aren't right, seems like all my attempts to streamline my workflow with this CS4 and beefy PC combo are crashing and burning.
Anyone else feeling this pain, or have recommendations?
Thanks,

Thomas, thanks for your suggestions on Vista optimization. That Sheer Codec looks nice, but hard justify the cost when I've been working for years with essentially uncompressed codecs that work well. Will play more though to see if the cost would actually pay off in the long run though.
In general I made a decision that it was too early to throw in the towel on my old uncompressed codecs. The Quicktime animation codec has always been for me the safest, most universally accepted, and most reliable "uncompressed" codec. It's always worked in the past, not gonna give up just cuz media Encoder CS4 has troubles.
Mylenium, thanks for the reminder about the silly platform wars. I've always felt the same as you, but when I'm stressing sometimes the silly propaganda can get to me. Makes me forget that no matter what system ya got, it never works perfect!
Here's an update. I have trying my best to learn more about the bug and have come to some interesting realizations. The AME does work with larger files, just not the larger files that I had been using at the current moment. Older files of mine as big as 20GB can be inputed into AME with fine results.
This being said, it scratches out most of the RAM overload thoughts with AME.
The difference with my current files that were causing AME crashes: larger than a few GB, came from AE, had the 1.21 pixel aspect ratio metadata.
When I re-interpreted the file in AE into a square pixel aspect ratio, exported it, it was then successfully inputed into AME.
I have read just now that there were changes in After Effects widescreen pixel aspect ratio interpretation in CS4. Can this change be causing problems in my AME. Not positive, but I'm now thinking after many days of testing that the bug could have its roots somewhere in this ball park.
If anyone from Adobe is reading this, I would love any ideas you might have on this issue. In general, there is really no support for the Adobe Media Encoder itself. This is not good, considering how it is so necessary for AE and Premiere users like myself.
Thanks,

File size extremely high for .avi after render PE 9

I'm very new to PE and have tried to learn quick to redact info (faces etc) in .avi files for a government agency. I was able to open the file (in the trial version) and make the track matte by dragging the original file to the timeline then dragging it again to the video 2 timeline for the top layer, Question 1) is this the same as copy and paste or am I doubling the size already? Anyway, I was able to get the matte and everything done. Now, to Render and save... I choose computer/avi again (I need to keep it the same) and it took 1 hr 45 min to render it, that seemed long to me but maybe not... but mainly the file size was then 100,883 kb! Starting with a 29.7 kb file. This is what my question is about....could this be right? I can't use it if this is what I get. So, here are the particulars as I got G-spot and looked it up, as per serveral suggestions I saw here. I'm trying to understand the CODEC info but I fear I have a ways to go before I can figure out what I did wrong. (This is my test computer, the future work would be done on a newer, better computer). The videos I would be working with come from various sources and will vary in length but will probably all be a kind of avi.
Intel Pentium processor 1600 mhz
221 mhz, 2.00 gb ram
Microsoft windows xp sp3
video:
length: 0:27.261
frms: 817
Kbps: 28770
pic: 720x480
codec: dvsd dvc/dy
I appreciate any help you can give

Thanks for you response and the information was very helpful. I was able to choose and output that gave me a good file size and I do want DV-AVI (I don't remember what I chose but it worked) but, I don't see an option for DV-AVI - is that a general DV output selection, because there seem to be numerous (AVCHD, NTSC, DV STANDARD) acronyms (I have tried to understand what each is) which do I want?
From: Bill Hunt <[email protected]>
To: Mid Century Modern <[email protected]>
Sent: Wednesday, September 28, 2011 6:07 PM
Subject: File size extremely high for .avi after render PE 9
Re: File size extremely high for .avi after render PE 9 created by Bill Hunt in Premiere Elements - View the full discussion
For the use of Track Matte Keying, with say a Gaussian Blur, or maybe Moasic Effect, if you have not altered the In & Out Points, then just dragging the Asset to both Video 1 and Video 2 will work fine. If you HAVE adjusted the In & Out Points, you can just click-drag from the Source Monitor, where you set those In & Out Points, and all is good. The Copy/Paste is just another way to do it.
As you are doing an "overlay," the output File Size will not be affected in any way. You are also limiting the Blur, or Effect on Video 2 to just the area "exposed" by the Track Matte, so the pixel count will not be altered.
As Steve points out, the output CODEC in the AVI will determine the output File Size. File Size is basically determined by the Timeline's Duration and by the Bit-Rate of the output file. With DV-AVI, that Bit-Rate is pretty well set, and your Timeline determines the Duration. At ~ 13GB/hour, a DV-AVI will be pretty large, but that is the nature of the beast. Also, and as Steve points out, if you are going to do additional editing, and will be Importing that file into a New Project, DV-AVI is about as good, as it gets.
Good luck,
Hunt
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/3943683#3943683
To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/3943683#3943683. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Premiere Elements by email or at Adobe Forums
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

Random Artefacts with AVCHD/Mpeg Footage

Hi,
I have an issue with rendering an edit that contains .m2t clips (Windows explorer says they have AVCHD-Codec). I'm editing with Premiere Pro CS 5.5 on a Windows 7 Home OS.
The footage is HD 1920 x 1080i25. A recording of a live perfomance of a band on a music-stage.
Everytime I export the project-sequence to various formats (Mpeg2, Mp4, WMV) I get these artefacts/glitches on the finished clip. They are also occuring when editing in Premiere.
It's only affecting the video, the audio on the other hand is fine. They look slightly different after each render-export process and depend on the output-codec. But they always appear at the same point of time. The artefacts last about 3 to 10 frames each time and sometimes only parts of the image are affected. For example: a horizontal bar (let's say 1/10 of the image) pixelating the image and blurring the pixel or giving parts of the picture a ghosting look.
However the raw footage is alright and contains no glitches or video artefacts. Plus they didn't appear right of the bat after importing the footage into Premiere. It took some time before the first glichtes arrived. Approximately after 1-2 days of editing.
I tried watching these exported clips in different players. But always got the same result. Mostly the artefacts appear right after a cut in the video. None of the affected clips have effects or changes applied to them. However I managed to eliminate artefacts of some clips by adding effects or changes (eg. scale value 1% up, adding brightness/contrast effect, or just changing the field dominance) to the affected clips and deleting them again, to make Premiere render the clips anew. Since the clips are neither yellow nor red in the timeline.
My sequence settings are set to video-preview: "I-frame mpeg only" and 25fps timecode.
I hope for some help around here.
Is it Premiere's render technique or settings that are to blame?

This is certainly not normal or a missed setting. Try this:
1. Open PP and create a new empty project.
2. Go to Edit>Preferences>Media and take note at the top of where the Media Cache files are stored on your system.
3. Below that, Clean the Media Cache Database.
4. Close down PP.
5. Use Windows Explorer and delete the Media Cache files you located in step 2.
6. Restart PP and open the project. Wait for file processing to finish.

How many CS Increments will it take to handle ProRes Correctly

Two Simpleton-tests with AE 5.5 revealing that AE still hasn't learned a darn thing in regards to the ProRes Codec
Test 1:
1) Import ANY Canon 5DMKII into AE CS5.5
2) Add it to a new Comp
3) Add that comp to the render queue
4) Select ProRes 4444 as output codec
5) Render and compare with your original Canon Footage
Expected Result in the Quicktime Player 7:
The ProRes File Should look somewhat like the original.
It does NOT.
Actual Result
Gamma is WRONG
Color is slighty shifted
And Noise/banding has been increased significantly.
Test 2:
1) Open Apple's Compressor
2) Import the same Canon File
3) Setup a 4444 Codec like in AE
4) Render out
Expected Result in the Quicktime Player 7:
The ProRes File Should look somewhat like the original.
It does.
Actual Result
ProRes transcode looks 100% identical to the source
Test 2 Expanded
Import the Compressor-created 4444 file into AE and repeat test 1
Expected Result in the Quicktime Player 7:
The ProRes File Should look somewhat like the Compressor-Created file.
It does NOT.
Actual Result
Gamma is TOTALLY WRONG
Color is LESS shifted than when exporting the Canon file directly
Noise/banding is MORE than the compressor created file but LESS than when exporting the canon file directly...
I am more or less speechless. I have been reading about this problem on a million blogs. Including adobe's own.
Since at least since CS3. There have been several invain work-arounds. And now this. CS 5.5 - with the same problem.
Adobe, how many versions do you need to get it right.
Perhaps, you could look a little a Apple's technology, as it seems to be much more effective and advanced than yours.

Hi Rick,
first things FIRST ;-)
Thank you very much for taking the time to make that post.
My color settings in AE are correct. And I am using a color managed workflow -)
It plays NO PART whether I enable the "Use Legacy Gamma"....
Your example is correct in BUT it only applies to the realm in which you created it > RGB
and it does not exhibit temporal H264 artifacts stemming from a YUV 4:2:0 (609 Color Space) Matrix
You dont exaclty round-trip the way that I was describing a rountrip in my initial post.
I know that a ramp can reveal certain things but it is a highly virtual comparison and does not really apply to live-worl footage.
At least in this case ;-)
You take RGB-generated grays and then output to ProRes
I took a YUV-color-realm movie entered into the realm of RGB (AE) and then exported to ProRes
And THAT is where the problem lies.
I am uploading the file in question. It is a movie from the 5DMKII.
That is the source I have been testing with all along.
It is great in that it has a dark area with quite a bit of noise. THAT noise after AE has encoded it to ProRes will look banded and become worse.
Not so when encoding with Compressor.
Besides, and this I cannot wrap my head around, when compressor is compressing the exact same file it is 295MB in size but when doing it with AE it is 413.
Something wrong there ?
Anyway, here is the link to the file if you wanna try with that.
I am uploading a screen shot to show you which area you should look out for.
And rememeber this is NOT visible when looking at it in AE. you HAVE to rountrip and open the source and the rountripped file in the Quicktime Player.
Remember, most folks are WATCHING the movies in the quicktime player on OS X... So I would LIKE my files looking identical to the source when watched in the QT player. I dont believe that any consumer out there, just aiming to watch a movie has AE installed so that he can watch the movie in the way I (all AE users) intended it to look.
Adobe we NEED this to work.
When/if you do the test - make a real world comparison.
Open the Original source in AE and out-encode it to PR4444.
Then open the quicktime player and load up both (PR4444 and ORG source)
Put them on top of each other and flip back n forth. Huge difference in the area that I have hi-lighted in SS below.
The noise in the original is very present in the original file in that area...
When looking at adobes encode the noise has become large square fields(almost) looks a little like banding.
When using Apple's compressor to rountrip it looks exactly like original.
Might I add, taking the original file and opening it directly in AME (bypassing AE altogether) will have the same impact on the file
as when exported directly from AE. So it seems as if adobes Quicktime encoding framework has a bug altogether. I tried all of this with the
cineform codec as well. When using adobe to encode to cineform it displayed the same artifacts.
Original Source Footage Download
Screenshot of area to look for

HD output codec

Similar Messages

Maybe you are looking for