GoPro Hero 3 Black 4k and Adobe Media Encoder CS6

As a current Creative Cloud member and a Premiere Pro user, I wanted to see if the Adobe Media Encoder can be used as an alternative to GoPro's Cineform Studio (free version), mainly as a batch encoder for use in Adobe Premiere Pro. The main issue with the GoPro footage in Adobe Premiere Pro is that its codec is not compatible with playback in Premiere, there's a conflicting codec that GoPro uses that unfortunately causes it to have choppy playback in Adobe Premiere Pro. Another issue is that the Adobe Cineform Studio (free version) is that one can only export one video at a time. And, finally I wanted to have more export options than what's available in the Cineform.
This is what I've come up with:
• 4Kcin and 4K show no preview footage in the encoder, and will export as black video - the encoder sees "no video"
• 2.7cin & 2.7k and below all show preview and export appropriately.
The main issue is that Adobe Media Encoder does not recognize the 4kcin or 4k footage from the GoPro camera. But it can encode 4k or above footage since it has a REDCODE plugin.
Any thoughts or suggestions?

Hello,
You may follow the instructions given in the link below and see if that helps
http://helpx.adobe.com/creative-cloud/kb/error-a12e5-installing-creative-cloud.html
If you still face any issues you may contact us directly through chat using Contact Customer Care or email us directly at [email protected]
Regards
Himanshu

Similar Messages

Premiere Pro and Adobe Media Encoder running slow

Hello everyone,
I'm having trouble with CS4, which is running significantly slower than CS3 did on a older machine. The CS4 suite is installed on a Dell Precision M6400:
Windows Vista 64-Bit
Intel Core 2 Duo CPU T9400 @ 2.53 GHz
8 GB RAM
NVIDIA Quadro FX 2700M Graphics with 512MB dedicated memory
The OS is running on a 57.5 GB HD (C:) and the Adobe suite is installed on a 298 GB Solid State HD (D:), except for Adobe Media Encoder, which is installed on the C: drive.
My project has 4 15-16 minute sequences. The sequences are in DV NTSC, 29.97 fps, My scratch disks are set to a folder on the C: drive. Media Cache Files and the Media Cache Database points to a folder on the D: drive.
These are some of the problems I'm having:
- Premiere Pro CS4 generates peak files every time I open a project
- It then takes 3-5 minutes to render before I can preview a 16-minute sequence
- Adobe Media Encoder takes 5 hours to render a 16-minute sequence (as flv) that has been previously rendered
- AME takes 1 hour to render every 15 minute sequence that has never been rendered before
Are my settings affecting their performance? Is there any way to improve it? Thanks.
(Premiere Pro is the only app that is slow)

The data rate for replay is one thing, the data rate from disk to memory then from memory to CPU and back the other way are different matters and ought not to be confused. It is well-established that for a computer to edit AVCHD you need top end components, and note that I said there were three tasks to distinquish with increasing hardware requirements, namely merely replaying the video, specifying edits in the editor and then the rendering. It is commonly accepted by all the industry vendors that to do remotely commercial AVCHD rendering you need a minimum Quadcore CPU then that eats data fast, in order to not let it go to waste you need a fast motherboard bus fast memory and in order for none of those to go to waste you need the fastest disk set-up you can manage. I in fact have a 4-disk RAID0 volume using SATA (I think the disk model is SATAII but I have to await return from the repair center before I can confirm). For this RAID0 volume I have run speed test software from BlackMagic because I have one of their HDTV capture cards. It recorded that this volume which remember is doing parallelised IO is just fast enough to receive a encoded HDTV stream from the BlackMagic card but too slow to receive an uncompressed HDTV stream, indeed when I tried both I found the volume did keep up with compressed but fell behind with uncompressed. Remember that with a RAID0 volume of 4 SATAII disks a given file gets spread over the four disks and hence IO is spread over those 4 3G/s data lanes. Also remember with these disks 3G/s is just a burst speed, for AVCHD we are interested in sustained serial IO which is much less.
Before my machine broke down, I found that it took 5 hours to render 33 minutes of HDTV albeit as it went along it transcoded from AVCHD to a Microsoft HD format for Vista-only. Another interesting thing is that I found that the longer this render ran the slower it became, the estimated time started at 3 hours but the actual was five and the last one third took maybe 3 hours. Because the machine broke after that run I couldn't figure the bottleneck. For my machine bear in mind that at the repair shop we found that the Quadcore had only half the necessary electrical power plugged in, the monitor software showed however that it constantly ran around 90% of whatever capacity that reduced power supply permitted. Now then we can puzzle over why it got slower and slower and yet CPU consumption remained consistent and near to full capacity, memory was not the bottleneck because that was constant at 6.4G. But you can say that this was maybe performing like a Dualcore and was hitting some sort of wall, if you had a 1 hour render with that rate of degeneration of performance factored in what would happen to the render time, and for 3 hours you could be running indefinitely. I hope when the machine comes back the correct power supply will make it behave like a Quadcore should for this type of application. Anyway I have two theories for the degradation. First is just that PrProCS4 was getting its knickers in a twist and thereby just doing more computation per minute of video to be rendered as time went by, maybe internal resource management related to OO-type programming maybe, or related to disk IO falling behind, both these theories have problems, for the latter the CPU usage should then have dropped also.
Anyways, you need really a Quadcore system and blazing fast disk to work fully with AVCHD commercially, we found an external SATAII disk so if I were you I would just go get one and move on with your life.
Message du 03/06/09 16:08
De : "Jim Simon"
A : "JONES Peter"
Copie à :
Objet : Premiere Pro and Adobe Media Encoder running slow
For AVCHD you MUST have FAST disks.
AVCHD actually has a lower data date than DV. You need lots of CPU muscle, but disk speed is really not a factor specific to AVCHD. Anything that works for DV will work just as well for AVCHD (and HDV as well).
>

