Media Encoder making 4K output file 'blink'... What is going on?

Working off Premiere CC. I have a 4K sequence displaying two 1080p videos side-by-side to compare quality between HEVC and H.264. Effects includes dissolves, freeze frames, and word labels created with Premiere's title maker.
Watching all the way through in Premiere timeline on my new Mac Pro it works fine. All video loaded, audio playing back, everything is great.
Ctrl+M, settings include Quicktime, Apple ProRes 422 (HQ) (have also tried Uncompressed YUV 10 bit 4:2:2 as an alternative to no avail), 3840x2160, 29.97, Progressive, Square Pixels, check box on 'Render at Maximumm Depth and 'Use Maximum Render Quality'. Queue it up, hit play and the video encodes fine for a while. Then, during a random transition, the little preview monitor on the encoder starts blinking! Sometimes the top half of the screen, sometimes the entire screen. Upon review of the final output shows that the preview was telling the truth.
Help! What is going on?!

Hi bgmc101,
bgmc101 wrote:
Hello Kevin,
Thanks for getting back to me. It's not actually HEVC. We load in the uncompressed AVI clips into Premiere instead. If they were real HEVC then Premiere wouldn't even let me import them, yes?
Right! I was confused about how you even imported the footage.
bgmc101 wrote:
The blinking does not start until 50 seconds to a minute in, and randomly persists through the rest of the video. We've had to export 30 to 40 second segments of the video and stitch them together using our stuff... not the most favorable workflow.
Any ideas?
Are you exporting via the Export button (from Premiere Pro) or the Queue button (AME)? Does it work using the other method?
Thanks,
Kevin

