CS4: Media Encoder - Black Bars of Doom

I dont see a forum for the Adobe Media Encoder so I'm sorry if this is the wrong place for this.
I have the CS4: Design Premium. Everything is updated so the encoder is at verson 4.2.0.006.
Now when I have some video dont for NTSC TV 720x480 (left) and I rendered (right) it using the same as source preset (9.0 or higher) and I get this big black bar on the right side of my video. I've played with the settings and resizing the video and I always get these black bars, usualy on the right and bottom of my video.
secreenshot of the .mov next to the .f4v: http://oniring.com/ame.png
This is really not ok. I can go back to using CS3 to render my videos but they dont look as good, but I dont get a big black bar on them either.
I cant seem to find any solutions with this when I do a google search.
How do I get rid of these black bars?

i have had this happen too. why is a mystery. i still cant find out why its happening. I crap solution is to make the video bigger and i Mask it in Flash. i hate Media Encoder.

Similar Messages

CS5 Media Encoder - black bars of DOOOOOM

Hi Folks,
Need a little help from my Friends:
When I put a 720 x 576 .mov file through the video encoder, it's got black bars on the left and right of the actual video. I've got a feeling that Adobes Encoder doesn't particularly like anything other than a video with an Aspect Ration of 16:9. Anyone know a fix for this?
Also, if the clients videographer cannot provide me with a 1024 x 576 .mov (16:9) file instead, is it possible for me to get his 750 x 576 down to the required size of 512 x 288?
Any help on this, appreciated.
Kind Regards,
Boxing Boom

I'm pretty sure you can export to any dimensions, but this is nothing to do with AS3 so please post it to appropriate forum

CS4 Media Encoder doesn't render Quicktime at all

The CS4 Media Encoder will render H.264 and FLV, but doesn't render any form of Quicktime at all.
The Queue loads the project, pretends to render, but does not show progress frames. Seconds later (way too early!) there is a green checkmark that the render completed successfully. The log file looks successful with essentially the same content as for H.264 and FLV.
For example this log file shows a 1-minute sequence "rendered" in 30 seconds -- normally takes 3 minutes -- and no .mov was created.
10/29/2008 7:09:16 AM : Queue Started
- Source File: C:\DOCUME~1\MARATH~1\LOCALS~1\Temp\happyValleyBeijingMoreHighlights_5.prproj
- Output File: C:\Documents and Settings\Marathon Runner\Desktop\china\finished\happy valley beijing\more highlights\Sequence 01.mov
- Preset Used: NTSC DV
- Video: 720x480, 29.97 [fps], Lower, Quality 100
- Audio: 48000 Hz, Stereo, 16 bit
- Bitrate: DV/DVCPRO - NTSC
- Encoding Time: 00:00:00
10/29/2008 7:09:45 AM : File Successfully Encoded
10/29/2008 7:09:46 AM : Queue Stopped

>always save the project before you export
Very good advice.
I would also say, save your project after any edit that you feel you can't afford to lose.
Cheers
Eddie
PremiereProPedia (
RSS feed)
- Over 300 frequently answered questions
- Over 250 free tutorials
- Maintained by editors like
you
Forum FAQ

CS4 Media Encoder

Like many others, I have encountered a problem with CS4 Media Encoder upon start up. It quits unexpectedly.
I have a Quad-Core Intel Xeon Mac running 10.6.2.
Here are the problem details if someone understands it:
Process:         Adobe Media Encoder CS4 [299]
Path:            /Applications/Adobe Media Encoder CS4/Adobe Media Encoder CS4.app/Contents/MacOS/Adobe Media Encoder CS4
Identifier:      com.adobe.ame.application
Version:         4.1 (4.1)
Code Type:       X86 (Native)
Parent Process: launchd [113]
Date/Time:       2009-11-10 23:49:32.541 -0700
OS Version:      Mac OS X 10.6.2 (10C540)
Report Version: 6
Interval Since Last Report:          24036 sec
Crashes Since Last Report:           10
Per-App Interval Since Last Report: 505 sec
Per-App Crashes Since Last Report:   9
Anonymous UUID:                      9203213B-94A6-4772-A9E6-EFAC9F6ED5DE
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000c276e1a8
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
I have tried removing the ".pref" file without improvement. On another thread there is mention of removing an "Watch folder info.xml" file, which I can't find on a Mac.
Would appreciate any help
Kurt

