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

Similar Messages

Audio Problems with Prores444 file (preview and render)

I'm having this problem, I have a number of prores4444 files with audio that I exported from redCine. The audio plays fine in quicktime, but when I import into AE something goes wrong. I can see what apears to be the correct waveform in the Audio chanel, but when I atempt to preview, or I render with audio, everything just sounds like static or white noise. Is ths an AE bug?

You need to be more specific. What version of AE? What version of QT? On which tracks is the audio? Sample and bit rates?
Mylenium

Why can I not preview and render all sequence clips on a CS6 project when using CC?

I am having issues with rendering all of the sections in my sequence. Some clips will render just fine while others simply display as a blank screen (see screenshot 1). Also, parts of a clip will render while others will not (see screenshot 2).
Screenshot 1
Screenshot 2
Thanks for the help in advance.
About my Mac:
Proccessor: 2.4 GHz Intel Core i5
Memory: 8 GB 1333 MHz DDR3
Graphics Intel HD Graphics 3000 512 MB
Software Mac OS X Lion 10.7.5 (11G63)

Hi, drhalm.
Thank you for visiting Apple Support Communities.
This sounds like your music is not stored locally on the device and accessing your purchases in the cloud. There is a new feature in iOS 7 that shows all purchased music and requires and Internet connect to play this content. You can download any missing media via the steps in the first article below. If the media is located in your iTunes music library, you can sync the media from your Mac to your iPhone. If unfamiliar with the process, I have included the steps in the second article below.
Downloading past purchases from the iTunes Store, App Store, and iBooks Store
http://support.apple.com/kb/ht2519
iTunes 11 for Mac: Set up syncing for iPod, iPhone, or iPad
http://support.apple.com/kb/ph12113
Cheers,
Jason H.

Extremly bad previews and render times.

i have been working on a video in AE CS6 for a couple of days now but something changed after i added a 3D Solid layer with render set to ray-traced 3d, and now i can barely see my project in the compositon window as it gets
extremly pixelated. whith extreme difficulty i managed to complete the project but when i started the render of the viedo it gave me an estimated render time of 104 hrs for just one 3d layer that is only present in the
video for about 5 seconds out of the 4min long viedo. unfortunatly i cant enable GPU Ray-tracing because it says its not complatible even after i updated my drivers.
Specs
Gpu: AMD HD-7870
Cpu: A10-5800K (APU)
RAM: 8 gb

That GPU is not one that After Effects will use for PGU acceleration of the ray-traced 3D renderer.
The ray-traced 3D renderer is quite slow when it is just running on the CPU.
For details of GPU processing, see this page:
http://blogs.adobe.com/aftereffects/2012/05/gpu-cuda-opengl-features-in-after-effects-cs6. html

Caching, SSD's, improving RAM preview and rendering in After Effects CC

I've read a few posts and looked at some of the optimising After Effects for performance posts but I'm wondering if anyone has any suggestions on settings for helping getting the best performance out of After Effects for my setup. I'm like to be able to explore more advanced effects like Trapcode and things like that but for them to preview and render as quickly as I can... as I'm sure we all do.
I have a 12 Core Mac Pro 2012 with 64GB RAM, a SSD that I use just for the system, a 4TH HDD for all my files and projects and 2 new SSD's that I installed today that I thought I would use as a cache disk and and a disk for my renders.
I decided this based on these guidelines that I found:
My Media and disk cache settings:
If I set the Conformed media disk as another disk separate from my cache is that good for rendering and previews?
My memory and multiprocessing details are as follows:
Installed RAM: 64.00 GB
Current RAM Usage: 3.26 GB
Allowed RAM Usage: 48.00 GB
Process ID
Application Name
Min Needed Memory
Max Usable Memory
Max Allowed Memory
Current Memory
Current Priority
548
After Effects
0.40
64.00
48.00
3.26
1 - High
Video preview, I'm not entirely sure what this is for, can anyone explain please?
I've only just discovered the Cache Work Area in background option shown here:
http://tv.adobe.com/watch/learn-after-effects-cs6/global-performance-cache/
That's going to help massively!
Just how much faster would things run with a new graphics card installed? Say a Nvidia Quadro K5000 for Mac? Is a GPU it worth investing in?
Current I just have this setup:
ATI Radeon HD 5770:
Chipset Model: ATI Radeon HD 5770
Type: GPU
Bus: PCIe
Slot: Slot-1
PCIe Lane Width: x16
VRAM (Total): 1024 MB
Vendor: ATI (0x1002)
Device ID: 0x68b8
Revision ID: 0x0000
ROM Revision: 113-C0160C-155
EFI Driver Version: 01.00.436
LED Cinema Display:
Display Type: LCD
Resolution: 2560 x 1440
Pixel Depth: 32-Bit Color (ARGB8888)
Main Display: Yes
Mirror: Off
Online: Yes
Rotation: Supported
Connection Type: DisplayPort
So, any tips that people think might help me speed things up and get the best out of After Effects CC would be very much appreciated.
Thank you in advance.