Similar Messages

  • Premier Pro CC and Media Encoder crashing on long file export.

    Please forgive the length of this inquiry. But it is complicated and has a lot of variables.
    I have an hour long mixed format timeline both Red 3K footage and Black Magic ProRes 1080P footage that I want to make a DVD from and it takes forever and crashes half way through. I have tried doing it every way possible and the only way I was able to get even a partial export was using the "MPEG 2 DVD" export option in Premier CC. It goes fast at first telling me it will take about 2 hours but even though it starts quickly doing about 15 fps it slows down to less than 1 fps and finally just stops and crashes my Cuda Core enabled Macbook Pro Laptop.
    I really don't know who to ask about this since there are so many different variables. I never had a problem like this on my MBP with PP6 on a 4K timeline exporting to DVD or Blue Ray or to H-264 or Even Prores. But I wasn't mixing formats either. But on this project the first 20-30 minutes of footage goes through fine in a couple of hours but something seems to be bogging down the system on longer projects. My work around was to break the project up into multiple exports and combining them on the DVD timeline but I can't do this on every project. I thought maybe it was a corrupted clip somewhere in the timeline but when I broke the timeline up into several parts I had no problems.
    I did notice a dramatic variance in the time it took to export footage based on the sequence settings. A one minute timeline comprised Red 3K footage and ProRes 1080P footage Here are some sample export results:
    From a Red raw 3K timeline 2880x1620  with 1080P Prores footage upscaled 150%)
    to .m2v Mpeg 2 720x480 format    1:48 Minutes ***
    to .mov  Prores 422HQ  1080P                         22 Minutes
    to .mov H.264  1080P                    22 Minutes
    to .m2v Mpeg 2 1080P                                                22 Minutes
    From a 1080P timeline Prores footage at 100%  (Red footage downscaled to 67%)
    to .m2v Mpeg 2 720x480 format                         13 Minutes
    to .mov  Prores 422HQ 1080P                             13 Minutes
    to .mov H.264  1080P                                                             14 Minutes
    to .m2v Mpeg 2 1080P                                                            14 Minutes
    Since I am going to DVD,  I chose the fastest option  Red to m2v Mpeg 2 720x480 format which only took 1:48 per minute. Why? I have no idea. Maybe someone here knows the answer. But again these numbers are for a ONE MINUTE clip when I tried to convert the whole hour timeline to  the 720x480.m2v DVD File the Red timeline froze my computer after several hours even though I had set sleep mode to “Never” and turned the display off manually and I had to convert it in multiple chunks. In 20-30 minute chunks it did go fast about 1:48 per minute like the test indicated. But I would like to be able to convert the whole hour and not to have to try to stitch the clips together in my DVD authoring program.
    I don’t want to have to avoid using multiple formats on the same timeline or waste time transcoding everything to the same format.
    Can anyone give me any suggestions as to why the computer is crashing or bogging down in long exports and what timeline settings I should be using?
    I have plenty of room on my Scratch Disk and 8 Gig of RAM and according to my Activity Monitor during the export process  have about 800 Meg of System Memory during export but the CPU Usage is 98% and in my Activity Monitor I see under “Process Name” ImporterRedServer flashing up at the top of the list about every second during export.
    Why .720x480 mpeg DVD setting is so much faster than all the other export codecs?
    And if there are any other settings I can use to get higher speed exports in HD? 14x1 seems a little slow especially since every time it crashes I have to start over.

    Hi,
    Since a long time I did not encounter the crash of Media encoder with
    long file export.
    But I take care of a lot of details before the export :
    - clean up Media cache and Media Cache Files within PP CS6 and/or CC,
    - delete all render files with Preview Files,
    - rendering of sequences until the rendering is completed,
    - PP CS6 and/or Pp CC opened during export to AME and/or Encore CS6,
    I guessed to leave Adobe but this company remains the last with a
    serious authoring software (Encore CS 6).
    I tested :
    - Avid Media Composer, Final Cut Pro X, both are very good software but
    no really authoring software for these video editing softs.
    Th only way is to "flood" Adobe with "bug reports" and "wish forms"
    which are not very easy to use.
    And also to call the Adobe support day by day until they send they
    escalate the bug.
    Le 16/05/2014 16:51, alainmaiki a écrit :
    >
          Premier Pro CC and Media Encoder crashing on long file export.
    created by alainmaiki <https://forums.adobe.com/people/alainmaiki> in
    /Premiere Pro/ - View the full discussion
    <https://forums.adobe.com/message/6384665#6384665>

  • Adobe Media Encoder CS4 converted FLV files have sound but no picture

    Hi,
    It would be great if anyone can help - I am using the latest trial version of Flash CS4. I have used the Media Encoder to convert mpg4 files to FLV however the resultant files play with sound but no picture - just a black screen. Is there a solution to this issue?

    mostly this problem is caused by lacking of
    some nessery codec. Which means when reencoding your video to flv, it can not generate the video.
    Does Riva FLV encoder needs any extra codec? I am using Moyea Flash Video MX 6. It do not need any extra code. It needs in the former versions but in version 6 it can convert nearly any video format now.

  • I'm using CS6 Design Web & Prem.  When I use Media Encoder to convert WMV file to FLV the top portio

    Hi,
    I'm using CS6 Design Web & Prem.  When I use Media Encoder to convert WMV file to FLV the top portion of the video is not visible.  How can I fix the issue?
    Thanks!

    It's a Windows Update bug:
    WMV files corrupted on import or export
    Mylenium

  • I have just upgraded to the latest version of OSX as invited by Apple. Since then iTunes will not play and my volume controls have stopped working - in Preferences the sound controller is not able to find any input or output devices. What is going on?

    I have just upgraded to the latest version of OSX as invited by Apple. Since then iTunes will not play and my volume controls have stopped working - in Preferences the sound controller is not able to find any input or output devices. What is going on?

    Please read this whole message before doing anything.
    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
    The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, or by a peripheral device. 
    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode* and log in to the account with the problem. The instructions provided by Apple are as follows:
    Shut down your computer, wait 30 seconds, and then hold down the shift key while pressing the power button.
    When you see the gray Apple logo, release the shift key.
    If you are prompted to log in, type your password, and then hold down the shift key again as you click  Log in.
    *Note: If FileVault is enabled under OS X 10.7 or later, or if a firmware password is set, or if the boot volume is a software RAID, you can’t boot in safe mode. Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs. The next normal boot may also be somewhat slow.
    The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin. 
    There will be no audio output in safe mode. The question to be answered by the test is whether any devices are listed in the Sound preference pane. After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test.

  • There is an exclamation pt. next to several songs in itunes. When I click on that song, it can't locate it. When I click on locate, it pops up a menu with numerous files. I'm afraid to click on the files. What's going on?

    There is an exclamation pt. next to several songs in itunes. When I click on that song, it can't locate it. When I click on locate, it pops up a menu with numerous files. I'm afraid to click on the files. What's going on?

    This happens if the file is no longer where iTunes expects to find it. Possible causes are that you or some third party tool has moved, renamed or deleted the file, or that the drive it lives on has had a change of drive letter. It is also possible that iTunes has changed from expecting the files to be in the pre-iTunes 9 layout to post-iTunes 9 layout,or vice-versa, and so is looking in slightly the wrong place.
    Select a track with an exclamation mark, use Ctrl-I to get info, then cancel when asked to try to locate the track. Look on the summary tab for the location that iTunes thinks the file should be. Now take a look around your hard drive(s). Hopefully you can locate the track in question. If a section of your library has simply been moved, or a drive letter has changed, it should be possible to reverse the actions.
    Alternatively, as long as you can find a location holding the missing files, then you should be able to use my FindTracks script to reconnect them to iTunes .
    tt2

  • Media encoder making file sizes 3x bigger

    I've been using Adobe Media encoder CS4 for a while now and haven't had any problems, but lately every file I try to encode comes out bigger when it should be smaller. I've tried to tweak every setting I can but nothing seems to make a difference.
    I would blame it on the fact that I'm trying to encode .wmv files but am encountering the same issue with mp4 and .mov (quicktime) files. Here is a screen shot to show you what I'm dealing with - the other file, the .wmv is 77 MB but the estimated file size is 1097MB and the encoder just ends up crashing. any help you can provide to get the encoder behaving like it used to would be appreciated:

    Hi bgmc101,
    bgmc101 wrote:
    Hello Kevin,
    Thanks for getting back to me. It's not actually HEVC. We load in the uncompressed AVI clips into Premiere instead. If they were real HEVC then Premiere wouldn't even let me import them, yes?
    Right! I was confused about how you even imported the footage.
    bgmc101 wrote:
    The blinking does not start until 50 seconds to a minute in, and randomly persists through the rest of the video. We've had to export 30 to 40 second segments of the video and stitch them together using our stuff... not the most favorable workflow.
    Any ideas?
    Are you exporting via the Export button (from Premiere Pro) or the Queue button (AME)? Does it work using the other method?
    Thanks,
    Kevin

  • Adobe MEdia Encoder Crashes with big files inputed

    Hello,
    There isn't a forum for the Adobe Media Encoder, so I thought this would be a good spot. I am an after effects and Premiere user who likes the idea Adobe seems to have of using the media encoder to cover all my encoding needs.
    My typical workflow, especially since these days I'm doing more shorter form animations, is to render out to a Quicktime Animation codec file as my main archive file. From there, output all the various different web versions, flv, etc from that core archive file. Since my projects usually aren't running more than 5 minutes, this leaves me with a nice 3 - 7gig file.
    Problem: I'm running CS4 and the media encoder crashes when I input files that are in this file size range. The program locks up when I push start que, and then eventually crashes. Works fine with smaller size files that are about under a gig.
    I can run a render out of after effects, which seems to be more stable. But I'd love to be able to use this great new tool.
    Here's my machine specs if it helps:
    PC
    Intel Quad Core Q9550 @ 2.83 ghz
    4gB RAM
    Windows Vista 64 bit ultimate
    All updates current for CS4 apps as of 01/30/08
    Running Adobe Media Encoder V 4.01.078
    Hard drives are nothing special. 7200 rpm western digital internal and external. I've tried all sorts of hard drive configurations, where the input is coming from, where it's going, etc. No difference.
    I have been experimenting with using Lossless AVI's as my "uncompressed" archive file. Works well, but same crashing with the Media Encoder.
    Also tried experimenting with frame size alterations during encoding, no difference there. Also, whatever the output codec is, be it FLV, H264, etc. no difference.
    Anyone have any thoughts or have experienced similar issues? I hope all my MAC friends aren't right, seems like all my attempts to streamline my workflow with this CS4 and beefy PC combo are crashing and burning.
    Anyone else feeling this pain, or have recommendations?
    Thanks,

    Thomas, thanks for your suggestions on Vista optimization. That Sheer Codec looks nice, but hard justify the cost when I've been working for years with essentially uncompressed codecs that work well. Will play more though to see if the cost would actually pay off in the long run though.
    In general I made a decision that it was too early to throw in the towel on my old uncompressed codecs. The Quicktime animation codec has always been for me the safest, most universally accepted, and most reliable "uncompressed" codec. It's always worked in the past, not gonna give up just cuz media Encoder CS4 has troubles.
    Mylenium, thanks for the reminder about the silly platform wars. I've always felt the same as you, but when I'm stressing sometimes the silly propaganda can get to me. Makes me forget that no matter what system ya got, it never works perfect!
    Here's an update. I have trying my best to learn more about the bug and have come to some interesting realizations. The AME does work with larger files, just not the larger files that I had been using at the current moment. Older files of mine as big as 20GB can be inputed into AME with fine results.
    This being said, it scratches out most of the RAM overload thoughts with AME.
    The difference with my current files that were causing AME crashes: larger than a few GB, came from AE, had the 1.21 pixel aspect ratio metadata.
    When I re-interpreted the file in AE into a square pixel aspect ratio, exported it, it was then successfully inputed into AME.
    I have read just now that there were changes in After Effects widescreen pixel aspect ratio interpretation in CS4. Can this change be causing problems in my AME. Not positive, but I'm now thinking after many days of testing that the bug could have its roots somewhere in this ball park.
    If anyone from Adobe is reading this, I would love any ideas you might have on this issue. In general, there is really no support for the Adobe Media Encoder itself. This is not good, considering how it is so necessary for AE and Premiere users like myself.
    Thanks,

  • 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 - Issue with exporting file

    When I send a file to Adobe Media Encoder and I hit queue I get an error, "could not read from source file, please check if it has been moved or deleted".
    The source file location that the AME is trying to use is C:\Users\User Name\AppData\local\temp\file name.prproj
    Is this file location correct?
    Why is not using my scratch disk file?
    How do I change the file that AME is trying to use?
    I have not been able to export a video since I have purchased Premiere CS4.
    Any help with this would be greatly appreciated.

    If you want a quick work-around do not try exporting from Premiere, just save and exit the project after you are through editing.  Open AME and under File, select Add Premiere Pro Sequence, browse for your project file and click on it once--have patience Adobe's feedback here is lousy--your sequence will finally appear in the Sequence window, click on it and then click on OK.  Select your Format,.Preset and Output location.  If you want to tweak your settings just click on the Settings button.  Then hit Start Queue.
    Do you have the project on an external removable drive?

  • Adobe Media Encoder All Video Output 'White'

    Hi all,
    I am attempting to use Adobe Media Encoder to  export a QT h264 optimized for upload to facebook from a QT file exported 'Same as Source' from Avid MC 5.0.3, whic would be 1080i60 1920x1080.  The source file playsback correctly in QT player or VLC, but even the output preview screen in AME shows only a white image.
    I've also tried converting a completely different QT file created in Premiere Pro, with the same white video output issue.  I've tried opening/closing AME with no luck, but hte last time I used it I didn't have any problems and was able to produce the desired end result.
    Thoughts?
    Thanks for your input,
    Lindsay

    Hi,
    Yes you are correct in assuming the two software packages are on different machines. I am using Premire Pro CS5 5.0 and Avid Nitris DX MC 5.0.3 And no, I do not believe I have installed any Avid Codecs.  I just followed your link, will download and do so now.  I'm assuming this will fix the bug, but if not I will let you know.
    Thanks for your help!
    Lindsay

  • Media Encoder Fails to display file dialog

    PP CS3 3.2
    I have some video and I get media encoder to load properly.
    No matter what settings I select, when I click OK to encode the video the window disappears for a moment, then reappears with no messages and the file and folder dialog never appears.
    I have a fully registered version of CS3 on Windows XP SP2.
    This is awfully frustrating since I am a long time PP 1.5 user and wanted to load up some video and jump right into getting it ready for the web.
    Anyone with a similar problem or advice?

    First thanks to everyone who has gone before me on this issue. I just ran into this problem for the first time.
    I prepared a sequence named "Welcome/Intro" when I tried to use the media encoder I had the same problem discussed here. I do think that at least an error message would have been appropriate here. For the screen to just flicker and return rather than display the "File Dialogue" is really difficult to trouble-shoot. If I hadn't found this post I'd still be baffled. I have used PP for years and have never seen this issue before - I don't recall if I ever read about "forbidden" characters in Sequence Names.
    Additionally because you can re-name the files you are exporting once you get the "File Dialogue" it seem that Adobe PP could allow you to progress to the dialogue screen and then allow the windows "invalid file name" error to handle the issue. Well, thanks to everyone again. I have not up-graded to CS4 - yet. I really would be interested to know how it is handled there - not that I'll ever use the "/" in a sequence name again.

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

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

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

  • Adobe Media Encoder making blocky videos

    The backstory: I have two Mac laptops: an old Powerbook G4/Panther running Imovie 4 and a brand new Macbook Pro/Snow Leopard running Imovie 9.
    I've now made several FLVs that play beautifully on the internet: I imported old clips *that had been extracted using the Powerbook/Imovie 4* into my Macbook Pro/Imovie 9, edited the videos in Imovie 9, exported them as standard m4vs, then encoded them into FLVs using Adobe Media Encoder CS4 4.2+. They look terrific.
    The problem:
    For the first time yesterday, I used my Macbook/Imovie 9 combo to import clips shot with the same exact camera, then did everything exactly the same. The exported m4vs look fine. However, the resulting re-encoded FLVs are badly blocky, as though a mosaic filter was laid on. This is mostly happening when there is any increased motion in the footage.
    I tried exporting into .mov then encoding for Flash in the same way, and no difference. The adjustment I'm currently trying is to bypass the presets on AME to enable a 2-pass scan rather than 1. There does not appear to be a keyframe-interval selection option in AME CS4 4.2, or I would adjust that as well. This custom encoding is taking 5 times as long to complete as the preset encoding: over an hour versus 15-16 minutes. It may or may not work, but regardless, I don't have that kind of time - I have a bunch of videos to make.
    I'm really sick about this, because my beloved Powerbook has a dying harddrive, which is why I bought the new laptop. I don't want to believe that it was Imovie 4 that was responsible for those lovely videos. Later Macs no longer support Imovie.
    Is there something I'm missing that will make AME work with Imovie 9 to eliminate the problem? I know Imovie 9 is a turkey, but it did make those lovely videos with the old clips from version 4. There's gotta be a way.
    Thanks in advance.

    After playing Youtube go to your temp internet
    files and copy the file to HDD which is a mp4.
    Add this to the Media Encoder and see if it will work now.
    If it still does not work, your ME is prob. not working right.
    I sometimes use AME as a converter and it handles mp4 just fine.

  • Media encoder is killing my file

    I have a windows video file that works fine when I run it.
    I used the Adobe Media Encoder CS5.5 to try to convert it into flv format.
    It attempts to load the file, but gives up, saying that the file has a bad header.
    After that, the file HAS a bad header, and no longer works.
    Luckily I had back up copies so I was able to replace the 12 +megabyte file.
    I can reproduce the problem every time, using my back up copies.
    The file is on line at http://www.slaithwaitemoonraking.org/images/movies/MoonRaking2.wmv
    Other files encode to .flv with no problem, so it must be a problem this file alone.
    Regardless of a file error, Media Encoder should not make changes to a file just by accessing it.
    Has anyone else had this problem?

    Can also confirm this  on Windows7, although it doesn't  happen when I import in into AME CS6 on the Mac.  One clue might be the non-western characters that show up in the Inspector when I open it in Quicktime X, see attached screenshot.
    I'll log a bug about AME altering the header of this file on Windows, we shouldn't be doing that...

Maybe you are looking for