Me too. Sometimes it works. Sometimes, even the smallest file will crash the ENTIRE COMPUTER and it will force restart itself. I have tried it with h.264 and MPEG2-DVD, and both have crashed it.
I thought it might be overheating my MacBook Pro, so I have been watching the temperatures. The CPU gets almost to 200f. The process viewer shows encoder process average around 167%.
It is unfortunate because when it does work, it actually makes very pristine encodes.
I also tried updating the licensing through a FLEX update, as the console was reporting the same message over and over again. That message has stopped, but the crashing has not.
My fans run constantly when watching training videos on Adobe's site, and the computer never crashes. So I assume it is not a heat problem. That said, I don't know whether the CPU or the GPU are responsible for video playback. In other words, if the GPU does playback, and the fans go on, it isn't getting hot enough to shutdown. If the CPU does does playback, and is causing the fans to go on, I would think that the computer would shut down just as it does when Media Encoder is encoding and causing the CPU to get hot.
At this point my hunch is that Media Encoder is causing some sort of kernel panic, causing the computer to restart. But this is just a stab in the dark.

CS4 Media Encoder Presets

Does anyone know if CS5 Media Encoder Presets are compatible with CS4 Media Encoder?
http://blogs.adobe.com/ktowes/2010/10/new-encoding-settings-for-multiple-screens-using-ado be-media-encoder-cs5.html
Thanks

The solution! :)
Now I only have one of these two folders containing all presets. The "other folder" is a symbolic link to this folder using this tool:
http://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html
Now it doesn't matter whether I am defining a preset in Premiere or in AME. It works fine!
Carlos

Premiere CS4 & Media Encoder CS4 didn't work..

i just install Premiere Pro CS4 & Media Encoder CS4..
i finished editing my videos in Premiere, but when i want to encode it in Media Encoder, it says "please verify that adobe premiere is installed in your computer"..
what should i do?
tnx..

Welcome to the forum.
Do you have the full-paid version, or the trial?
It sounds like your installation is not complete, or has become corrupted. This is a general CHECKLIST for installing most Adobe programs. Look over it, to see if perhaps you missed something.
If you did everything in the checklist, then I would attempt a Repair Install. Did you install from media, or from a download?
Good luck,
Hunt

Pro CS4 Media Encoder vs Sorenson Squeeze Quality?

