Render glitch?

Hi,
I'm working with characters shot with a Canon DSLR (1080P), edited in Pr, sent to Ae (via replace with Ae comp), but they are not intended to go back to Pr because they will be rendered out as a png sequence in Ae, then printed for a stop-motion piece via contact sheet in Ps.
Phew!
My goal at this point is to roto/mask/luma key the footage then render it out it for print. BUT, it does not render it out correctly. It actually erases some of the image (check out his jeans), one of my parameters isn't being reflected in the render. See my attached screen shots of both my monitors with a rendered QT file open with the playhead in the same place as the composition. I tried rendering out a png sequence, animation codec, and h264 codec. All produced this result frequently in different areas of the composition.
What could this be?
I'm printing these characters out card stock and then cutting them out indivdually. If anyone knows of a better way of preparing the files please let me know.
FYI: The original footage is 23.98fps, but I change the composition settings to 12 fps.

Here is a screen shot with full reselution ram preview

Similar Messages

  • AE CS6: Render glitches with timeremap expressions

    Version:
    11.0
    OS:
    Mac 10.7.4
    Source Footage:
    .ai files
    Problem:
    First of all, we've been using this method for character animation since AE 7.0.  We have had minor glitches here and there, but nothing consistent enough to a real problem.  We're currently using CS5.5, and considering the CS6 upgrade.
    I am filing an official bug report for this, but am curious if anyone else is experiencing this.  I don't want to share my project here as it's for a TV show in production.
    Starting with CS6, we're experiencing random, arbitary render glitches all over the place.  Our character comps are generally two comps deep.  Meaning in the character comp, we have timeremapped comps for sequences of eyes, eyebrows, mouths, etc.  Inside those comps, there is a lot more going on than just an image sequence.  We have mesh warp keyframes and other stuff.
    All of this is controlled by various expressions that link everything to some simple master controls.  I'm sure this sounds familiar -- it's very similar to the method used in these tutorials, but not even as complex.
    As for the glitches, they are hard to pin down.  There are different glitches depending on whether the character is continually reasterized in the scene or not, which comp we're in, etc.  Really random.  The problem is resolved by proxying those precomps (the eyes, mouths, etc) with prerendered sequences.  This is an OK workaround for most cases, but we can't depend on it.
    Thanks for any help.  In the meantime we'll be sticking with 5.5.
    Bryan

    Has anyone had any success talking to Adobe about this?
    I would really like to know if they can fix this in CS6, and not wait to fix it in the CC version.  I am not sure I can convince my studio to make the plunge onto the cloud, and so we may be stuck with CS6.
    I found what sounds like a similar bug described in the previous patch (11.0.2):
         Fixed difference in rendered result between ray-traced 3D renderer and Classic 3D renderer when using time-remapping on precomposition layer with collapsed transformations.
    If they were willing to fix this, maybe they could fix this other time-remapping inconsistency bug.

  • Motion and Final Cut render glitch

    I am having a problem with renders, The Problem seems to be in Final Cut and Motion. Usually when I bring .motn in to my Final cut sequence, though some times the glitches happen in Motion as well. When I rerender, the glitches will usually appear in a different location than the first render.
    These are picts of what the glitches look like.
    http://unkevan.googlepages.com/Picture1.png
    http://unkevan.googlepages.com/Picture2.png
    I am running Final Cut Studio 5 and editing HD 720p30
    I will be monitoring the thread so ask for clarification as needed. Thank you.

    In the olden day, when SCSI was the drive protocol, render glitches that occurred in different places on every render were usually caused by bad connections between the drives or between the drives and the computer.
    Render glitches that happen in the same place each time are almost always caused by errors in the media files. Sometimes they are invisible until an application like Motion or After Effects tries to use them.
    bogiesan

  • Render glitch in AE (and FCP7)

    Every so often I will get glitched frames in AE, and also in FCP7 . The glitch happens when a clip is rendered. Most often, a diagonal line appears in a frame. Sometimes there are other issues, such as artifacting. The glitches never appear for more than one frame, and it is rare or more than one glitch in a single clip. The way we have been fixing the problem is to cut the clip around the glitch and re-render the affected area.
    We haven't been able to pinpoint the cause. It doesn't have to do with a certain filter being used. We primarily use BCC, FxFactory, and CoreMelt plugins, and haven't seen any correlation between any one filter being used and glitches appearing. We tried the usual fixes, and just recently reformatted the computer and reinstalled from scratch. It seemed to work better for a couple weeks, but the glitch came back.
    Here are two examples. I used an artist sketch filter on the video. The first glitch is a diagonal line, the second is distortion of the video/filter. The clean frame came between the two glitches.
    1st glitch: http://i.imgur.com/pdT5t.jpg
    2nd glitch: http://i.imgur.com/p3p7l.jpg
    Clean frame: http://i.imgur.com/jLXa9.jpg
    Specs: MBP with 2.66 GHz Core i7, 8GB DDR3 ram, GeForce GT 330M 512MB, currently running Lion 10.7.4
    If I've left out any information, please ask. I'm just typing as I think.

    What codec are you using? What version of AE. I'm not having any issues with any of the ProRez formats CS6 and OSX 10.7 0r 10.8

  • Render glitch in FCP7 (and AE)

    Every so often I will get glitched frames in AE, and also in FCP7 . The glitch happens when a clip is rendered. Most often, a diagonal line appears in a frame. Sometimes there are other issues, such as artifacting. The glitches never appear for more than one frame, and it is rare or more than one glitch in a single clip. The way we have been fixing the problem is to cut the clip around the glitch and re-render the affected area.
    We haven't been able to pinpoint the cause. It doesn't have to do with a certain filter being used. We primarily use BCC, FxFactory, and CoreMelt plugins, and haven't seen any correlation between any one filter being used and glitches appearing. We tried the usual fixes, and just recently reformatted the computer and reinstalled from scratch. It seemed to work better for a couple weeks, but the glitch came back.
    Here are two examples. I used an artist sketch filter on the video. The first glitch is a diagonal line, the second is distortion of the video/filter. The clean frame came between the two glitches.
    1st glitch: http://i.imgur.com/pdT5t.jpg
    2nd glitch: http://i.imgur.com/p3p7l.jpg
    Clean frame: http://i.imgur.com/jLXa9.jpg
    Specs: MBP with 2.66 GHz Core i7, 8GB DDR3 ram, GeForce GT 330M 512MB, currently running Lion 10.7.4
    If I've left out any information, please ask. I'm just typing as I think.

    so what are your clip settings (select a clip in the timeline and hit command-9)?  Frame rate, pixel dimensions, pixel aspect ratio and codec (or compressor) and field dominance are what we need to know.  And what are your sequence settings (in fcp) or compositon settings in AE?
    I'd think of 3 obvious things that might be responsible;  a non fcp friendly codec like h264, mismatched frame rates and mismatched field dominance.

  • Premiere CS 5 render glitch

    Hey guys! Im having serious render issues with Premiere CS5. I always
    use to render the work area before the export of a session. But this
    time there is a serious glitch during the rendering: The progression
    bar takes an insane amount of time. Even though the Sequence is just 2
    minutes long. For example: It takes 30-40 minutes to get from 90% to
    95%!! The percentage number just goes back and forth. I shot a 20
    second clip where you can see this weird glitch
    http://www.youtube.com/watch?v=MR_TGW6hLhA&context=C4ed381fADvjVQa1PpcFP9KzFRiX7LQnV7VMzVl f1eSBV1JS7qhgg=
    does anyone have an idea where this glitch could come from ?
    btw: when I go directly on "export" instead of rendering the sequence,
    everything works fine!
    cheers

    Not familiar with an issue where the render doesn't work and export does (I've always had export fail, too), but when I've had those issues with rendering/exporting, it's always been one of two problems: a) I've got a "black hole" in my video where there's a couple frames without any video in one of the tracks, or b) I've got a still image that's too big for Premiere to process.
    Honestly, though, unless you've checked the box for the export to "Use Render Files" in it's encoding, there's no need for you to render before you encode. I never do, and I have beautiful results. The only time I ever render is if I need to have a smooth playback of a complex timeline involving several layers of RED material and I need to have smooth playback at 100% for client approval before the encode. But even then, I never let the encoder use those render preivew files...
    My understanding is that it's easy for those files to get corrupted, so you can end up with unsatisfactory results in your export by using them.

  • Render glitches in Final Cut Pro 4.5?

    Anyone else having a problem with audio and video glitches in the render files when using Final Cut Pro 4.5? I'm operating on a G5, OS 10.4.1, and 4 gigs of RAM.
    -Patrick-

    I recently updated the OS, and I'm running QT 7.0. This just started happening 2 days ago. So I don't think the OS is the issue. Everyone else at work is running 10.4.1 and they don't seem to be having the same issues.

  • Preview and Render Glitches

    Hello I am working for past 3 years on same system and hardware setup, till this days everything was fine. Glitches like this show up:
    <iframe src="https://www.flickr.com/photos/jnatheanimal/17043805548/in/set-72157651694316889/player/" width="800" height="450" frameborder="0" allowfullscreen="allowfullscreen"></iframe>
    System info:
    Windows7 Professional, SP1
    Intel Core i7 2600 3.4GHz
    8gb RAM
    Nvidia GeForce GTX 570
    Adobe Premiere CS 5.5 - updated
    Footage info:
    Canon 5D - 25fps - works well
    Canon 7D - 50fps - gives glitches
    I tryed to block CUDA, in Premiere and from the icon toolbar, nothing changed. Have updated quicktime, divix h.264, but doesn't helped at all.
    Do You have any ideas?

    Well, I don't really have a clue. The only other thing that springs to mind is a CoDec breakdown/ incompatibility in the given environment, but you made no special mention of what footages you use (and I forgot to ask, admittedly). Do the renders go thru without any external footages (simple text layers, internally generated effects)? I would also look into the media cache and disk caches. Especially the media cache can get humungously large sometimes and then disk access will be erratic, even more so on a notebook where disk speed is limited. Use the preference options to clean it out and maybe move it to a more suitable directory than the default one in your user home directory.
    Mylenium

  • Major FCP Glitching Render Problem - Any Ideas?

    Hey folks, I'm running into massive render glitches with FCP. Here's what happens:
    In a scene with a lot of fast cutting, and dupe frames, it all plays fine in realtime. However, once I render the footage, or make a self contained QuickTime, these areas lock up and get exported as freeze frames. These freeze frames are of the last frame of the previous clip before the cut. They stay on through the length of the next clip, and when FCP reaches the cut after that, it then plays fine again. It's very bizarre. It's almost like FCP can't keep up with accessing the media, and just skips the clip. I don't know why it would do that though, because it all plays as smooth as butter in realtime preview.
    The only correlation that I've found is that there are dupe frames present in the areas where this is happening.
    I've tried relocating my render drive to another disk drive... Deleting FCP preferences... Deleting render files... Pulling my Kona card... Nothing seems to fix the issue.
    There's also another issue, which might be related. Whenever I try to apply certain filters, I get the following message, where EFFECT NAME is the name of a good number of effects:
    "The effect 'EFFECT NAME' failed to render. Your hardware cannot render at the requested size and depth."
    OR
    "The effect 'EFFECT NAME' cannot be rendered in a sequence of this size with the current graphics card."
    So, are these issues because I have the stock ATI Radeon 2600?
    Here's my rig:
    Sequence / Codec:
    Apple ProRes 422 (normal) 1920x1080 23.98 psf
    Mac:
    FCP 6.0.3
    OS X 10.5.2
    2 x 3.2 GHz Quad-Core
    8 GB 800 MHz Ram
    ATI Radeon HD 2600
    Kona 3 card with 5.1 drivers (latest)
    Media Storage / Render Drive:
    8TB Raid 5 ESATA storage
    HighPoint ESATA controller card
    ATI Radeon HD 2600:
    Name: ATY,Lamna
    Type: display
    Driver Installed: Yes
    Bus: PCI
    Slot: Slot-1
    Vendor ID: 0x1002
    Device ID: 0x9588
    Subsystem Vendor ID: 0x106b
    Subsystem ID: 0x00a6
    Revision ID: 0x0000
    Link Width: x16
    Any help or insight here would be extremely helpful!
    Thank you in advance,
    Blake

    Tried that, no dice. The media is fine. It plays without a hitch when it doesn't need to be rendered, or if it's rendered with non problematic filters on it.
    After fiddling with the freeze frame render glitch issue some more, it appears to be directly associated with "Basic Motion" changes.
    I can stack tons of filters, and it doesn't happen. As soon as I move the shot around with "Basic Motion", it locks up the clip in the render, and creates a freeze frame.
    Perhaps this is linked to the graphics card errors I am getting?

  • Random Render Line Glitch in AE CS6

    Hey Adobe Community!
    Although I have been quite happy with After Effects CS6, I have been running into some render glitches which are giving me real problems (whether CS6 is the culprit or not I don't know). On a number of jobs I am currently working on, the renders out of AE have strange bars that appear for about one frame at random times throughout the rendered clip. I can't find any pattern to the timecode or the screen location when they appear. Take a look below at the two pictures below for examples.
    Quick note: This problem appears to be similar in some respects to the issue in this discussion (http://forums.adobe.com/message/4409423#4409423). Just thought I would post it for reference.
    #1
    #2
    Here is some information about the two clips.
    Clip for picture #1
    Time: 2:06 (two seconds and six frames)
    Output: Quicktime
    Compression: None
    Composition: There is 1 mask and some motion tracking
    Clip for picture #2
    Time: 20:06
    Output: Quicktime
    Compression: None
    Composition: Utilizing the "Warp Stabilizer" in order to smooth camera movement.
    This is obviously a problem that cannot continue since AE is a huge part of my work. I really appreciate any insight you can provide on this problem.
    I know I have probably left out information that you would like, so if there are any questions please feel free to ask.
    Thanks!
    -Barrett

    Premiere and AE should be able to handle H.264 clips directly out of the 5D and 7D without transcoding, but if you're still working with the original aquisition codec after switching to another program in the pipeline then that might be the problem.  In that case, you might be forced to transcode your entire Premiere project to another lossless production codec using AME, which will give you the same quality as any other lossless codec.  This is actually a step that a lot of editors take before doing anything with their footage, if they know it's going to go through several programs down the line.  And if I understand correctly, Uncompressed QTs and high quality PNG QTs are both actually compressed.  However, they are compressed with lossless formats.  As Szalam said the QT PNG codec is the same quality as an Uncompressed QT, although I'd also suggest Apple ProRes 422 (HQ) if you have it.  Uncompressed 10 bit, Uncompressed 8 bit and Animation are lossless, but the file sizes will be huge.  If you have Black Magic you could also try that.

  • New Pond5 plugin for PPro CS6

    Just got an e-mail from Pond5 about a beta plugin for PPro CS6. Curious what everyone thinks about it:
    http://www.pond5.com/adobe
    This is definitely something I was hoping to see one day (had actually mentioned it in a recent survey).

    First off....Anyone install this yet?
    This is kind of funny....I just saw this for the first time on Pond5's website and thought it was something that was new, due to NAB15.....after a search here, I'm shocked. It's been a thing since over 2 years ago?? Wow, I never knew....I think its a great idea, but had some reservations about the integration. Wondering if it screws up anything or runs smooth as butter? I too think it is amazing that you can edit with the proxy and conform right to the HD after purchased. Still scared to install, due to my system running very well lately after getting my hands on a new Mac Pro. Don't worry, I've been part of the whole discussion about the 2013 Mac Pro render glitch thingy...Hence me grabbing one of the new ones when they got to the office and I did the switcherooo.
    Pete

  • Render problem - strange glitches after rendering in new PP 2014.1

    Hi there,
    I've updated my Adobe Premiere Pro CC 2014 to 2014.1 and since then all my renders have strange glitches.
    Both old (converted) and new projects. It's second day I can't render any usefull file. I've deleted media cache, tried not using any plugins nor effects at all and yet, it still doesn't work properly.

    I've found, that happens only when I use lumetri looks in the sequence.
    Any idea how to fix this?

  • Premiere Pro CS6 Render and Export Screen Glitch and Freeze

    I use Premiere Pro CS6 on a 2012 Macbook Retina display - 16GB RAM, 751GB Flash Storage, NVIDIA GeForce 650m Graphics Card, 2 External 4TB hardrives for scratch disks, Thunderbolt connection. When I try to render and export videos I often get a graphical glitch like in the pic shown below and my computer freezes. It happens very often, especially when there are a lot of effects in the videos - I use the GenArts Sapphire plugin often.
    This has been going on basically since I bought my Macbook 2 years ago, but it is starting to become more and more common -  considering this was the most expensive Macbook Pro you could buy I am very annoyed with this - even on some videos where I have applied no plugin effects or any color correction it happens, especially when trying to export videos.
    Any help on this issue would be appreciated.

    I am having precisely the same problem as bricklaneeditor, and have exactly the same setup: MBP early 2011, 16GB RAM, 512 GB SSD,
    30" ACD, Mac OS 10.7.4 , PPro 6.0.1
    Indeed, a restart of Premiere Pro always fixes the problem -- for a while.  I've also seen similar behavior in Media Composer 6.0.1 once or twice so am wondering whether it's an issue with this machine/OS, as the playback software architectures are so different on those two NLE's. 
    I should also mention that the problem is not isolated to any particular file format -- have seen it with timelines containing 7D footage, HDV and ProRes files.  
    I strongly suspect some sort of problem on either Apple's or Adobe's end with the GPU in this machine, as it is ATI and not Nvidia -- and is, as far as I know, the only non-CUDA GPU, at least on the Mac side, certified to work with the CS6 Mercury Playback Engine.   
    Also wondering whether an over-the-top or a clean install of Mountain Lion might shake things up enough to make a difference.  (Otherwise I'm in no big hurry to upgrade my OS.)  Is anyone seeing this problem with PPro under 10.8?  Might be worth installing 10.8 over an external HDD clone of the System drive and booting temporarily from the clone just to see if the problem persists in Premiere.  
    Anyone have any thoughts on these possibilities? 

  • Premiere Pro "3 frame" render preview glitch

    When I create a render preview in Premiere Pro, sometimes the render preview renders the same frame for three consecutive frames. In other words, after the render preview is complete, the render preview creates three consecutive frames that are the same, and then moves on to the fourth frame. It looks like a jump cut where there is none. this costs me a lot of time, since to fix it I have to unrender and then rerender my render preview.
    How can I avoid this problem?

    Hey Ann, I know that deleting the render files and rerendering will work. But this costs me a lot of time.
    Is there a way to avoid this glitch in the first place?
    It happens quite often. Am I doing something to cause this glitch?

  • Red video glitch at render and export in Premiere Pro CS6.

    I keep on experiencing red screen glitches in my videos while viewing after render and when exported into any format. After replacing the clip with another, the same problem appears at the exact same time as before. The only way to get rid of the glitch is to build a completely new project. I have attached a picture of the glitch (the JPEG is green for some reason).
    Any solutions?

    Thank you for fast answer.
    my version is  6.0.5.  ( 001 (MC: 264587))
    i use more kinds of cameras, but each provide different video file type.
    this problem is with  HC-V700 Panasonic, which is creating the AVCHD files.
    i am talking about working video window, where you see the movie you cut and edit! (not the green/blue/red bar in timeline)
    (after finishing the rendering, sometimes without it), and in case when i see it red, it is exported as well as RED screen .
    and - on the other side : i can play such movie file, by double clicking on it, (from project files list, or from timeline ) where new window appears for playing that file.
    thank you for your interest

Maybe you are looking for

  • Load XML records in a normal table

    Good afternoon all, I have a very simple question: I get a XML file and want to store that data in my Oracle database in a normal table. I have seen so many answers everywhere, varying from LOBs and using XDB etc. What i don't understand is why it is

  • Map the XCreateWindow to Frame or window in C and JNI

    I am having a window which is created in C++ using 'XcreateWindow' function I am using JNI as a interface How do i get the Window Id / handle to java frame. If I am giving any actionlistener to my frame that has to be reflected in C window Anybody ca

  • Differences in Depreciation key table structure between SAP 4.5b and mySAP

    Depreciation keys in SAP 4.5b were stored in a different table structure to depreciation keys stored in mySAP ERP 2005. Deprecation Keys that existed before the SAP upgrade still exist in the old set of tables; these have a status of “Migrated” in SA

  • The loading bar can't work correctly!

    hello, everybody, i creat a loading bar, but it can't work correctly, the code is that: as u see, the"will_load.swf" is in the same file

  • IMac Monitor not working properly

    My iMac 24 monitor has started acting strangely.  I hve what looks like snow or flickering across the whole screen.  I tried rebooting and at the Applw startup screen the scrrne is covered with noise and the Apple lgo is semi duplicated higher on the