Media Encoder output size vs. input size

I'm having trouble preserving the qualities of the source in the output
The source, imported into a .Prproj is:
Video: MPEG4 Video (H264) 1920x1080 23.975fps [VideoHandler - MPEG4 Video (H264) (eng)]
Audio: AAC 44100Hz stereo 116kbps [SoundHandler - MPEG-4 Audio (eng)]
and about 25mins in runtime with an on-the-disk size of 1,269,xxx KB
the output result after saving .Prproj and importing that into Media Encoder CS5.5 then encoding:
Video: MPEG4 Video (H264) 1920x1080 23.998fps [Mainconcept MP4 Video Media Handler - MPEG4 Video (H264) (eng)]
Audio: AAC 48000Hz stereo 157kbps [Mainconcept MP4 Sound Media Handler - MPEG-4 Audio (eng)]
and about 8mins in runtime with an on-the-disk size of 1,322,xxx KB
the specs are close to identical, and from my mind, not different enough to cause a sequence roughly 1/3 of the original to end up being physically larger than the source.
All the other formats and presets don't (seem to) allow for anything close to the original specs. I found the dropdown for the audio to be set to 44100. I realize that's trivial to the data load <smirk>
I'm pretty ignorant to the effects other options can have -- and I presume that the options pre-selected by ME are grabbed from the source.
Am I wrong or is there anything I'm missing? another codec would help (the Mainconcept is a hog?)
If so can anyone direct me to one and the directions for having ME make it available?
thanks for any help you can offer!

The AVI file plays with the correct dimensions in Windows Media Player, and the Quicktime version also has the correct dimensions. I don't have Premiere Pro, and I'm using the version of AME that came with the Design Premium CS4 package.

Similar Messages

Media Encoder File Size Estimates Very Inaccurate (How to Reduce Blu-ray File Size)

Hello there!
I made several wedding videos last summer and exported my video and footage to HD .m2t files using a high profile h.264 codec and they always came out being plenty small to fit on my single layer Blu-ray disks. But this year I filmed a wedding (same camera) but my files seem way larger, so I'm doing something different, and I'm not sure what. Should I use MPEG2?
I'm attaching an image of my Encoder settings. I will say that the files it outputs are playing at the proper rate (in this case, the video rate hovers around 12mb/s like it should). Encoder estimates a file size of 2.7 gb, but the final file is 16.4 gb. That's not very close. This file is full HD, 23.976 fps, 8-bit and about 30 minutes long. I should be able to easily fit this, and the other videos I need on the same disk at these low data rates right? I have some of my Disney Blu-ray movies ripped on my computer and they play at 40 mb/s. That's twice my max rate and those files are 20 gb for an hour of video (including 3 5.1 audio streams, a 7.1 stream and several subtitle tracks, I just have stereo audio).
So should I switch all my files to MPEG2? What are your favorite settings for a putting Canon DSLR h.264 footage on Blu-ray? Thanks!
EDIT: I re-exported using MPEG2 and the file estimates were correct.

Encore, and I suspect most authoring programs, allows a maximum of 40 Mbps COMBINED video and audio. so anything over 35Mbps video only risks problems.
I don't know what all the specific differences are between Adobe Media Encoder/PR/EN's H.264 preset vs the H.264-Bluray, but bitrate going over 35 is one of them. And Encore clearly does not like that. Many encoders result in small (and for some larger) variations that result in spikes over the allowed level. Any of those issues can result in Encore "seeing" a file as not BD legal.
I think all Ann was saying was the she agreed with your using the H.264-BD present with multiplexing off. And she suggested (I thing with the H.264-BD preset) selecting the max bit depth. I'm not sure if she actually meant max bit depth, or max render quality.

Adobe Media Encoder - File Size HUGE. HELP

I have a MPG that is 216mb. When I attempt to use Media Encoder 5 or 5.5 the estimated file size for a 640 x 480 f4v is 26456mb.
I have used the computer at my school with the same file and the file size is 2mb. What am I doing wrong at home? I can't image encoder can make a 216mb file become 2.6 gb.
Please help.
Howard