ERROR: DF024: Adobe Media Encoder CS6

I Have a 2012 Mac Pro running Mavericks. I started having issues with Premiere Pro after video card upgrade. I get the following error message when trying to reinstall CS6 Production Premium:
Exit Code: 6
Please see specific errors below for troubleshooting. For example, ERROR: DF024 ...
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 1 error(s)
----------- Payload: Adobe Media Encoder CS6 6.0.0.0 {CC006FD6-00EF-46FC-ACA0-7A28EFF44D20} -----------
ERROR: DF024: Unable to preserve original file at "/Applications/Adobe Media Encoder CS6/Adobe Media Encoder CS6.app/Contents/Frameworks/AdobeCrashReporter.framework/AdobeCrashReporter" (Seq 309)
I backed up, and deleted all Production Premium applications; ran the CC sweep tool, and got the same error.
Can anyone recommend a fix, or point me in the direction of an Adobe tech for more answers?

Oké, the next steps will remove all Adobe folders from your system, so put's you in a clean state where you should have no issues re-installing. Please be sure you have settings saved as a backup. The locations below will only clean the Adobe applications.
1. Please remove all adobe software from the machine (use uninstall or use the clean-tool)
Steps see: http://helpx.adobe.com/creative-suite/kb/cs5-cleaner-tool-installation-problems.html
2. Remove by hand all still existing Adobe entries: http://helpx.adobe.com/x-productkb/global/delete-previously-installed-application-files.ht ml
~ Files / Folders ~
/Applications/Adobe*
/Applications/.AdobePatchFiles
/Applications/Utilities/Adobe*
/Library/Application Support/Adobe*
/Library/Application Support/FLEXnet Publisher/
/Library/Preferences/com.adobe*
/Library/Preferences/FLEXnet Publisher/
/Users/[user]/Library/Application Support/Adobe*
/Users/[user]/Library/Caches/Adobe*
/Users/[user]/Library/Caches/com.adobe*
/Users/[user]/Library/Preferences/Adobe*
/Users/[user]/Library/Preferences/com.adobe*
+ Please notice that the [user] library in above steps is hidden by default:
http://helpx.adobe.com/x-productkb/global/access-hidden-user-library-files.html
3. Re-install and update the software.
http://helpx.adobe.com/creative-cloud/help/install-apps.html see Update apps
Good luck!

Adobe Media Encoder cs6 error 0xc000007b

Recently i installed Adobe Media Encoder CS6 , on start it showing application unable to start due this error 0xc000007b, please resolve ASAP, if anybody knows.

