Media Encoder CS4 hangs when opening large XDCAM HD MXF files

I am having a problem with Media Encoder CS4 hanging consistently when importing large (18GB) XDCAM HD (25mbps, MPE-2 HD) MXF files. Smaller files are not a problem. This is on a soupped up system, HP XW8600 Workstation / Windows Vista Pro. The same files work fine in After Effect CS4.
Any idea what could cause this?
Thanks.
T.

Yes, I did. Thanks for the tip though.
Thierry Humeau, DoP
Télécam Films, LLC
4400 MacArthur Blvd. NW
suite 201
Washington DC, 20007
o: +1 202.298.0030
c: +1 202-255-8696
www.telecamfilms.com

Similar Messages

Adobe Media Encoder CS5 hangs when adding files of varying HD resolutions.

I've seen questions similar to this related to CS4 but never explained very well, and my CS4 for mac worked fine. I am unsure if this is a new problem or a windows specific problem but here is the situation, if you need more information I will gladly provide it.
For the past week or so I have been encoding 1920x1080i mov files (h.264/aac) to 1280x720p (vp6/mp3) flvs. When I stick to that single HD format in the AMC processing que everything works great. However, when I add older HD content into the AMC que, content with non-standard presets, the program hangs. I tried to import about 15 files last night and the program just sat there all night in a '...NOT RESPONDING' state. The video's have different audio and video settings and it's little difficult to pinpoint exactly what they were. Some are 1440x1080, some are 1280x900, some have PCM audio some of mp3.
Now I temporarily resolved this issue by simply using cs4 master on my mac pro which worked great. However I have noticed a huge speed increase in CS5 64bit AMC. It takes 2-3 hours to encode 1 flash video on my mac pro (dual quad core xeon 2.9Ghz/32GB ram) with CS4. It takes ~20 minutes on my windows 7 station (single core 2 quad 3Ghz/8GB ram) with CS5.
How to replicate:
If I drop a single file into the AMC CS5 que, regardless of the resolution, frame rate, or sound codec; it will import. If I then add another file with a different resolution AMC will hang and become non-responsive. It never crashed but I can't wait 12+ hours to see if it accepted a job or not. As I said before this problem was not observed on CS4 for mac - it worked flawlessly, albeit a little slow.
Software used:
Adobe Media Encoder CS5 windows 64bit
Adobe Media Encoder CS4 mac 32bit
System specs:
Windows 7 home:
Core 2 quad 3Ghz
8GB ram
80GB SSD x25-m
nVidia Quadro 580
OSX 10.6.3:
Dual Xeon 2.99Ghz
32GB ram
4 7200 disks in 4TB raid 0
Radeon HD 2600
Matrox MAX h.264 compressor card
Any advice on this situation would be greatly appreciated. Thank you for your time
-Michael Emanuel

Hi Michael,
Sorry to hear you're having problems with Adobe Media Encoder. I'd like to get some more information about the problem so I can better understand your workflow, and potentially try to recreate the problem. For what it's worth, I often import files of different resolutions without any problem, so I want to find out what's different about how you're using AME.
Apologies for the long list of questions; the small details can be important.
-- After you import the first file, what else do you do in AME? Change the preset? Change the settings? Change the output destination?
-- What are the properties of the files that are causing the problem? You said it happens on "non-standard" files, but can you describe the specifications for one or more files that cause the problem? Please include file type, length, frame rate, frame dimensions, field order (if applicable), alpha mode (if applicable), and audio type and rate. If you know more the bitrate, both video and audio, that would be nice, too.
-- If any of the files are small enough, could you post a couple online that I could try on my machine?
-- How were these files generated? What application created them?
-- Where are the files stored? A local drive, a network drive, a removeable drive (USB or Firewire), etc.?
-- Which Adobe application or suite do you have installed? AME a limited set of options if you're using Flash or Web Premium compared to Master Collection, Production Premium, Premiere Pro, or After Effects.
-=TimK
-=Adobe Media Encoder QE

Media Encoder CS4 crashes when launching

I have Master Collection CS4 for the PC and when i try to open Media Encoder or export from Premiere Pro (which auto-launches ME) the program goes through the typical loading process and as soon as gets past the ME loading badge it crashes.
PLEASE HELP! I can't encode/export any of my projects any more
Thanks in advance for any advice.
lh

