Premiere CC and/or Media Encoder audio bad renders

Occasionally, but not always, when I export a timeline to Media Encoder queue, the video renders out with no audio.
I have not found a repeatable way to replicate this, but when it happens, it really blows up my workflow.
Typically I:
Import a ProRes 1080 clip into a fresh timeline, and only trim down the ends. Audio and Video playback great in premiere. I then, without changing anything, export to media encoder queue in h.264 1080p OR 720p (vimeo preset).
The queue runs and bang, video file with no audio.
My extended workflow is as such - once the h.264 file has arrived in the folder (it is a watchfolder), there are presets set to create OTHER Files - wav for CD, mp3 for podcast, DVD for distro, mp4 for podcast. So, as you can see, it snowballs into a trainwreck. I would also automate/schedule the podcast postings, but obviously I can't rely on media encoder/premiere to do it's job.
Has anyone experienced any lack of audio render issues? Is it tied to hardware at all, or is it just freak randomness? I even got to point to where I reboot the machine right before each original capture begins, but the error is always in the first render out of premiere.
I have checked for any muted tracks and such, and there are none. As I said, it is VERY random. For instance, this week, I dropped the capture into a timeline, exported as usual, and got a bad render. Did it again, this time moving the audio down a track. Still a bad render. Rebooted the Mac, tried it all again, and finally got a working render. This is the first time it has happened TWICE in a row, and I'm getting tired of it, as these renders are fairly long.
Any help would be much appreciated.
- Ben

