Old quicktime with flash layer + adobe media encoder

Hi,
I have some quicktime .mov files.
These play fine in the older quicktime 6
They do not play in the newer quicktime 7
I posted about this issue at a Quicktime forum and discovered it is an issue with the flash layer in the newer quicktime.
These files do not display in Adobe Media Encoder.
My question is how is Adobe Media encoder affected by the Quicktime codecs?
Would removing Quicktime 7 from my machine and installing an older version effect AME?
Would it then be able to se the files and encode them to f4v?
If not are there any other solutions?
Rather desperate, I am doing a site for an animator and all the content I have been provided with is like this.
I could send a sample file if needed
Thanks
mark

Anders,
I have to make sure we are talking about the same thing. In the Effects Control Panel, you twirled open the Opacity intrinsic effect and clicked on the stopwatch to create a keyframe, correct?
I ask this because you can also adjust the Opacity by using the clip's opacity "rubber band" in the timeline, but no keyframes get added there unless you use the Pen tool or a modifier key in combination with the selection tool.
For the workaround to fix the issue, a keyframe has to be created.
-Jeff
PS - You're welcome. :)

Similar Messages

Adobe Media Encoder CS5 doesn't work anymore (WHY? WHAT's WRONG?)

The system I use is Adobe Production Premium CS5.
I have often used Adobe Media Encoder CS5 started from the export of a film sequence in Adobe Premiere Pro CS5.
On the 31st of December 2013 my computer crashed and dumped more or less at the end of a process of Adobe Media Encoder CS5. There was no complete output.
Since then this program Adobe Media Encoder CS5 cannot start up anymore.
It stops at the start-up saying that the program does not work anymore and that there will be looked for a solution. But then it finishes saying that it will be reported if a solution becomes available in the future.
I have tried the following:
- Run Adobe Media Encoder CS5 (exe) from directory C:\Program Files\Adobe\Adobe Media Encoder CS5 => same problem.
- Stop security control AVG while not online with internet => run Adobe Media Encoder CS5 => same problem.
- Reinstalled complete Production Premium CS5 suite => same problem.
- Removed complete directory C:\Program Files\Adobe\Adobe Media Encoder CS5 and then reinstalled Adobe Premiere Pro CS5 => the full directory C:\Program Files\Adobe\Adobe Media Encoder CS5 with contents was there after the install, but subsequent running of Adobe Media Encoder CS5 => same problem.
- Removed complete contents of D:\mediacache\database\Media Cache and D:\mediacache\Media Cache Files => same problem.
What more can I do ??????
I would be very grateful for a solution.
Regards, Arie de Jong, Rotterdam

Hi Jim,
Thank you very much for the suggestions for a solution. First I considered
re-installing Win 7 Pro, because I did not have a fall-back point
predefined. So I could not try to reload a previous system environment. But
for your information the following.
Yesterday my son suggested that there could be some corruption in a control
file of Adobe Media Encoder, because re-installing that program did not
give a solution. Obviously that then would have to be a file which is not
affected by a program re-install.
What he then did for me is to remove directory
Users\owner\ AppData\Roaming\Adobe\Adobe Media Encoder (he actually
renamed it to hide that directory for Media Encoder).
Thereafter we ran program Media Encoder from Premiere. The result was that
a new directory ......\ Roaming\Adobe\Adobe Media Encoder with proper
control files was automatically generated and the problem was solved.
Regards from Arie de Jong

Premiere Pro CS6 stops during export (Adobe Media Encoder also)

Hello,
I have been using the Adobe CS6 Video Bundle for a few years now and suddenly I've been having an issue with exporting my timelines in an H.264 format.
Any H.264 video that I try to export that exceeds approximately 900MB stops in the middle of the export and gives me this message:
My video bundle has been doing some odd things lately and this is possibly the most annoying. My computer is a custom built workstation so it's not like my computer can't handle it.
-Intel i7 4.2ghz overclocked CPU
-32GB RAM
-Adobe Video Bundle installed in 120GB SSD
Any help or advice would be greatly appreciated.
Thanks,
Nate

Thank you for your response.
-I tried exporting an AVI and the file exported succesfully but with a warning "Adobe Media Encoder Could not write XMP data in output file." The file plays fine though and is over 5.5GB. So that's odd that my h.264 which is under 1GB won't fully export.
-Yes, the same thing happens when exporting directly from PrPro instead of using AME.
-In this project I am using NO Dynamic Links.
-I have not installed any codec libraries.
-I do not use 3rd party plug-ins.
-My destination drive has several terabytes.
Thanks,
Nate

Adobe Media Encoder CS4 H.264 iPod video format green flashes in Quicktime