Harm Millaard is from the Netherlands. http://vimeo.com/user457793
Dutch culture is very direct, in a surgical kind of way. A Dutch person will make very precise criticism of others, on the understanding that it is important to focus on the details of what can be changed. Criticism of one aspect of a person's behaviour is not considered a criticism of the person as a whole.
In the part of the world where I grew up, there is a completely opposite cultural attitude, which I think is best summed up by the phrase: "If you spit on one person, you drown them all." I have had to learn to appreciate Dutch directness.
This is a multi-cultural forum, where developers with the same interests and from many cultural backgrounds work together. Each of us needs to be mindful that people from other cultures may not share our values. Except in exceptional cases, we can assume that every member of this forum is here with the intention to learn and to help others. Each of us does this from within our own cultural perspective.
You may like to look at the impressive list of helpful responses that Harm Millaard has made over the past nine years. I think that you will see that his intentions are clear.

Adobe Media Encoder CS6 hangs when "hidden" or when paused for longer than a minute

When I hide Adobe Media Encoder while it's encoding, it always hangs (ie. I can't unhide it). Also, if I pause an encode for longer than a minute, AME freezes and I have to force quit. Has this happened to anyone else and have you found a fix for this?
Mac OSX 10.9 (this issue also happened when I was on 10.8)
2 x 3.06 GHz 6-Core Intel Xeon
56 Gb 1333 MHz DDR3
Thanks

I know OSX 10.9 Mavericks introduced a power saving feature called App Nap which is meant to slow down applications that it determins are inactive (could also happen with minimized applications). This would mostly likely be the problem if your issue only happens in OSX 10.9... but if it happens in OSX 10.8 then it I'm puzzled.
Did you check the Console for any error messages?
Anyways, try disabling App Nap for AME first...
Go to your Applications folder
Expand the Adobe Media Encoder CC folder
Right-click on "Adobe Media Encoder CC.app" and select Get Info
Add a checkmark beside "Prevent App Nap"
Restart the application
You could also do the same for other Adobe applications.
-Pete

Macintosh Adobe Media Encoder CS5 Hangs When Launching

I have a Mac Pro with OS 10.6.6, 20 Gb of RAM and plenty of hard drive space.
I have been using Media Encoder with no problems, but now when I launch the application, it hangs and crashes. Anyone have any idea on what I can do to fix it? I haven't installed anything new on my system, I have repaired permissions, but the app just started crashing out of the blue.
Suggestions are most welcome!

Have you installed the
recent updates?

Media Encoder CC hangs when working with 96/24 audio

Title says it all! Has anyone else had this problem with Media Encoder CC? I just upgraded from CS5.5 to CC, and there were no issues with encoding 96/24 audio with CS5.5. I can reduce the audio files to 48/16 and theres no issue, but all the asset files for audio are in 96/24 and I'd of course rather work with the high resolution audio. I've tried searching the interwebz on the issue but can't find anything specific to the audio causing Encoder to hang. Thanks!

Thomas Nord wrote:
Update: We have discovered an issue where you can get this behavior if the source is a Premeire Pro sequence whose sample rate doesn't match that of the clips in that sequence. The solution is to match the sample rate of your sequence to that of your clips. Please let me know if this does not resolve your issue.
Thanks,
Tom
I had some 96/16 audio from an H4n recorder. AME just sat there. Also had the same problem exporting directly from PPro without using AME. Just sat there, no error, just nothing.
Changed the final sequence samples to 96kHz sampling and problem solved. That's a real bummer, since Adobe definitely pushes the sort of "edit anything" mantra a lot, and having to tailor sequence settings to a recently added audio clip is a step in the wrong direction. Glad to know it CAN be fixed, since these renders need to happen, but need that one patched up.

Flash CS4 Hangs when opening a flash CS3 file

Hi to all,
I'm having a big problem with a flash file. I installed CS4,
and trying to open a flash CS3 file crashes CS4. It´s a
complex file, but it opened quickly with no problems in CS3.
Windows Vista Home Premium 32bit
Intel Centrino Duo T2050 1.6 Ghz
2 Gb RAM
Nvidia GeForce 7600
Thanks in advance

