Render tiff sequence starting with comp frame# in adobe media encoder?

Hi
Does anybody know how to render out a tiff sequence with AME using an after fx comp where the tiff frame numbering generated by AME reflects the same frame numbering in an After fx comp? so if my work area bar in AE comp starts at frame 73 then the first tiff frame rendered out of AME starts at frame 73. at present it seems to always start at 0 which is no good because i then have to renumber all the frames to ensure they replace the correct frames in the image sequence. i already know how to do this rendering directly out of AE. however its nice using AME because you can continue to work in AE while AME runs in the background.
cheers!
angus

Unfortunately you cannot specify a start file number.
That would make a good feature request.
Cheers
Eddie

Similar Messages

Export with .mov extension in Adobe Media Encoder

Hello Forum,
How do I get media encoder to export a H264 with a .mov extenstion rather than a .mp4 extension?
Mac OS 10.8.5
Media Encoder 7.2.0
Thanks all!
- Ryan

Hi TacoRye,
Thanks for posting on Adobe forums.
Please choose Format QuickTime in Export Settings to get .mov files.
If you do not have QuickTime Player installed on the system please install from this link
http://support.apple.com/downloads/#quicktime
Please update if this works out for you.
Regards,
Sandeep

Where do I set the "Time Span: Length of Comp" in an Adobe Media Encoder Preset?

Since Adobe is removing H.264 from After Effects, I'm trying to get the workflow set up with AME. However, when I send a comp to AME, it doesn't render the whole comp, just the work area.
How can I set it up to automatically render the entire comp, like I do with the Render Queue?

Just open up the render settings and look at the bottom. Render settings is where you would expect to find the render settings. Double click any file in the cue to open.

Horrible video output quality with Premiere Pro CS4 + Adobe Media Encoder

I am trying to make some changes to a DV format file, and output as the same DV format. When the video is brought into Premiere, it looks crisp in the left-hand video box. But, when playing it on the right window and when encoding it, it comes out as a mess with substantial compression artifacts.
What confuses me is, I have experimented with a lot of codecs--even uncompressed AVI. There is no change in the video resolution--source is 720x480, as is output. I am keeping all the pixel aspect ratios the same as the source footage.
What is creating this distortion? I have no scaling of the video whatsoever in the sequence...
Is there some compression box I'm not seeing here?
I've attached a screenshot of a still from the video. As you can see, substantial artifacting around the lettering, making the text unreadable.

Some suggestions and answer at least the 16 questions at the end of the Wiki article.

Cineware C4D Render Fails in Adobe Media Encoder

I'm trying to render an After Effects composition using Cineware and a very basic C4D Lite layer.
It renders fine directly in the AE render queue, but hangs and eventually fails in Adobe Media Encoder.
The error message is:
Encoding Failed
Export Error
Error compiling movie.
Unknown error.
I'm using Windows 7, Adobe Creative Cloud. I've opened the default TCP port 5030 in Windows Firewall & tried disabling Windows Firewall altogether. I've tried rendering with both CUDA and software only. I've cleared my render cache and restarted several times. I've had no problems rendering in Media Encoder until I try to enable a Cineware layer. It makes a sheep noise.

Has anyone successfully rendered Cineware using Windows 7 platform ?
Is there a particular port I should try besides the default 5030? And do I need to set this port somewhere in Adobe Media Encoder CC settings or just under the Cineware effects settings?
There's no reason why this shouldn't at least be documented somewhere. I'm using a brand new clean vanilla install of Windows 7 and Creative Cloud with Intel Core I7 + NVidia GPU.
"Unknown Error" to me says some code was sitting in a huge "try/catch" type block with the exception not being handled.

How to have a sequence start with specific number in mapping

Hi,
I can not find a way in the mapping to specify the "start with" attribute for sequence. Currently I have to execute this from sqlplus; select max(id) from tableA, then create sequence start with max(id)+1. I would like to integrate this step into owb. I'm using 9ir2. Thanks.

You can do this from a stored procedure that you invoke from your pre-mapping trigger:
- Scan the source and get the max_id
- execute immediate 'drop sequence; create sequence ... start with '||max_id+1
Etc.
Good luck, Erik Ykema

Could not complete the Render Video command because of a problem with Adobe Media Encoder.

So initially, my problem was solved, but it stopped working again. Same issue. I tried installing the media encoder app, but no luck please help!
Here's the original post:
Hello, I'm running a macbook pro retina, and previously I was able to render video with no issue, and now this is popping up. I've tried deleting and reinstalling photoshop, but it was not helpful. I would very much appreciate any help or guidance. Thanks!
Here's the error message I get:
Could not complete the Render Video command because of a problem with Adobe Media Encoder.
Here's the original thread: Could not complete the Render Video command because of a problem with Adobe Media Encoder.