See this page for information about memory and improving performance in After Effects: http://adobe.ly/dC0MdR
See this page for resources about making After Effects work faster: http://adobe.ly/eV2zE7
See this page for information about hardware for After Effects: http://adobe.ly/pRYOuk

Display and render bug with FCPX 10.8 on a MBP retina 15"

Hi,
I have a brand new MBP Retina 15, 2.7 GHZ with SSD, OS X 10.8.3 and FCPX 10.8 and I have a problem with most of video fx that just doesn't preview and render.
When I try to preview it display black on the viewer (or white picture or no effect or something uncorrect).
When I apply the fX it render it as pur black or white. Same with Magic Bullet look, when I render it's just black picture.
No problem on geometrics fx
Same story with Motion
I throw the pref and all the basics rescue opération, even re-install FCPX and Motion following the apple process, no changes !
I've got same configuration on the MBP 17"(2009 model) and no problem.
Does it ring a bell to sbdyelse ?
Do you know a way to contact by email sbdy at FCPX apple ?
thanks
cheers
Seb

here is what I did :
Timemachine save of the mac
Restart > format the drive
Install Mac OSX
Timemachine BUT NOT APPLICATION
Re-install all app's
and it works
Important
I did a first try when I had everything from time machine except application, then FCPX was working. Then I re-installl everything from app store and webpages of the other soft (no so many) : FCPX was working. Finally to get the last few app (like office) I decided to use timemachine/application to install them... and the same problem came back. (...)
I start from start... format again... and install the app from app store and webpages, even MBL - Slice X and other different plugin and it work. I decided to not install some recent things before saving my system.
The main 2 things I didn't install are
from appstore : Resolution Tab
and from web
the SONY XDCAM driver I used this week to check some F55 files
http://www.sonycreativesoftware.com/pdzk-lt2
So It could be one of those... maybe, but I don't want to loose anymore time to know it for sure.
cheers
seb

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

Measuring preview and file render times

Does anyone know how I can accurately measure preview and file render times other than a stop watch? I know the Premiere Pro benchmark does this, but I'm trying to figure out the gains I will get with different settings for my own projects and wanted to know if there is any way to accurately capture this information or find it somewhere within the software.

There's no data base you can go to for this info. You really just need to watch the screen.
Run short tests - 1 minute, 5 minutes, 10 minutes. That way you're not waiting forever for an export to finish.

Strange previews and renders appearing with blue rectangle glitch

I am getting these strange artifacts on my previews and renders in PP Cs6. The footage is proresHQ. I have attempting adjusting every setting I know and doing a clean reinstall of PP. Any ideas?

Hi NoxPhoenix,
Have you updated your GPU drivers lately? Try that.
Thanks,
Kevin

The images imported to my stage turn up as blank and render every image previous to the rogue imported image as red squares that fill the perimeters of the image which then renders the publishing and scene testing features in flash useless, what can i do