I just want to make sure anyone with the same problem who comes across this thread is made aware of some things to try and at least one solution that has worked for multiple people...
As the Adobe Staff member here mentioned, the 0xc000007b error usually has to do with a 32-bit/64-bit confusion on the machine. More specifically, as someone stated in a Windows forum: "this error is most likely a result of a 32-bit (x86) executable trying to load a 64-bit (x64) DLL."
http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/error-the-applicati on-was-unable-to-start/05a2b904-3f61-4d08-94d6-e2ff92161111
What has worked for others is copy & pasting the msvcr100.dll & msvcr80.dll files from the After Effects Support Files folder to the folder of the app that is giving this error (usually Media Encoder or Premiere Pro or Lightroom). It was mentioned several times in the threads below, and worked for me as well...
http://forums.adobe.com/message/5020877#5020877
http://forums.adobe.com/message/4861711#4861711

Mac Pro restarts with kernel panic error during Adobe Premiere CS6 or Adobe Media Encoder CS6 render/encode.

Multiple times this week, my Mac Pro at work has been restarting during renders in Adobe Media Encoder CS6 and Adobe Premiere CS6. This seems to be specific on this computer only. Identical computers don't have this problem. Here is the system report after it reboots to OS X:
Interval Since Last Panic Report: 252068 sec
Panics Since Last Report:          2
Anonymous UUID:                    7DF9A04B-0693-5FC4-60CF-4BC6ABDB3C1E
Fri May 17 15:37:07 2013
panic(cpu 0 caller 0xffffff8009ab7e95): Kernel trap at 0xffffff8009e1b814, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x00000000000000b8, CR3: 0x000000000c3d3000, CR4: 0x00000000000206e0
RAX: 0x0000000000000001, RBX: 0xffffff8039ebfb98, RCX: 0xffffff800a08eb00, RDX: 0xffffff82413abde8
RSP: 0xffffff82413abde8, RBP: 0xffffff82413abe20, RSI: 0x00000000000000b8, RDI: 0x0000000000000001
R8: 0x0000000000000000, R9: 0x00000000000003ff, R10: 0xffffffffffffffff, R11: 0x00000000ffffffff
R12: 0x000000000000004a, R13: 0x0000000000000371, R14: 0xffffff8040611cb0, R15: 0xffffff80404ec008
RFL: 0x0000000000010206, RIP: 0xffffff8009e1b814, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x00000000000000b8, Error code: 0x0000000000000002, Fault CPU: 0x0
Backtrace (CPU 0), Frame : Return Address
0xffffff82413aba80 : 0xffffff8009a1d626
0xffffff82413abaf0 : 0xffffff8009ab7e95
0xffffff82413abcc0 : 0xffffff8009acd4dd
0xffffff82413abce0 : 0xffffff8009e1b814
0xffffff82413abe20 : 0xffffff7f8bcf4d54
0xffffff82413abe60 : 0xffffff7f8bcf72f1
0xffffff82413abf20 : 0xffffff8009d86e2b
0xffffff82413abf60 : 0xffffff8009a3dcfe
0xffffff82413abfb0 : 0xffffff8009ab2977
      Kernel Extensions in backtrace:
         com.apple.nke.asp_tcp(7.0)[78FAA01C-ABC4-3AD3-8D9A-6187F7911E1A]@0xffffff7f8bce f000->0xffffff7f8bcfbfff