Have you tried re-installing Photoshop?
Benjamin

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

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

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

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.

Problems rendering Every-line Composer texts with Adobe Media Encoder

I find the text paragraph setting "Adobe Every-line Composer" a huge time saver when dealing with large amounts of text in after effects. I rarely have to do any manual tracking or line breaks to make it look good, as opposed to working with the standard Single-line Composer.
The problem is that when I render through Adobe Media Encoder (which I'm forced to do since they removed H264-mp4 support from AE:s internal renderer) the text is treated like single-line composed text. So the final render doesn't look like my AE project.
I've found two solutions to this problem:
1. Render a lossless video file in the AE renderer and then compress it with Media Encoder. This takes more time and HDD space, and it doesn't allow me to continue working in AE while rendering.
2. Only use Single-line composed text and make all adjustments manually, the old school way. This would not be a problem if I had not already used, and fallen in love with, the Every-line option.
Is there anyone that can think of a third, and preferably better, solution?
I use the CC 2014 versions of AE and AMC.

No, the text doesn't animate at all. It's just a normal static text box. The text part is extremely simple. All animations are done in other layers and pre-comps, combined with pre-rendered 3D graphics from Cinema 4D, rendered as image sequences. My problem is a bug, plain and simple. Or perhaps you could call it a "lack of feature support" or an "incompatibility between AE and Adobe Media Encoder".
My problem appears only when my AE project has text boxes with the "Every-line Composer" option enabled (press the menu button in the Paragraph window to find it), AND the project is rendered through Adobe Media Encoder, no matter which output format I use. I have no problems what so ever inside of after effects, or when rendering Single-line Composer text in AMC.
So, the problem is that Media Encoder doesn't recognize Every-line composed text. Instead it changes it to Single-line composed text, messing up text tracking and line breaks.
To clarify: the Adobe Every-line Composer is analyzing the entire text box instead of only the current line. That way it can automatically change the tracking of individual lines to better distribute the line breaks and build a better whole, avoiding those stray words on the last line for example. Extremely handy, if you could only render it.
I never wrote anything about animating text or that the codec is related to the text problems in any way. AMC is the problem. The codec is only a secondary problem since its the lack of mp4 H264 support that forces me to use Media Encoder in the first place, instead of using the AE render queue as I did in previous versions of AE. I like many things about rendering through AMC, like being able to continue working in AE while rendering, but there are still way too many glitches. And of course, there's the inability to render flv-files in AMC CC 2014, and Adobe's inability to provide a solution other than "Use an older version of AMC". Flv is their own damn format for christ's sake.
Well, enough rambling.
To put it simple:
Has anyone had a problem with "Every-line Composer" in combination with Adobe Media Encoder? Did you find a solution other than the two less-than-perfect ones in my first message?
Thanks!

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.

Adobe Media Encoder CC renders do not reflect changes to Dynamically Linked After Effects Comps

When rendering a Premiere timeline with a dynamically linked After Effects composition, Adobe Media Encoder will sometimes use an older version of the linked composition (even after I have saved changes in the After Effects comp).
For example, if I correct a spelling mistake on some text in After Effects, save the composition, and then add the sequence to the render queue in Premiere, the final output from media encoder still has the old spelling.
If I do a straight export from Premiere instead of adding to render queue, the output is always correct. I've noticed this problem on several different Windows 8.1 systems.
All versions of the software are up to date as of today.
Why is this? Is it something to do with the disk cache in After Effects? Does media encoder have it's own cache that I need to clear?

Hi, I've been having this same issue. Here are some additional things I've noticed about it:
Changes are reflected properly when played back on timeline in Pr CC 2014.
Happens regardless if the dynamic link file was rendered or not, thus deleting the render files does not fix the issue.
The issue can persist through saving, closing, and reopening both AE and Pr.
I'm using OSX 10.9.4, so this is not just a PC issue.
Other than manually watching for every change to be reflected in the render, there is no way to know a problem has occurred. Needless to say this can be incredibly costly.
Please address this quickly, it's completely unacceptable that what we render out could be a different version from what we see on the timeline.
PS Some additional things I will be testing:
Does the issue persist through closing all CC apps, including Media Encoder.
Does rendering directly out of Pr, i.e. not using Media Encoder, fix the issue.

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,

Having major issues with Adobe Media Encoder (AME) - exporting with weird image flickering/colour anomalies, crashing regularly, freezing during encode...!

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 Cameron

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.

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.

Render tiff sequence starting with comp frame# in adobe media encoder?

Similar Messages

Maybe you are looking for