Please drop the source clip into MediaInfo and check what it says the duration is. (If you don't have MediaInfo, you can download it for free from the Internet.) If possible, please post a link to the clip so that we can download it and check it out for ourselves.
Two details catch my eye in the Source Summary. Both screenshots show that the field order is Unknown and that the clip has no audio. I doubt either of those details accounts for the incorrect duration, but the unknown field order, at least, makes me wonder whether AME is having trouble interpretting the footage correctly. I suggest going to the Interpret Footage dialog (right-click on the clip in AME's queue and select Interpret Footage), and setting the Field Order to the correct value [Upper Field First, Lower Field First, or No Fields (Progressive Scan)]. While you're there, check whether the frame rate is accurate--according to the screenshot, it's 30.000 fps. Is that accurate?

Media Encoder - wrong size on AVI files

I have an 720 x 480 AVI video, and Media Encoder keeps importing it as 640 x 480. I don't see a setting or control for enforcing the right aspect ratio, and the Pixel Preview setting doesn't have an effect on the output. I've tried Resize Video to enforce the right dimensions but I still get black bars on the sides. Any suggestions?
I have the same video in MOV format, but Media Encoder won't recognize it even though I have QuickTime 5 installed. Do I need to upgrade to QT7?

The AVI file plays with the correct dimensions in Windows Media Player, and the Quicktime version also has the correct dimensions. I don't have Premiere Pro, and I'm using the version of AME that came with the Design Premium CS4 package.

Alpha channel in Adobe Media Encoder output

Hello, I would like to know how to get the same result in Adobe Media Encoder as you get from AE rendering using Quicktime container and PNG + alpha codec.
On the left is the SS from playing AME rendered video in any player, even Win preview, on the rigth is how it is played if rendered from AE with same settings. (AME has 32bit. AE has RGB + alpha)
Even the file sizes are different so this clearly isn't equivalent to AEs render. And yes, if you import what AME rendered into AE, it looks ok, but I need this to look OK in video players.
Am I missing something, or this simply isn't possible?
Thank you for your time.
Sandi

I want to do in "AME", the functions that have After Effects.
Are they?
RGB - Opaque = Colors / Transparent = black.
Alpha - Opaque = White / Transparent = Black.
RGB+Alpha - Opaque = Colors / Transparent = Transparent.
As in After Effects.

CS4 / PremPro / Media Encoder - output settings needed

I have imported a 1920x1080 Quicktime ( *.mov ) file; made some edits; now want to export with same specs ( 1920x1080 mov file ), but I can't find the proper settings in the Media Encoder for this. Any help would be greatly appreciated?
Sonny

steve,
What? Never before? If you think that CS4 was a great pay for Retail Beta privilege, you should have been around for the true 'public beta' and the nine Retail Beta version and dot releases of Adobe LightRoom. Retail Beta Joy like never before! :)
Compared to that CS4 is super stable and bug free--pretty sad for a paid Retail Beta, actually. But, hang in there, there's hope. CS5 is coming, and that could potentially be an ADOBE Paid Retail Beta Triumph :) :)

Media Encoder: outputs "Media Offline," freezes during H.264 Export

Hi,
I've been experiencing multiple issues with AME...firstly, on occasion when exporting timelines with linked AE comps, one or two of those comps will output with "Media Offline" frames even though the comps are online and fully playable in the timeline. I have to scrub through my output files now to ensure these frames aren't there, and I've had a few slip by, so this is a big issue that needs to be addressed. Exporting directly from Ppro works fine.
Secondly, when exporting H.264, AME just plain stops encoding in the middle of exporting. This isn't repeatable across different timelines, but if it does freeze on a particular clip, attempting to export that one timeline will always freeze at that same point. Exporting directly from Ppro works fine.
These have happened on multiple timelines, multiple projects, across two machines: a 2010 mac Pro and a 2013 macbook pro retina.

Hi Mark,
I did install the CC 2014.0.1 update and the issue remained. I had a colleague tell me that he experiences the same issue for Format= Quicktime, Codec= h.264 when he has the "limit data rate" option checked with a value. When I unchecked the limit data rate (of my standard 10,000 kbps 720p preset) I got a clean render devoid of the previously mentioned artifacts. However, it defaulted to a 70,000 kbps data rate which of course is higher than I'd like/need. For now I guess I'll be exporting .mp4 h.264, but I'm still curious why the limit data rate doesn't behave like it did in CS6.

Media Encoder output created with incorrect permissions (OS X + XSAN)

Output from AME doesn't seem to respect the umask settings in launchd-user.conf (OS X 10.8 & 10.9).
In order to allow multiple users on the SAN to access and edit files, we set the default permissions to be both user and group writeable - however, output from AME is consistently only writeable for the user who created it. This leads me to believe that AME (or some component of it) is running as a system-level process and disregarding the user application umask settings.
Has anyone else in a shared media environment experienced this issue?

You might try unlocking the window and attempt to delete the custom users. Be sure to back up your system before attempting anything.
Highlight the first one and see if you can hit the minus sign to delete it. The system user should be the owner. if you highlight it and click on the triangle at the bottom, it should have "make system the owner" available is it already isn't. If the system user with the Custom priviledges is the owner, you will have to change that first before you can delete it.
You might also try resetting user permissions and see if that helps. This should be the same for ML:
Repairing User Permissions in OS X Lion
You’ll need to reboot to perform this, and then use the same resetpassword utility that is used to change passwords in Lion, but instead choosing a hidden option.
When you use the Disk Utility app and Repair Permissions — it doesn’t actually repair the permission settings on folders and files in your Home folder where your documents and personal applications reside.
In Lion, there is an additional Repair Permissions application utility hidden away. This tool is located inside boot Repair Utilities. Here’s how to access it.
Restart Lion and hold down the Command and R keys.
You will boot into the Repair Utilities screen. On top, in the Menu Bar click the Utilities item then select Terminal.
In the Terminal window, type resetpassword and hit Return.
The Password reset utility launches, but you’re not going to reset the password. Instead, click on the icon for your Mac’s hard drive at the top. From the drop-down below it, select the user account where you are having issues.
At the bottom of the window, you’ll see an area labeled ‘Reset Home Directory Permissions and ACLs’. Click the Reset button there.
The reset process takes a couple of minutes. When it’s done, quit the programs you’ve opened and restart your Mac. Notice that ‘Spotlight’ starts re-indexing immediately.

Media Encoder Output Destination

Why is ME defaulting to an old destination, when I am invoking it from Premier Pro CS4? Shouldn't it at least default to the folder from where the project resides? How do I change this?

steve,
What? Never before? If you think that CS4 was a great pay for Retail Beta privilege, you should have been around for the true 'public beta' and the nine Retail Beta version and dot releases of Adobe LightRoom. Retail Beta Joy like never before! :)
Compared to that CS4 is super stable and bug free--pretty sad for a paid Retail Beta, actually. But, hang in there, there's hope. CS5 is coming, and that could potentially be an ADOBE Paid Retail Beta Triumph :) :)

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,