BSD process name corresponding to current thread: kernel_task
Mac OS version:
12D78
Kernel version:
Darwin Kernel Version 12.3.0: Sun Jan 6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64
Kernel UUID: 3EB7D8A7-C2D3-32EC-80F4-AB37D61492C6
Kernel slide:     0x0000000009800000
Kernel text base: 0xffffff8009a00000
System model name: MacPro5,1 (Mac-F221BEC8)
System uptime in nanoseconds: 76945023460235
Model: MacPro5,1, BootROM MP51.007F.B03, 8 processors, Quad-Core Intel Xeon, 2.4 GHz, 20 GB, SMC 1.39f11
Graphics: ATI Radeon HD 5770, ATI Radeon HD 5770, PCIe, 1024 MB
Memory Module: DIMM 1, 4 GB, DDR3 ECC, 1066 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 2, 4 GB, DDR3 ECC, 1066 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 3, 1 GB, DDR3 ECC, 1066 MHz, 0x80CE, 0x4D33393142323837334648302D4348392020
Memory Module: DIMM 4, 1 GB, DDR3 ECC, 1066 MHz, 0x80CE, 0x4D33393142323837334648302D4348392020
Memory Module: DIMM 5, 4 GB, DDR3 ECC, 1066 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 6, 4 GB, DDR3 ECC, 1066 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 7, 1 GB, DDR3 ECC, 1066 MHz, 0x80CE, 0x4D33393142323837334648302D4348392020
Memory Module: DIMM 8, 1 GB, DDR3 ECC, 1066 MHz, 0x80CE, 0x4D33393142323837334648302D4348392020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.106.98.100.16)
Bluetooth: Version 4.1.3f3 11349, 2 service, 18 devices, 1 incoming serial ports
Network Service: Ethernet 1, Ethernet, en0
PCI Card: ATI Radeon HD 5770, sppci_displaycontroller, Slot-1
Serial ATA Device: HL-DT-ST DVD-RW GH41N
Serial ATA Device: WDC WD1001FALS-41Y6A1, 1 TB
USB Device: Keyboard Hub, apple_vendor_id, 0x1006, 0xfd300000 / 2
USB Device: Apple Keyboard, apple_vendor_id, 0x024f, 0xfd320000 / 3
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x5a100000 / 2
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8215, 0x5a110000 / 3
FireWire Device: built-in_hub, 800mbit_speed

That doesn't look like a complete panic report. Is there any more to it? Regardless, I suggest you run the extended form of the Apple Hardware Test. If it fails to identify a fault, remove the RAM upgrade and test with the original RAM.

Adobe Media Encoder CS6 Random Crashing Mid-Render

