Problem with cs4 media encoder

When I try and export media and use Microsoft avi i get a problem.
At first it would give me pop up dialog box that said scratch files are only readable and it would place them in My documents. You can only check yes or it will not let me go further.
Then the program sayss that premier has encounter a problem and shuts down.
I'm not sure what's happening.
I did visit with someone that says if I had the trial version ,( which I did), and the when I bought the hard copy just installed with the new number, that I might try uninstalling the trial version and reinstalling.
Please help.
Thanks.

Ted,
If you did have the trial installed, you need to uninstall your paid-version. Get and run the Adobe Clean Script CS4 a couple of times. Check for any remaining Adobe folders and delete them. [I would also run a good Registry cleaner, like CCleaner, but that is up to you.] When done, do a full installation of CS4 and then run any updates. This should take care of it. Note: Adobe Clean Script CS4 is very, very important.
Good luck,
Hunt

Similar Messages

Could not complete the Render Video command because of a problem with Adobe Media Encoder.

So initially, my problem was solved, but it stopped working again. Same issue. I tried installing the media encoder app, but no luck please help!
Here's the original post:
Hello, I'm running a macbook pro retina, and previously I was able to render video with no issue, and now this is popping up. I've tried deleting and reinstalling photoshop, but it was not helpful. I would very much appreciate any help or guidance. Thanks!
Here's the error message I get:
Could not complete the Render Video command because of a problem with Adobe Media Encoder.
Here's the original thread: Could not complete the Render Video command because of a problem with Adobe Media Encoder.

Have you tried re-installing Photoshop?
Benjamin

Problem with Flash Media Encoder

We're having problems trying to use Flash Media Encoder in
conjunction with an Opsrey 230 card. The device shows up in the
Encoding Options panel but when we try to change any settings we
get the following error "Problem with video capture device. Please
verify that it is working correctly and is not already in use"
The card works fine with Windows Media Encoder. Viewcast
support suggested trying it again with SimulStream enabled, but
still no joy.
Can anyone help?
System - Windows XP Pro 2002 SP 2
Thanks
Phil

Doesn't look like any of your capture cards are on the
confirmed compatibility list... I wish there was a confirmed
INcompatible list (add three from above).
http://www.adobe.com/support/documentation/en/flashmediaencoder/FME_DeviceMatrix.pdf

Problem with windows media encoder

Hello all,
I am developing an application using labview which has to take the screen capture and should be able to save as *.avi or *.wmv.For that i am windows media encoder application from microsoft.I am using windows vista 64 bit OS.I am getting this error
"E:\DashBoard_Production\wmcmd.vbs(378, 1) WScript.CreateObject: Could not create object named "WMEncEng.WMEncoder".
Can anybody help me to solve this?
Thanks and regards,
srikrishnaNF

hi, did you solve your problem?
i have the same problem with python script i have made.
lucas

Problem with Adobe Media Encoder

When I customize a H.264 preset and then save the preset for example as (1.00 Mbps bitrate) and then start the encoding, the defeault 3Mbps bitrate replaces any changes I made thus increasing the file size far beyond my desired file size. Is this a bug?
Also, I have noticed when I select an output directory under the preferences, AME encodes the files to the source files directory instead of the directory I have designated.
Anyone else experiencing these problems as well?

Yes, also see this doc for more info: http://blogs.adobe.com/kevinmonahan/2014/02/12/prevent-crash-on-export-with-premiere-pro-c c-adobe-media-encoder-cc/
Thanks,
Kevin

Startup problem with adobe media encoder on mac

adobe encore media does not start on Mac by this error:
Process:         Adobe Media Encoder CS6 [553]
Path:            /Applications/Adobe Media Encoder CS6/Adobe Media Encoder CS6.app/Contents/MacOS/Adobe Media Encoder CS6
Identifier:      com.adobe.ame.application
Version:         6.0.2 (6.0.2.81)
Code Type:       X86-64 (Native)
Parent Process: launchd [142]
Responsible:     Adobe Media Encoder CS6 [553]
User ID:         501
Date/Time:       2014-02-18 11:04:24.447 +0100
OS Version:      Mac OS X 10.9.1 (13B42)
Report Version: 11
Anonymous UUID: F6D50A8A-F4DF-3614-6A0B-CE4C30343769
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
terminating with uncaught exception of type dvacore::filesupport::dir_create_exception: $$$/dvacore/filesupport/DirCreate=The directory '@0' could not be created. Please check the parent directory protection or permission rights.
abort() called