Media Encoder CS4 output file size varies--why??

I was batch encoding several files yesterday, and one of the files failed. Adobe Media Encoder provided no details, other than when I hover over the yellow exclamation point error icon, it says: "Error compiling movie. Unknown error." Very insightful.
Today I reprocessed the file same file with the same preset [FLV - Same As Source (Flash 7 and Higher)] and it worked fine. To check for instability on my machine, I actually ran the same job 10 times, and each job succeeded. But the curious thing is, even though I was using the same input file and output preset, I see that the output files vary in size. The output sizes are:
30,739,977 bytes
30,750,834 bytes
30,750,504bytes
30,750,654bytes
30,739,928bytes
30,740,044bytes
30,750,615bytes
30,740,001bytes
30,739,979bytes
30,750,637bytes
Now I understand that this variation is less than 10kB on a 30MB file, so it's prety small. But I am curious as to why the file size would vary in this way.
Any ideas?

I would guess that you are overclocking your cpu and the cooler is not able to make the cpu cool enough and some calculations can go wrong. There are programs that put the cpu in a high load and check if it's running properly as expected. Give them a try.

Sizes In Adobe Media Encoder...

I make a PAL movie in Premiere Pro CS3 with clips from my Panasonic GS500 camera. Export to Adobe Media Encoder CS3 and it gives an output frame size (for FLV) of 1024 x 576.
I open the same sequence in Premiere Pro CS4 and Export to Adobe Media Encoder CS4 and the frame size becomes 1050 x 576.
Why the two different width sizes? I have not done any resizing or cropping.
If I do resize the video by half, so that 576 becomes 288 (keeping the proportion link checked) the size becomes 512 x 288. 512 is not half of 1050.
Also, why is there no Deinterlace button, as there was on CS3. Do we assume that the video is being deinterlaced by default? Or, as some others have complained when exporting to DVD, is the exported video remaining interlaced? This might account for why I cannot get the same FLV picture quality, using exactly the same settings, as I did with CS3.
Any help greatly appreciated.
Spok.