Hello -
I've been dealing with this issue for enough months and across enough computers to finally seek out some advise here, hope it works out...
Basically I've got a 2 hour long film that I've been trying to export using Adobe Media Encoder CS6. It's never made it all the way through. I can usually skim through the generated quicktime file up to the point where the crash occurred. I've tried using that as a reference to check out my sequence in Premiere but there is never anything suspicious going on there. Most frustratingly the crash occurs randomly. Sometimes it will go through 10 minutes of the film; sometimes an hour. Regardless I get a crash with a report that has no specific information.
Footage:
r3d - Various resolutions, all being cut in a 2048x1152 sequence.
Quicktime mov - ProRes4444 for the most part.
Machine(s):
I had been attempting to render this for the past few months with a Macbook Pro running OSX 10.8.4 w/ 16GB RAM, 2.7 GHz Intel i7, NVIDIA GeForce GT 650M 1024MB - never made it through a render longer than 50 minutes of the 2 hours.
We recently got one of the new 2013 Mac Pro systems running OSX 10.9 w/ 16GB RAM, 3.5 GHz 6-Core Intel Xeon E5, AMD FirePro D500 3072 MB
The hope was that this new powerful machine would overcome the issues we were running into with these renders. Since I'm posting this now you can probably figure out that it didn't really work out that way...
Software:
AME- 6.0.2.81
Premiere - 6.0
I know there are updates to be used here, but whenever I update Premiere from just 6.0, the project itself becomes a buggy mess, crashing constantly. I also run Creative Cloud and have tried to just jump over to Premiere CC hoping all my problems would vanish, but instead, I again get a buggy project that constantly crashes. The only version of Premiere that seems to work with this project is 6.0, so general updates have not been useful (and instead damaging, I've wasted several days trying everything I possibly can to make the project work in the updates).
Any help appreciated. Thanks.

Thanks for the reply MMeguro.
Last night I was able to get my first full render through by doing a combination of things (so I'm not sure what did the trick in the end).
To answer some questions first, never attempted to do the FULL render directly out of Premiere, always switched over to AME for that, so that potentially could work too. Smaller renders have worked directly out of Premiere Pro, but they've also worked out of AME.
The initial render attempts that had been failing for the last few months were on the MBP which did not support GPU accleration due to an incompatible graphics card. I assumed the issue must be tied to something else because of this and was using it on the renders with the new 2013 Mac Pro. Using the workflow of Pr6.0, AME 6.0 and GPU rendering turned ON, I was failing to render to both Quicktime h264 and ProRes 422.
What worked for last night's render:
1. Convert Pr6.0 project to PrCC project (when I've done actual editing in CC after converting this project it tends to crash, but I figured just generating the project itself without doing any editing in it might satisfy what I was attempting to do).
2. Open AME CC and import PrCC Sequence. Used custom ProRes 422 setting.
3. Turned OFF GPU acceleration.
So as long as I the PrCC project I create stays stable long enough to save it (without crashing, which has been a problem with that Pr6.0 to PrCC conversion) then it seems like this will work. Kind of an annoying couple extra steps but I'm just out of my mind glad that I can actually render this thing finally. We're still in the rough stages so being able to turn around a review version within a day is very important.
Wish I could do more tests to figure out exactly which combination actually made this work for the benefit of others, but can't afford to do multiple 10 hour+ renders with random crash times.
Anyway, thanks again for the reply MMeguro much appreciated.

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.

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.

Adobe Media Encoder CS6 (6.0.1) update available

The Adobe Media Encoder CS6 (6.0.1) update is available.
It has bug fixes and some new features.
You'll see from the post above that one of the features is left somewhat unexplained for the moment. That's because we wanted to get the bug fixes for Adobe Media Encoder out as soon as possible, rather than hold this update and wait for it to coincide with certain other events. Stay tuned. We'll have more information about that new feature quite soon.

I'm having a problem with Media Encoder 6.0.1 - it will encode for a few minutes, then slow down and sit, and then stop with an error (Error compiling movie. Unknown error). This happens with both h.264 and MPEG2, exporting 1080p. This is with Windows 7, and the Task Manager shows the used memory increase and the CPU usage increase when ME starts, and when it slows down the CPU usage stops and the memory usage goes down.
(When it stops with the error it makes a loud noise, like a goat dying! Must be the programmers idea of how to notify there is an error!)
This is happening on two different computers running Production Premium CS6 , and is pretty consistent between the two. I don't know if ME 6.0 had this issue, only had CS6 a few days before the 6.0.1 update and may not have exported a file. There have been no encoding issues at all with CS5 and CS5.5.
Any ideas what is causing this - something in the setup? A bug?

Adobe Media Encoder CS6 crashes when quit

OS X 10.7.4
Multiple hardware types
Adobe Media Encoder CS6 as installed from Adobe Production Premium CS6. NOTE: CS6 was installed under a different user than the new user that is having AME crash.
Issue:
Open AME. Encode a file or do not encode a file because the end result does not matter. Now quit AME (either hotkey or File --> Quit). AME then crashes. Keep in mind that no other CS6 programs are affected this way, just AME.
I ran into this problem weeks ago and found a solution that worked. The fix was to delete one of the many many folders Adobe creates in your user folder. The problem now is I cannot find that same posting where the fix was listed.
I deleted this "mystery folder" we will call it and then AME CS6 worked fine. The catch was that I had to redo the whole "Adobe ID" sign in BS and retype the serial number when I opened one of the other programs.
Any guesses as to where this folder might be so I can delete it again? I was hoping some others may have run into this same issue. I will keep looking for the fix, and post it back here if I finally find it.

Just deleting the Adobe Media Encoder folder in the given directory works just fine and this saves a lot of trouble because your settings are maintained as are your presets.
But thanks a lot for the help

Adobe Media Encoder CS6: Freezes after starting encoding process

Adobe Media Encoder CS6: When trying to export media I Click on the Queue tab. I then click the Start button. The program shows the first few frames in the review window and then freezes with no error codes or any other notifications. Clicking on the S
I am running Adobe Media Encoder CS66.0.3.1 on Win7 64 with Intel i7-4770K CPU 16 GB Ram.
The source file is 1920 X 1080 29.97 fps. Output file is H.264 Android Tablet 1080 P 29.97 fps
I do not see any indication what so ever of what is going wrong. I have uninstalled the program completely and re installed it with no effect.
Need some help!

Can you export directly from Premiere Pro?
Have you tried disabling GPU acceleration?

I cannot run Adobe Video Encoder, I get this error: ' Adobe Media Encoder CS6 6.0.1 Update Installation failed. Error Code: U44M2P7'

I cannot run Adobe Video Encoder, I get this error: ' Adobe Media Encoder CS6 6.0.1 Update Installation failed. Error Code: U44M2P7'

Hi
Uninstall the Adobe Application manager from your computer.
and download the latest version of the AAM from the below mentioned sites.
http://www.adobe.com/support/downloads/detail.jsp?ftpID=4774- For Mac
http://www.adobe.com/support/downloads/detail.jsp?ftpID=4773 - For Windows
Once installed , Then try to update the application by launching the application and Help--> Update
Hope It Helps
Thanks

How to register adobe media encoder cs6

Please anyone could explain to me how to register Adobe Media Encoder CS6. When I installed the new AP 10. I began to prepare my presentation and when I tried to import a video from my hard drive to a slide. It prompt a message Thanks for using AP 10. The product you have installed have not been registered yet. ....
Thanks in advance

El 25-08-2014, a las 2:05, Jay13 <[email protected]> escribió:
How to register adobe media encoder cs6
created by Jay13 in Adobe Presenter - View the full discussion
Hi terapaca,
Is your AP 10 licensed? if not can you please License it and then Check.
If it is licensed and still you are getting the same issue then please do the following.
Please provide us with the Screen shot of the prompt and "oobelib.log" file.
The location of "oobelib.log" is :-
If you are using windows:
C:\Users\<User name >\AppData\Local\Temp
OR
just open the run the window and type %TEMP%
For Mac
/Users/<user name>/Library/Logs
Please provide the above files so that we can look into the issues soon.
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at https://forums.adobe.com/message/6670470#6670470
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page:
To unsubscribe from this thread, please visit the message page at . In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Adobe Presenter by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/thread/416458?tstart=0.

Adobe Media Encoder CS6 - Startup crash

I am not able to start Adobe Media Encoder CS6 on Mac (Lion 10.7.3) - it always tries to load and gives me an "Adobe Media Encoder CS6 quit unexpectedly"
This happens with a freshly installed Web & Design Suite AND on both of my Macs.
I just re-installed Flash CS6 to verify - and still, no chance to open it.
Super annoying! What can I do?
Thanks
Steffen Funke

So, I was able to resolve it based on this (old) thread which deals with the same kind of problem under CS5:
http://forums.adobe.com/message/3975390
In short: delete the "Adobe Media Encoder" Folder from your User Preferences (/<Username>/Library/Preferences/Adobe Media Encoder).
It will be recreated on next Startup.
What was strange was, that I need to provide admin password for deleting the Folder, although i's under my User Prefs.
This should not be the case and I suspect this to be the reason for the crash (Folder rights issue, preventing Adobe Media Encoder from writing in it's own Preferences Folder)
Hope this helps someone else.

MPEG-2 codecs missing from Adobe Media Encoder CS6 installed with Creative Cloud Membership

Some people who have downloaded Adobe Media Encoder with Premiere Pro CS6 as part of a Creative Cloud Membership subscription have a problem in which the MPEG2, MPEG2-DVD, MPEG2-Blu-ray, Dolby Digital, & MXF OP1a codecs are missing.
To fix this issue, install the Adobe Media Encoder CS6 (6.0.1) update. Choose Help > Updates to install the update.

It's true. We reached the conclusion that the version CS6 is inferior, a step back, than 5 or 5.5. What's good about it, is the Audution CS6, which is a great replacement for the flawed Audition CS5 accompanying Suite 5.5. You can almost forget the Soundbooth ... Soundbooth ... hmmm, better not comment, but anyway, the most polite thing that i can say it, is that it is a demonstration of how a company decides that its users are not able to think and not able to learn or understants anything. Anything else that i want to say about Soundbooth can not be written here ....
Adobe has demonstrates this development cicle along all this years. The products takes an uphill curve of development, and suddenly, goes back, showing wrong decisions was taken. So after some time , the products starts to evolve again . CS6 shows this stop evolving point. Now we have to wait untill new uphill curve of development starts again.
Well, but like their predecessors AA CS6 still not are good enough to dispense Audition 3, but it is a good outcome for the Suite CS5.5 Audition at least was a sign of improvement in this Creative Suite CS6
Many of the features and effects that have been deliberately taken out of version 5, now returned in 6, (some) showing that at Adobe at least recognizes when misses badly. But the optimal effects panel of AA3 did not return, some effects of AA3 as fade in and fade out did not come back in AA 6, the optimum VST support of AA3 to not are present in AA6 like many VST we have here that was expensive, you do not work in 6, thus, by these and other reasons we can still not dispense AA3.
Maybe in CS7 we users cam be satisfied.

GoPro Hero 3 Black 4k and Adobe Media Encoder CS6

Similar Messages

Maybe you are looking for