I have been working on animating a scene in flash for a few weeks and recently I have encountered a problem with importing my images on to the stage where the images I import do not turn up, however the key frame that I attempted to import the image onto shows that it is occupied by an image and every frame previous to the key frame that just imported an image that does not show turns up as a red square that fills the original perimeters of the image, there is no solution to this problem any where on the forum and the adobe technical support staff will not help me find a solution to this problem what can I do to get Flash running normally again and fix this problem?????
Also after the first time i publish a preview after i begin using flash, flash renders the publishing and scene testing features as useless and claims that there is no HTML template found, or if the images if i import any images onto the stage that come up blank and render every image previous to that image as a red square and then try and publish a preview flash renders the publishing and scene testing features as useless and claims that there is no HTML template found. What can I do to fix this problem??? there is no solution on the web anywhere to this problem either.

I don't know if Flash has a memory limit of its own. The memory for your Flash file is based on the available memory on your computer.
There is a limit on the number of frames that you can have in any given timeline. I think that it's about 15000 frames, but that's a guess. Flash does all of its work at runtime, this means that no part of your animation is pre-compiled like it is in a video file. So the more objects that you have on the stage, the more work Flash has to do. It follows that the more objects that there are to animate, the more work your processor and the video card have to do.
Here's a list of articles on memory management that might be useful:
Garbage collection internals for Flash Player and Adobe AIR | AdobeDeveloper Connection
actionscript 3 - What are good memory management techniques in Flash/as3 - Stack Overflow
AS3 Memory Management Tips

Full screen preview and slideshow are blurry / fuzzy

Hi folks-
I just upgraded from CS2 to CS4, in part to improve efficiency of selecting photos - I wanted the zoom and loupe features. Unfortunately a very basic function has been compromised and I'm hoping there's a solution: In both full-screen preview and slideshow the full-screen image is notably blurry. This is a problem for two reasons: 1. I can't judge pictures accurately by just flipping through them in full-screen mode (without zooming to 100% to see if they are well-focused). 2. I can't use Slideshow for, well, slideshows. I've had to resort to keeping another app (like Windows Picture Viewer) open just to be able to quickly flip through and evaluate images full-screen or to show slideshows.
I've tried setting all the options related to image quality (they mostly have to do with caching thumbnails and speeding 100% viewing); I've tried purging the cache files. Nothing helps.
Any ideas? Thanks!