HI Colin,
well, i used to be very happy with SorensonSqueeze, but for more than a year now, I'm just using Compressor (indeed from FCStudio).
It's VERY handy and lets you manage your settings in a way AME can't even think of in version 8... I mean nothing extraordinary, just the way it should, with possibility to move, edit, group, duplicate, rename, describe your settings...
And as for flv encoding (at the time of CS3, which I still have on my desktop machine) by installing the Suite, it would also install the codec for Compressor.. Excellent! Which CS4 doesn't do anymore... which forces us to use this terrible AME.. That's the scandale to my humble opinion!
But ok, via Compressor, you get the settings for flv... with the deinterlace box as on the attached image. Indeed with VP6 encoder.
And no, me neither, i'm not torn up, but it would have been nice Adobe gave us the info!
Compressor does also a great job in slomo. That's quite new but impressive. And Compressor is MUCH faster than AME.. AME takes ages! For a good result, I agree.
voila...

.mov to flash banner ad via media encoder, size issues

Looking for some compression feedback, as I cannot get the results dialed in thru Adobe Media Encoder CS4.
Creating a flash banner ad, 11 seconds total, with 5 seconds of video from final cut. The size of the exported .mov is 784 KB, and I still have to hit a target of less than 60KB (yikes) on the final FLV export for the ad specs. Anyone had any luck here in these type of productions? When I convert to FLV (heavily compressed) and import into timeline of flash as embedded file, keeps increasing in size, hovering just below the 1MB mark. Without the video, the flash ad is at 20KB, so I really only have 40KB to work with.
When I open the FCP .MOV in Quicktime Pro and "export for web," I see a small file size of 4KB, could it really be that compressed?
But when I bring that 4KB file into Media Encoder, it goes over the 60KB limit.
Also, should note that final ad needs to be Flash 7 friendly...
Your input is appreciated.

Predicated on info in the other THREAD, I will now ammend my previous post:
2.) Assets - that's why I asked
3.) Project - could still be a possibility
Looks like the Bug is still in the running and gaining fast.
Have you filed a Bug Report/Feature Request with the data that you've furnished in your two thread?
Good luck,
Hunt

Maximum file size with Adobe Media Encoder?

I seem to be having a problem when converting files in AME.
I'm converting .m2v files into quicktimes files, using the DVCPRO HD 1080i50 codec. No sound is being exported with the audio.
Dimensions are 1440 x 1080, frame rate, field type and aspect are locked at 25, Upper First and HD Anamorphic 1080 (1.333) respectivly.
I've encoded about eleven other files of the same type without fail, however this certain file is at 1.7gig compared, where as every other file I wanted to encode is under 1gig.
I'm using an Asus N53SV with 16gig of ram, so I'm sure my laptop can handle whatever is thrown at it. I'm using a 64bit operating system on Windows 7 home premium Service pack one.
Processor: Intel Core i7 - 2630QM CPU @ 2.00Ghz
RAM Memory: 16gig
Graphics card: Nvidia Geforce FT 540M
Progam: Adobe Media Encoder CS5.5 ver. 5.5.1.12
The error log reads:
- Source File: G:\Digital Postcard\To convert\Untitled-6.m2v
- Output File: G:\Digital Postcard\To convert\Untitled-6_2.mov
- Preset Used: Custom
- Video: 1440x1080, 25 fps, Upper, Quality 100
- Audio:
- Bitrate: DVCPRO HD 1080i50
- Encoding Time: 00:09:50
04/19/2012 03:19:30 AM : Encoding Failed
File size that I want to encode is 1.7gig
I'm assuming either the file is corrupt or I don't have sufficient specs to handle the large file.
Any help will be great,
Thanks.

