Alpha Output with Media Encoder

Hallo
I would like to use the "Export to Adobe Media Encoder" command in After Effects to send a comp with an Alpha Channel to be coded in the Media Encoder, but this workflow doesn't seem to support Alpha Channels, or am I missing something? I am using CC2014
Please Help
Nick

You want STRAIGHT alpha in almost every case. Avid, FCP, PPro, AE and every other compositing or editing app I've ever used prefer straight alphas.
Create a custom template using, for example, QuickTime JPEG2000 and pick 32Bit like this.
You'll end up with a straight alpha QT that will work just fine in any app. If you must have pre-multiplied then you have to use the Render Cue and beware of the edges when compositing.
Here's the result of the test render in AE. Note the file interpretation and the transparency.
BTW, you can save the preset (I did) and use it at any time by adjusting AME's preferences.

Similar Messages

Can't Edit While Encoding With Media Encoder

Does anyone else get this happening to them:
When I begin the encoding process with Media Encoder, then go back to editing in Premiere Pro CC, EVERY time I hit the space bar to play a clip, Media Encoder Pauses its Encoding. Then when I stop playing the clip in Premiere Pro, Encoder begins encoding again. I'm fairly positive that Adobe touts that you can be encoding and editing at the same time, but I can't believe that this is happening. Anyone else?
Also, Encoder refuses to use my destination folder preference, instead targeting a folder I had used long ago and I have to manually target for every encode, every day.
THANKS!!!

Encoding is a real CPU/disc hog ... heh, it's an intensive process. Trying to both encode and playback in real-time ... um ... if you've got a rig with say four CPU's with 128GB RAM, two really hot v-cards that the Adobe program actually love to play with, and all programs/cache/footage/outputs on RAIDed SSD internal drives, you can maybe do both at the same time.
Think about what playback is doing ... it's not just playing the video off the disc ... not hardly. It's taking bits of video from this spot on the disk, skipping to this section of another video file there, to that one here ... and while doing that it's also immediately "reading" whatever changes you've made in editing, whether sound, size changes, color/grading, masks, EVERYTHING ... and applying that to the video it's grabbing of a disc somewhere AS it is playing it. Using a ton of CPU, disc read/write throughput, and probably a chunk of the v-card's GPU & vRAM. What's left for AME to use?
I've seen a lot of complaints around here as to why editing playback isn't smooth ... hey, in VLC, play that file, it plays back easy, what the * is PrPro doing?
Um ... VLC is playing the "straight" file, PrPro is playing back the file with all the other stuff added to it ... which isn't yet added to the file in reality, it's only instructions as to what to do to the file. So ... PrPro is essentially doing much the same work as when AME renders to an output simply to play the file in the program monitor.

Media Encoder CS6 with Media Encoder CC

Hi,
I have finally gotten Media Encoder CC installed. I still have Media Encoder CS6 on my computer. Can I uninstall Media Encoder CS6 without having problems with Media Encoder CC or any other CC apps? There is no uninstall optiion for ME CS6.
Thanks

Uninstalling Media Encoder CS6 shouldn't cause any problem to any CC apps, including Media Encoder CC.
There is no stand-alone uninstaller for Media Encoder CS6. In order to uninstall it, you need to uninstall all CS6 apps on which Media Encoder CS6 is depending. Those CS6 apps includes, Premiere Pro, After Effects, Flash, Prelude, SpeedGrade, and InDesign. Media Encoder CS6 is installed as a part of those apps. If you have any of those CS6 apps, please uninstall all of them. This also uninstalls Media Encoder CS6.

Premiere CS4 with Media Encoder CS5?

Hi,
When I was given my CS4 suite (production premium) years back, it included Premire Pro. Then, when I told my boss I needed to upgrade to CS5, he purchased the Web Premium Suite. This was fine, for the most part, as Illustrator, Flash, and Photoshop are the main programs I use, but we just recently got a video project that is giving me some issues.
We created what turned out being a 4 min + video. After some trial and error we settled on creating multiple segments in Flash and exporting them as uncompressed MOV files from Flash. Then we brought all of those MOV files together in a premiere pro project. The problem seems to occur when I export out an MP4 video from Premire Pro CS4. Premiere launches Media Encoder CS4 and then creates the MP4. The MP4 plays on a cellular device like we want it to, but it will not display a thumbnail/preview of the video when viewing the video in the phones gallery.
We have tried some other tests, and if we export out an MOV or AVI from Flash CS5 then convert that to an MP4 using Media Encoder CS5, there suddenly seems to be a thumbnail on the phone for the video. After multiple tests, it appears the problem might be related to which version of Media Encoder our final MP4 is produced in. ME CS4 - No thumbnail. ME CS5 - thumbnail.
The problem is, we HAVE to use Premiere as our final compiling tool, but I cant seem to get a Premiere Pro CS4 file to work with Media Encoder CS5.
Any thoughts???
Thanks,
Justin