Guys,
When outputting a video to Flash (for this discussion, let's assume Flash V8, medium size.....with the Web as the target audience), does anyone have experience using both PProCS4 Media Encoder and Sorenson Squeeze---being able to comment of the quality of each? Is CS4 Media Encoder doing as good a job (apples to apples) as Sorenson Squeeze would do? For general info, they want SD video in 4:3 ratio.
I've want to provide the best quality video I can to a client who is selling web training for a professional methodology. They are using video to provide additional visual support to their audio segments.
TIA,
jd

I purchased Squeeze after the release of CS4, the Adobe Media Encoder was fine in CS3. I noticed after installing CS4 that the end product (usually Quicktime, AVI, Mpeg-2 DVD and BluRay for me) was soft and fuzzy. I dug around various forums and found that many had this issue with the AME in CS4 and saw Sorenson Squeeze highly recommended. It should be noted that I use a Matrox RT.X2 card with my CS3 and now CS4 environment. I now export out an uncompressed i-Frame Matrox AVI and bring it into Squeeze and it works great.
I am finding the same issue in a non-Matrox project. We are doing a spot now that was shot in DVCPRO-HD. The image is gorgeous in PP, however when I use the AME, the resulting file is soft and dull.
Question to anyone who can help. In a non-Matrox project, what can I use to get it into Squeeze? With my Matrox projects, the uncompressed Matrox export bypassed the AME and gave me a clean image to bring into Squeeze. In my current non-Matrox DVCPRO-HD project I tried uncompressed AVI but it reduced my size to 720x480, and it reduced the quality. How do I get my footage out of Premiere and into Squeeze without using the AME?
Thanks,
Marty

Does The New CS4 Media Encoder Seem Slow?

I selected some B-Roll that was shot in P2 1080i and brought it into a standard definition project. I scaled it to about 44% and sped up one timelapse segment by about 900%. The resulting length was about 8 minutes.
Transcoding this 8 minute sequence into 720x480 NTSC With the CS4 Media Encoder is taking over 3 hours! This is on a system with an Intel Q6600 processor.
Has anyone else noticed that the new Media Encoder seems slower? I don't think it uses existing render files like previous versions of Premiere.

"DV project. If you have three clips AND THE 2ND ONE is color corrected then you do a 'preview render' that 2nd clip is rendered to dv so it will play real time in your timeline. Then when you render out to DVD clip 2 is rendered yet again to Mpeg-2. It has been rendered twice, it a second generation image unlike CLIP 1 AND 3 WHICH are still first generation before the Mpeg encoding"
Sorry typing faster than my brain. Sorry trying to get work done and help people got the better of my fingers brain. The above is corrected with the corrected in CAPS.
In a nutshell when you use preview files your telling the computer to use files that have already lost a generation to make your edit faster.
If you edit DV the preview renders the effect (or whatever) to whatever is set in the sequence files. So a new DV file is made, which is rendered into an MPEG (or quicktime, Blu-ray whatever).
"But if you are saying that re-render renders the already rendered preview clip, I believe that you may be in error. I thought re-render ignored the previews and looked to the source file(s) again. Am I wrong?"
Yes your wrong because your assuming the preview render was done in the format your outputing in AME. If re-render 'ignored the previews and looked for the source file(s) again' there wouldn't be any render to 're-render'.
The Preview render renders a new file based on your media codec (dv to dv, HDV to i-frame. dvcpro to dvcpro). It has no way of knowing what your final setting in AME are going to be. So preview files are double rendered.

Windows 7, CS4 Media Encoder freezing and crashing upon clicking "Start Queue" - every sequence!

Windows 7, CS4 Media Encoder freezes when queue starts with sequences from Premiere. However, sequences opened from Media Encoder's "Add Sequence" export fine. Have re-installed (without first un-installing), issue is ongoing. I have several important deadlines fast approaching, please help! Media cache has been cleared (both automatically and manually), computer has been defragged and scanned for disk errors... I am absolutely stumped!

I've checked the anti-virus (I didn't think of that!), but it doesn't seem to make any change.
I've had Window Task Manager running while trying to export, it would seem that the problem occures when PProHeadless.exe opens. If I manually close it right before clicking "Start Queue", AME doesn't freeze until PProHeadless.exe re-starts once more.
Any information on forums regarding PProHeadless.exe seem more to do with an error message, not that the application itself is causing problems. I've tried multiple different sequences, all with different footage, different types of files and all with the same result.
Would a complete reformat or Windows and CS4 be the only answer? I dread the thought but I'm getting desperate.

Adobe Media Encoder CS4 Suddenly Adding Black Bars To L & R