Yes, also see this doc for more info: http://blogs.adobe.com/kevinmonahan/2014/02/12/prevent-crash-on-export-with-premiere-pro-c c-adobe-media-encoder-cc/
Thanks,
Kevin

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

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

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!

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.

FLVs created with ADOBE MEDIA ENCODER CS6 do not display thumbnails in ADOBE BRIDGE CS6

Could you please attempt to shed some light on why FLVs created with ADOBE MEDIA ENCODER CS6 do not display thumbnails in ADOBE BRIDGE CS6, yet apple finder is able to display thumbnails for these same FLVs without issue?
I'm running CS6 Production Premium with ALL updates installed on 10.6.8
I appreciate any input and help provided the input is provided by someone who either
A) knows the answer because they actually work for adobe
B) actually tried this themselves before attempting to provide a solution
If the conclusion is that it is a codec issue or a header issue with the FLVs You'd have to present a very strong case to back that claim up as it makes no sense whatsoever that CS6 is unable to generate thumbnails for media encoded using CS6, yet Apple finder can without issue. NOT to mention the FLVs in question are CREATED on the same machine with the same codecs installed that is trying to generate previews in Bridge.
Apologies if my frustration is showing, I've gotten and seen several... incompetent replies on this forum regarding this issue and it has never been actually addressed properly as far as I can tell by Adobe support.

We are all just incompetent users here. As pointed out before this is just a user to user forum, Adobe rarely checks in.
I was hoping by now you would have gotten to the bottom of this problem and were offering a solution.

Having major issues with Adobe Media Encoder (AME) - exporting with weird image flickering/colour anomalies, crashing regularly, freezing during encode...!

Hi Guys
I am having some real issues with Adobe Media Encoder (AME) at the moment. It appears that I am unable to encode an h.264 for Vimeo from a Premiere Pro Project file at the moment without at least some weird image issues that are not supposed to be there. These include weird flickering, colour changes, artefacts etc. This is if I am lucky...often I am unable to get the process to complete as the application either crashes and tells me there has been a problem or it simply freezes and I have to force quit the application and often restart my machine.
The problem seems to not to just be with h.264 for the web encodes but also with BluRay h.264 as well. As yet I haven't seen if there is a problem with MPEG-2 for DVD so I will check this out too!
Does anyone else see this happening or does anyone know what might be the problem?
I thought the Premiere Pro project might have been corrupt so tried a different project but the same issues were happening here too.
Any help would be really gratefully received.
Cheers
EDIT - I have just found this online which is exactly the problem I am having! Thanks a bloody bunch Apple! 10.9.3 causing headaches for Mac Pro users | MacIssues
Message was edited by: Alex Cameron

Agreed, I now have a project to GET OUT, and AME crashes consistently 1/3 into the render. It appears to halt all processing after (real time) 00:02:30
Am seriously considering uninstalling CC as I am beginning to find other issues in some apps, and going back to CS6/MC just so I can get work out. Durn it Adobe this is AWFUL!!
Alright, let's try to be constructive instead of throwing rocks... but the frustration level is high, and I have material on deadline. Let's get with this, guys...
What OS Win7, 64-bit
What version of AME/PPro (Please be specific by getting the full version number in the About Adobe Media Encoder screen) 8.2.0.54 Ppro: 8.2.0 (65)
When is it crashing (Again, the more detail here about where it was in the encoding process the better) roughly 1/3 into the sequence, always on exactly the same frame - tried replacing the clip with something different to see if it was a timeline error, and NO EFFECT.
What is your source (PPro project or media file (what kind?)) PPro
If the source if a PPro project, does it work when exporting directly from PPro? NO
What format are you exporting to? H.264, QT, WM, tried everything my client can play.
Do other formats work? MPEG2, QuickTime, etc? NO
Have you tried with GPU rendering on? How about turning it off by switching to Software-only mode? Mine doesn't have any choice, it's software-only.
Have you tried disabling Native Sequence Loading? (AME Preferences: General > Enable Native Sequence Loading) No effect
Other things I tried: uninstalling/reinstalling AME, setting cache to a fast local disk.

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

I need help with the Media Encoder, but do not see a forum for that

I'm having difficulty with some large Windows Media Files--200 to 300 MB--using the CS4 Media Encoder to encode into FLV. Is there a file size limit for source files? I moved the files locally to remove any network issues. If this is not the correct forum, pelase advise.
Thanks!

http://forums.adobe.com/community/ame

Problem with cs4 media encoder

Similar Messages

Maybe you are looking for