but to automatically open up AME CS5 ... hmmm.. maybe a hack?
No, that will not work. Even if you have Audition 4.0 installed (beta), edit in Audition from CS5 will only access Audition 3.0.
The only way to try it is to open AME CS5, go to File/Add Premiere Pro Sequence and select the CS4 project and then the correct sequence.

How to output from media encoder to camcorder via firewire?

I am using CS5.5 media encoder to output edited hi def footage from premiere as DV widescreen to sony FX 1 camcorder via firewire.
How do I route the output from media encoder to the firewire output?
This is the same camera I use for acqusition & import into premiere via firewire.
Media Encoder appears to be encoding the footage properly.
Thanks in advance for any help.
Sewerguy

How do I route the output from media encoder to the firewire output?
You don't--or can't, rather. You'd need to use Premiere Pro for this. Check this help page for details: Exporting to videotape

Clips exported with Media Encoder from AE are choppy (CS6)

Hi!
I'm using Media Encoder (6.0.3.1) to export clips from AE (11.0.4.2) so that I can work with them in PPro (6.0.5).
In Media Encoder I go to add AE composition and I've tried the YouTube HD 1080p 25 and the Broadcast HD 1080p 25 presets (the latter creates a much bigger file but I don't think the file size is the issue - for example, the biggest clip of approx. 1 mintute is 276MB).
The curious thing is that most of the clips that are exported are fine, i.e. they play back fine - the problem is that some of the clips go slow or choppy towards the end of the clip. So the last couple of seconds will be choppy. It basically looks like the frame rate isn't quite right.
Once exported from Media Encoder, I import them into PPro to do some more work - the problem with the clips is apparent when I play the original file in VLC (for example) or in PPro. So it seems like the problem occurs during the export from AE. When I export the video containing the AE clips from PPro the problem is obviously still there (wishful thinking on my part). I use AE just for keying and making some basic titles, nothing massively complex.
I had some problems with RAM preview in AE before, in other words, it wasn't playing the clips back in realtime and the exported clips with the problem look exactly like that (i.e. looks like the frame rate isn't right). I deactivated Enable Disk Cache in AE (Multiprocessing was already deactivated) and now I can play back clips ok in AE using RAM preview - even the ones that go choppy towards the end when they are exported with Media Encoder play back fine in AE.
Could Media Encoder be going back to some previous render files saved somewhere on my system and could that cause some of the exported clips to go choppy?
I'm new to Adobe so I'm just guessing here and I don't want to go about and delete stuff that might not have anything to do with this problem. As I've adopted the computer I'm working on from my predecessor and it's had several users since, the system is a bit of a mess and there are files all over the place. Empting the Disk Cache doesn't actually delete anything for example.
I'm really stuck here because I can't finish the projects I started working on with AE.... I would appreciate someone's input!
Many thanks in advance!
My system specs:
Intel Core i7-3930K, 3.20GHz, 16GB RAM, 64-bit operating system, GeForce GTX 680, Windows 7, Creative Suite CS6
Before using Media Encoder to export clips from AE I was just relying on Dynamic Link between AE and PPro by the way and that made all of the clips choppy for the whole duration (this was before I solved the RAM preview problem and I haven't checked if a working RAM preview would make a difference to dynamic link). So Media Encoder nearly solved the problem. I posted this original problem on creativecow (http://forums.creativecow.net/thread/2/1045810) but no one has gotten back to me about the new issue unfortunately.

Thanks for your reply!
I tried using Quicktime with PNG and it created a big file (1.18GB for a 1 minute long clip) that doesn't play back nicely in PPro unfortunately. But I then tried rendering the clip using a lossy format, H.264, in AE and it's playing back ok in PPro! I will just do that for the rest of the clips and hope that this is finally resolved. Many thanks for the tip!
Out of curisoty, do you know what might be causing the problem when I use Media Encoder?

Problem with interlacing when exporting with Media Encoder CS 5.5

It seems that when exporting a Video with interlacing in Premiere 5.5 with Media Encoder 5.5, the exported video is still interlaced although it is rendered with progressive settings. When rendering with the same settings through Premiere 5.5 without Media Encoder 5.5 (Button "Export") it is correct and progressive.
I tried this with H264 and MPEG2. Anyone experiencing this problem too?
Thanx!

Were the field interpretted correctly in the first place? Even if you think they are, try reversing them. I've just been through hell doing something similar with a mishmash of client material from around the world.
In some instances I switched field order (In the File>Modify) although it didn't seem logical. In others, I used AE CS5.5 to added the Reduce Interlace Flicker filter.

Having troubles with Media Encoder CS6

Hello,
I am having the issue with Media Encoder where the it tries to connect to the dynamic link server for a long time and then ultimately fails with the message Could not read from the source. Please check if it has moved or been deleted. I have so far tried everything that I found online so far, that being uninstall and reinstall and creating the Premier shortcut in the Program Files (x86)\Common Files\Adobe\dynamiclink directory but nothing has worked. I am queuing the job from Premiere Pro CS6. I am not sure where to go from here and really need some help. This is on a Windows 7 machine. Thanks.

There are several different ways to add a Premiere sequence to AME, see if either of these alternative methods work for you:
Opt 1) Save your Premiere project, then drag your sequence from Premiere's Project panel and drop it into AME's Queue panel.
Opt 2) Quit Premiere but leave AME running. Drag your Premiere project file from the desktop (or wherever you've saved it) and drop it into AME's Queue panel. You should see an import dialog asking you to choose the sequence you want to import.

Is there anyone out there happy with Media Encoder?

After almost year of working with CS4 under both XP 32 bit and now Windows 7 64 bit, I am delighted with Photoshop and After Effects, tolerant of the defects in Premiere, and absolutely insanely angry about Adobe Media Encoder. I have spent a great deal of time following other people's posts and recommended "fixes." None have made the slightest difference in the ponderous performance and frequent crashing, especially when exporting AC3 files through Surcode.
I have tested this setup with no greater happiness on clean installs with NOTHING else on the computer but CS4 with all updates. These systems have all significantly exceeded Adobe's requirements for the software.
I have used in that time three different motherboards. I have worked with Premiere for years, literally since version 3. A have loads of experience optimizing computers for video. I also have lots of experience with other editing systems, having done in-depth reviews of NLEs for DV Magazine for a number of years. This is not to say that I have not missed something, but the consistent complaints I see reveal a critical lack of attention to the broken bits of this system.
I see lots of posts on this and other forums about the poor performance of AME. I see very few where anyone is happy with the software.
My current 2-hour project which loads into Premiere in under a minute can take 20 or 30 minutes to load in AME. Even when exporting only audio, AME appears to launch PPheadless and render all video frames before getting to the audio, and I have repeated issues with the program locking up when exporting more than 20-25 minutes of audio.
The decision to remove all direct exporting ability from Premiere and use the often broken Dynamic Link to AME was a gross mistake which in my opinion takes Premiere off the table for any professional shop. I do not do work for hire, but I cannot imagine explaining to a client who is paying by the hour why we have to sit and wait for fifteen or twenty minutes for AME to load the project that was already loaded in PP to just export a brief section. The architectural decision might be OK if all the bits that were involved were bulletproof and reliable, but the ImportProcessServer.exe and other dynamic link bits are clearly the source of problems for many people.
So here's my question: is there ANY professional end user out there that is happy with the current incarnation of AME and the decision to remove direct export ability from PP?

What format(s) do you work in? What length of project? Do you output to AC3? I have no problems with AME for short projects or to output the same size/format -- for instance, I can usually output full HD for Blu-Ray but experience lots of crashes if scaling down to SD for DVD. The crashes also occur above certain lengths, usually 20 min +. With audio, I can output 5.1 uncompressed WAV in the same format (for instance, 16 bit) but if I try to output 24 bit (which AME is supposed to be able to do) I get "Encoding Failed - Unknown error." In fact the error log is ALL that very helpful message, always when transcoding to another format/bit depth/size. When outputting 5.1 to AC3, AME freezes up and fails at around 20 minutes.
Our systems are very silimar -- the current system is i7 proc with 6gb ddr3 ram on a gygabite GA-EX58-UD3R.
A have not had any huge issues really with AME for short videos or output to FLV for web.
But the workflow I use is something that CS4 is SUPPOSED to be able to do. And the very unusual issue is that I have seen posts about the same type of errors (with ImportProcessServer etc) on Macs as well.

Problem Encoding WMV to FLV with Media Encoder CS4 (but not with CS3)

Hello,
I have been attempting to encode some WMV files with Flash Media Encoder CS4 (I have Adobe Creative Suite CS4 installed) but it has failed, generating this error:
- Source File: C:\Documents and Settings\usf\Desktop\incoming\ch01.wmv
- Output File: C:\Documents and Settings\usf\Desktop\incoming\ch01_3.flv
- Preset Used: Custom
- Video: 624x343, Same as source [fps]
- Audio: MPEG Layer III (MP3), 128 [kbps], Stereo
- Bitrate: VBR, 400.00 [kbps]
- Encoding Time: 00:06:36
5/28/2010 11:26:16 AM : Encoding Failed
Error compiling movie.
Unknown error.
On another computer where Adobe Media Encoder CS3 is installed (with Creative Suite CS3), I experience no such problem. I do notice that when I add the WMV to Adobe Media Encoder CS3, it opens a window that prompts me to use "ffdshow", which will apparently work if it's configured to decode the file. I click "OK" and start the queue in the encoder. A few minutes later I get a successfully encoded FLV file.
I have come to question whether Adobe Media Encoder CS4 should be re-installed, whether the entire Suite should re-installed, or if there is some patch or fix I can install somewhere. Adobe Media Encoder CS4 is installed on my "production" computer which also has Adobe Premiere Pro (CS3) and Adobe Premiere Elements (7).
Could use some advice here.
Glen
P.S. the files will also not export to FLV using Adobe Premiere or Premiere elements...

Again, the reason we are capturing with Windows Media Encoder is because we tried using Live Flash Encoder to capture directly into flash but our equipment wasn't fast enough and it was dropping frames all over the place. We also don't have the space to capture into an uncompressed format because we don't have the available storage, and our events can be 8 hours long or more (each video is about 15 minutes, 20 or more videos)
Ive listened to everything in my workflow and it sounds fine until the outputted FLV file from AME.
WME is capturing at the following specs:
160kbps 48KHz Windows Media Audio 9.2 codec (stereo) 1 pass CBR
1800kbps 1 pass CBR video
29.97 fps
640x360 resolution
buffer size: 5 seconds
key frame interval: 8 seconds
I have verified this with a codec info utility I ran on the wmv files.
AME is encoding with the following specs:
FLV Multiplexing
On2 VP6 codec
620x360 resolution
800kbps 2 pass VBR
100% undershoot at best quality
160kbps stereo MP3 audio
I verified the above with the same codec info utility (gspot 2.70a) and it is all acurate, it also told me that the audio is at 44.1KHz rather than 48 (there was no place to specify this, is this a limitatino of the VP6 codec?)
Yes, these are our source assets. They're being captured either through an XL2 via firewire, or from an analog program feed converted to firewire via a Canopus converter box.
If anyone has any suggestions on how to get rid of this, or a different encoder (either to capture with rather low cpu resources, or to encode into flash) let me know. I can provide a sample of the clipping if you need
Thanks,
Peter

Premiere Pro CS4 Export fails with Media Encoder CS4 "Encoding Failed"," Could Not Read From Source.

There has never been a history of Adobe CS3 installation on the brand new MAC Pro I am using prior to installing Master Collection CS4, despite other posts claiming that chief cause of this issue is a previous CS3, Beta or trial installations of previous versions. I simply had a straightforward installation of CS4 and have had trouble since day 1.
I have uninstalled and reinstalled Master CS4 three times, two times with the action script cleaner for CS4. I tried changing Adobe Cache folder locations to alternative drives. I ran shift start many times to correct any inconsistencies and corrected for permissions using disk utilities repeatedly. All updates have been installed and I am still getting the same error when exporting my timeline to Media Encoder CS4, be it a large High Definition project or a small one consisting of few stills.
No matter what presets I chose, the job appears as one of the items in the render qeuee of Media Encoder CS4 and sits there with the status WAITING until i hit Start Queue. When I do, it still says WAITING under Status and at the bottom corner of the window it reads : Loading "project name.prproj" and after an average of about 6 minutes, a yellow caution sign appears. No render whatsoever takes place. When I click on the yellow caution sign, it reads a log of all errors in connection with each job, including the ones that have gone before it. Here is one:
Start of the Error Paste
- Source File:/users/myname/Library/Caches/TemporaryItems/test.prproj
- Output File:/ users/my name/Documetns/Adobe/Premiere Pro/4.0/Sequence 01.mov
- Preset used :NTSC DV
- Video:
- Audio:
- Bitrate:
0 Encoding Time: 00:33:01
Sat Mar 21 17:12:25 2009 : Encoding failed
Could not read from the source. Please check if it has moved or been deleted.
END OF ERROR Paste
Please any gurus out there know how to troubleshoot this damn thing on Mac, I really appreciate it. I have not yet encountered any posts of Mac owners with no previous CS3 installation having this issue. I am in the middle of 3 projects with tight deadlines and need your urgent help. THANK YOU!

Hello There,
I resolved the issue through a simple process of elimination. So simple in fact I wonder how I missed it. Since there has been no history of prior CS3 installation on this machine and every conceivable trick was applied to resolve the problem (refer to my original post earlier in the thread) ending in frustration, the problem had to reside in a factor or series of factors that were only present in this machine. Of the two remaining causes different in compare to other machines, I had to look into the possibility of any hardware and/or software conflicts. After all, this very same installation works perfectly fine on my colleague's Apple Macbook Pro and several Windows machines.
It turns out that I had installed Pro Tools on this machine that comes with all kinds of optional plug-ins in the so called ignition pack. One of these optional plug-ins is called IZOTOPE (three varieties include Spectron, Trash and another one that escapes my mind). They were all lite version licenses that would automatically pop up on their own when you would start a program where they had been residing. One such program where an association existed was indeed the Premiere. An annoying dialogue box directing you to buy the full version when you would start the premiere would refuse to go away. Sometimes it would even start on its own culminating in a a permanent dialogue box.
The cause of the problem was right before my eyes and I had overlooked it. Once uninstalled using IZOTOPE clean uninstaller on step 4, the problem was resolved. Projects are now loading very fast into the AME and encoding begins in earnest. I have never had any issues ever since.
Long story short, if you have any plug-ins specially the ones that are loading upon the start of any program or the ones that reside inside the premiere or the ones that start on their own independently, they could be one of the highly probable causes of this error. I have seen other similar posts complaining of plug in folders inside premiere that needed to be moved to resolve the issue for instance the ones that needed to be moved to AE folders. If you are a plug-in admirer, I would suggest to look into them seriously.
On the side note, many combination and causes may lead to the same error. I am not claiming that this is the solution for everyone.
It must also be noted that I applied the trick of creating a shortcut of Premiere (and naming it exactly as such) and dropped it into the Adobe Dynamic LInk folder (even though this was suggested for windows)and have changed the adobe Cache locations to an alternative folder on a separate drive. I haven't been able to establish conclusively if the latter steps are also essential in fixing the error on MAC but I can confirm that since the latter steps were taken before the uninstalling of Izotope plug-ins and i still had issues, probably uninstalling those plug ins or finding a way to move them to a place where they don't interfere (if you absolutely need to keep them) is the one essential step that solved the problem.
Hope this helps.

Popping sounds when transcoding wmv to flv with media encoder

Whenever I use adobe media to transcode a wmv file created in windows media encoder to a flash file, I get pops in the audio track (similar to hissing bacon). The pops only occur during the begining of the video, when it's quiet and go away once the music or any loud noises begin. I did some research and found that it's a common problem when changing sample rates but the thing is that it doesn't happen on every conversion, and happens across multiple computers. We've tried it on Dell precision m65s (xp pro) as well as a Dell xps (vista 64bit) and a MacBook pro running xp pro in bootcamp. Here are the settings we use in windows media encoder: 1800kbps video 160kbps CBR audio at 48khz 640x360 resolution 29.97 fps keyframe: 8 seconds And here are the settings we use in AME: flv multiplexing on2 vp6 codec 2 pass vbr at 800kbps "undershoot" at 100% (quality: best) mp3 audio at 160 Kbps we have found that these settings work best for our cdm (brightcove) Again, it only happens at the begining of a video when it is quiet. Does anyone have any idea what could be causing this? Before anyone asks, the reason we don't capture it directly into flash with live flash media encoder is because the motion in our content causes the processor to peak resulting in dropped frames. When we get better equipment we will switch to live flash media encoder but until then we are stuck with windows media encoder. Thanks, Peter

Again, the reason we are capturing with Windows Media Encoder is because we tried using Live Flash Encoder to capture directly into flash but our equipment wasn't fast enough and it was dropping frames all over the place. We also don't have the space to capture into an uncompressed format because we don't have the available storage, and our events can be 8 hours long or more (each video is about 15 minutes, 20 or more videos)
Ive listened to everything in my workflow and it sounds fine until the outputted FLV file from AME.
WME is capturing at the following specs:
160kbps 48KHz Windows Media Audio 9.2 codec (stereo) 1 pass CBR
1800kbps 1 pass CBR video
29.97 fps
640x360 resolution
buffer size: 5 seconds
key frame interval: 8 seconds
I have verified this with a codec info utility I ran on the wmv files.
AME is encoding with the following specs:
FLV Multiplexing
On2 VP6 codec
620x360 resolution
800kbps 2 pass VBR
100% undershoot at best quality
160kbps stereo MP3 audio
I verified the above with the same codec info utility (gspot 2.70a) and it is all acurate, it also told me that the audio is at 44.1KHz rather than 48 (there was no place to specify this, is this a limitatino of the VP6 codec?)
Yes, these are our source assets. They're being captured either through an XL2 via firewire, or from an analog program feed converted to firewire via a Canopus converter box.
If anyone has any suggestions on how to get rid of this, or a different encoder (either to capture with rather low cpu resources, or to encode into flash) let me know. I can provide a sample of the clipping if you need
Thanks,
Peter

When I export the the F4V to a MOV with Media encoder, why does it loose all of the animation sync?

I need to turn the F4V file that Captivate outputs into a quicktime movie. However when I use media encoder (i also tried it with premeire), The final product is all messed up. The audio plays back in real time, but the video simply runs through the animations one after another, until they end, and then the mov cuts off abruptly. What is going on? How can I turn the f4v into a quictime movie?

If you sync an iPod automatically with an iTunes library, it will replace the contents of the iPod with the contents of the iTunes library.
Apparently, you had music on your iPod that didn't exist in your iTunes library. iTunes did exactly what it said it was going to do (remember that warning you didn't bother to read?)... it replaced the contents of your iPod (your music) with the contents of the iTunes library (your videos).
I'm sorry you lost your music, but this is how it has always worked.
Cheers!
-Bryan