I think I may be going crazy.
Every video I have ever shot has been cropped to 720x340 in After Effects then exported as an uncompressed Quicktime movie file at 720x340. For the last year I have done this process exactly the same everytime.
On my website (www.stevenbogda.com) videos are either 360x170 or 480x226 FLV files, both variations of the original 720x340 Quicktime file. I would just bring a 720x340 file into Adobe Media Encoder CS4, adjust the dimensions and bitrate and export and it would work perfectly. Now all of the sudden, when I bring anything I shot and exported recently into AME CS4 to get it ready to go on my website, it adds BLACK BARS to the left and right side of my video (refer to image 2).
I thought it was just a visual problem in AME CS4 until I exported it as the FLV file that I planned on doing, just to find that the actual FLV file is in fact the dimensions I wanted, EXCEPT it has black bars on the right and the left...
I immediately blamed it on After Effects and started re exporting uncompressed Quicktime files with different settings and managed to get AME to work properly but it was random. Some videos were exported with "settings 1" and worked in AME but other videos with the same settings didn't work.
I went to my hard drive where I store my master Quicktime files that were used to make the videos on my site and brought some into AME CS4 and they acted the same way that the new videos I made do, with black bars on the left and right. These videos worked the way I wanted them to in AME CS4 last month, but now suddenly are doing what my more recent files do and I have no idea why.
I found out that by lowering the width of the video (refer to image 3) the black bars would dissapear slowly, but then the video would be a smaller width that it should be. I really think I am just missing something, or set some setting wrong by accident because this never used to happen and now is happening with files that once worked correctly.
Any help or ideas would be greatly appreciated because I am spending way too much time re exporting uncompressed files just to find out they don't work.
Thank you,
Steven

Stan,
I was using the on2VP6 codec at data rates from 275k to 400k with good results. -- with the new CS$ endcoder i am used h.264 at 500k to 700k, video quality looks good but the graphic overlays look like alised crap. In the encoder settings the edges of the graphics get jaged when I make the field order progresive...
I am starting with DV NTSC video at 720x480.
I am going to go back to my old work flow and test it. The settings are a bit different from premiere pro 1.5 to CS4 -- in 1.5 i could export out an unconpressed .mov with square px and then bring that large file to flash media encoder to create the .flv

CS4 media encoder crashes if On2, 2 pass selected

Hi,
I have tried this with several .mov files of different sizes,
both in pixels and in duration. (from 6 minutes to 5 seconds)
When I encode to F4V everything is fine.
When I encode to FLV with ON2 and 1 pass everything is fine.
When I encode to FLV with ON2 and switch on 2 pass the
progress bar stops at the half way point for a while and then Media
Encoder closes. A zero byte file is left in the directory.
I am using CS4, on windows XP. I have downloaded all updates
for my Adobe products. I have restarted my computer. None of these
things make any difference.
It crashes every time with 2 pass on.
Addition to post.
I have now reinstalled flash pro CS4 and media encoder.
BEFORE checking for and installing any updates I tried encoding a
completely new file and experienced exactly the same crash when set
to ON2 2 Pass.
I then installed all updates again. No change, same crash of
Media Encoder.
Mark

Hi Mark,
I tried encoding a source mov file to On2 VP6 with 2 pass and
it worked for me for both CBR as well as VBR case. This was on
Windows XP and I have Premiere Pro and AME installed on the system.
If you import the file directly into AME (instead of sending
it via Flash) and then encode, do you still get the crash?
Thanks
Aurobinda

CS4 Media encoder - Crop+Resize problem