It seems to me that there is something wrong with it.
I am trying Bridge CS4 as a viewer for my JPEG files.
I also noticed that the previews were fuzzy. I activated the high-quality previews as well as the option to generate the previews at screen size.
Here's what I noticed. I went to check out a specific photo that is quite sharp with a number of straight lines, angles, details, where it's very easy to detect a lack of sharpness. That photo immediately looked fuzzy to me, which didn't jive with my memory of it. I quickly opened it in other viewers, which displayed it as intended with all the expected sharpness.
So, I went through the settings to see where the problem could be and I immediately thought of checking the box to get software previews instead of hardware, restarted the app, purged the cache, tried again. There my photo had recovered its sharpness, or at least most of it. I thought I found the culprit, but not quite.
I went to browse other photos and found one in particular with a lot of fine detail (hair) and that photo also didn't display all the sharpness that it should have (I was still using software mode). The difference was very slight and to make sure of it it required A/B comparison between Bridge and PS, but there was a difference.
Now I tried the opposite. I went back to hardware rendering mode, restarted, purged the cache, tried again. That second photo looked alright in preview, but the previous photo looked fuzzy again.
So, it doesn't work the same way for each photo...
What's the main difference between the first photo, obviously fuzzy in hardware mode, and the second one, alright in hardware mode but slightly fuzzier in software? The ratio. The first one is a vertical photo, the second one is horizontal (close to square).
I quickly checked other vertical photos and they showed the same behavior...
Now staying in hardware mode, I noticed something else. When I preview the vertical photo and click on it, or double click, it quickly jumps, switching between 2 versions of the photo: the one displayed originally (fuzzy) and another one, with a very slightly different size, which is sharp. During that manipulation it also briefly displays "100%" at the top of the screen. It doesn't stick when you click and immediately switches back, so it looks like a glitch.
Now in software mode, I tried the same, this time you can click once on the photo (which is originally displayed *almost* sharp). When you click once, it displays "100%" but also displays a very slightly smaller version that is clearly fuzzy. Clicking again goes back to the other, less fuzzy one, but doesn't display "100%" this time.
Doing the same test on horizontal photos shows no change that I can see.
So, it seems to me that in the preview mode, Bridge has trouble displaying some photos (vertical ones?) in their actual resolution (100%)
and since there is a slight resizing going on, it brings fuzziness. This doesn't explain the very slight fuzziness seen on horizontal photos in software mode.
Now I'll mention, for those still awake, that I saw no fuzziness on the same vertical photos when I go to Review Mode with *hardware* rendering. Photos there are sharp. Now if I go to the review mode with software rendering enabled, vertical photos are not 100% sharp (akin to the small difference I mentioned earlier while in software mode), while they are sharper in preview.
To sum up, it seems that the only configuration that gives me consistently 100% sharp (=as they were meant to be after post-processing) photos no matter what their orientation, is when I stay in hardware rendering mode and use the Review Mode, instead of preview.
This all really smells like a bug.
For info, I am using Windows 7 and an ATI HD4850 card, and this only about processed JPEG files, not RAW files.
Perhaps the preview is really meant as a quick preview and not a tool to view final photos at 100% accuracy...

RAM previewing and rendering not working correctly

Hi,
Today I was just about finished editing a video on CS6 and then when I'm about to add the last effect and render it it stuffs up on me:(. What happens is that while RAM previewing at some point during the loading of the preview it will stop loading, It will then proceed to play the ram preview on loop and when I press a button to stop it a small box pops up in the centre of my screen and the ram preview bar to show what has loaded (the one which shows green for parts that are loaded and blue for cached) turns black and sometimes other parts of after effects turn black. This has happened before and I fixed it by uninstalling and reinstalling After Effects about 6 times. I would do that this time though I would like to know the cause of it and any possible fixes as it is quite irritating. Another thing that may be happening is the RAM usage is slowly filling as I render. This has happened before on my laptop and I did not manage to fix it though it was not related to the first issue that time. The last time when it happened on my laptop the RAM usage eventually filled up to 100% and it would no longer render. I am not sure if it is happening this time as it is still currently rendering though I will update the thread if it does. Finally my render is going very slowly, I am not sure if this issue is realted to any of the above or if it is just the effects I am using though. My memory and multiprocessing settings are using 6 cores of 7 with 2 GB of ram allocated to each with multiprocessing on. My ram allocated for other programs is 6GB. To fix these Issues so far I have tried clearing the cache, purging the memory and image cache, restarting my computer and reinstalling after effects. My specs are:
i7 4770k non overclocked
GTX 780
G.Skill Ripjaws Z 2133mhz 32GB
Samsung 840 pro
Seagate Barracuda
MSI Z87-G45
H100i cooler
Any reply is appreciated
Thanks in advance
Sam

How much experience do you have with AE? Ram preview can be lengthened by adjusting the resolution of the composition window, different parts of the project can be previewed using the work area, and preview length and render time are both a function of composition frame size. Complex, memory intensive effects like particle systems will reduce the render time and the length of a ram preview. Without knowing the details of your composition it's hard to say if you are running into a bug, running out of resources, or experiencing normal behavior.

Curious question about Lightroom previews and Camera Raw Cache

