MXF XDCAM OP1a Red Frames in Media Encoder

It was advised in the other thread about red frames to start a new one for this kind of the red-frames-problem.
So my usual workflow is:
Export a masterfile from Premiere via Mediaencoder as XDCAM OP1a 1080p5025fps.
From that I generate various versions for my clientst directly in MediaEncoder. Almost only h264 in all different sizes.
Since the update 3 days ago this doesn't work anymore. The h264 files that are made from the mxf have many red frames and mediaencoder reports errors like:
: MXF read error "\\?\V:\xxxxx-1080p-XDCAMHD50PAL.mxf" frame 383.
In a 3 minute clip 8 of those errors at differnet frames are reported. I suppose that is where the red frames are generated.
Yesterdays update (the Audio Buzz fix) did not change the redframe problem.
So I used my 2nd installation that was not updated for weeks. There everything works as expected.
When I generate the MXF there, it's fine and h264 files are made from it without any problems.
So I have a working MXD XDCAM OP1a 1080p 50 PAL25fps.
That same file in the updated media encoder again gives many "MXF read errors". So it's obviously the Mediaencoder that cannot handle that (working) MXF file.
I hope that helps the developers to get rid of that problem as soon as possible.
__Peter__

We are having the same issue at our shop.  We have 8 suites, all are experiencing red flashes ever since we upgraded to 7.2.1.
All the systems are Win7, and we've encountered red flashes with XDCam 35, XDCam 422 and Mpeg4 clips.  We haven't been to develop a workaround as the flashes occur in very inconsistent patterns.
For example, just a moment ago an editor called me in because he was getting red flashes on his exports.  We went to his timeline, and the timeline was showing red flashes as well.  We deleted the clip (an XDCam 422 clip) from the bin, and re-imported it.  It played in the viewer fine with no flashes.  We put it on the timeline and again it played fine.  We exported the sequence directly out of Premiere as an XDCam 422 clip (delivery format needed for the client) and the exported file contained red flashes.  We went back to the timeline and it had red flashes, and the clip in question had red flashes when viewed directly! WTF?! 
So we deleted the clip again, and re-imported it.  Played fine with no red flashes.  Put it on the timeline - no red flashes.  This time we exported the timeline as an AVC-I 100, and the exported file had no flashes.  As a test we went back and exported the timeline again as XDCam 422...and red flashes on the exported file, AND the timeline and original clip had red-flashes as well.
Could it be something with XDCam and/or MPEG compressed clips in general?  We've only done one more test with AVC-I (which was successful) but I'm not confident enough yet to say that exporting as AVC-I is a consistent workaround. 