I`m attempting to both crop and resize a video at the same time.
I have an AVCHD 1920X1080 premiere CS4 project. I export it to media encoder.
I`m attempting to encode it to flv or f4v.
After having cropped the video in Media encoder I would like to resize it but then I encounter a problem:
I have 3 options in the output settings:
Scale to fit/Black borders/Change output size.
`Black borders` is not what I want. I need my frame to contain nothing outside of the image.
If I choose `Scale to fit` the video immidiately becomes terribly blurred. It can`t be not a resolution issue as the size is 429X622 after the crop and the original is HD (and if I encode it the result is accordingly strangely blurred) I can resize the video but it will be `blurred`.
If instead, in the output settings I choose `Change output size` I get a normal video image (no blur, that is) but the the `resize video` interface under the `video` tab is disabled - it is greyed out ( even though the checkbox next to it is still marked) and the width and height boxs are greyed out too. I can`t resize.
I`ve attached to this message a JPEG capturing a part of the frame to show the strange blurring problem as well as the greyed out `Resize` interface.
What am I doing wrong ?

Jim Simon asked:
But isn't that the size you want? If not, how did it get set that way?
Thanks for your interest, Jim Simon. Well, no, it`s not the size I want. I want to be able to resize at will, after I had cropped. How did it get set that way ? I got that 429WX622H frame merely by cropping the original 1920X1080 frame by using the `Media encoder` crop function, while the output is set to`Change output size` . If I would go now and rechange the size of the cropping frame I would get different dimension numbers. But as to how it got `set` this way, and now I refer to the word `set` as in `not being able to change anymore, being greyed out and disabled` - I have no idea at all, and this actually stands at the core of my bewilderment. If i choose to go about it differently and change the order of actions by resizing first and then cropping, for example, if I would choose first to change the size of the video from 1920X1080 to let`s arbitrarly say: 720X440 and then I would go and crop it in order to exclude from the frame certain imagery that I don`t need, then, Oddly enough, my previous resizing action will be strangely ignored and the cropping is re-calculated from the original 1920X1080 frame. I may even end up with a `crop` which is larger than my `resize`.
In other words: I need to be able to change both what I include in my frame and the final video resolution, and media encoder would not allow it in `Change output settings` and it would allow it in `Scale to fit` but then it insists on adding a strange and impossible bluriness effect even in the result encoded video.

CS4 Media Encoder Crash after rendering - two files, help?

I'm not a professional so I would appreciate any advice you can offer. I was encoding a WMV HD video (edited in Premiere Pro from CS4) that was just under 2 hours long. On an i7-920 with 9GB of RAM, it took just over 16 hours. At the end of the encoding, the Media Encoder bar displayed 0:00:00 time left. But it then froze at that point for about 30 minutes. Then the program crashed. I planned to take these WMV files and put them, via Encore, onto a dual-layer DVD with a few other special feature-related videos.
I now have two versions of the file in the destination folder, one that has the title I gave it and another that has a "._00_" before the title. Both files are .wmv files and the one with the normal name is 6.64 GB whereas the one with the ._00_ before the name is 6.60 GB. Both have problems if I try to play them beyond the 60% or so point.
Is there a way to salvage these files without another 16 hour render?
How long should I expect, on a normal/successful render, for Media Encoder to continue to process the file after the countdown reaches 0:00:00?
Thanks. Any advice for this very untrained editor would be appreciated.

On the topic of opening a project on the exact same version of Premiere Pro CC 2014 (yes it is definitely up to date, and the 2014 version), to overcome this export crash problem that ZachHinchy has brought up - you can't. Technically speaking, one should easily be able to open a Premiere Pro CC 2014 project from one system on another system running the exact same up to date, legitimate version of Premiere Pro CC 2014 without any kind of error. But for some reason, this has been disallowed(?) by Adobe. It has facepalm written all over it. Does anyone agree that this is at least a little bit silly?
I have tried exporting a Final Cut Pro XML from my project to try and open the sequence at uni on a Mac, so I can render my project when I finish my edit. It half works - the clips are there, but the sequence is gone - i.e. 12 hours of painstaking sequencing and micro-edits that had me at several points in time wanting to insert my hand through my monitor with enough force to make a large hole. I really cannot afford redo this sequence, as my assignment is due tomorrow, and I have to work at 6 oclock in the morning, so I also cannot afford to stay up till the early hours of tomorrow morning. Wish me luck that some miraculous event has taken place overnight that will somehow allow me to just open my project, on the same version of Premiere, on a Mac, without hassle. (Apple OS is not friendly to anything but its own selfish nature, so I am having doubts).
Adobe please, if you can do anything at all to help, you will save my assignment, and my faith will be restored. Otherwise, I'll just get my money back and buy Final Cut instead.
I cant even
If I find a way to fix either of these problems, I will post straight away.

CS4 Media Encoder waits 20 min before starting