Quicktime 7.3.1 apparently shows no flashes but 7.4.5, 7.5.5 and 7.6 all show green flashes on videos encoded in AME CS4 H.264 iPod video small.
No other quicktime versions tested.
Videos play fine in VLC Player and Adobe Media Player.
Videos encoded with the latest MediaCoder sourceforge application play fine in Quicktime.
Clearly something's wrong with the way Adobe exports and the way quicktime 7.3+ reads H.264 videos.

I think it may be the QuickTime Player issue and not Adobe Media Encoder. Its seems to play find in other players like Adobe Media Player and Windows Media Player after installing Windows Essentials Media Codec Pack 2.2c. (http://download.cnet.com/Windows-Essentials-Media-Codec-Pack/3000-2140_4-1066270 9.html). Haven't check to see if it plays correctly on my i-Touch. Not all videos I encode from .AVI to .MP4 using the i-Pod small preset seem to have this issue.

Can I output for flash 7 with adobe media encoder

Our Flash Player 7 needs to play this movie.
Adobe Media Encoder doesn't seem to give me many options for what Flash Player my output file will work with.
But I don't know much about video so maybe there's a way.
Anyone know?

Look at it from the viewpoint of what codecs the player will accept, and proceed from there.

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,

Adobe Media Encoder and Macromedia Flash MX 2004

I already posted this question here: http://forums.adobe.com/thread/777473?tstart=0
When I first posted I thought it had something to do with Premiere but now think it has something to do with the Adobe Media Encoder.
If you want to delete that message then feel free.
I'm using Adobe Premiere Pro 2.0 and have recently installed Macromedia Flash MX 2004.
Now when I go to export to Flash I don't get the Adobe Premiere's Flash Export dialog box when I press "Options" from the Export Settings. I get the Flash MX Professional 2004 "Flash Video (FLV) Exporter." It doesn't allow me to change any of the parameters.
I then un-installed Macromedia Flash MX 2004 but still get the same "Flash Video (FLV) Exporter."
Any ideas on how to get the Premiere exporter back?
I uninstalled all macromedia programs, Dreamweaver, Extention Manger, and FreeHand.
I now I get this message when selecting Macromedia Flash Video from the export settings:
"Cannot find Flash Video export Module for QuickTime. Please install and retry."
So I un-installed and re-installed QuickTime and got the same message:
"Cannot find Flash Video export Module for QuickTime. Please install and retry."
No quite sure if the above message was talking about reinstalling QuickTime or Premiere, so I uninstalled and reinstalled Premiere again, agian and got this message:
"Cannot find Flash Video export Module for QuickTime. Please install and retry."

Well there is no answer to my question, but I did finally get the Adobe Media Encoder dialog box to come back again.
After uninstalling Premiere and QuickTime, then shutting down the computer, rebooting and logging on to the Admin account, shutting down again, rebooting again, logging in to the Admin account again ...
I then went in to the registry and removed all the Entries that had either of these in it:
C:\Program Files (x86)\Common Files\Adobe\DVA\COM
C:\Program Files (x86)\Common Files\Adobe\DVA\FLASH
and these as well
C:\Program Files (x86)\QuickTime\QTComponents\FLV.qtx
C?\Program Files (x86)\QuickTime\QTComponents\FLV.qtx
Rebooted the computer, logged back in to Admin.
I then re-installed QuickTime, and rebooted.
I then installed Premiere and the Adobe Media Encoder Flash dialog now shows up.
I'd be careful messy with the registry if you are trying to fix this type of problem. Try uninstalling quicktime and premiere and do the above shutdown, reboot sequence a number of times before doing anything to the registry.
I'm not sure what I'm going to do about that Flash Website I've working on...

Adobe Media Encoder CC won't start if flash player plugin is installed

Few days ago I installed windows 8.1 pro on a brand new PC and I was having problem starting AME, clicking on icon simply doesn't sort any effect, the software didn't open. I tried starting it as administrator, deleting \AppData\Roaming\Adobe\Adobe Media Encoder\, reinstalling any CC program and even using AdobeCreativeCloudCleanerTool didn't solve the problem.
At the same time, I was having problem with flash player and firefox; it was just crashing at start, for example at the beginning of a youtube video. Even reinstalling the plugin or firefox itself won't resolve the issue. I resolved by disabling protected mode on flash and after that, the plugin works perfectly in firefox.
Going back to the AME problem, after a few tries, I managed to resolve it by doing this:
- uninstall Premiere pro and relative AME
- uninstall Creative Cloud app
- uninstall flash player plugin
- run AdobeCreativeCloudCleanerTool and clearing ALL the stuff
- install CC app
- install PP and relative AME
- NOT INSTALLING flash player plugin for firefox
Only by doing this, AME starts without any problem. Even after a couple of reboots, it starts nicely.
After that, I tried to reinstall flash player plugin for firefox. Just after install, with firefox still closed, i disabled the protected mode to avoid any crashes. And by this point, AME won't start anymore. By just installing the flash player plugin (without even let it crash once) AME doesn't start. The only thing that worked was to uninstall everything again, use the cleaner tool, reinstall CC and leaving firefox without the flash plugin. At this point AME starts without any problem. I tried again to reinstall flash plugin and voilà, again AME simply can't start.
What should i do to fix this? It sounds so stupid that i have to choose between flash plugin or AME, why they can't live togheter on my system? Maybe i just have to wait for an update (for firefox or flash) and see if it changes anything?
Here are some specs of my system, if it helps:
winows 8.1 pro x64 updated
16gb ram
Intel i7 3820
GeForce GTX 670
latest version of flash, CC and firefox
no plugins installed for any CC software
flash on internet explorer works well

I finally find out how to fix this.
With flash plugin installed and protected mode disabled, I also disabled hardware acceleration in flash plugin options. So I re-enabled protected mode and the plugin worked fine.
After that, I uninstalled everything from adobe, used cleaner tool and than reinstalled all the stuff. Now AME works fine.
Hope this fix will help someone.

Why does Adobe Media Encoder fail to export Quicktime Files?

I'm using Adobe Media Encoder CC 2014 on a Windows 7 Pro 64 bit PC.
While exporting the Quicktime variant of H.264 for ATSC television broadcast files, Adobe Media Encoder fails. Non-Quicktime H.264's render correctly, but some television stations require quicktime.
Troubleshooting reveals the problem only occurs when attempting to make a 1920x1080 H.264 QuickTime file.
Using the same original file (1920x1080), Adobe Media Encoder WILL export a 720x480/486 H.264 MOV file.
More interesting still, it will ALSO export at 1280x720.
Testing this information to it's limits, I found that the cutoff for a successful render is between a frame size of 1610x906 and 1609x905.
Useless, random sizes, I know... but that's the breaking point for Adobe Media Encoder CS6 (6.0.3.1 to be precise) and H.264 Quicktime files.
Others are having a similar problem:
http://forums.creativecow.net/thread/3/934721#953485
This information did not correct the problem:
http://helpx.adobe.com/premiere-pro/kb/error-compiling-movie-warning-or.html
Any help or ideas are greatly appreciated.
OS: Windows 7 Professional 64-bit SP1
CPU: 41.6GHz (dual octo-core Intel Xeon E5-2670 @ 2.60GHz)
RAM: 64GB
GPU: NVIDIA Quadro 5000 v334.95 (2.5Gb GDDR5 RAM)
VID: Blackmagic Design DeckLink HD Extreme 3D+/Desktop Video v10.1.1
DRV: Facilis TerraBlock 16TB RAID/ATTO ExpressSAS R680 v2.19
NLE: Adobe Premiere Pro CC 2014
James Brady
Senior Editor
Results Video, Inc.
El Paso, Texas
http://www.resultsvideo.com

I'm trying to make a file with the extension ".MOV" using AME's "HD 1080i 29.97, H.264, AAC 48kHz" preset. AME fails every time with the following message:
"Encoding Failed
Export Error
Error compiling movie.
Unknown error."
Any other file extension (MP4, M4V, etc.) renders fine. The issue seems only to happen when attempting to make an MOV file. It doesn't seem to matter whether I use AME's built-in preset, or customize my own render settings--the problem always happens with any MOV larger than the size I mentioned above.
All of this used to work just fine on the same machine 2 years back with Adobe CS5, previous version of windows and QuicTime. I've been all through the Adobe and Windows possibilities, so I'm grabbing at straws here with QuickTime maybe having something to do with it.
Interesting.
Would you happen to know if Adobe has made any changes to its manner of muxing long-address MPEG-4 AVC data to the MOV file container? Since the MP4 and M4V files encode properly, have you tried opening these files in a media player and simply using the "Save As..." option to move the date to an MOV file container without transcoding audio or video data? I.e., is there any obvious relationship between the size of the MOV file encode (less than/greater than 4 GB) as a function of the resolution "break point" previously discovered?

Problems rendering Every-line Composer texts with Adobe Media Encoder

I find the text paragraph setting "Adobe Every-line Composer" a huge time saver when dealing with large amounts of text in after effects. I rarely have to do any manual tracking or line breaks to make it look good, as opposed to working with the standard Single-line Composer.
The problem is that when I render through Adobe Media Encoder (which I'm forced to do since they removed H264-mp4 support from AE:s internal renderer) the text is treated like single-line composed text. So the final render doesn't look like my AE project.
I've found two solutions to this problem:
1. Render a lossless video file in the AE renderer and then compress it with Media Encoder. This takes more time and HDD space, and it doesn't allow me to continue working in AE while rendering.
2. Only use Single-line composed text and make all adjustments manually, the old school way. This would not be a problem if I had not already used, and fallen in love with, the Every-line option.
Is there anyone that can think of a third, and preferably better, solution?
I use the CC 2014 versions of AE and AMC.

No, the text doesn't animate at all. It's just a normal static text box. The text part is extremely simple. All animations are done in other layers and pre-comps, combined with pre-rendered 3D graphics from Cinema 4D, rendered as image sequences. My problem is a bug, plain and simple. Or perhaps you could call it a "lack of feature support" or an "incompatibility between AE and Adobe Media Encoder".
My problem appears only when my AE project has text boxes with the "Every-line Composer" option enabled (press the menu button in the Paragraph window to find it), AND the project is rendered through Adobe Media Encoder, no matter which output format I use. I have no problems what so ever inside of after effects, or when rendering Single-line Composer text in AMC.
So, the problem is that Media Encoder doesn't recognize Every-line composed text. Instead it changes it to Single-line composed text, messing up text tracking and line breaks.
To clarify: the Adobe Every-line Composer is analyzing the entire text box instead of only the current line. That way it can automatically change the tracking of individual lines to better distribute the line breaks and build a better whole, avoiding those stray words on the last line for example. Extremely handy, if you could only render it.
I never wrote anything about animating text or that the codec is related to the text problems in any way. AMC is the problem. The codec is only a secondary problem since its the lack of mp4 H264 support that forces me to use Media Encoder in the first place, instead of using the AE render queue as I did in previous versions of AE. I like many things about rendering through AMC, like being able to continue working in AE while rendering, but there are still way too many glitches. And of course, there's the inability to render flv-files in AMC CC 2014, and Adobe's inability to provide a solution other than "Use an older version of AMC". Flv is their own damn format for christ's sake.
Well, enough rambling.
To put it simple:
Has anyone had a problem with "Every-line Composer" in combination with Adobe Media Encoder? Did you find a solution other than the two less-than-perfect ones in my first message?
Thanks!

F4v encoded with Adobe media encoder CS4 (longer than 71 minutes)

Hi I don't know if this is the correct place for this post. So apologies me if this is the wrong place.
Encoding with Adobe Media Encoder CS4 (4.2.0.006 and 4.0 too)
Source: MOV (DVPAL) longer than 71 minutes
Dest: F4V (H.264)
Result: freezed frames and only plays audio at 01:11. Media Player goes crazy and starts showing some diferent parts freeze frames.
In Quicktime crashes, in VLC the same of MediaPlayer. Sometimes the audio starts to downsampling and sounds like the pitch goes down.
Totally agree with this other post: http://forums.adobe.com/thread/580391
(extract)
I recentlly encoded afew F4V using Adobe Media Encoder Cs4. MOst of them are working properly but I don't know why, all of my video that are longer than 71 minutes seems to have trouble playing back. They all Freeze when they reach 71 minutes or if I navigate pass this point.
thanks and help us please!
Kik

Thanks for the interest.
I'll try to explain all details:
MacPro 1.1 (mid 2006) under Mac OS X 10.4.11 (Darwin 8.11.1 kernel)
System files: journaled HFS+ and a unix based NAS (under samba connection)
I have all material on the NAS and also I make the transcoding over it. Is a simple mov containing DV PAL WIDE interlaced 25fps with stereo audio. typical settings with nothing out of DV PAL standard.
The version of MediaEncoder CS4: 4.2.0.006 (it happens with older versions too)
The settings of MediaEncoder are:
Audio: AAC stereo 44,1 kHz
Video: F4V. MainConcept H.264, fps like source, profile high, level 4,1. CBR compression.
The problem only appears with videos longer than 71 minuts. At 01:11 starts with crazy problems. It seems like the player have some read or problems.
Tell me if you need some other kind of information.
thks

Adobe Media Encoder cuts off video layer when the Ultra Key effect is applied

I am working on a Mac (10.8.5) using the latest verison of Premiere Pro CC. I am using Ultra Key to remove the chroma key background from the "talent layer" and adding a "new background layer" behind the talent video layer. When I export directly from Premiere, the sequence exports as expected. However, I have many sequences, and wish to speed up the process using Adobe Media Encoder. When I export the same sequence using Adobe Media Encoder, the top half of the "talent layer" is completly cut off:
The issue has something to do with the Ultra key effect because when I remove the effect from the "talent layer" it exports in tact (with a chroma key background of course). Adobe Media Encoder CC is up to date as well; are there any known bugs with Media Encoder CC and the Ultra Key effect in Premiere Pro?
Thanks!

Block noise in CC2014 Adobe Media Encoder Quicktime H.264 Export

I would love some input from the community here. Perhaps someone else is having a similar issue.
I've been wanting to make a full switch from CS6 to CC2014, but I am experiencing a host of issues that I don't experience in CS6. For one, when I export my Canon 5DMK3 DSLR timeline using Quicktime (H.264), I get an abrasive global noise all over my rendered video as if I was using a low data rate. I use the same settings in CS6 and experience no issues.
Since YouTube compression hides these artifacts, so please download and view original file: Dropbox - RenderArtifactsQuicktimeH264.mp4
Format: Quicktime
Video Codec: H.264
Quality: 100
23.976fps
progressive
Use Max Render Quality
Render at Maximum Depth
10,000 kbps
What I've tried:
1) exporting at 720p and 1080p
2) another codec (H.264 mp4 exports are clean)
3) all combinations of the "Use Max Render Quality" and "Render at Maximum Depth" settings
4) exporting straight from Premiere
5) rendering with and without effects (Magic Bullet Looks, sharpening)
6) GPU (CUDA) enabled and software only (on project and on Adobe Media Encoder)
Custom Desktop Specs:
Intel i7-3960X @ 3.3GHz
32GB RAM
GTX 780 Ti 3GB (and tested Adobe certified regular GTX 780 3GB)
GPU Driver: 340.52 (up to date)
Windows 7 Professional 64 bit
SSD OS drive
WEstern Digital 2TB data drive
SSD adobe cache drive
I'm at a complete loss. What else could be contributing to this?

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.