Similar Messages

  • CS6: Premiere exports MXF Op1a (mpeg based) but Media Encoder does not.

    As a company we use several local machines with a full installation of CS6.
    Premiere Pro exports in our broadcast format (MXF Op1a - mpeg based - Long GOP - 50Mb - Top Field First - etc...) still Media Encoder does not.
    They we both installed in the same procedure, full installation of CS6. MXF presets are present on both directories (Premiere and Media Encoder).
    ME simply doesn't recognize "any know exporters" even if I force a preset, when it comes to MXF.
    We have to import every single video into Premiere to export as MXF. It's difficult to create an effective workflow this way.
    Any thoughts on why is this happening?
    NOTE:
    - Updated twice all machines - first to 6.0.3, now to 6.0.5 = no result
    - Copied presets from a working trial installation = no result
    - Microsoft based OS core i7 with 12Gb RAM, 3Tb HD and Nvidia Quadro 4000
    Regards, RicardoM

    I've read a lot of suggestions towards similar issues. None worked.
    - installed codec packs incluiding different mpeg variations = no result
    - copied /common preset files from premiere to AME = no result
    - copied and replaced the full directory of AME from another working AME (with MXF exporter) = no result
    - re-installed CS6 = no result
    - updated CS6 twice = no result
    - added MXF Preset zip file available in the official Adobe support (although it refers to mac presets) = no matter... no result
    I really don't know what else to do.
    It's difficult to accept suggestions like "format c and start over" cause of the impact on the production room, so I really need more options other than the extreme ones...
    Any ideia Jim Simon?
    Thanks in advance!
    BTW: Must add that in all processes above, MXF exporting was allways possible in Premiere, just not in AME.

  • MXF issues on CS6 (Premiere and Media Encoder)

    Hello all,
    In our station workflow we use Sony XDCAM (DV25). Until last week we were running PPro CS5 without any problems with the MXF files. Since the upgrade (skipped 5.5) we have serious issues with this wrapper. Importing takes ages, espescially on large files (>0.5Gb). And I'm not talking about conforming or indexing... I'm talking about the import stage. The edit suite freezes until the file is imported. And we have 5 editing suites and all with the same issue. The same happens if we drag/drop a MXF file in Media Encoder. It takes about 10mins from the 'drop' file until we're able to change encoding settings.
    The second serious issue is that the MXF file sometimes (randomly) during editing looses it's audio. A program restart sometimes restores the audio, sometimes doesn't.
    The QT32server service is running more than one instance (in CS5 there was only one instance no matter how many CS apps were running). If I terminate these instances the pc runs smoothly.
    All CS6 apps are fully updated.
    Any ideas?

    The second serious issue is that the MXF file sometimes (randomly) during editing looses it's audio. A program restart sometimes restores the audio, sometimes doesn't.
    I wish I had a solution for you, but I don't. We are experiencing the exact same thing.
    Have you (or anyone else) figured out what's up? Our situation is IDENTICAL.

  • MXF decode errors and red frames in exports

    Ever since upgrading to Premiere Pro release 2014.2 (8.2.0 (65) Build) we've been having problems with random red frames appearing in our exports.  These errors are always associated with our Sony PMW-200 media files (.mxf files.)  Red frames during editing happen very rarely, but are usually present in our exports.  For short form work re-exporting the sequence will work sometimes, but may cause red frames to appear elsewhere...  For long form work we've adopted a very lengthy work-around to fix the errors after exporting.
    Phone support recommended deleting the media cache files, but we've tried that and the problem still exists.  This problem is happening with new media that has been imported since the upgrade as well as old media that we imported before the upgrade.  We're editing with many mixed media files all in their native codec and the only media files that get flagged with decode errors are the .mxf files.
    We edit a large volume of work daily and this problem is a huge setback in our confidence with our exports as well as Adobe products.
    For the record were editing with Mac Pros that are about a 3-5 years old with OS X 10.8.5 and an Xsan shared storage system.  We have a Cloud for Teams subscription and all our software is updated frequently.
    Any thoughts would be helpful.  Personally I would love to escalate this problem to a higher level support team.
    Regards,
    Eric

    I have the same problem running Adobe CC on high-end PCs. - My business is smalish, but this leads to having a rather big impact on my confidence.
    MXF-files from Canon C300 and Sony FS7 platforms.
    - With FS7 footage I've had the frames appear throughout a clip with perfect distance (16 frames apart) - when applying Denoiser 2 from Red Giant. - The plugin simply stopped the frames from appearing on a random basis.
    - I've also experienced that when the error was present, dissolves became cuts.
    - I've tried to isolate software/hardware rendering, but it does not seem to change anything to select one over the other.
    I try work around it by rendering uncompressed sections of the timeline and replace it where it works, and then try again and again. - Very time-consuming and cumbersome.
    Best
    Torsten
    Denmark

  • Live text template render issue when using Media Encoder?

    I'm running into flash frames with Media Encoder exports of Premiere sequences using the live text templates.
    Unfortunately, AME doesn't flag it as an error, so the render completes without any issues in the render log and the only way to find it is to watch the rendered file.
    I have tried different combinations of having After Effects open or closed, with the live text template comp open or closed; I can't consistently reproduce the problem with any certainty and so am having trouble pinpointing the source.
    My only hypotheses so far are that:
    The glitches seem to be happening in the dynamic link between AME and PP, not AE and PP. The live text will pop back to the duplicated comp's text for one frame. Video playing simultaneously doesn't pop.
    In other words, the AE text template said: "name here". In PP it was edited to say "John Doe", then that comp was duplicated and edited to say "Bob Smith". Everything looks fine in PP. There are no keys on the source text in AE (I have noticed that if there are keys on the source text in AE, the text will pop back to the original AE text at that key in PP).
    When rendered out of AME, halfway through Bob Smith's title, it will read "John Doe" for a single frame, then pop back to being Bob.
    I've only had this happen so far with AME renders. The renders out of PP haven't given me any issues so far.
    It might happen more frequently on longer segments? If a title is up for 45 sec instead of 10 sec, it may be more likely to pop.
    The issue seems to occur more often in batch renders out of AME (happened to 3 of 5 files rendered in a batch, AME 2014.1) and/or with unrelated AE comps open (on a single render from AME 2014.2)
    Again, it doesn't happen every time or to the same title, or in the same spot. Files are being rendered to ProRes 422 HQ. Unchecked "Use Previews" in AME.
    Would be nice to get to the bottom of what's happening so I can recommend something to the editors when I hand off these live text templates to them.
    I realize that the live text is a new feature as of 2014.1, but haven't found anyone else talking about this. Would love if this was a very simple fix that I'm missing.
    I was able to reproduce the error on 2 different machines, with similar specs:
    Premiere CC 2014.1 and 2014.2
    Media Encoder CC 2014.1 and 2014.2
    Mac tower 2010
    2x 6-core Intel Xeon
    RAM: 64 GB
    Graphics: ATI Radeon HD 5770 and NVidia Quadro K5000 (or K4000)
    OS: 10.8.5 Mountain Lion

    I'm running into flash frames with Media Encoder exports of Premiere sequences using the live text templates.
    Unfortunately, AME doesn't flag it as an error, so the render completes without any issues in the render log and the only way to find it is to watch the rendered file.
    I have tried different combinations of having After Effects open or closed, with the live text template comp open or closed; I can't consistently reproduce the problem with any certainty and so am having trouble pinpointing the source.
    My only hypotheses so far are that:
    The glitches seem to be happening in the dynamic link between AME and PP, not AE and PP. The live text will pop back to the duplicated comp's text for one frame. Video playing simultaneously doesn't pop.
    In other words, the AE text template said: "name here". In PP it was edited to say "John Doe", then that comp was duplicated and edited to say "Bob Smith". Everything looks fine in PP. There are no keys on the source text in AE (I have noticed that if there are keys on the source text in AE, the text will pop back to the original AE text at that key in PP).
    When rendered out of AME, halfway through Bob Smith's title, it will read "John Doe" for a single frame, then pop back to being Bob.
    I've only had this happen so far with AME renders. The renders out of PP haven't given me any issues so far.
    It might happen more frequently on longer segments? If a title is up for 45 sec instead of 10 sec, it may be more likely to pop.
    The issue seems to occur more often in batch renders out of AME (happened to 3 of 5 files rendered in a batch, AME 2014.1) and/or with unrelated AE comps open (on a single render from AME 2014.2)
    Again, it doesn't happen every time or to the same title, or in the same spot. Files are being rendered to ProRes 422 HQ. Unchecked "Use Previews" in AME.
    Would be nice to get to the bottom of what's happening so I can recommend something to the editors when I hand off these live text templates to them.
    I realize that the live text is a new feature as of 2014.1, but haven't found anyone else talking about this. Would love if this was a very simple fix that I'm missing.
    I was able to reproduce the error on 2 different machines, with similar specs:
    Premiere CC 2014.1 and 2014.2
    Media Encoder CC 2014.1 and 2014.2
    Mac tower 2010
    2x 6-core Intel Xeon
    RAM: 64 GB
    Graphics: ATI Radeon HD 5770 and NVidia Quadro K5000 (or K4000)
    OS: 10.8.5 Mountain Lion

  • Red frames popping up after upgrade to media encoder cc

    I'm having some issues with Media Encoder CC. My workflow is AMA SxS card (footage is in XDCAM HD 1080/50i) into Avid Media Composer 6, edit, and export as XDCAM HD 1080/50i mxf file into a watch folder that Media Encoder picks up and converts to SD mpeg2 (its the way the TV stations want it) that file is then ftp'd using Media Encoder. It used to work fine with Media Encoder CS6, but since I upgraded it keeps giving me red frames (cant read frame errors) usually just before or after there is a cut in the footage. I've resorted to transcoding the footage in Avid to DNxHD 120 after editing and that seems to resolve the issue, but it's just an extra step that adds loads of time to my workflow.
    Avid Media Composer 6
    Adobe CC
    HP EliteBook 8760w
    Windows 7 64bit

    The whole point is that I dont want to transcode into DNxHD at all, DNxHD is the extra step. The can't read frame errors are also very inconsistent in Media Encoder CC.  I might export a file and it gives me a few red frames (can't read frame errors) but if I then take the same file and rename it they sometimes work.  I've tried uninstalling and reinstalling but that hasnt helped...

  • Red frames when exporting mfx from new media encoder

    I edit TV programs each week that are mastered as MXF comps. Updated to premiere pro 8.2 (MacPro Late 2013) yesterday. Now when I export a program using the updated Media Encoder que, I'm getting full page red frames intermittently. How can I go back to the previous release? I can't wait for the bugs to be worked out.

    This should guide you through rolling back: Install a previous version of any Creative Cloud application

  • Media Encoder CS4 hangs when opening large XDCAM HD MXF files

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

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

  • Mxf op1a match source Media Encoder

    I'm trying to use the mxf op1a match source (rewrap) preset in Media Encoder. I've got a variety of source material from Gopros, XF305s and a couple of others. The preset fails consistently with Gorpro footage, and I've had problems with some other sources too. I keep getting the "The source file's video stream is not compatible with this preset. Please choose a different preset." error.
    My question is: given that I'm only trying to use the mxf preset as a container, keeping the source material as it is - why am I getting compatibility errors? As I understand it, mxf can be used as a container for a variety of video types, I've not come across anything that states it doesn't work for Gopro files or any others, so what's the problem?
    Thanks
    Bransby

    This won't work for GoPro footage because our MXF exporter doesn't support GoPro CineForm. Unfortunately the preset has to do a little more than just copying the streams to a new wrapper. We have to have an ability to write that stream natively to MXF and currently we can't do that. If you wanted to make a feature request, you should request that we support GoPro CineForm in an MXF wrapper. Once that exists your workflow will work. Feature requests can be made here:https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

  • Red Frames in export to h.264 original files XDCAM MXF

    We still find red frames in exports to H264
    original files in this codec:
    Format XDCAM HD 422
    Codec MPEG2
    4:2:2 Profile (422P) @ High Level (HL)
    Bitrate 50 Mbps
    Constant Bit Rate (CBR)
    Display aspect ratio 16:9
    1080i/25 1920 x 1080 25, 50 fields Interlaced
    adobe premiere pro cc 2014.2 release 8.20.0 (65) build
    Mac Pro Mid 2012 Yosemite
    24 GB RAM
    Nvidia Quadro K5000
    No problem until last update...
    Any solution or update in future?
    Hope to hear from Adobe.
    Bart

    We are having the same issue at our shop.  We have 8 suites, all are experiencing red flashes ever since we upgraded to 7.2.1.
    All the systems are Win7, and we've encountered red flashes with XDCam 35, XDCam 422 and Mpeg4 clips.  We haven't been to develop a workaround as the flashes occur in very inconsistent patterns.
    For example, just a moment ago an editor called me in because he was getting red flashes on his exports.  We went to his timeline, and the timeline was showing red flashes as well.  We deleted the clip (an XDCam 422 clip) from the bin, and re-imported it.  It played in the viewer fine with no flashes.  We put it on the timeline and again it played fine.  We exported the sequence directly out of Premiere as an XDCam 422 clip (delivery format needed for the client) and the exported file contained red flashes.  We went back to the timeline and it had red flashes, and the clip in question had red flashes when viewed directly! WTF?! 
    So we deleted the clip again, and re-imported it.  Played fine with no red flashes.  Put it on the timeline - no red flashes.  This time we exported the timeline as an AVC-I 100, and the exported file had no flashes.  As a test we went back and exported the timeline again as XDCam 422...and red flashes on the exported file, AND the timeline and original clip had red-flashes as well.
    Could it be something with XDCam and/or MPEG compressed clips in general?  We've only done one more test with AVC-I (which was successful) but I'm not confident enough yet to say that exporting as AVC-I is a consistent workaround. 

  • Red Frames and .mxf read failures PP CC 2014 8.1 update. Oct 6.  Anyone else see the new update fail? Any suggestions?

    Hi,
    I cut 9 hours worth of broadcast video in PP CC 2014 8.0. (The yellow interface.) I had no issues. It was all great. For some reason, before I exported the finished cuts for broadcast, I updated the Adobe CC 2014 suite to v1.8.0.447 (PP has the blue interface). I feel stupid. I broke my own rule of not updating software until the projects you work on are done. Now I can't open this project without Red Frames in my timeline and in my exports. I have been reading about this Red Frame that seemed to first appear in PP CC 7. (Maybe even as early as 2006) I never had the problem then, I run Premiere Pro everyday.
    My Issue seems to be a bit different than most of the issues that have read. I have cleared the cache, & I have ditched the preview files. This did not fix it as stated it would in previous forum posts.  I have moved the footage location from a server to a local thunderbolt SSDrive and renamed the folders and re-linked the video footage. Still Red Frames.
    What is odd, is when I boot up the project and after all media has loaded, it looks like it is going to work for a few minutes. I get happy and scrub the timeline checking for the red frames, hoping the problem solved when I cleaned the cache etc.. Everything seems to be fine, audio synch, picture, lower thirds and graphics all appear fine. Then the red frames appear over time, and by 5 minutes after scrubbing, I see mostly red frames. Audio is still there though. Even weirder, is that when I resize the height of the video track, the red frame comes and goes with no real pattern.  The clip preview picture flickers with the red frame. The red frames export through through Premiere and through a Media Encoder cue which say .MXF read error so I'm hooped. ( it does render the video, but has the red frames )
    I run a Mac Pro;
    OSX Yosemite 10.10
    3.5 GHz 6-cor Intel Xeon E5
    16 GB Ram
    AMD FirePro D500 3072 MB
    Canon XF-305
    .MXF files
    1080p 29.97
    5 Cam Multicam Seq.
    Adobe CC 2014
    Version 1.8.0.447
    released on October 6, 2014
    I am noticing something interesting with my source footage folders. I am getting some .mxfindex files with really long names, like temp files almost, that don't go away. I still get Red Frames after deleting them, clearing cache, changing drive locations and file and folder names and relinking. When I delete these long files the software wont boot the project very well and crashes a few times before it opens, still with red frames. This problem with this project occurs on every computer (4)  in the studio, which are the same as mine, we all updated at the same time. 
    Files look like this:
    What happened in that update? Is there a fix for this? Any suggestions? If not, Is it possible for me to roll back my whole CC 2014 version to 8.0?  I am terrified to open any other of our projects... I am under time pressure and am starting to do the re-edit of this in CS6 which seems to run flawlessly, but because of Adobe's RIDICULOUS FAIL in backward compatibility, I can not open this project in anything but PP CC 2014. 120 hrs of lost editing will certainly have me scratching my head about continued use. Any suggestion, links or information would be appreciated.
    Thanks .

    Hi 5neaky c,
    5neaky c wrote:
    For some reason, before I exported the finished cuts for broadcast, I updated the Adobe CC 2014 suite to v1.8.0.447 I feel stupid. I broke my own rule of not updating software until the projects you work on are done. Now I can't open this project without Red Frames in my timeline and in my exports.
    You should still have a Premiere Pro CC 2014.0.1 (8.0.1) project file available to you by default. Can't you go back to that version and complete your project? That's what I'm recommending those having this problem do.
    5neaky c wrote:
    I have been reading about this Red Frame that seemed to first appear in PP CC 7. (Maybe even as early as 2006) I never had the problem then, I run Premiere Pro everyday.
    As long as you ingest the footage via the Media Browser and do not update the project file, you shouldn't have issues like this. I have heard complaints in new projects with Premiere Pro CC 2014.1 (8.1), so I have reopened a previously closed bug.
    5neaky c wrote:
    My Issue seems to be a bit different than most of the issues that have read. I have cleared the cache, & I have ditched the preview files. This did not fix it as stated it would in previous forum posts.  I have moved the footage location from a server to a local thunderbolt SSDrive and renamed the folders and re-linked the video footage. Still Red Frames.
    If this is not working, please complete your project in Premiere Pro CC 2014.0.1 (8.0.1)
    5neaky c wrote:
    What is odd, is ...
    Everything seems to be fine...
    Then the red frames appear over time….
    Yes, I've seen this with another customer's updated project.
    5neaky c wrote:
    I am noticing something interesting with my source footage folders. I am getting some .mxfindex files with really long names, like temp files almost, that don't go away. I still get Red Frames after deleting them, clearing cache, changing drive locations and file and folder names and relinking. When I delete these long files the software wont boot the project very well and crashes a few times before it opens, still with red frames. This problem with this project occurs on every computer (4)  in the studio, which are the same as mine, we all updated at the same time.
    Sometimes, deleting sidecar files can help the situation but not always. It looks like you are having trouble when deleting them.
    5neaky c wrote:
    What happened in that update? Is there a fix for this?
    A bug that was fixed for red frames in 8.1 was somehow broken by the time we shipped this version. We have reopened the bug, but currently, there is no fix.
    5neaky c wrote:
    If not, Is it possible for me to roll back my whole CC 2014 version to 8.0?
    Yes, see my blog post here: Install a previous version of any Creative Cloud application
    Included in the post is a patch for Premiere Pro CC 2014.0.1 (8.0.1).
    5neaky c wrote:
    I am under time pressure and am starting to do the re-edit of this in CS6 which seems to run flawlessly, but because of Adobe's RIDICULOUS FAIL in backward compatibility, I can not open this project in anything but PP CC 2014.
    Thanks .
    You can always try exporting a FCPXML for backward compatibility, but for complex sequences (like multicamera), this isn't always an option. There aren't many NLEs providing backward compatibility, sorry. Feel free to request that, if you like, here: http://adobe.ly/feature_request
    Thanks,
    Kevin

  • Red frames and MXF decode error

    Hi there,
    I have Premiere Pro CC and running Mac OSX 10.9.5. I have one long 32 minute long C300 MXF clip in my timeline which seems to be fine until around the 26 minute mark, where the entire frame goes red. The audio still works, but I can't see anything. I have tried to convert the clip to ProRes in Media Encoder also, but the same issue happens.
    In the report log from Media Encoder I get the following message repeated many times:
    MXF decode error in "[FOOTAGE LOCATION]/Card 1/CONTENTS/CLIPS001/E51151/E5115107.MXF" at frame 47650. Frame 47618 was substituted.
    And then occasionally it says:
    MXF read error in "[FOOTAGE LOCATION]/Card 1/CONTENTS/CLIPS001/E51151/E5115107.MXF" at frame 239.
    Any advice about this??
    Thanks,
    Simon

    Hi there,
    I have Premiere Pro CC and running Mac OSX 10.9.5. I have one long 32 minute long C300 MXF clip in my timeline which seems to be fine until around the 26 minute mark, where the entire frame goes red. The audio still works, but I can't see anything. I have tried to convert the clip to ProRes in Media Encoder also, but the same issue happens.
    In the report log from Media Encoder I get the following message repeated many times:
    MXF decode error in "[FOOTAGE LOCATION]/Card 1/CONTENTS/CLIPS001/E51151/E5115107.MXF" at frame 47650. Frame 47618 was substituted.
    And then occasionally it says:
    MXF read error in "[FOOTAGE LOCATION]/Card 1/CONTENTS/CLIPS001/E51151/E5115107.MXF" at frame 239.
    Any advice about this??
    Thanks,
    Simon

  • Red r3d 3k fails on CUDA export Media encoder CC

    Been having some problems with Red 3k.
    Several times recently for some low budget stuff I have shot 3k and put it in a 720P timeline.
    All of my 3k material will fail under media encoder CUDA export.....it works under software but a 20 minute CUDA encode is 7 hours with 3k in software encoding
    4k 5k all work fine no problems.....just the 3k stuff. And this has been the case over several shoots for months.
    It is also the same with 1080p sequences and at any frame rate, and it also fails from PPRO direct export (not queued)
    Thanks
    Win 8 64 core i7 6core 980 24GB ram, 2x GTX 470 1X GTX 590 SSD's

    Yes, AME queue is a problem.  I have a 28 minute weekly broadcast for a client that must be encoded in 6 different formats for TV Broadcast, mpeg2 DVD, vimeo, mp3, h.264 for vimeo, etc.  If I attempt to encode all 6 in the queue I will have some success and also failure.   If I queue several videos that all require mpeg2 (though with each requiring several different specs, i.e., upper field vs. lower field, mpeg2 dvd, mpeg2 HD, etc.) it will complete the task.  Yet if I add h.264 to the mix all encodes will fail.  I can encode h.264 by itself with no problems.  So yes, you are not alone.  Not sure what the solution is.  In CS6 one could queue all of these formats and walk away.  Can Adobe acknowledge these issues and then propose a solution?

  • Turning off frame blending in Adobe Media Encoder

    Is there a way to turn off frame blending in Adobe Media Encoder?  I have a bunch of
    Flip Mino HD footage (1280x720p) which I wish to convert to P2 720p format so that
    I can more easily mix and match it in the Premiere timeline with actual P2 footage
    shot on an HVX200.
    I successfully used Media Encoder to perform this task but there is one problem.  The
    Flip footage is 30fps and P2 720p is 29.97fps.  So Media Encoder uses frame blending.
    The frame blending sometimes creates obnoxious artifacts so I would like to turn it
    off but there seems to be no way to do this (or alternatively "conform" the 30fps input
    to 29.97fps so that no blending is nescessary).
    After Effects CS4 would seem like an alternative since it has nice batch composition
    creation and rendering features but it cannot render to the P2 format - it appears to
    have a older version of Media Encoder embedded within it - predating P2 support.
    I would like a solution that is easily "batchable" as I have several hunderd Flip Mino HD
    clips that need to be processed.
    You might also ask, why not just import the Flip clips unchanged into Premiere CS4
    and mix them with the P2 clips?....I have tried this and it seems to drive Premiere crazy
    introducing various crashes and other strange behaviors.  The pre conversion to P2
    route seems to work fine.  I just want to get rid of the frame blending.

    I happened upon this video just before I made my posting and it doesn't help with the
    crashes/hangs.  When I import more than about 20 Flip Mino HD clips it seems to trigger
    some sort of memory corruption bug in Premiere.  Some of the clips start to just
    show as solid green in their thumbnail views in the timeline and scrubbing the timeline
    eventually hangs Premiere altogether.  This is reproducible on two different computers
    although the exact symptoms change slightly each time it is tried.  Importing only 3 or 4
    clips actually seems to work, at least for a short while.
    The problems happen even if the only thing imported into the project are Mino footage and
    the Sequence is set to Desktop or XDCAM mode.  So the crashes have nothing to do
    with P2 editing mode.
    The same installation of Premiere CS4 on one of these computers has been just used to
    successfully edit and render out a P2 project with hundreds of clips, stills and titles so the
    basic CS4 installation seems to be solid.
    I'll eventually file a bug report but for now I'm more interested in getting the job done.

  • Encoding from mov to flv  - issues with red frames

    Any ideas how to fix this issue?  Everytime I try to encode this .mov file in the begining of the encode there seems to be some issue where a number of frams turn all red and gets pixelated then it runs smoothly?

    This issues seems to be with Adobe Media Encoder software which comes along Creative Suites.
    Please post in Creative Suite or AME forums.

Maybe you are looking for