Posted in the Flickr Lightroom Group as well:
I have noticed something about the Lightroom (3.6) previews and Camera Raw cache that have me puzzled.
I create a brand new empty catalog and purge the Camera Raw Cache.
Then I import ONE Nikon RAW (NEF) file with dimensions 2592 x 3872 (10 megapixels - 10,036,224 pixels).
Next I export that NEF file to an uncompressed 8-bit TIFF file. You would expect the size of that TIFF file to be roughly 30 megabytes (10 megapixels x 3 bytes per RGB value) and in fact the TIFF file is 30,135,830 bytes in size. If you export the same TIFF file but specify ZIP compression the resulting file size is 10,834,038 bytes. Obviously the compression obtained here is going to be highly specific to the image but so far no surprises.
During import I specify render 1:1 previews and I go into Loupe mode and view the entire image at 1:1 size. I also visit the develop module and do a bunch of manipulations on the image but no cropping.
At the conclusion of all of that I exit from Lightroom and examine the size of the Camera Raw Cache folder as well as the Lightroom previews folder. It would be my expectation that the previews folder should have a rendered full image and that the Camera Raw Cache should also have a rendered form of the raw data. What would you expect the size of those respective folders to be?
In fact - in my trials the previews folder totals a mere 1,675,264 bytes and the Camera Raw Cache which contains one DAT file corresponding to the one cached image is merely 267,374 bytes. This does not seem like nearly enough bits to preserve the rendered image nor is there a full size image tucked away in the actual catalog either - that file is not large enough to contain that. And yet I can use Loupe mode at 1:1 size and move from image to image with no loading delays (even when importing multiple files).
I'm wondering if I've missed something obvious in my analysis and if not, whether someone might care to speculate as to what magic Adobe is practicing here. Even if we grant them some special algorithm to compress their previews I don't see how they can achieve a compression so much greater than the ZIP-compressed TIFF file achieves.
And for those that might think to ask - I've repeated these experiments with multiple raw images and on both the PC and MAC platforms.
I look forward to some answers or interesting theories or perhaps someone might replicate the experiment and report findings.

MadMan and Hal - thanks so much.
So that was my D'Oh moment of what I was missing - the use of re-rendered JPGS as previews. That certainly does fit with the file sizes I am seeing. I had naively assumed that the previews might have tried to preserve the full fidelity of the image - But as you suggest that full fidelity is likely only there in the develop module.
This perhaps explains another observation from the Develop module - moving from one image to another might display "Loading" either briefly or across a longer duration. My guess is that the length of the loading process might have to do more with what is cached in RAM than cached on disk in the camera raw cache. More of a shame then that 64-bit Lightroom on 64-Bit Windows cannot grab more RAM than it seems to do at present.

Which mac is really good for hdv working process and render??

I'll work my hdv native workflow soon and I'm really very interesting on how to get the most of Mac product,s but I'm still asking me what is the minimun of features do I need on a MAc to process without any disturb or overload and render my video in Blu ray for distribution and broadcasting purposes.

The MacBook Pro provides one key advantage not possible with the 12-inch PB -- the ability to create a second firewire bus using the ExpressCard/34 slot.
In this manner, you can separate fw drives from camera/deck -- a big issue with FCP5 and certain cameras and hard drives.
It is a key difference for anyone considering video editing.
You'll get a beefier video card, and the ability to preview.

Bit Depth and Render Quality

When you finally export media to some sort of media format via the encoder does the projects preview Bit Depth and Render Quality settings affect the output file?
I know there is "Use Preview files" setting in the media exporter dialogue but I just want to be sure of what I am doing.