Adobe Media Encoder CS6 hangs while encoding Quicktime movies

Every day I am enoding 2-3 videos 15-40 min long with AME CS6 and every second day it freezes or slows down to almost zero. The source material is mostly Quicktime ProRes 422 LT 1080 25p or Quicktime XDCAM EX 1080 25p. Target files are H264 videos in different sizes. The workstation is a MacPro 5.1 Xeon 8core, 12GB Ram and Nvidia Quadro 4000 with OSX 10.8.2. Only restart of the computer helps but just for a while then it slows down or freezes again. I am also using Davinci Resolve 9 lite which is sometimes not able to adress the QTencoder when AME is open ... ?
Any Ideas for a solution?
Thank you!

I think it is a problem of Adobe QT32 Server. Adobe Media Encoder is encoding all Quicktime Movies through this Adobe QT32 Server, which is somehow the link between Adobe and Quicktime. But since Adobe QT32 Server is a 32bit application and Adobe Media Encoder a 64bit application it somehow blocks the Media Encoder. And if you have other applications running which somehow try to use Quicktime codec when Media Encoder is using the Adobe QT32 Server than everything slows down or collapses. These are my observations so far. I avoid any other video application as long as AME is open. For example: I close Davinci Resolve when I want to launch AME and close AME when I want to launch Davinci Resolve. This helps so far.

