AME Render Issue

I had an interesting issue come up yesterday that seems to have stumped Tech Support. I rendered a project to Media Encoder since AE CC does not support MP4 compression anymore. The output screen for AME and the render did not show 3d. I had lights in scene that did not display items correctly and the extruded shapes were flat planes with no 3D. I rendered it in AE Render Queue and it worked fine. Have you ever encountered this before and is there a fix.

In general, it is a bad idea to try to render and export compositions that use the ray-traced 3D renderer through Adobe Media Encoder, because renders through AME can't use the GPU acceleration for that renderer. The recommended workflow is to render and export a losslessly encoded master file from After Effects and then use Adobe Media Encoder to transcode that master file to your final delivery format(s), such as .mp4. The watch folder feature of AME is very useful for making this an automated process.

Similar Messages

  • By default, does AME render an AE project with the "use no proxies" setting?

    By default, does AME render an AE project with the "use no proxies" setting? I use lots of proxies in my files and I want to make sure they are being ignored when I'm rendering in AME.

    Adobe Media Encoder encodes After Effects compositions using their current appearance. There is no control the appearance of the composition, with one exception; there is no equivalent to the Render Settings controls in the After Effects Render Queue. If you want proxies to be used, or not, set up your composition for the desired configuration before you encode in Adobe Media Encoder.
    The exception to this rule is Guide Layers. In Adobe Media Encoder, right-click on an After Effects composition and choose Source Settings, from this dialog you can control whether or not the Guide Layers in the composition are rendered.

  • Render issues with text

    I have made a short 1 min movie, and have rendered it.  I want to download to youtube, but when I try to export using quicktime conversion, it shows render issues wherever I have text.  Once I get cancel out, it shows no render problems.
    When I remove the text, the render problem still remains.  I can export with quicktime, but not sure youtube will allow this to be downloaded.  

    Please define: "render issues" and also the phrase "Once I get cancel out"
    -DH

  • 560GTX render issue help please

    I've got the MSI 560GTX-Ti twin frozr video card in my Sandy Bridge system.  It is NOT overclocked, I am running it at all factory resets.  This is the second card I have received and they have both had some rendering issues.  I'm using the latest drivers from Nvidia 266.66
    Everything looks good in general usage, but when I play the game Rift (using High settings) I am getting some rendering artifacts.  The card does not appear to be overheating as far as I know.  I have run Furmark and it looks ok.  Temps do go up to close to 70c but no graphic anomalies show up.  In Afterburner the settings are all stock factory settings.  At no time in the game does the fan seem to crank up to be audible.
    I would include an image of the screen but don't know how.  Basically the landscape will display square beams of texture protruding from random areas of the screen.  Any ideas on what is going on and how it can be fixed?
    Willax
    edit:  I ran Furmark right after getting the render issues in RIFT and the fur donut had some holes in it, the temperature was running close to 70c
    Then I changed the fan speed from AUTO to 70 percent and the temp in Furmark dropped to a steady 65 but there were still render issues with holes and extended triangles in the donut.
    It seems that this card is getting too hot and not rendering correctly, but it shouldn't be happening.  I even turned the fan up to 100% and although it got loud the temp did not change
    very much from 65c

    Well, I clicked those items and told it would be active after I started afterburner.  I restarted and the voltage slider was not active.  Nothing I clicked would let me do anything.  I hadn't really planned on doing any o/c stuff with this card, but purchased it because of the GREAT reviews on it.  I prefer to run at stock settings, and it's not giving me very good performance with those 
    I'm glad I got the extra year warranty on it and will probably call New Egg tomorrow to replace it.

  • 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

  • Any fix for CC render issue with the new MacPro Firepro D700.  Getting lines and flicker as documented in threads

    Hi,
    We're facing some critical problems with our new MacPros, CC, and the Firepro D700's.   It appears that after we upgraded to 10.9.3 the D700's no longer work with Creative Cloud.  Our Premiere renders are full of artifacts, lines, and drop out.   Same issue as documented in RENDER PROBLEM - AME and Premiere Pro CC causing random horizontal lines on H.264 Renders     Can you advise as to when the fix will be pushed?  We have turned to "software only" render, which is killing us for time.  We have a huge amount of work that goes through 4 edit bays and its putting us days behind.
    Please let us know,
    Sincerely, Jim Janicek
    Janicek Media, Inc.
    720-891-6276
    [email protected]

    You need to ask in Community: Premiere Pro | Adobe Community but do not expect Adobe to discuss future plans
    https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform for bug reports or feature requests
    This forum is about the Cloud as a delivery process, not about using individual programs
    If you start at the Forums Index https://forums.adobe.com/welcome
    You will be able to select a forum for the specific Adobe product(s) you use
    Click the "down arrow" symbol on the right (where it says All communities) to open the drop down list and scroll
    Also, this is an OPEN forum, not Adobe support... please do not post personal information

  • PAL Widescreen Render Issues

    Hello Adobe,
    I'm in need of some desperate help. For quite awhile now all video not matter what quality or format has rendered out terrible looking video. I usually work within After Effects and render out graphics using adobe media encoder. I create graphics in a HD composition (720p) and add to AME queue for render and change the preset to PAL DV Windscreen which results in terrible render quality. I have some examples below and all settings used. I need these videos in PAL for DVD render.
    Here is my workflow and settings.
    After Effects:
    1280X720, 25P 8bpc
    Graphic has been pre-comped with continuously rasterize enabled.
    AME
    MPEG2
    PAL Widescreen, Progressive.
    Screenshots for more information:
    I have done a very basic graphic to test the quality  - Render Quality test - YouTube
    Help would be much appreciated, Thanks.

    Hi
    He described the problem that the menu would not let them select any buttons, and that the menu was cut off top and bottom.
    What size did you use to build your menu backgrounds and overlays?
    Anyone have any suggests on how to get the first play to work?
    It uses to be so simple as selecting what item do you want to run first in DVD Inspector in DVDSP. What element is your first play? The Menu? You cuold try building a very short track (3/5 secs), with just black image and use that as first play (or a simple slideshow with a single black image). I have heard around the forums about some issues with some specific players with a menu as first play.
    Hope that helps !
      Alberto

  • Audio Render issue - Media Encoder

    Hello All,
    I just ran into a odd audio issue after a render.  Anyone have any idea as to why this is happening?  (audio file below)
    Sequence is :  ProRes 1080p 2997.   Rendering to ProRes.  Audio source is a .WAV
    http://www.rtbstudio.com/Clients/AudioError.aif
    Additional testing has shown that the issue only occurs when I render out of Adobe Media Encoder.
    Rendering straight out of Premiere does not produce this issue.
    Thanks!
    - Ryan
    Premiere 7

    You are correct Jim,  I was in a bit of a hurry and didn't check my language.
    It is on exports.  Odd thing about this, it only gave me an audio issue when 'exporting' to ProRes.  I did a multitude of client review Quicktime H264's and never had the issue.  Even with the 'Native Premiere Support' checkbox enabled. 
    It appears de-selecting the 'Native Premiere Support' option works for the prores.
    Will Adobe ever address this issue?  This issue makes me really nervous when exporting batches via AME.
    Cheers!
    -Ryan

  • AVDHD - Sony NXCAM - Render Issues

    Hi everyone,
    I've searched all over the forums and the rest of the Internet and still can't find a definitive answer, so I need some help, please!
    Here's the system specs:
    Camera:
    Sony NXCAM (AVCHD Format)
    The camera appears to use the mp4/h264 codec, according to the manual.
    Shooting:
    video: 1080 / 30p (at the highest bitrate setting)
    audio: 16-bit LPCM
    Workstation:
    Windows 7 
    Intel Xeon Quad-Core 2.67
    6 Gb Memory
    NVidia Quadro 2000
    These are the steps that I have been using:
    1. Copy the original footage onto a folder on the computer (I have been copying the entire AVCHD folder so the meta-data etc is all there).
    2. Create a new project and sequence in Premiere Pro. I have tried many different formats, but the one that I am using is under the "AVCHD Presets" --> AVCHD 1080p30 29.97 fps at 1920 x 1080. This is the exact same setting we are recording on the camera... the camera's settings are progressive and not interlaced, and they are also not anamorphic. I understand that there are discrepancies to what is "better" or what is truly being recorded (30p vs. 60i).. I did see that in the owners manual it states the system "Video Signal" is HDTV 1080/60i, 720/60p. Either way, the settings on the camera are set to 1080 30p.
    3. I can successfully import the media into the media bin in a Premiere Pro project.
    This is where there are a few issues:
    4. When I preview the clips, they are very jumpy, have some pixelation and artifacts, and appear to have a wobbly movement to them. Note - once they are rendered, this goes away.
    5. Upon bringing this clips onto the timeline - it always shows a red line above the clip, indicating it needs to be rendered. Usually, the amount of time it takes to render is equal to real-time... I was working on a project today with 2h 30m of clips and it took over 2 hours to render. I called Adobe support, and the person on the phone ASSURED me that EVERY clip needs to be rendered.. my reply was "even if the sequence settings are the EXACT same as the clip?", and he assured me that every clip needs to be rendered always.. which I don't believe. If the settings on the sequence are right, there's no reason that the clip should have to render.
    I understand that .MTS files must be stored and compressed heavily to be put on a memory card - so is this always a necessary step? Do the files need to be "unpacked" somehow? If so, why not just use tapes like before? The entire reason that our video unit switched to tapeless formats was because of the ease in workflow. If it takes almost realtime to render everything, what is the big benefit of using a tapeless format?  I understand that there are some upgrades in version 5.5, but I am not sure that we can upgrade at this point, do to budget concerns.
    Any help would be much appreciated - Like I said, we called support and didn't feel like we recieved any. Again, all we'd like to do is be able to import our footage and begin editing without having to render raw footage.. many of the clips we have to work with are just raw, uncut video files that need to be burned to dvd in a timely manner for training purposes. Thanks again for your support.
    David Jensen
    Video Producer
    N.C. Dept. of Justice

    Thanks for the help, guys..
    I tried both techniques, and there is still a yellow bar present above the clips.
    I understand that the yellow bar indicates that it may not be necessary to render, however the clips still appear very jittery on the timeline just as they do in the preview monitor. Is this a 60i vs. 30p de-interlacing issue that I'm looking at?
    Not to jump the gun here, but is this a situation where we should be sending files to AME if we have several hours of footage that was taken for documentation purposes vs. importing the smaller projects directly into Pr where the clips will be much smaller edits?
    I guess the follow up question is, should we be using an interlaced timeline at 60i? This isn't my first choice - I'd rather be at 30p for the timeline settings.
    Again, much appreciated!
    Dave

  • AME Freezing Issue

    Ok so I have a project recorded on all canon DSLRs and my sequences are no longer then 5 min. I want to use AME to queue up all 6 sequences to render them. I am exporting each sequence to the H.264 Vimeo HD preset. Everything gets into AME no problem, but when I click the start arrow, the first sequence just stays at 'waiting.' While this is goin on, nothing ells on my computer will respond. I can open up folders, but new applications/web pages will not load. If I try to close anything that may be open, it will not close. I attempt to end the process in the task manager, and the window and process will go away, but everything will still be stuck as is. The only way to fix this is to unplug the computer and reboot. I have no issues exporting my sequences by just clicking export in Premiere. I have not been able to find anything that seems to be going wrong in the Event Viewer, but I may not be looking in the right place. Any help would be greatly appreciated.
    Specs:
    Adobe CS 5.5 (all applications up to date as of May 29th 2011)
    Intel i7 2600k
    12gb DDR3 RAM
    EVGA GTX 470 with GPU Acceleration selected in Premiere.
    7200RPM HDDs

    We've had a couple of other similar hangs reported where Cuda hardware acceleration is a key piece of the puzzle. Do you have a Cuda-enabled graphics card, with Hardware Acceleration enabled in PPRO? If so, please switch Video Rendering & Playback to "Mercury Playback Engine Software Only" (Project > Project Settings > General) and then try queueing to AME again. Also, please report what graphics driver version you're on.

  • Low Memory Environment Render Issues...

    Howdy folks,
         I've been working on a 13 minute promotional video for a non-profit summer camp. It is made up of mostly still images with some ken burns effects, a narration track, a music track, some titles, and some logo overlays.
         I am doing this on a 3.2 Ghz P4 with only 1.5G ram under XP sp3. I realize this is not an ideal PPro box.
         Windows XP is configured to use 2 drives for VM paging (3Gigs each). All drives have over 100gigs of free space on them.
         Now until recently I've only had a couple of small issues which I suspected were related to trying to do this in a low memory environment. In one case a flash render would die at the same point every time (error was something along the lines of "did not return a valid frame"), and simply scaling down the still image clip at that point in the sequence so that it was closer to the project size took care of it. That method also helped in a few cases where some images would not render at all, and just appeared as black screens in the final video (the render process did not fail, but the end result was missing clips).
         Then there was one case it seemed to fail at random points. A simple reboot took care of that, and it exported just fine.
         But now, however..... Now it's back to failing at random points (sometimes it gets 3500 frames in... sometimes as far as 13400... or anywhere in between) and additionally, by viewing the incomplete flash video file with VLC (which I need to do in order to find out where it failed because PPro never tells me) I find that some of the images are black screens, as before.
         The problem now, is that it's never the same point of failure, and it's never the same images blacked out. And rebooting and or killing off extra processes does not help.
         Now this was rendering fine last week. Here's the kicker - I haven't changed much of anything since then. The project is still the same length, with just about the same number of cuts, tracks, and assets used. The only things I've done since then are:
         1) I duplicated the sequence so that I can make some changes unique to the web-version of the video, and still save the old sequence to go back to. The old sequence has remained untouched and I haven't even looked at it since then.
         2) Created 2 new titles and inserted them in place of some old ones in the new sequence which weren't appropriate for the web version of the video (only the text is different in these new titles... they are the same style, size, etc. as the old ones they replaced)
         3) I shortened some empty time/space/pauses between sections of the sequence.
         So those are all minor changes... but I can't shake the rendering issue no matter how many times I restart or scale down an image that was blacked out or appears at one of the random points of outright failure (again, with the "did not return a valid frame" issue).
         I did notice that after I duplicated the original sequence, the project takes much longer to open. Does having another sequence present in the asset bin use that much more resources? Even if the clips in that 2nd sequence use the same assets as another? I'm tempted to remove the original sequence and see what happens, but I don't want to lose it and have to un-edit the web version whenever I want to go back and re-render the DVD version.
         So basically I'm looking for anything that might cause the small changes I made to be giving me so much grief now.
         Any input is appreciated. Thanks.

    You may have a corrupt project. Try creating a new project and importing the old one into it.
    If you still experience problems then carefully do each of these troubleshooting tips. One or more of them is likely to help.
    Cheers
    Eddie

  • Dreamweaver 8 Design View render issue

    I was wondering if anyone else has noticed a highly
    irritating issue with DW8 that is apparently not an issue in the
    Design View of DW MX 2004.
    In DW 8 for some reason I'm getting an extra 150 pixels of
    white space to the right of my #content container. It only appears
    to happen when the content within the #content container does NOT
    exceed the length of the content in my menu container (#priNav2).
    In other words, if the content is longer then the menu, it renders
    fine.
    See here:
    Dreamweaver
    8
    But, in DW mx2004 the exact same file shows up how it should.
    Dreamweaver
    MX 2004
    Does anyone have any suggestions on how to resolve this issue
    or have a clue as to why this is happening? It's really one of the
    only bugs left preventing me from upgrading to DW 8 anymore.
    Thanks,
    - Paul

    After some tinkering around and a call to Tech. Support I
    eventually resolved this issue by pointing out a bug to Adobe.
    Apparently the problem is the View / Visual Aids / Invisible
    Elements option. If this is turned on, and you have a website set
    up similiarly to
    this one, you will
    experience this sporatic, extranenous white space that shifts your
    content around. It is not an issue in DW MX 2004, only DW 8.
    The solution is to just simply turn OFF the "Invisible
    Elements" option. Then the page will render the way it should.
    A bug report has been submitted.

  • UI Problem: Tab render Issues on page navigation

    Hi All,
    I am with a ADF application using jDev11g where i have some JSF pages and have navigations between those pages.
    In the first page i have two tabs.
    In the second tab of that page I have put the ViewObject (ViewObject is based not base on Query, ie. not on any Entity Object) attributes as input text fields.
    After that i have a Search page next where i search on some conditions and from the result table I select a specific row and catch its column values. Using the row record I populate the viewObject of that first page while clicking on a button on the second page (this button calls a AppModuleImpl class method to populate the ViewObject).
    Till this it works fine. But there are some UI related issues associated with it.
    Query--1:
    Approach 1: As i have dropped a View Object as inputText and it is not populated on on the first go it will have label field but the value field will not be rendered at all. But this doesnot meet the UI requirement. I need to have a value field (white box with no data). How to resolve this? Are there any property for that to render.
    Please suggest.
    Work Around: For this problem i applied a work around by dropping some extra input texts beside the VO attributes (as text field without label) in my 2nd tab of first JSF page. And while navigating to second page i made these extra i/p fields as hidden (through Disabled/Rendered property) in the backing bean.
    Then i populate the ViewObject from second page and returned to the first page(default goes to first tab) and opened the 2nd tab i found all the extra nput text fields visible which i had disabled. Can you tell why it's happening?
    Please suggest for these 2 approaches.
    Query--2:
    Is there any way that when i navigate back to the first page by default the second tab will open instead of the first?
    Please suggest.
    Thanks in advance.

    Hi,
    Query--1:
    Approach 1: As i have dropped a View Object as inputText and it is not populated on on the first go it will have label field but the value field will not be rendered at all. But this does not meet the UI requirement. I need to have a value field (white box with no data). How to resolve this? Are there any property for that to render.
    Please suggest.
    an input field need an object to write to to display the input area (otherwise its read-only). So you can create your input form pointing to a managed bean initially any then, when users enter and submit data, save it manually in ADF and after this hide the bean bound fields and show the ADF fields. Or - before getting onto the page - you create a new row if the current collection is empty.
    Short answer: there is no declarative way to do this
    Is there any way that when i navigate back to the first page by default the second tab will open instead of the first?
    Please suggest.
    The ShowDetailItem component that is used to render tabs has a Diclosed property that you can point to a managed bean method. When you navigate back, you have the managed bean returning false for all but the second tab.
    Frank

  • Round Trip and Render issues - Color back to FCP

    Graded, rendered, send to FCP. Looks good on the timeline, minor issues with some variable speed clips and sound (for some unknown reason) but i had duplicated timelines and was able to gather everything onto one timeline and each clip plays back fine, but i can't really get a good read thru, the timeline after about 5-7 secs will start to hold up. I think maybe its having a problem playing back the rendered files off the internal harddrive and the firewire 800 drives I use for capture scratchs. So I export a self-contained movie file and it won't play without stopping in either quicktime or FCP. I can't figure out what the problem may be or how to fix it. My next call is apple support but i figured maybe one of you esteemed gentleman may be able to see the tree in my forest. Thanks, Steve

    Michael Trauffer wrote:
    but i figured maybe one of you esteemed gentleman may be able to see the tree in my forest.
    I see a lot of trees here, so I'll grab my chainsaw and start swinging away
    I appreciate that, as here in south louisiana we keep our chainsaws oiled and ready to roll
    Graded, rendered, send to FCP.
    I follow you up to this point. I'm assuming you're using XDCAM EX footage?
    Yes
    Looks good on the timeline, minor issues with some variable speed clips and sound (for some unknown reason)
    I should point out here that it's been documented on numerous occasions in this forum that Color doesn't necessarily play well with variable speed clips. The Color User Manual has a section on page 75 that shares some steps that should be performed before sending a sequence to Color. One of those steps is baking a variable speed clip into a quicktime movie.
    Gotcha, I actually did that to solve that issue.
    but i had duplicated timelines and was able to gather everything onto one timeline and each clip plays back fine,
    Sorry, I can see how this can be confusing. What I meant to say that is when i had the weird audio issue (it sounded as if the stereo pair were out of sync with eachother, giving it a wierd audio reverb even though i could not visually identify from any information available on the timeline) I then overwrote those audio files and that fixed it. But all this was on the initial sequence timeline that i had loaded from color after the grading.
    but i can't really get a good read thru, the timeline after about 5-7 secs will start to hold up.
    Define "read thru". If the sequence is dropping frames, it sounds like a bandwidth issue with your scratch disks, or a hardware setup problem.
    Yes dropping frames is exactly what it was doing...I am running a quad-core xeon with 2.8ghz, with 4 daisy-chained firewire 800 drives.
    I think maybe its having a problem playing back the rendered files off the internal harddrive and the firewire 800 drives I use for capture scratchs.
    How many drives do you have designated as capture scratches?
    I have one folder on one of the 800 drives designated for this project. In color I chose a different 'render Directory' on the internal hardrive (i believe it was a default)
    What specific drives are you using?
    Lacie 500gb drives
    If by "internal harddrive" you mean your system drive, this is a big no-no. I can only assume here, but I think you're working with ProRes material at this point. Depending on your specific Mac, the internal drive may not be up to the task. If you consider that that drive is running your entire OS, plus any open application, plus Final Cut Pro, plus accessing the render files, plus any other source material that you may have stored on that drive, you're asking that one drive to do a whole lot of work.
    I get that. But should i change Color's render directory to somewhere in the project folder on the Lacie Drive?
    So I export a self-contained movie file and it won't play without stopping in either quicktime or FCP.
    A self-contained movie file of what?
    The sequence.
    How are you exporting?
    FCP export > quicktime Movie > What are your sequence settings?
    Xdcam 720p30 project settings based on xdcam clips, 1280 x 720
    Open the file in Quicktime Player, and press Command I to open the Info Window. Make a note of the format information and post that information here.
    I wish i could and I will when i get back to the office after dinner.
    Chainsaws can get pretty heavy after a while. I'll take a break here and see if I hit anything of value.
    I think you did...but confirm for me. Color's render directory, whats a better place for it? And thanks for the quick response it is duly appreciated.

  • Apple Pro Res 422 / FCP7 render issues

    Hello,
    I do a lot of timelapses and have pretty good workflow for all this. However, I am experiencing one issue that makes everything a bit difficult. I appreciate if anybody could help me.
    My workflow is:
    1. Shoot some stills RAW
    2. Develop in Adobe Camera RAW
    3. Import stills sequence and render in AfterEffects CS4 to AppleProRes 422
    4. Import to FCP7 and edit
    5. Grading / color correction
    6. Publishing
    All works fine, however I am having very often an unpredictable issues with the Apple Pro Res 422 codec under FCP7.
    I always render a bunch of sequences from AE using the same settings for all files. The only difference is resolution.
    My render settings for exporting from AE are:
    - Apple Pro Res 422 wrapped in MOV
    - render in 10-bit YUV from RAW 16 bit sequence files
    - AE project in 16 bit
    - Resolutions of rendered all files around 3500x2500 px, this vary from file to file.
    The sequences render fine in AE.
    The sequences play properly in QT, I can import them to FCP properly, play in FCP properly. I can drag to timeline, scale, rotate, scrub etc.
    However: Some sequences fail to render in FCP7.
    When I drag them to my working sequence in timeline (Usually a Full HD 1080p, Pro Res 422, YUV), scale down (usually) and try to render timeline footage (don't mean exporting here yet) I get the following error:
    "Codec not found. You may be using a compression type without the corresponding hardware card."
    This happens on many computers including iMac, MacbookPro and a Mac Pro.
    I discovered that setting the footage size to even width and height figures when exporting from AE eliminates the problem sometimes, but it does not help in all cases.
    Also it sometimes help if i take such sequence, crop and export using QT under the same settings, just a few pixels less in size. But again - it helps sometimes.
    Can anybody help me with these?
    Anybody experiencing similar issues?
    Thanks a lot.

    I had the same problem when we started to edit on Pro Res timelines. The solution I found was to go the Sequence Settings > Video Processing > and change the Render setting to "Render in 8-bit YUV" that allowed me to actually render the timeline and view my work. Hope that helps.

Maybe you are looking for