When I export media (flv-video or mp3-audio) after I hit the 'Start Queue' button the Media Encoder just waits(?) for 20 minutes before it actually starts encoding. During that 20 min elapsed time remains at 0:00:00, PProHeadless.exe uses CPU at 45% and nothing else. After 20min 'elapsed queue time' jumps straight to 00:20:xx and starts counting, CPU crunches at 100% etc. as if nothing is wrong.
Annoying especially when exporting short mp3-files... Any ideas, anyone?

Everyone may have already got what they wanted from the answers given in the post but I thought I'd add my PAL experience of this.
I tried to media export a timeline to one large mixdown file. (blackmagic mjpeg) the timeline had simple premiere titles fading up and down to black before each video module. The media encoder worked fine but none of the dissolves from timeline to title worked - they translated as cuts in the mixdown. In the end I dropped premiere generated black video over the titles and used variable opacity to bring them in and out. This worked fine and proves that you can export with black at the front.
What it proves however is that CS4 really is working differently to CS3 in lots of ways.
As far as media encoder is concered, I'm sure this is a grandmother sucking eggs business but it's critical for performance that the USE PREVIEW FILES option in the settings box is selected. Otherwise CS4 starts to re-render everything and seems to be much slower at doing it than a basic timeline render. Including metadata files doesn't seem to offend too much but I only evr include this when I'm exporting final versions anyway.

CS4 MEDIA ENCODER (not responding) please help...

I'm working with a PC VISTA home premiere 4gb ram, Nvidia gt 220 GPU, dual core, and CS4 MASTER SUITE.
Used PREMIERE PRO CS4 to capture NTSC dv widescreen footage (from DVX100B)
Used CS4 AFTER EFFECTS for GRAIN & TITLE GRAPHICS and rendered each clip as a QUICKTIME (newest version) .MOV animated file.
SAVED RENDERED CLIPS TO a 1TB external hard drive...connected to pc via usb...not esata yet...
IMPORTED RENDERED .MOV files into PREMIERE PRO and EDITED together a nice SEQUENCE just over 3min in length.
EXPORTED TO MEDIA (used serval different export settings with the same result) SEQUENCE FILE PULLS UP IN ENCODER and I click START QUE
and it trys to load then (not responding) freezing MEDIA ENCODER where I have to reboot...due the task manager wont shut it down.
Everything I have tried (Current Updates Installed, Video Card drivers updated, Re installed Premiere Pro, quicktime update, ENCODER update) is not working.
1) Are my .MOV files to large? ( what is a good size for a .mov) they range from 60-500MB
2)I read some forums about debugging and corrupt .dll files (please advise if the makes sense)
3) How do I run a clean script...will that help?
4) I HAVE A BUNCH of audio files .wav and aaf files...in the squence are they loading it down?
and thank you...hope I described the problem well enough.

Alirght my ENCODER IS NOT WORKING...a week later...I have compressed my HUGE 50-650mb clips to tiny FLV files...MY CS4 ENCODER cant encode more than 2 clips on the CS4 PPR sEquence...just says status: waiting then I hit >start queue and it freezes >not responding
every once and a while it will unfreeze (2% of the time actually) and encoding a file...
TROUBLE SHOOTING HELP
I dont have a previous copy of cs3 installed (never installed on this pc)
I have rebuilt my project in a small compress FLV and AVI formats.
I have unistalled and reinstalled twice.
I have cleared my media encoder 4.0 from my app data roaming file
I have tried the Premiere.exe short cut fix in C: dynamiclinkmanager file
Im stuck somebody out there has to had this problem...
Im running a 32bit Vista Dual core 500gb hardrive, 200mhz processor, nvidia geforcegt220 video card, 550w power adobe CS4 MASTER SUITE COLLECTION...CLEAN COMPUTER NEVER ONLINE ALOCATED just for editing purposes...
WTF ADOBE!!!

CS4: Media Encoder - Black Bars of Doom

Similar Messages

Maybe you are looking for