After Effects + Adobe Media Encoder + Flash = Most Random File Sizes Ever

Asking this question in this AE forum because I think more would have knowledge on the topic here than the Flash Forum.
I've heard that video compression is more of an art than a science... Could someone provide me some insight on the following?
-Created a 12 second, 30 FPS, 300x250 banner animation inside of After Effects
-Exported for FLV/Flash to be placed inside of a 300x250 .FLA
-Comps rendered directly from Adobe Media Encoder standalone instead of Render Queue in AE (for 2 pass .FLV's, and heard from various that .FLV's from render queue are not the prettiest at times).
I've always been under the impression that I would get smaller file sizes with SWF's externally linking to an FLV. If I do it this way, I end up with:
41 KB .SWF + 668 KB .FLV = 709 KB
However, if I EMBED the same 668 KB .FLV to the FLA's timeline (not using the flvPlayback component) I end up with a 381 KB file size!
I am just confused on the logic here, could someone explain the reasons for this? I always thought my file size would be bigger if it was embedded to the timeline.

Actually I think it's the tons of extra AS code that make linked players fatter. Never could make sense of the why and how myself, but you can find enough alternate free players/ skins (nonverblaster for instance, which I use) that are a lot leaner.
Mylenium

Old quicktime with flash layer + adobe media encoder

Similar Messages

Maybe you are looking for