Ben, I'm having the same issue.  Never had it before yesterday. 
I'm editing on CC with R3D's.  I have 8 tracks of audio.  When I'm exporting (either through Encoder or through Premier) I'm getting a final product that has no audio, and in its place a loud clicking sound.  I performed a number of reboots and got it to export once.  But I've tried dozen's of times now and can't get audio to export through this sequence. 
When I go to render the project I'm getting an "Error Compiling Movie.  Unknown Error" message.   I suspect that's related.  Not sure what's happening.  I'm going to keep testing.  I'll let you know if I discover anything.  But it is VERY FRUSTRATING:(  Deadlines are looming. 
-Brian

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).
    >

  • Premiere Pro CC 2014 & Media Encoder Crash when rendering

    Every time I try and render something out of Premiere Pro CC 2014 it will crash before it completes the render. I have no idea why. I am on a windows 8 machine running the latest version of Premiere Pro CC 2014.Any idea what is going on?
    Here is the log from Event Viewer:
    Faulting application name: Adobe Premiere Pro.exe, version: 8.0.1.21, time stamp: 0x53c7b17f
    Faulting module name: mc_enc_avc.dll, version: 9.8.11.6624, time stamp: 0x536af65d
    Exception code: 0xc0000005
    Fault offset: 0x00000000000e7f80
    Faulting process id: 0x650
    Faulting application start time: 0x01cfb99562fe469a
    Faulting application path: E:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
    Faulting module path: E:\Program Files\Adobe\Adobe Premiere Pro CC 2014\mc_enc_avc.dll
    Report Id: f30f38a1-2589-11e4-bf2c-bc5ff467c039
    Faulting package full name:
    Faulting package-relative application ID:
    Here is the Report.wer that windows automatically generates: http://pastebin.com/hriEegkJ
    I have also tried rendering out of media encoder and I get a crash also (Report.wer: http://pastebin.com/Dpvk6bDb):
    Faulting application name: Adobe Media Encoder.exe, version: 8.0.1.48, time stamp: 0x53c99d97
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x000000002c2cce3d
    Faulting process id: 0xcf8
    Faulting application start time: 0x01cfb9906060796e
    Faulting application path: E:\Program Files\Adobe\Adobe Media Encoder CC 2014\Adobe Media Encoder.exe
    Faulting module path: unknown
    Report Id: 07096c20-2584-11e4-bf29-a0f3c1153ce7
    Faulting package full name:
    Faulting package-relative application ID:

    More hardware information might help someone give you an idea
    -Premiere Pro Video Editing Information FAQ http://forums.adobe.com/message/4200840
    or
    http://blogs.adobe.com/kevinmonahan/2014/01/13/computer-shuts-down-with-premiere-pro-or-af ter-effects/

  • Premiere, After Effects, Speedgrade, Media Encoder and... the dynamic link

    My feeback after working with the dynamic link these days. Basic project. Editing, color correction, animated titles.
    I'm using a 3.5Ghz iMac 24GB Ram and a GTX 780 4GB. (2014 versions & last updates).
    Rendering the timeline in Premiere is sometimes extremly slow (with AE comps). Need to quit and reload the project to get a good speed.
    Too long delay of refresh for the AE compositions inside Premiere (with the dynamic link). Need to go in AE then back to Premiere to get the refresh.
    When i export to media encoder i need sometimes to save then send it 2 or 3 times to get the last edits in the export.
    Even worse with the AE compositions. If i change something in AE then export from Premiere i need to quit and reload Media Encoder to get the last changes.
    Really fast export from Premiere to Speedgrade and from Speedgrade to Premiere.
    But !!! Lumetri fx is not compatible with AE.  And Speedgrade doesn't support BlackMagic but only this nVidia Sdi thing.
    And why we could not export h264 from AE anymore ???
    Quiet disappointing :-(

    Using Premiere Pro CC 2014.0.1 (build 21) and Media Encoder 2014.0.1 (build 8.0.1.48) on OS X 10.8.5
    If I Export a video from Premiere, I can continue using Premiere, but if I Queue an export, returning to Premiere produces the beach ball of death. If I give it time, the beach ball goes away and the arrow returns, but trying to click anywhere in Premiere simply returns the beach ball. There is nothing to be done but Force Quit Premiere. I can leave Premiere and run any other application, but if I leave to execute the Media Encoder queue, I cannot return to Premiere and use Premiere. I can visit Media Encoder (call it to the foreground) and return to Premiere after the queue is done.
    My current workaround is to use Export from Premiere and not use Queue from Premiere.

  • Premiere Pro CS4 and Adobe Media Encoder Problems

    I am using Adobe Premiere Pro CS4 on a Mac running 10.6, and I consistently encounter this problem when trying to export a Premiere project using Adobe Media Encoder.
    What does this mean? And has anyone else encountered this problem as well? I really need a fix if there is one, because I really need to be using Premiere. I have reinstalled several times, but to no avail. Help me please!

    Jim, thanks for testing.
    My concerns are about a)distribution and general b)compatibility.
    a) When videos are distributed most of the users will probably try to open the files with Windows Media Player. So it is not a good start to have fresh exported h.264 videos which won't run fine with the 'main' player on windows
    b) I am wondering if the Problems with Windows Media Player may also be a sign of a general compatibility issue of the h.264 video itself
    At least in case b) Adobe would have to look into this.
    Here is another test video:
    http://www.tsxn.com/storage/transfer/Serenity.zip
    Thank you
    Chris

  • I cannot import .mov files to Premiere Pro or Adobe Media Encoder.

    I cannot import .mov files to Premiere Pro or Adobe Media Encoder.
    How do I around this problem?

    We need to know a lot more if we're going to help you.
    What happens when you try? Do you get an error message? If so, exactly what does it say?
    What version of Premiere Pro? Have you installed the recent updates? What operating system?
    Does this happen for all .mov files or just some? Has this ever worked before? What version of QuickTime do you have installed?
    Here's a page written for After Effects, but the information is relevant to Premiere Pro and AME, too:
    http://blogs.adobe.com/toddkopriva/2011/02/troubleshooting-quicktime-errors-with-after-eff ects.html

  • Premiere now freezes on Media Encoder Queue

    After updating to the Oct 2014 CC Update, upon exporting media using the Media Encoder queue, Premiere freezes on the "Preparing Data for Export" box.  It launches Media Composer, but it never makes it out of Premiere.
    Just exporting from the application works, as well as importing sequences straight into Media Encoder.  But I need the queue to work.
    On a Windows 8.1 PC
    24b 1333 mhz ram
    3.2 ghz Intel Processor
    NVIDIA Quadro FX 3800
    R

    I am having the same problem (see Premiere now freezes on Media Encoder Queue)
    I am on 2014.1 of both programs (8.1.0 on premiere, 8.1.0.122 of AME).  I know an update just came out today, but it seems to be just a RAW photo update.
    Mine hangs when premiere is "Preparing Media for Export..."  It launches AME and AME boots up fine... so from where I sit, it looks like a Premiere problem as it's compiling the project file to export.
    Neither "import natively / non natively" or GPU acceleration help.  However, I wouldn't expect them to, given this seems to be a premiere problem, not an AME problem.
    That thread does not apply re: nView.
    R

  • GPU acceleration is grayed out in Premiere and AE, but not in Media Encoder. However, rendering is slow in all 3 programs.

    It worked fine in CS6.
    Now, everytime I open a project (Pr or Ae) I get the message: This project was last used with GPU Accelerated rendering. This happens with all projects, even with those that I created in Pr/Ae CC, with GPU Accelerated rendering already disabled.
    In Media Encoder, the GPU Acceleration is not grayed out, but still if I render a premiere sequence or an ae comp via ME, its very very slow. (takes 5 hours for a video that took 20 mins in CS6)
    Any thoughts?
    Thanks, Daniel

    I think I found the problem. On the website you linked, it says:
    The following notebooks are not compatible with this tool:
    Notebooks equipped with switchable graphics
    Toshiba® notebooks
    Sony® VAIO® notebooks
    Panasonic® notebooks
    And I have a Sony VAIO.
    When searching for drivers, I only found sites like these: AMD Radeon HD 7650M drivers
    Are these legit?

  • Premiere Pro and Media Encoder crash while rendering H.264

    Very recently, a problem's popped up where Premiere Pro and Media Encoder (CC) will crash while rendering H.264.
    It's only while rendering H.264 - other formats seem to work fine.
    And I don't mean that it returns an error, I mean it hard crashes with a Windows "Adobe Premiere Pro CC has stopped working" popup.
    It doesn't crash at a consistent time during the render, even on the same project. Occasionally, it won't crash at all, but this is usually not the case.
    I've tried disabling CUDA and my overclock to no avail. Please help!

    On the topic of opening a project on the exact same version of Premiere Pro CC 2014 (yes it is definitely up to date, and the 2014 version), to overcome this export crash problem that ZachHinchy has brought up - you can't. Technically speaking, one should easily be able to open a Premiere Pro CC 2014 project from one system on another system running the exact same up to date, legitimate version of Premiere Pro CC 2014 without any kind of error. But for some reason, this has been disallowed(?) by Adobe. It has facepalm written all over it. Does anyone agree that this is at least a little bit silly?
    I have tried exporting a Final Cut Pro XML from my project to try and open the sequence at uni on a Mac, so I can render my project when I finish my edit. It half works - the clips are there, but the sequence is gone - i.e. 12 hours of painstaking sequencing and micro-edits that had me at several points in time wanting to insert my hand through my monitor with enough force to make a large hole. I really cannot afford redo this sequence, as my assignment is due tomorrow, and I have to work at 6 oclock in the morning, so I also cannot afford to stay up till the early hours of tomorrow morning. Wish me luck that some miraculous event has taken place overnight that will somehow allow me to just open my project, on the same version of Premiere, on a Mac, without hassle. (Apple OS is not friendly to anything but its own selfish nature, so I am having doubts).
    Adobe please, if you can do anything at all to help, you will save my assignment, and my faith will be restored. Otherwise, I'll just get my money back and buy Final Cut instead.
    I cant even
    If I find a way to fix either of these problems, I will post straight away.

  • Issues rendering Premiere CS4 movie with Media Encoder

    I'm new to this but thought that someone might be able to provide some insight. I have Premiere CS4 and created a movie from a HD video camcorder.
    The imported clips are in the following format:
    Type: MPEG Movie
    Image Size: 1920 x 1080
    Pixel Depth: 32
    Frame Rate: 29.97
    Source Audio Format: 48000 Hz - compressed - Stereo
    Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
    Average Data Rate: 1.3 MB / second
    Pixel Aspect Ratio: 1.0
    Now I'm simply trying to export the movie (Ctrl+M) using Media Encoder. I've been messing around with several different formats, including H264, MPEG and AVI and so far regardless of what output format I pick (even downsize) I'm getting some sort of "tearing" up in my clips. I'm not entirely sure how to describe this but it almost looks like a ghost effect with subjects leaving a ghost image when the scene starts moving around a bit.
    I rendered the same exact clip using Windows Movie Market just for the sake of it and everything looks fine.
    I'm rendering the clip on a Core i7 920 @3.7Ghz with 6GB of RAM so I don't think the speed is an issue as either (HD is a 300GB Velociraptor).
    Any ideas what I am doing wrong
    Thanks,
    Sam

    >Any ideas what I am doing wrong
    Second thing wrong is posting in this forum. People in the Premiere forum will do a better job of offering help This forum is dedicated to helping people with suite-wide issues such as installation.

  • Media Encoder isn't rendering all my audio tracks?

    I've been using Media Encoder to render my Adobe Premiere sequences and up until yesterday, I never had a problem with it. Out of nowhere, it won't render more than 2 audio tracks. The audio plays fine in the timeline preview in Adobe Premiere, but when I render it, some of my audio is missing! I have no idea what could be causing something like this!
    I'm rendering in h.264 at Youtube 1080p 29.97 settings. I've done this for all of my previous videos and haven't had a single problem having 3+ audio tracks until the last two videos I've done

    Sometimes a project can be weird/corrupted and do strange things. Then you need to outsmart the computer. For example, try an audio-only export. Create a .wav file and import back into project, and if all tracks are properly represented in that mix, add .wav to timeline, mute all other audio tracks, and do your final AV export using that new audio.
    Thanks
    Jeff Pulera
    Safe Harbor Computers

  • Media Encoder - very bad resizing quality

    The problem is when i want to resize HD video from it's original size 1440x1080 50i (16x9) to DV PAL 720x576 (4x3) 50i to the full frame size (without black borders) using crop - the video quality even in preview looks really bad. The whole image gets blurry and kinda "half resolution" looking.
    I think it's a bug of media encoder 4.0.1
    This is really annoyingg cause we're filming using XDCAM and clients often want to get material in DV PAL. Any solutions?
    The same thing done and rendered natively in After Effects looks fine

    Try importing the clips into Premiere and resizing them manually in the timeline. Then send those off to Media Encoder. Make sure you select "Maximize Render Quality" from the sequence settings or use "Maximum Render Quality" in your export settings.
    There was a similar issue with CS3 when "Scale to Frame Size" was selected on a clip. The resulting video was softer using this feature compared to resizing the clip manually.

  • 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: Audio won't export with video

    I am trying to convert an AVCHD video for viewing on my iPad 3. I use Adobe Media Encoder and select the iPad 2 settings (1920x1080) and it exports the video perfect, but no audio. I have "Export Audio" checked off. I tried it with 5 other settings and it just wont include the audio. Any ideas?

    Seems random people are running in to this, so hopefully this solution will be found by whomever's looking.
    If you're exporting video files from Final Cut Pro as .mov, and then trying to convert said .mov to an .mp4 using Adobe Media Encoder and are losing audio even though you're multiplexing, try this...
    Make sure that you export only a 2-channel audio track from FCP.   When I export from FCP, I split my audio into various tracks by default.  Great for making master clips, but problematic if uploading to YouTube or doing further encoding in Adobe Media Encoder.   Like YouTube, if you have more than 2 tracks of audio, Media Encoder seems to get confused and ignores all audio tracks.  Combine all audio into a 2-channel stereo track and see if that solves the problem.
    Regardless of editing program, see if reducing number of audio channels from source clip solves problem.

  • Adobe Premiere Pro CC or media encoder MFX OP1a Bug

    Hi I'm outtputting for broadcast TV Commercial and getting a consistant audio issue with adobe premiere pro cc MFX OP1a using IMX30 pal export master. Orginial project is HD exported AVI from After effects, audio is .wav 48k. The audio has a glitch where it almost seems to drop out by a frame. I tried this over and over again with all my projects and the same issue. It's usually around 1 second in and occurs once. My projects are 30 second in length or 15 second at a time. I have ended up going back to Adobe CS6 so I can fix this issue and send to the tv station for playout (cs6 is fine). Is there any chance someone could look into this or check to see if there is an issue here?  I have tried this on all our computers here running CC and the same issue.

    Bumping this as it seems to be an update issue. I have noticed it now with premiere pro cs6 update. Works fine for 6.0.3 but the update to 6.0.5 has the same issue as above. Have reported this to Adobe however don't see any changes, this is a major problem since this is the broadcast standard for uploading to station down in NZ and the media uploaded has confirmed other cases of this issue around.

Maybe you are looking for