There are no file size limits to the software beyond what would be imposed by the operating system itself and the file format of the drive.
So...assuming you have enough drive space, something else is going on.

MP4 encodes fail when output size is greater than 4GB, AME CC 2014.2 (8.2.054)

I have a jpeg image sequence about 45 min long at 30fps.
Using AME CC (7.2.2.29) I can successfully encode to MP4, CBR at 18 Mbps. File size is about 5.53 GB.
Using AME CC 2014.2 (8.2.054), with the identical preset (migrated directly from previous AME), the resulting file is unplayable.
AME CC 2014 gives following warning at the end of the encode:
- Source File: /Volumes/LS-GRAID-8TB-1/DDL_video/Output/1_Frames/2_Current/102-204-C01-CallanderVeryGold _16bit/102-204-C01-CallanderVeryGold_16bit_[00000-82441].jpg
- Output File: /Volumes/LS-GRAID-8TB-1/DDL_video/Output/2_Encode/1_Review/102-204-C01-CallanderVeryGold_ 16bit.mp4
- Preset Used: DDL-MP4-CBR18
- Video: 1920x1080 (1.0), 30 fps, Progressive, 00:45:48:02
- Audio:
- Bitrate: CBR, Target 18.00 Mbps
- Encoding Time: 00:55:28
01/19/2015 03:33:17 PM : File Encoded with warning
Adobe Media Encoder
Could not write XMP data in output file.
When I either reduce the bit rate OR reduce the work area, so that the final output file is under 4GB (or more specifically, under approximately 4,096,000,000 bytes), I do not get the XMP warning, and the final file is playable.
Again, please note that the previous version of AME CC does not have this problem when using an identical preset on identical source, so it does not seem to be a problem with the source frames or the output format chosen, it seems to be an issue with the current build of AME.
Is there a solution to this issue?
thanks

I have had the exact same problem, I am now trying to encode with audio. ( I also did not need audio ).
My file size and bit rate is a little higher . and using VBR not CBR but it is a mp4 encode and exact same problem, unplayable.
I am now trying an encode with audio on at lowest possible rate, to see if it assembles the video correctly.
I can confirm the work around, With AUDIO on, the export works.
BTW: also tried the sequence directly in Premiere 2014.2 and same error.
-----:LOG:-----
03/06/2015 08:19:46 AM : Queue Started
- Source File:Adobe Premier Edit_1.prproj
- Output File: FullRez1080_59.94fps_VBR10-50_noAudio.mp4
- Preset Used: Custom
- Video: 1920x1080 (1.0), 59.94 fps, Progressive, 02;53;33;46
- Audio:
- Bitrate: VBR, 1 pass, Target 10.00 Mbps, Max 50.00 Mbps
- Encoding Time: 03:40:33
03/06/2015 12:00:19 PM : File Encoded with warning
Adobe Media Encoder
Could not write XMP data in output file.
03/06/2015 10:12:51 PM : Queue Started
- Source File: Adobe Premier Edit_6.prproj
- Output File:FullRez1080_59.94fps_VBR_20-50.mp4
- Preset Used: Custom
- Video: 1920x1080 (1.0), 59.94 fps, Progressive, 02;53;33;14
- Audio: AAC, 16 kbps, 8 kHz, Mono
- Bitrate: VBR, 1 pass, Target 20.00 Mbps, Max 50.00 Mbps
- Encoding Time: 05:11:45
03/07/2015 03:24:36 AM : File Successfully Encoded
Machine:
Mac Pro 6,1
12-Core Intel Xeon E5
64GB RAM

Media Encoder output size vs. input size

Similar Messages

Maybe you are looking for