Purging every frame whilst rendering After Effects project with Media Encoder?

SOOOOO.
I am rendering with ACCURATE anti-aliasing on Vector files.
This causes rendering to crash if I do not purge every frame.
IF
I want to render in background using Media Encoder,
CAN
I get IT to purge every frame also?
Does it follow the project settings?
Or is this a different preference in Media Encoder?
Thanks
Tris

> I never saw the point in multiprocessing either, why not just use all processors to do one frame at a time rather than splitting RAM and threads.
That is done, too. Different compositions benefit from different allocation of resources.
See this video for a demonstration of multithreading as well as Render Multiple Frames Simultaneously multiprocessing:
http://www.video2brain.com/en/videos-5355.htm
> Ditto Open GL rendering. why would you?
The OpenGL - Interactive mode is very useful. OpenGL - Always and using OpenGL to render for final output are seldom useful.

Issues rendering Premiere CS4 movie with Media Encoder

I'm new to this but thought that someone might be able to provide some insight. I have Premiere CS4 and created a movie from a HD video camcorder.
The imported clips are in the following format:
Type: MPEG Movie
Image Size: 1920 x 1080
Pixel Depth: 32
Frame Rate: 29.97
Source Audio Format: 48000 Hz - compressed - Stereo
Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
Average Data Rate: 1.3 MB / second
Pixel Aspect Ratio: 1.0
Now I'm simply trying to export the movie (Ctrl+M) using Media Encoder. I've been messing around with several different formats, including H264, MPEG and AVI and so far regardless of what output format I pick (even downsize) I'm getting some sort of "tearing" up in my clips. I'm not entirely sure how to describe this but it almost looks like a ghost effect with subjects leaving a ghost image when the scene starts moving around a bit.
I rendered the same exact clip using Windows Movie Market just for the sake of it and everything looks fine.
I'm rendering the clip on a Core i7 920 @3.7Ghz with 6GB of RAM so I don't think the speed is an issue as either (HD is a 300GB Velociraptor).
Any ideas what I am doing wrong
Thanks,
Sam

>Any ideas what I am doing wrong
Second thing wrong is posting in this forum. People in the Premiere forum will do a better job of offering help This forum is dedicated to helping people with suite-wide issues such as installation.

Alpha Output with Media Encoder

Similar Messages

Maybe you are looking for