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.
Similar Messages
-
Audio and video timing thrown off on export to Adobe Media Encoder
Hi.
I have a two and a half minute video which includes a lip-synched character. Everything is working perfectly inside Premiere Pro CS4. When I export this using F4V format, I set it to match frame rate as source then typed in 24fps for good measure.
The audio track is way off after going through Adobe Media encoder however.
The original video (generated in Carrara 7 Pro) was set to 24fps, but it looked like Premiere tried to import it as 29.97 fps. I right clicked on the clip and used Interpret Footage to set it back to 24fps when first setting up this project. (looking in my Project Panel right now, I see the flv icons are all set to 24 fps, but the blue icon representing PremiereProProject is indeed set at 29.93 fps, plus and incorrect size (720x480 px as oppsed to the 608x464 px of my actual flv files).
Seems like it's still pulling in that faster frame rate though when it goes to encode, even though I'm setting stuff to 24fps wherever I see the option.
Any ideas how to fix this (and how to prevent similar problems in the future)?
Again, everything works fine within the Premiere Pro CS4 context. It's just when I export that the video seems to play at a higher frame rate, thus begins running way ahead of the audio.
If there's not a way to fix this (change the project settings) within this file, is there a way to copy all of my data and simply paste it into a Premiere Pro file with the right size and fps? I've now created a custom preset with the correct info.
ThanksYeah, I'm pretty sure that was the issue.
I bring my stuff in from a 3d program (Carrara) which exported a png sequence at 24 frames per second (in square pixels). I didn't see an appropriate preset, so I chose a randomish DV preset, with 29.97 fps and .9 pixel aspect ratio. i re-interpreted the footage to set back to the correct framerate (and pixels I think). But when I exported from PremPro, it pulls in that initial Project Stting of 29.97 fps, thus all of my audio is off.
Is there a way to re-set the Project Settings after the fact so I can correct my fps and pixel proportions?
Or is my only choice to reimport my footage to a new project with the corect settings?
Thanks -
FCP turns off when I turn off frame blending
Hi, I really hope that someone can help with this. I'm running FCP 5.1, 8 GB, 2.66 Ghz. Just starting yesterday, everytime I keyframe a move in the motion tab, as I click to turn off frame blending, FCP quits. No "app unexpectedly quit" warning or anything. Just shuts down. It's pretty annoying when you're on a deadline.
Anybody have any ideas? Please feel free to step up to the plate. Thanks!
mac pro G5 Mac OS X (10.4.8) Big HuevosDid you do any software updates recently? You should always clone your startup drive when you have a stable OS/Application combo. This way you can restore your system to it's previous state quickly.
Have you repaired permissions? -
Turning off frame blending option
In short, I'm slowing down a lot of clips but I want 'frame blending' off each time.
At the moment, it's a case of manually turning off the option every time I slow down a clip.
Is there a way to set FCP so that the "frame blending" checkbox is off by default?
Thanks in advance,
DudeAt the moment, it's a case of manually turning off the option every time I slow down a clip.
Is there a way to set FCP so that the "frame blending" checkbox is off by default?
Where are you finding this checkbox?
You should be able to create an export batch that remembers this setting.
Bogie - asking on this forum was my last resort, not my first.
Now that we know your handle is associated with two extensively researched posts, I won't suggest that again.
bogiesan -
Hey everyone! So I just switched from using AE CS5.5 to AE CC, which now has me use the Media Encoder to render all my files, which frankly is AWESOME. However, I sometimes like to render out a piece of a long video I'm editing so I can get a glimpse at how it is looking so far without having to wait for it to completely finish. With CS5.5 I was able to just *stop* rendering, and the video would publish to my desktop and end wherever I had stopped it. With Media Encoder when I hit stop, the file is nowhere to be found as if the program just throws it away after canceling. Is there a way to make it still render what it already got through so I at least have a partial file to view??
On further inspection, Even still renders are interlaced like mad...
What's wrong?!
EDIT:
I fixed it!!! Apparently when speeding up or slowing down clips, it merges the frames together giving off that horrible look! So I turned off "frame blend" And it looks super awesome. -
Adobe Media Encoder de-interlace question
My video in the preview displays horribly interlaced, this is odd because the footage in the timeline displays correctly and clearly as well as my original footage. What seems to be the problem, I've tried rendering with de-interlace as well, it still shows fairly bad after being rendered.
All my original footage is 1280x720, 25fps.
My settings:
Format: H.264
Range: Entire Sequence
NTSC, 1280x720, 25[fps], Progressive
AAC, 160 [kbps], 48 kHz, Stereo
VBR, 2 Pass, Target 8.00, Max 8.00 [Mbps]
Video Codec: MainConcept H.264 Video
TV Standard: NTSC
Width: 1280 px
Height: 720 px
FPS: 25Field Order: None(progressive)
Pixel Aspect Ratio: Widescreen 16:9
Profile: Main
Level: 4
Bitrate Encoding: VBR, 2 Pass
Target/Maximum Bitrate: 8
Attached Files to show ya what I mean.
Rendering an uncompressed video yeilds the same results as Media Encoder.On further inspection, Even still renders are interlaced like mad...
What's wrong?!
EDIT:
I fixed it!!! Apparently when speeding up or slowing down clips, it merges the frames together giving off that horrible look! So I turned off "frame blend" And it looks super awesome. -
Adobe Media Encoder 4.2 update forces Frame Blend
I didn't really want to repost, but I felt the title and info in my previous post were innacurate (http://forums.adobe.com/message/2576915#2576915)
In my previous post, I thought Premiere was to blame, but after a few reinstallations, I've found that the update to AME 4.2 causes the problem.
I've found that Adobe Media Encoder 4.2 forces Frame Blend, even if it has been disabled on each clip of the timeline, when the frame rate of your sequence settings differ from the frame rate of the target format.
Example: Exporting from 24fps Desktop -> MPEG2-DVD (23.976fps)
Adobe Media Encoder 4.1 does not have this behavior. I've reverted to 4.1 for the time being.
If anyone has a workaround for this, or any other info on this problem, please share.I am having a similar problem. Is it just me or is it Adobe? I have had so many problems with Adobe Premiere CS4. It may have also been exacerbated by the fact the I updated to 4.2.1 (mostly in part to determine if another issue was resolved with this update).
I have some editing background in the Windows Movie Maker and iMovie world, and was excited to use Adobe Premiere, but I have had nothing but problems.
Everything that I am trying to do, looks really washed out, and renders the video useless.
I am trying to do what you just described, with speeding up and slowing video to match the computer actions with the person's voice. I am capturing video using CamStudio and Helix YV12 CODEC, and tried to use HuffyUV lossless compression: using DV-NTSC as the standard format.
Then I go to compose my video, and output the video, but the video is crap. It sounds like the Adobe Premiere and Media Encoder are having major problems.
I tried rendering it to Uncompressed Microsoft AVI with UYVY @ 100% quality, and tried to compare it with Windows Media at the highest quality, and it is frustrating. When I hear that Frame Blend is being applied, it seems to look worse.
I am running:
Intel Core 2 Quad CPU 2.33 GHz (which is kind of slow)
8 GB RAM, 2 SATA 1 TB Drives WD Caviar Green (a little substandard)
Windows XP 64-bit
Let me know there is another process that I am missing. I don't really want to give up on Adobe Premiere, but from a end-user standpoint, I will have to revert back to using WMM due to time constraints. I want to take full advantage of all of the editing and effects capabilities of Premiere, but can't because I can't even produce a decent export to be used by any other program (and given that every conversion will in some way affect the quality of the output, I want to reduce any intermediate steps).
Arrggh!!! -
Adobe Media Encoder cuts off video layer when the Ultra Key effect is applied
I am working on a Mac (10.8.5) using the latest verison of Premiere Pro CC. I am using Ultra Key to remove the chroma key background from the "talent layer" and adding a "new background layer" behind the talent video layer. When I export directly from Premiere, the sequence exports as expected. However, I have many sequences, and wish to speed up the process using Adobe Media Encoder. When I export the same sequence using Adobe Media Encoder, the top half of the "talent layer" is completly cut off:
The issue has something to do with the Ultra key effect because when I remove the effect from the "talent layer" it exports in tact (with a chroma key background of course). Adobe Media Encoder CC is up to date as well; are there any known bugs with Media Encoder CC and the Ultra Key effect in Premiere Pro?
Thanks! -
Adobe Media Encoder CC constantly crashing during batch encodes
Hello!
We just made the big switch to Premiere Pro CC for our TV shows and now that it's time to finalize our first few episodes we are having some major problems batch exporting segments of the show. Sometimes it works, sometimes it works half way through the batch list then crashes, sometimes it crashes right away. There is no consistency, other than crashes are happening all the time. Here's what is happening:
• AME 7.2.0.43 (64-bit)
• Mac OS X 10.9.1 on 2x2.66 GHx 6-Core Intel Xeon, 40 GB 1333MHz DDR3 RAM
• Startup disk is SSD w/ 4GB free space (all footage is on external storage)
• Using Premiere Pro CC to export via AME.
• All recent updates insatlled as of 3/10/14.
The source footage is ProRes 422 720p 59.94 footage from AJA KiPros. Each project has 16 segments - these are individual sequences. There are 7 tracks of audio and 4-5 tracks of video in each. In addition to the video there are targa files that include the score bug, full screen graphics, etc (this is sports). There are also some Adoby Dynamic Link After Effects elements throughout.
Editing has been fairly crashless - however when I File > Export > Media and queue it up in AME, that's when the fun starts.
I can rarely get through an entire batch list - generally within a few files the preview window at the bottom shows that it has halted and nothing further will encode. There is no way to stop or close the program without force quitting. When I have tried to encode from Premiere Pro CC directly, it works, although it is much slower and will only do the one sequence at a time.
I have been trying to encode to two different formats from within AME:
1.) ProRes 422 720 59.94 (just like the source footage) with 4 channels of audio.
2.) ProRes 422 1080i29.97 with 4 channels of audio.
We have different broadcast partners so we need to deliver in these two difference specs. I get crashes regularly on both outputs.
Possibly unrelated but also weird - I've noticed that when AME starts this crashing cycle sometimes Premiere CC won't let me save anyome. The status bar comes up like it's going to save the project but it goes nowhere. I have to quit without saving. Weird.
Can anyone help me further troubleshoot? This is bordering near deal breaker to continue using this software if I have this much trouble when trying to get my project outputted. Thank you!Agreed, I now have a project to GET OUT, and AME crashes consistently 1/3 into the render. It appears to halt all processing after (real time) 00:02:30
Am seriously considering uninstalling CC as I am beginning to find other issues in some apps, and going back to CS6/MC just so I can get work out. Durn it Adobe this is AWFUL!!
Alright, let's try to be constructive instead of throwing rocks... but the frustration level is high, and I have material on deadline. Let's get with this, guys...
What OS Win7, 64-bit
What version of AME/PPro (Please be specific by getting the full version number in the About Adobe Media Encoder screen) 8.2.0.54 Ppro: 8.2.0 (65)
When is it crashing (Again, the more detail here about where it was in the encoding process the better) roughly 1/3 into the sequence, always on exactly the same frame - tried replacing the clip with something different to see if it was a timeline error, and NO EFFECT.
What is your source (PPro project or media file (what kind?)) PPro
If the source if a PPro project, does it work when exporting directly from PPro? NO
What format are you exporting to? H.264, QT, WM, tried everything my client can play.
Do other formats work? MPEG2, QuickTime, etc? NO
Have you tried with GPU rendering on? How about turning it off by switching to Software-only mode? Mine doesn't have any choice, it's software-only.
Have you tried disabling Native Sequence Loading? (AME Preferences: General > Enable Native Sequence Loading) No effect
Other things I tried: uninstalling/reinstalling AME, setting cache to a fast local disk. -
Hi Guys
I am having some real issues with Adobe Media Encoder (AME) at the moment. It appears that I am unable to encode an h.264 for Vimeo from a Premiere Pro Project file at the moment without at least some weird image issues that are not supposed to be there. These include weird flickering, colour changes, artefacts etc. This is if I am lucky...often I am unable to get the process to complete as the application either crashes and tells me there has been a problem or it simply freezes and I have to force quit the application and often restart my machine.
The problem seems to not to just be with h.264 for the web encodes but also with BluRay h.264 as well. As yet I haven't seen if there is a problem with MPEG-2 for DVD so I will check this out too!
Does anyone else see this happening or does anyone know what might be the problem?
I thought the Premiere Pro project might have been corrupt so tried a different project but the same issues were happening here too.
Any help would be really gratefully received.
Cheers
EDIT - I have just found this online which is exactly the problem I am having! Thanks a bloody bunch Apple! 10.9.3 causing headaches for Mac Pro users | MacIssues
Message was edited by: Alex CameronAgreed, I now have a project to GET OUT, and AME crashes consistently 1/3 into the render. It appears to halt all processing after (real time) 00:02:30
Am seriously considering uninstalling CC as I am beginning to find other issues in some apps, and going back to CS6/MC just so I can get work out. Durn it Adobe this is AWFUL!!
Alright, let's try to be constructive instead of throwing rocks... but the frustration level is high, and I have material on deadline. Let's get with this, guys...
What OS Win7, 64-bit
What version of AME/PPro (Please be specific by getting the full version number in the About Adobe Media Encoder screen) 8.2.0.54 Ppro: 8.2.0 (65)
When is it crashing (Again, the more detail here about where it was in the encoding process the better) roughly 1/3 into the sequence, always on exactly the same frame - tried replacing the clip with something different to see if it was a timeline error, and NO EFFECT.
What is your source (PPro project or media file (what kind?)) PPro
If the source if a PPro project, does it work when exporting directly from PPro? NO
What format are you exporting to? H.264, QT, WM, tried everything my client can play.
Do other formats work? MPEG2, QuickTime, etc? NO
Have you tried with GPU rendering on? How about turning it off by switching to Software-only mode? Mine doesn't have any choice, it's software-only.
Have you tried disabling Native Sequence Loading? (AME Preferences: General > Enable Native Sequence Loading) No effect
Other things I tried: uninstalling/reinstalling AME, setting cache to a fast local disk. -
Adobe Media Encoder stopped working in this project, works in others
Adobe Media Encoder just stopped working in my current project (in PPRO CS3). I'd output several MPEG2-DVD and Windows Media Files. Then I went to make one more MPEG2-DVD file, and when I clicked OK in AME, nothing happened. It should open a window to select where I want to put the file, and a few more options. No crash, no freeze, no error messages..and no output.
None of the AME formats work (WMF, Quicktime, etc). But other exports do work. I made my MPEG2-DVD file using Export to Encore.
I opened another project I'm working on, and AME does work in that project.
Back to my current project, and it still doesn't work.
I've rebooted, and uninstalled-reinstalled PP CS3.
Anyone fixed this? Thanks!After some more playing, I discovered that the other sequences in this project do still export using AME. So I made a new sequence, copied all the media from the problem sequence into the new one, and it exports OK. I lose fairly extensive Encore chapter marking, but that's a minor problem. No way to "cut and paste" chapter markers, I don't suppose?
For curiosity value, if I make a duplicate of the problem sequence, all the media in the duplicate sequence has a red bar (unrendered) except for the parts that have already been rendered, which have a green bar. This is straight transferred DVCam media and shouldn't need rendering. If I add some new video to the sequence, it gets a red bar too. Bizarre. Oh, and it won't export.
I tried a few other tricks with the original problem sequence: delete all media, and replace with one new short clip; delete the chapter markers; shorten the work area bar to just a few seconds and try to export "work area only"; turn off tracks; deselect either audio or video in AME... nothing worked to make this sequence export.
I also tried making a whole new project, and importing this one into it. Nothing changes - the problem sequence still wont' export, a copy of it leaves all media "unrendered..." exact same trouble as the original project. But it was while playing with this new project that I discovered that my other sequences did export, leading me back to the original project. That should have been the first or second thing I checked. Brain-dead Sunday.
Conclusion: something corrupt in the sequence, but darned if I can figure out what. Not the media. Not the chapter markers. There's code in the sequence itself, and I guess that must be it.
Enough time wated on this project. Thanks, all!
Gary -
Why is .flv not an option in Adobe Media Encoder or Adobe After Effects?
Also, when Adobe Captivate converts the video it looses the Alpha channel.
HelpThanks for taking the time to answer this question. Knowing this isn't possible at least narrows my options down. It would be helpful to provide some kind of list of what comp settings carry over into AME from After Effects. Is it essentially everything that is enabled in the Timeline? (I know that motion blur settings do.)
I'll put this in a feature request, but yes, we need the other half of After Effects Render Queue in AME in order for AME to be a good replacement for rendering from AE. I'll give you my thoughts on why Render Settings are essential before you would actually want to render with AME instead of doing so because you have to (either because you want to render in the background, or need a codec that has been removed from AE.)
1. Speed: Simply applying a Render Settings preset is much faster than manually setting motion blur, frame blending, work area, etc.
2. Reliability: Not being able to apply a Render Settings preset at the time of render is a recipe for missing a crucial setting buried in a comp, then having to redo a render and wasting time.
3. Features: As noted above, there is no way to approximate Render Queue's ability to change resolutions at render, which results in a lot of wasted time when that feature is needed.
Render Settings I think are crucial to making AME rendering worthwhile for AE users:
1. Rendering resolution
2. Work Area/Entire Composition toggle
3. Field Rendering (wait, does this mean AME can't currently render to fields?)
4. And PRESET ability these settings, so I'm not doing them manually every time.
I realize that your team clearly doesn't spend the same amount of time I do making low res H264 previews and sending final files out in H264 format, so you don't appreciate the impact of the changes you made. Moving to AME for that stuff is a real inconvenience, but implementing the settings above could help soften the blow.
Thanks,
Jerry -
Adobe Media Encoder CC 7.2.0.43 still crashes after beginning of encoding - bugs for months now!
Adobe Media Encoder CC 7.2.0.43 is still crashing after beginning of encoding! In my case this bug exists for months now and Adobe is not able to get rid of its own programming faults! The user pays a lot of money for the license and doesn't get a functioning software! I spent days to get a solution now, but NOTHING of your suggested help works!
This is my 'support' history beginning in AUGUST (!):
Sent: Thursday, August 15, 2013 ...
Subject: Bug Report
Product: Adobe Media Encoder
Product Version: CC
Operating System : Windows 7
OS version: Service P1
Concise problem statement: Steps to reproduce bug:
1. Go to Premiere Media Export
2. Stating Media Export Parameters for ME
3. Starting ME
4. Define video title and path
5. Start Media Encoder CC rendering
6. ME states 'Preview not available'
7. Rendering aborts after about 15 sec.
8. Media Encoder CC crashes, no matter which kind of video! Every time.
9. Direct 'Export' from Premiere CC is possible with all the same parameters, but CC AME crashes!
10. Also installed Premiere CS 6 Media Encoder WORKS without any problems, but not the CC Media Encoder!!
Expected results: Media Encoder CC WORKING. This is still my expected result as a paying customer!
My steps to solve these problems (with Adobe's help) were / are:
- Cleant every suggested media cashes.
- Tried to render the sequences also without audio.
- Tried to render as one pass.
- Even if I try just to export ONE simple standard SONY PMW EX1 mp4 file which should never cause problems it chrashes, also without audio.
- Also if I clean all preferences and caches before, EVERY file type crashes, no matter if I try to export a video or a still picture.
- This is not happening in Adobe AME CS6 with the same files, but in CC!! CS6 still renders reliably with preview, but CC crashes without being able to show any preview.
- Held the Shift key down while starting AME. This should reset preferences and so on...
- Deleted suggested "7.0" directories as described in other forum posts concerning this topic.
- Logged out of my CC account.
- Deinstalled and reinstalled PPro, After Effects, InDesign, Flash, using Adobe Creative Cloud Cleaner Tool. All is the newest version 7.2.
- Set GPU renderer to "Software Only". Some video cards have issues when GPU is set to "OpenCL" or "CUDA".
- Checked updates available for video driver. Latest is installed.
- Turned off "Enable Native Premiere Pro sequence import" in AME prefs.
- AMEEncodingErrorLog.txt doesn't have any content, not a single line.
NOTHING WORKED OR HELPED!
Windows Crash log: WER3A92.tmp.WERInternalMetadata.xml:
<?xml version="1.0" encoding="UTF-16"?>
<WERReportMetadata>
<OSVersionInformation>
<WindowsNTVersion>6.1</WindowsNTVersion>
<Build>7601 Service Pack 1</Build>
<Product>(0x3): Windows 7 Home Premium</Product>
<Edition>HomePremium</Edition>
<BuildString>7601.18247.amd64fre.win7sp1_ ... private data erased here ...</BuildString>
<Revision>1130</Revision>
<Flavor>Multiprocessor Free</Flavor>
<Architecture>X64</Architecture>
<LCID>1031</LCID>
</OSVersionInformation>
<ParentProcessInformation>
<ParentProcessId>9168</ParentProcessId>
<ParentProcessPath>C:\Program Files\Adobe\Adobe Media Encoder CC\32\dynamiclinkmanager.exe</ParentProcessPath>
<ParentProcessCmdLine>"C:\Program Files\Adobe\Adobe Media Encoder CC\32\dynamiclinkmanager.exe"</ParentProcessCmdLine>
</ParentProcessInformation>
<ProblemSignatures>
<EventType>APPCRASH</EventType>
<Parameter0>Adobe Media Encoder.exe</Parameter0>
<Parameter1>7.2.0.43</Parameter1>
<Parameter2>52a18991</Parameter2>
<Parameter3>libmmd.dll</Parameter3>
<Parameter4>12.0.12.2</Parameter4>
<Parameter5>5073ba44</Parameter5>
<Parameter6>c0000005</Parameter6>
<Parameter7>00000000000bfd76</Parameter7>
</ProblemSignatures>
<DynamicSignatures>
<Parameter1>6.1.7601.2.1.0.768.3</Parameter1>
<Parameter2>1031</Parameter2>
<Parameter22>4c50</Parameter22>
<Parameter23>4c50fbaed87d7d2a6adc173c5da6a755</Parameter23>
<Parameter24>28b8</Parameter24>
<Parameter25>28b834131666732fe13a476b5fa8febe</Parameter25>
</DynamicSignatures>
<SystemInformation>
<MID> ... private data erased here ... </MID>
<MarkerFile>1043_ASUSTEK_G74SX_V20_WIN7</MarkerFile>
<SystemManufacturer>ASUSTeK Computer Inc.</SystemManufacturer>
<SystemProductName>G74Sx</SystemProductName>
<BIOSVersion>G74Sx.203</BIOSVersion>
</SystemInformation>
</WERReportMetadata>
Adobe team, I'm at my wits' end now and don't know how to continue. Can you help me?https://www.youtube.com/watch?v=oJ0hz9JkLgM
-
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. -
Adobe Media Encoder CC Fails To Dynamically Link Embedded AE Comps Within PR.
When launching a PR project in Media Encoder to kick off a render. The dynamic link engine loads the PR sequence just fine but during the render it fails to read any clips that were "relaced with AE comp", instead inserting an "offline media" plate. Launching the PR project and reviewing as well as rendering from within PR works fine. Please note that this worked fine in Adobe Media Encoder CS6.
*****Edit
In doing some tests to consistently replicate the problem, it turns out that AE CC has to be open WITH the replaced clip comps loaded at the time PR OR Media Encoder is running with projects that contain the "replaced with AE comps" footage. Repeating the test with AE CC closed at the time yields the "offline media" result. This is definitely a bug I'd say. AE should not have to be launched with the project files loaded up in order for any dynamically linked comps to work.
****Edit
Please note the entire product chain is CC. Thank you.Update.....
Problem solved.
It turns out that any dynamically linked CC apps must be run by the same user on the same machine in order to work properly. In this case, PR and AME were being run as a standard user on the workstation while AE was being run as administrator via the shortcut launch properties. The latter being necessary to have certain plugins function properly in AE CC. Modifying the AE shortcut to not run as administrator resolves dynamic linking issues.
Although it can be argued that logically all Adobe apps should be run by the "same user" on the workstation, it would be nice for the dynamic link engine to be more "real world" about linking projects on the same workstation in the case where a particular resource needs to be launched as an administrator. Security considerations in towe, this ain't top secret government or banking data risk management folks. Lighten up. Maybe a little warning box that pops up and says "such and such needs to be run as administrator....do you allow?".....after all this is EXACTLY what the OS does anyway when you launch as anyone other than the administrator from a shortcut. Quite reasonable for you (Adobe) to simply cascade the behavior.
Maybe you are looking for
-
Do_handle_data vs do_handle_event
Hi experts , can we explain differences b/w Do_handle_data vs do_handle_event
-
After update to O/S 7.1.2 my iPad2 is stuck on Vertical Orientation and will not shift to horizontal as it has in the past. How can I get the flexible orientation back??
-
Hello, When we attempt to save an iBot we are getting this error: Oracle BI Scheduler Error: [nQSError: 68019] Authentication Failed. Error Details Error Codes: GYFPI8RN I have only been with the company for a few months, and anyone that has touched
-
Installing Microsoft 2013 Visio via Intune
I am trying to install microsoft visio using the Office deployment Tool Click and Run. I was able to get Office 2013 to successfully install by it self to over 28 computer with no problem. So I am basically used the same Configuration.xml file but wi
-
IPad and Content Redirect in Citrix not playing MP4.
We are trying to enable Content Redirect in a Citrix environment to play videos and show PDFs through a Wiki. We can get the PDFs to show but the videos are not working consistantly. Our assumption was that Content Redirect was not compatable with