Hmmm - I havent experienced this here - CS4 opens all of my
CS3 files no
matter how large or small and across netwrks. I would try
opening your file
in CS3 again, do a save as with a new name, then launch CS4
and try opening
the newly saved file.
Adobe Certified Expert
www.keyframer.com
www.mudbubble.com
(if you want to email me, don't look)
"sandesign" <[email protected]> wrote in
message
news:gembjl$a3f$[email protected]..
> Hi to all,
>
> I'm having a big problem with a flash file. I installed
CS4, and trying to
> open a flash CS3 file crashes CS4. It?s a complex file,
but it opened
> quickly
> with no problems in CS3.
>
> Windows Vista Home Premium 32bit
> Intel Centrino Duo T2050 1.6 Ghz
> 2 Gb RAM
> Nvidia GeForce 7600
>
> Thanks in advance
>

Adobe Media Encoder CS4 freezes when trying to convert .m4v files to .mp4 files

I'm trying to convert some things I got on itunes in order to put them on my android phone. Media encoder freezes before I even start encoding though, any ideas? My OS is Windows 7 Home Premium 64 bit, if you need any more info I'd be happy to provide it.

I meant the File->Save option should not be gray if you "make a change" anywhere in the document. I only have access to an OSX Server remotely to illustrate this point so SimpleText should help you understand what I mean by a grayed out menu item:
The big red arrow.
You can get to the Save As dialog so clearly grayed out menu items wasn't the issue. Moving on..
Your screenshot buttons may be unresponsive but they also aren't "grayed out". Here's a Save dialog with a truely grayed out button:
Your button is not grayed out.
Accurately describing your issue here will help quite a bit. The "save crash" issue has been so rampant it's the first suggestion I had so I offered it. Often repairing the FLA fixed the saving mechanism.
In your case I honestly haven't come across your issue so I have no more suggestions outside reinstall Flash completely. Good luck.

G4 hangs when opening or saving Word 2001 files in Classic mode.

Hello, everyone. I have a G4 400 MHz AGP Graphics ("Sawtooth") model with Microsoft Word 2001 that runs in Classic mode. Recently, when I have tried to open files, the symbol that looks like a tiny clock face with a spinning hand appears, but nothing else happens. This occurs before a dialog window appears prompting for the selection of a file from a particular folder. I can create a new file and type text, but when I try to save the file, the tiny clock face also appears, but nothing else. This also occurs before a dialog window appears prompting for the name of a file and for the selection of a folder in which to save. I can successfully open files in Microsoft Excel 2001 in Classic mode. I did not test PowerPoint 2001.
I'm wondering if the default folder where Word 2001 is trying to open and save files has so many files in it that this G4 isn't able to handle the resultant load. Has anyone encountered something similar?
Also, I'm wondering if I should try to reinstall Word 2001. Does anyone have any ideas in that regard?
Thank you.
-John

Hi John,
Have you tried changing the save location in Word's Preferences?
Might look into NeoOffice...
http://www.neooffice.org/
Or Open Office...
http://porting.openoffice.org/mac/download/index.html
I think they both have older 10.4 versions that can handle Word & Excel docs.

InDesign CS5 hangs when opening large file

I just completed a 128 page business directory with lots of ads (mostly PDFs) supplied by others (some good some crappy). Anyway, I worked on the document over the past month and all was well. Placed images were scattered in different folders. Anyway, upon completion, I packaged the final version. After packaging the file, I can no longer open it without ID hanging or crashing. After it crashes I launch ID again and autorecovery opens the file just fine. I then resaved the file and even exported as an idml file (first couple of times I tried that I crashed as well). Then I tried to open the idml file -- it runs through all the image names in the file but then when it should launch nothing happens and ID hangs so I must force quit. I work on the directory each year so I need a copy I can work with. I can open other ID files just fine without crashing. Does anyone have any suggestions? I could post a crash report if anyone wants to evaluate it. (BTW I did try and trash preferences but that didn't seem to help either.)
Thanks
Jeff

Here are the links (if I did this correctly):
The Sample Process Link: http://pastebin.com/CWuQHNkw
The InDesign Crash Report: http://pastebin.com/TtjhSe7G
Jeff, yes, those are correct.
The first indicates that InDesign is stuck in font manipulation code, and the second is somewhat more precise about where:
Thread 0 Crashed:: Main Thread Dispatch queue: com.apple.main-thread
0   AdobeCoolType                      0x009060cc CTCleanup + 338232
1   AdobeCoolType                      0x009046d2 CTCleanup + 331582
2   AdobeCoolType                      0x008ab7cd 0x855000 + 354253
3   com.adobe.InDesign.Font Manager     0x14c4d7ea 0x14c42000 + 47082
4   com.adobe.InDesign.Font Manager     0x14c4dfc0 0x14c42000 + 49088
5   com.adobe.InDesign.Font Manager     0x14cd53cf GetPlugIn + 440303
6   com.adobe.InDesign.Font Manager     0x14c873a7 GetPlugIn + 120775
7   com.adobe.InDesign.Font Manager     0x14c90dfe GetPlugIn + 160286
8   com.adobe.InDesign.Font Manager     0x14c752d8 GetPlugIn + 46840
9   com.adobe.InDesign.Font Manager     0x14c76e28 GetPlugIn + 53832
10 com.adobe.InDesign.Font Manager     0x14c7708c GetPlugIn + 54444
11 com.adobe.InDesign.Font Manager     0x14c76c83 GetPlugIn + 53411
12 com.adobe.InDesign.Font Manager     0x14c77249 GetPlugIn + 54889
13 com.adobe.InDesign.Font Manager     0x14c9bdc4 GetPlugIn + 205284
14 com.adobe.InDesign.AppFramework     0x0e1323cf GetPlugIn + 54943
Unfortunately, this signature is not consistent with either SING problems or problems with third-party font management tools, both of which have easy fixes.
The best we can say is probably "sounds like a corrupt font or group of conflicting fonts."
So, start by removing all non-system fonts and seeing if ID will open your document.
Assuming that works:
Then, divide the set of removed fonts in half and put half of the back -- see if it works.
If so, add another half set back, etc., etc. until you pinpoint the bad font.

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.

Can Ppro CS3 projects be imported by Media Encoder CS4

Hello:
I have Ppro CS3. I also have the Design Suite CS4. I would like to render out Ppro CS3 sequences or projects into F4V files in Media Encoder CS4.
Does anyone know if this is possible? When I select "add Premiere sequence" in Media Encoder CS4 and find the Ppro project in the file tree Media Encoder hangs just upon selecting the Premiere project without even attempting to add to the render queue. I am not sure if this is because CS3 project are incompatible, or for some other reason. As mentioned, Media Encoder CS4 hands as soon as the Premiere project is clicked to selected and before "ADD" is clicked to add to the render queue.
Anyone come across this problem? Is it fixable, or are Ppro CS3 projects just incompatible with Media Encoder CS4.
Thanks.
Jeff

I appreciate the reply.
However, unfortunately, I do not have Premiere Pro CS4. This is why I am trying to export to Media Encoder CS4. I own the Design Premium CS4 suite which has Media Encoder CS4 version built in.
Media Encoder actually is a stand alone product. When you bring the program up, It has import options for the files you wish to encode. One of the options is to import a PPro sequence. However, when searching the system for Sequences, I could only figure out how to get to the Pproj files.
Documentation appears to indicate the Pproj files are compatible with Media Encoder. However, when I droped in the Pproj file from Premiere Pro CS3, I got a message that it was not a compatible file (message text may not have been that exact statement).
This is why I was curious to see if there is a version compatibility issue, or if someone can tell me how to other render out of Premiere CS3 into the Media Encoder version that comes with CS4 suites.
Thanks.
Jeff

Media Encoder CS4 doesn't work with Premiere (pic related)

Oh hai!
I just got Adobe Master Collection CS4 and my Media Encoder doesn't work with Premiere CS4. When I try to export the file, Encoder starts normally. Then I click "Start queue" and Encoder starts loading. Loading takes almost five minutes, which is a long time, because my project is very simple. After that nothing happens, just a warning sign appears. When I click it open, some kind of log file open and it says:
Encoding failed
Could not read from the source. Please check if it has moved or been deleted.
And I didn't deleted anything. So what does that mean? Why that "Source Name's" path is different than my project files path? Can this problem relate that somehow?
I have also another problem with Premiere CS4, maybe there's a link between these two problems. I can't get Premiere projects linked to open in Premiere CS4. When I right-click the project icon, and click “Open with…”, I can't find Premiere from the list. When I click "Browse", I can find Premiere.exe from my computer, but if i doubel-clicked it, nothing happens. It won't appear to the list or anywhere else. Or have I missed something? So now the project files are linked to open in After Effects. Of course I can open projects from Premiere, but how do I get them open straight from file?
I have long experience using Adobe Premiere and this is the first time I got this kind of problems. I have also downloaded new updates for Premiere and Encoder, this didn't help. Does that matter, that I didn't installed Premiere in C-drive? However it's in my computers internal drive, I have divided my hard drive for five parts, one part contains all of my softwares. My scratch disks are in different hard drive (external), does that matter? I tried different location, but that didn't help.
Please help, I can't do any video editing, because of this problem. And sorry for my english, ask if you didn't understand something. =)

Hello, this is terrible problem, which i found in CS 6 softwares ...
solution i found only working, is uninstall and reinstall full package.. but it is not all,
you need to do BRAND NEW admin account in windows, and install it there.
that means, i could not export after repair from encoder in my original account never more (!!)   .. this is really terrible way how to repair this issue, because :
1.by reinstalling of software, client WASTE HIS TIME
2.by necessity to begin work in another windows profile you again WASTE YOUR TIME because of learning and migrating all other profile modifications, which i see really unaccpetable. Adobe means, this solution of repair is ok, and they did not do till today any steps of creating some "clever" solution.
I ask everybody, who will meet this issue in future, guys, please, complain about this situation, give "BUG Report" to them, and write "feature request" to them , in the way of creating some repair tool, which check actual "broken" connections between encoder and premiere, which refuses to "take material" from it and encode, and REPAIR it automatically..
   I am not IT, but ..does it seems so hard to create this ? Adobe IT developers should know their systems, and should create such utility tool really easy.
History of this problem and detailed description, HOW i did "repair" this. With wasting of app 2,5 days of my working time :
1. after repairing "error 5" problem , i solved it by reinstalling the suite from the new admin user profile (profile B) .
I continued my work on my normal working windows profile . (profile A)
Every cooperation (AE+Pr, export media via "queue" to Encoder) was working fine . . .
2. suddenly it stop working (without knowing any possible reason - i did not do installations )
and showed in error export log file :
"Could not read from the source. Please check if it has moved or been deleted."
3.repair via procedure(procedure "a"):
i did this procedure on the profile B (profile from last time installation of repairing problem error 5)
I did these steps :
a-uninstall master coll suite
b-i used Adobe cleaner tool (remove ALL)
c-removed raw directories in locations
•C:\Program Files\Adobe
•C:\Program Files(x86)\Adobe
•C:\Program Files\Common Files\Adobe
•C:\Program Files(x86)\Common Files\Adobe
•C:\ProgramData\Adobe
d-removed these links from registry file
•HKEY_LOCAL_MACHINE\SOFTWARE\Adobe
•HKEY_CURRENT_USER\Software\Adobe
•HKEY_LOCAL_MACH INE\SOFTWARE\Wow6432Node\Adobe
•HKEY_CURRENT_USER \Software\Wow6432Node\Adobe
e-restarted the PC
f- newly installed the Master Coll CS6
g-update the software
result of repair of "3" : problem still exists
4.Ok i find out after coordination with support, it should have been created ANOTHER NEW admin account.
4a:so i did the same procedure (uninstalling) in profile B
4b: and then i created brand new admin profile (profile C)for INSTALLATION of software
4c: restarted the pc (and did not updated it yet)
result :
==exporting of any sequence/raw/AE link video material from premiere via "queue" (Encoder) (profile C) : export WORKS
==exporting of any sequence/raw/AE link video material from premiere via "queue" (Encoder) (profile B) : export WORKS
==exporting of any sequence/raw/AE link video material from premiere via "queue" (Encoder) (profile A) : export DOES NOT WORK ! ! !
(in profile A, is possible to export some raw video material in encoder which is imported to it via "drag and drop)
problem i see:, i have my basic profile A, which i am interested to work, because of all my directory modifications are in there..
this issue should be some "broken" connections between encoder and premiere, which refuses to "take material" from it and encode.
what i expect :
to get from Adobe some repair tool, which automatically checks these connections and repair if necessary, without necessity of founding the new profile and reinstallation of whole software.. this is madness !
what i do NOT expect from Adobe:
to get from Adobe advice of kind : you have to reinstall full software in new admin profile. sorry , we do not know the solution, because we do not know, how do behave our software.

Using Adobe Media Encoder CS4 for MTS files

Hey everyone, I did some searching on this topic to no avail so here I am.
Anyway, I recently got an HD camcorder that records in 1080i AVCHD.
I have no problems getting the MTS files off of my camera but as I'm sure you can imagine, working with those files is a whole other issue.
I've found that Adobe Media Encoder CS4 works great in encoding these files to QuickTime format (.mov) but the problem is that the resulting file size is actually bigger than the original MTS file which is unacceptable, especially considering I'm encoding the files from 1920x1080 down to 1280x720.
Does anyone have any experience using AME CS4 to convert MTS files to a more workable 720p format for uploading to YouTube?
I've tried a number of different custom settings to no avail (where you see an "or" is where I've tried different options):
Format: QuickTime
Video Codec: MPEG4-Video or H.264
Quality: 100
Width: 1280
Height: 720
Frame Rate: 29.97 or 23.976
Field Type: Lower First or Upper First or Progressive
Aspect: Square Pixels (1.0)
I won't list the audio options because I don't think that has any bearing on my problem.
Any ideas as to why the encoded file sizes are actually larger than the MTS file sizes? Maybe AME CS4 is not what I should be using for this task?
Thanks for your help,
Tom

I figured it out.
If you select H.264 as the format you can then select YouTube Widescreen HD for the preset.
This will set everything up to convert your MTS file to 720p and reduce the file size by around 30% with little quality degradation in my experience so far.
The only problem I encountered was the video was kind of choppy when the camera panned but that was remedied by upping the frame rate from 24 to 29.97.
Hope this helps someone and if anyone has any suggestions to improve efficiency or reduce file size post it in here.

Adobe Media Encoder CS4 Crashing Immediately

Hello,
I am running the CS4 Production Premium suite on a Windows 7 64-bit computer with 12GB RAM. Up til last week, the whole Adobe suite had been running smoothly. (I primarily use Premiere, Media Encoder, Photoshop, and Encore). However, Encore started locking up the computer any time I tried to work on authoring a Blu-ray (it locked up immediately upon opening a Blu-ray project, and only locked up on a new project when I switched from DVD to Blu-ray mode).
I assumed that some of Encore's source code had either been moved, overwritten by something else, or that there was possibly a program incompatibility with something else on my computer. So I took the step to uninstall and reinstall Encore from the install DVDs.
Upon a "successful" reinstallation, I then went into Premiere CS4 to encode a timeline to a P2 file. Premiere seemed to be doing its normal exporting process fine, but Media Encoder would crash after the red splash screen disappeared. To be more explicit, the red splash screen would disappear and be replaced by a window the normal size of the Encoder program, but nothing appeared on screen in the window other than a small white box in the upper left with the rest just being plain gray (see attached photo). At the same time this white window appeared, Win 7 popped up a box saying that Adobe Media Encoder has stopped working and that it would search for a solution to the problem, which it never could do.
I then tried deactivating the suite, uninstalling the full suite and reinstalling, updating so the patches would bring it up to date, and then tried running Adobe Media Encoder again, this time running from the Start menu rather than from Premiere. Yet, it was still the same response: the program crashes immediately.
I would appreciate any suggestions and help that people can provide.
Sincerely,
Kevin T
San Diego, CA

Here is the only relevant info I could find in the Event Viewer:
Faulting application name: Adobe Media Encoder.exe, version: 4.2.0.0, time stamp: 0x4af13937
Faulting module name: WatchFolder.dll, version: 0.0.0.0, time stamp: 0x4af1344e
Exception code: 0xc0000005
Fault offset: 0x00011f03
Faulting process id: 0x834
Faulting application start time: 0x01ca9d3e4234c82b
Faulting application path: C:\Program Files (x86)\Adobe\Adobe Media Encoder CS4\Adobe Media Encoder.exe
Faulting module path: C:\Program Files (x86)\Adobe\Adobe Media Encoder CS4\WatchFolder.dll
Report Id: 89095e2b-0931-11df-a5f1-00248c778de6
Does this seem fixable to anyone?

Media Encoder CS4 hangs when opening large XDCAM HD MXF files

Similar Messages

Maybe you are looking for