Jeff's response is my perspective, as well, which is both backed up by my own tests and the official Adobe word.
Exhibit A: My Tests
That is DV footage with a title superimposed over it in a DV sequence, with a Gaussian blur effect (the Premiere accelerated one) applied to the title; all samples are from that sequence exported back to DV. This was to show the relative differences of processing between software and hardware MPE, Premiere export and AME queueing, and the effect of the Maximum Bit Depth and Maximum Render Quality options on export (not the sequence settings; those have no bearing on export).
The "blooming" evident in the GPU exports is due to hardware MPE's linear color processing. I think it's ugly, but that's not the point here. Further down the line, you can see the effect of Maximum Bit Depth (and MRQ) on both software MPE and hardware MPE. I assume you can see the difference between the Maximum Bit Depth-enabled export and the one without. Bear in mind that this is 8-bit DV footage composited and "effected" and exported back to 8-bit DV. I don't understand what your "padding with zeroes" and larger file size argument is motivated by--my source files and destination files are the same size due to the DV codec--but it's plainly clear that Maximum Bit Depth has a significant impact on output quality. Similar results would likely be evident if I used any of the other 32-bit enabled effects; many of the color correction filters are 32-bit, and should exhibit less banding, even on something 8-bit like DV.
Exhibit B: The Adobe Word
This is extracted from Karl Soule's blog post, Understanding Color Processing: 8-bit, 10-bit, 32-bit, and more. This section comes from Adobe engineer Steve Hoeg:
1. A DV file with a blur and a color corrector exported to DV without the max bit depth flag. We
will import the 8-bit DV file, apply the blur to get an 8-bit frame,
apply the color corrector to the 8-bit frame to get another 8-bit frame,
then write DV at 8-bit.
2. A DV file with a blur and a color corrector exported to DV with the max bit depth flag. We
will import the 8-bit DV file, apply the blur to get an 32-bit frame,
apply the color corrector to the 32-bit frame to get another 32-bit
frame, then write DV at 8-bit. The color corrector working on the 32-bit
blurred frame will be higher quality then the previous example.
3. A DV file with a blur and a color corrector exported to DPX with the max bit depth flag. We
will import the 8-bit DV file, apply the blur to get an 32-bit frame,
apply the color corrector to the 32-bit frame to get another 32-bit
frame, then write DPX at 10-bit. This will be still higher quality
because the final output format supports greater precision.
4. A DPX file with a blur and a color corrector exported to DPX without the max bit depth flag.
We will clamp 10-bit DPX file to 8-bits, apply the blur to get an 8-bit
frame, apply the color corrector to the 8-bit frame to get another
8-bit frame, then write 10-bit DPX from 8-bit data.
5. A DPX file with a blur and a color corrector exported to DPX with the max bit depth flag.
We will import the 10-bit DPX file, apply the blur to get an 32-bit
frame, apply the color corrector to the 32-bit frame to get another
32-bit frame, then write DPX at 10-bit. This will retain full precision through the whole pipeline.
6. A title with a gradient and a blur on a 8-bit monitor. This will display in 8-bit, may show banding.
7. A title with a gradient and a blur on a 10-bit monitor
(with hardware acceleration enabled.) This will render the blur in
32-bit, then display at 10-bit. The gradient should be smooth.
Bullet #2 is pretty much what my tests reveal.
I think the Premiere Pro Help Docs get this wrong, however:
High-bit-depth effects
Premiere Pro includes some video effects and transitions
that support high-bit-depth processing. When applied to high-bit-depth
assets, such as v210-format video and 16-bit-per-channel (bpc) Photoshop
files, these effects can be rendered with 32bpc pixels. The result
is better color resolution and smoother color gradients with these
assets than would be possible with the earlier standard 8 bit per
channel pixels. A 32-bpc badge appears
to the right of the effect name in the Effects panel for each high-bit-depth
effect.
I added the emphasis; it should be obvious after my tests and the quote from Steve Hoeg that this is clearly not the case. These 32-bit effects can be added to 8-bit assets, and if the Maximum Bit Depth flag is checked on export, those 32-bit effects are processed as 32-bit, regardless of the destination format of the export. Rendering and export/compression are two different processes altogether, and that's why using the Maximum Bit Depth option has far more impact than "padding with zeroes." You've made this claim repeatedly, and I believe it to be false.
Your witness...

Preview and Render Glitches

Similar Messages

Maybe you are looking for