Tiff causes re-render

I've got a small watermark .tif and everytime I click out of FCP 6 I have to re-render the sequence. This has never happened until recently. Old projects or new projects doesn't matter and only if the watermark is in the sequence. This is not a major problem, just an inconvience that slows things up if click out of FCP to find a file or photo.
Cheers,
D

Jim,
That worked.
It had many months and many, many projects since I trashed preferences and using digitalrebellion.com worked quickly, seemlessly and beautifully and the price was right.
Thanks!
Is this something that needs to be done periodically or something to first try when things start acting screwy in FCP?
Thanks again,
db

Similar Messages

My video can't export cause of render problems!

Hi there,
I am trying to export my video as a digital video (.dv) but when I do it says it can't find a render file.
I have gone to Sequence->Render All->Both. Renders the whole video then I go to export it and it still says that some render file is missing.
How can i overcome this. I am on a Mac g4 runnning Final cut pro 4.5.

Glad that did it.
Thanks for marking your post solved it helps keep things organized and if you want you can throw a couple of "solved" points my way if my post solved your issue. Just our way of sharing the love!
K

Just simple titles causes long render times

Lately I have noticed that adding simple titles really seems to take a very long time. These are not complex titles. They do have a border, but 10 minutes for a 1:30 tiltle over just one layer of video? What's going on here?
Best,
Tom

Obviously 10 minutes for a "simple" title is ridiculous so there must be something unusual about your project and workflow.
It will be impossible to guess what those factors may be without detailed relevant info on the title and project specs.

AE CC Render error output module failed

Hi, I tried my best to find this answer on the forums but couldn't find anything current.
I have isolated two issues in AE CC where I can duplicate a failed render with this message:
After Effects error: Rendering error while writing file "xxx". An output module failed. The file may be damaged or corrupted. (-1610153464)
This happens when opening an AE CS6 project and trying to render a simple comp with only one text layer and a moving mask. It also just happened after my first round trip test with Cinema 4D. I could RAM preview the c4d layer but the output to Quicktime h.264 failed.
I have even tried a full reinstall of AE CC. I have the basic FxFactory Pro plugins and MagicBullet Looks installed, but neither are being used since this is a single 1280x720 comp with a single C4D layer. Plus like I said it failed with the same error in past CS6 files.
I don't know how to force disable a plugin to test that, but I can't see how an unused plugin could cause a render to fail like this.
I'm on a new (late 2012) 27" iMac
3.4 GHz Intel Core i7
8GB RAM
NVIDIA GeForce GTX 680MX with 2GB VRAM
OS X 10.8.4
AE CC 12.0.0.404
CUDA driver 5.0.59
Thanks for any suggestions!
Matt

Olaf, did you read my reply where I explained my solution? First you should try the steps outlined in the article Todd references:
http://blogs.adobe.com/aftereffects/2011/02/troubleshooting-quicktime- errors-with-after-effects.html
There seems to be a good way to isolate if it's the same issue I had, though. Let me go into a bit of depth for you.
The trick was to launch the OS X app called Console, located in Applications > Utilities. It is a program that compiles and displays the system logs in real time. It's great to see the little things happening in the system that don't make it into the user interface. When I had my Console up and generated that same error you're having, I noticed this error in the log:
The key here is the Adobe QT32 Server, which is mentioned in the TCP part of the article I linked to above from Todd. In my case at least, what was happening was that a third party app called AirServer was talking to the system's QuickTime over the same TCP ports the QT32 Server engine was trying, and it resulted in Adobe QT32 Server crashing, and that alert being thrown up in AfterEffects.
If you're in the same boat, it means you have some sort of app or system extension that is also talking to QuickTime over TCP. That may not make any sense, but the easy thing to do is quit ALL third party apps, then quit AE, then restart AE.
In my situation if AE gave me the error and then I quit AirServer, the error still happened because Adobe QT32 had already crashed. You have to relaunch AE after closing the offending third party app.
To be sure you've quit all third party apps, open Activity Monitor (Applications > Utilities), chose "My Processes" from the dropdown menu, and scan through the list to make sure. You don't have to recognize all the processes there, but you should be able to recognize any third party ones you put there.
Hope that helps!
Matt

Is anyone else having serious issues with Dynamically linked clip render times in CC 2014.2

Short clips stalling and taking forever to render. Longer ones taking several hours???
I've noticed arbitrary little fixes, such as re-opening the after effects window, then going back into the premiere window causes the render to instantly speed back up in some cases.
A restart of the program I believe solves the issue too. As does simply rendering the clip out in after effects.
The problem is that I have long, overnight renders set up that need to run automatically. In this case, 9 clips, all about 30 minutes long. And pretty much all one long dynamically linked comp (I created a picture in picture effect in after effects compiling 2 30-minute video feeds, and then added some color correction). When I left at night, the total time kept creeping up and up to about 2.5 hours for one video. Even THAT sounds like a lot to me, but I let it go. I return to the computer 13 hours later, to see only 3 videos completed, and the one CURRENTLY in the queue saying over 6 hours remaining. I cancel the render.
I feel like there is some breakdown of communication between afx and premeiere happening here.
Anyone have any experience with issues like this?
Running PP CC2014.2 on a tricked out 2011 Macbook pro 17" OSX Yosemite

I'm on windows 7, and similar dynamic issues were a result of having two versions of the same app on the machine, and not associating the files to use the latest version, etc, or a version mismatch.
Another workaround is to close PPro and import the project into AME, rendering it from there.

Render problems on an HDV 1080i60 timeline

I'm editing a project for a friend who is on fcp 6 so I'm using my version of 5.5. Her footage is HDV 1080i so I chose the sequence preset HDV-1080i60 to match her footage. Drag any of her footage onto the timeline individually and you don't get a render line...so far so good. Create a multiclip sequence and suddenly I have a render line which makes it nearly impossible to edit. So I went searching for differences in the footage and the timeline and here is what I have.
My sequence is this
but when I choose file≥new sequence I get this:
Is this causing the render issue and why am I getting it if I'm choosing a preset sequence. Most importantly how do I fix it?

I'm not sure how to manually change the sequence setting once it's created. In fact I'm confused as to why the presets are 16 point integer but when I simply do new>sequence I get a sequence with this:
My drives are internal hard drives and I'm using three angles on the multi-clip. The odd thing is that I've never had trouble like this with this system before. It's been an amazing little workhorse. Now mind you I didn't shoot this or digitize this footage myself. It was given to me by someone who needed an edit done quickly (drat!). She's given me footage before where two of her cameras are fine in terms of the footage being shot in the same format and one of them is shot in a different format causing me issues, but this time all three cameras seem to be the same. This seems to be a sequence issue.
Can you tell me how to change the sequence once it's created?

Render Previews Size and Aspect Ratio

We are currently editing several projects that have an odd editing dimension but a standard output dimension. These videos are for a live event with rows of four projection screens set somewhat tightly together. From a production standpoint, we wanted to have content flow freely across all four screens. We prefer not to have to visualize this, so we set up a "Desktop" mode, square pixel sequence within a project with a dimension of 2560 x 540. The 2560 dimension is because most of the footage is from the Panasonic P2 camera (HVX200P). This camera shoots video at a rectangular pixel dimension of 1280 x 1080. The pixel aspect ratio is 1.5. So 1.5 times 1280 = 1920, the final output square pixel dimension. In this case the final output WOULD be 1920 x 2 or 3840 x 540 high. 3840 divided by 4 = 960 x 540. So we're outputting standard def widescreen to each screen. Premiere automatically creates the final output through nesting the 2560 x 540 sequence twice in a DVCPROHD 1080i sequence of standard size. The two 2560 x 540 sequences, one on video layer 1 and the other on video layer 2 are positioned so that the video that corresponds to screen one is positioned top-far right and the second instance of the sequence is positioned bottom far left. The final output file is an avi in the Canopus HQ codec at 1920 x 1080. This output file is a video that is actually four standard def videos in one 1920 x 1080 video. The Grass Valley Turbo 2 outputs this standard hi-def file to a Vista Spyder which will isolate and project the four videos-in-one, to the appropriate four screens.
This type of project would not have been possible without CS5 and Mercury. Premiere is handling this oddity extremely well.
One minor issue for the support gurus:
When we render the Desktop mode square pixel 2560 x 540 sequence timeline, we get what appears to be random, mixed render results. Sometimes this odd shape renders perfectly, other times it renders out to small dimension that is less than half size. Other times if renders out with pieces of the elements small. but positioned with spaces between them. Playing around with sequence render settings and playback resolution, sometimes SEEMS to cause the render to correct itself. Sometimes a computer restart SEEMS to correct the issue. Any thoughts?

Colin Brougham wrote:
Barring previewing, are you able to export to your intermediate/final movie without problems?
The final exported video is 1920 x 1080. I have test exported in a number of formats without any problems at all.
The 2560 x 540 version, (BEFORE it is "processed" through 2 instances of itself in a standard DVCPROHD sequence) is for editing purposes only, so we can actually see how the video will play across four projection screens.
The remaining issue I'm trying to work out is, how to best get the finished video into the grass valley Turbo 2. The Turbo 2 takes an AVI file transcoded into the Canopus HQ codec natively without having to transcode. The only way to get an avi from Premiere Pro CS5 into the Canopus HQ codec is to first export the finished video as an uncompressed avi from Premiere, import it into either "Edius" or "Procoder 3" and export in the HQ codec. The export from Premiere CS5 + Mercury takes 15 minutes. The export (HQ encoded file) from the trial version of Edius takes around 10 minutes. IMO grass valley should create a plug-in for Premiere CS5 and shouldn't allow the quickest export to be Canopus exclusive. I seriously doubt many Premiere CS5 users will switching to Edius any time soon.
According to grass valley, the Turbo 2 will accept an MPEG-2 Pgm Stream, whatever the heck a Pgm Stream is???. I did a Google search without success. Of course Premiere will export an MPEG-2 file, but how the Pgm Stream relates to this, I have no idea. There are a mind boggling array of settings and the preset seems to export a rather compressed looking video.
My current thinking is to try to convince the boss to buy Procoder 3.
BTW:
the 3840 x 540 version sequence renders fine part of the time and then for whatever reason starts creating a preview that is about 35% of the correct dimension... So back to the original Sequence settings of 2560 x 540

Unusual render times

Hello, I seem to be experiencing weird, fluctuating render times with my projects. Some 10+ minute projects render in 20 minutes or so, others like the one below take far too long for what they are.
I am running a Macbook Pro, 2.5ghz Intel Core i7, 8GB 1333 Mhz DDR3 ram, and an AMD Radeon HD 6770M 1GB.
Here is a current project I am working on at the moment - please excuse the blurred sections, this is an internal business video and I am required to do this for security.
The maximum filesize will only be est. 134mb, the length of the video is 3 and a half minutes, and I am only rendering at 720p with 90 second keyframes. When I render this file it takes upwards of 2 hours; sometimes longer.
The source files are 1920x1080 and 1440x1080, and I have 4-5 nested sequences approx 10-20 seconds long each with warp stabilizer applied to them.
I also have fast color corrector applied to all clips. I usually have a VBR of min-4 max-6 but attempted to change it to CBR to see if that decreased rendering time; it didn't.
I've also tried optimizing the memory for both rendering and memory in the preferences window, but I see no difference.
Can you spot anything that might be causing this render to take so long?
Thanks in advance for your help.
Brendan

Thanks for the speedy reply, shootemz. I had no control over the source footage unfortunately and the video needs to be uploaded to a private Youtube channel, so I just selected the Youtube preset from the Export Settings section - and Youtube seems to have a sad every time I try to upload anything that isn't 29.97fps so that's the one I chose.
So all of the things you mentioned increase the encoding time? I didn't know that! I am new to this type of export. It's always been very straight forward in my past jobs. I guess I will play around with the settings and see if I can keep them as close to the source as possible. Thanks for the reply! If anyone else has any other suggestions I would love to hear them also.

Motion 5 shape styles make render extremely slow?

Hi guys, I just wanted to ask about your experience with shape styles in Motion 5.
I'm currently working on a blue screen animation type video. I'm encountering extremely long render times for comparatively short videos and simple animations. When I isolated all the individual elements in my video to see which one is causing these render times, it came down to a bunch of lines which have shape styles applied to it.
The design is basically a relatively simple spider web, made up of 9 individual lines. I applied the "chalk easy" shape style to each of these lines and used a simple animation using "last point offset", just to have the lines come on 0-100%, nothing fancy.
When I remove the shape styles, rendering takes less than 30 seconds, with the shape styles applied it takes 10 minutes or longer.
What I wonder is, do you guys use shape styles? Have you experienced issues like this? Is there a viable alternative to shape styles?
I rarely use them, but it seemed like a good idea here because we're going for a bit of a drawn look, therefore I wanted the lines to look a little irregular without too much effort.
Cheers

Shape styles fall into the category of replicator/emitter. You are increasing the complexity of the artwork significantly and it will slow down Motion both in playback and rendering (depends on the style and complexity of the style.)

Reducing Render TIme

Hi All,
My render times for a 10 minute clip are getting ridiculous ... about an hour.
I was thinking, what if i change the sequence settings in some way so as to reduce render time between edits? All i want to do at this stage of the game is get a rough idea of how my edits work.
Once i'm all done i can just reset the sequence settings to where i want them and do a final render prior to export.
Any ideas of good, quick, sequence settings to get this process moving along?
Paul

Your sequence settings should be set to "lower", not none... might have a problem set to none with field order.
Sounds like your compositing is causing the render times, and the ONLY fix here is to quit compositing. (not a good idea of course) or get thee to a faster mac... Rendering times in any codec or sequence setting are heavily dependant on CPU speed. The faster the machine, the faster the render. You want a lower quality render for editorial? you can change that in the render settings... just don't forget to re render in high quality in the end of course.
Jerry

FCPX crashes after update to 10.0.5

Hi,
I updated FCPX yesterday from 10.0.3 to 10.0.5. I could continue working in the open project. But when I tried to open another project today, FCPX crashed every time. Now, FCPX starts, loads all projects and events and when I see the projects' overview it crashes. I cannot do anything inside the program.
I replaced all projects with their backups and renamed the old ones CurrentProject_old....
It didnt work.
I tried to regenerate the old FCP version with time machine, but that didnt work either. I work on a Mac Pro (2x2.4Ghz Quadcore). I would be perfectly fine to reset the status before the update. Is there any way to do so? Or any way to make the program running?
I contacted the Apple support, but someone of you might have the same problem or even better an idea for the solution.
Since I need the program for work I would be very grateful for support.
Best
Johannes

I render because it makes playback better.
Things are stable now. I've deleted the still image that was causing a render crash. I've opened the image with Photoshop, resaved, and reimported. I've also redone the Motion project that was giving FCP a problem loading.
Now my project renders and plays. Next I'll see if it will export.
Ross Hunter

Rendered Video has Glitches

I'm from Toronto, Canada and right now working on an online for a PAL tv series. This project's been a long process, originally all the required files were on the suite's FW800 RAID drives but now they're all on drives supplied by the client: FW 400, 300 GB external drives, no RAID (just FW 400 daisy chain).
I'm onlining using a 10-bit PAL timeline, making sure all my elements are in place, then I render this timeline. Upon playing back the render, there's a few visual glitches every now and then (e.g. flash of a pink frame, or green blotches showing up on text renders). If I re-render these problem sections, the errors go away.
Does anybody have any idea why these errors are appearing in the first place? Maybe the slower read/write of the FW 400 drives are causing a render issue? Yes, I do realize I would be unable to playback my timeline due to FW400's slow speed.

Wouldn't the computer 'slow down' to compensate for the slower drive speed when rendering? So the drives can't keep up with the speed the computer sends the rendered frames back so it only gets 'part' of the data for that frame?
I adjusted the opacity setting for it and the blotches disappeared...
Lower 3rd was a text track, a semi-transparent black rectangle behind it, and finally a DV PAL clip in the background. This was all being rendered in a 10-bit PAL timeline. Effects Rendering? Pretty sure only Final Cut is doing that on this system. Unless an AJA IO would have any effect.

Field Dominance problem and questions

I am trying to capture 24p Advanced DVCAM material. I've been using the easy setup. I've tried test captures of about 15 seconds (using capture now) which come into FCP with a field Dom. of NONE and load into my 23.98 sequence timeline with a olive green render indicator (I know I can edit with that as that is just a playback resolution downgrade). If I rewind to approx. the same start point on the tape and capture a 9 minute clip, it comes in with a field dominance of EVEN and loads into the exact same timeline with an orange render indicator. First off, that seems odd to me. Secondly, I've read in other forums that there is a possibility that I can change the field dom. of my longer clips and/or my sequence, but I'm not at all clear on it. Will changing the field dom. allow me to edit w/o render indicators? Do you think that it is the field dom. issue that is causing the render indicators' to appear, or could it be other issues. It seems to me that the fact that I can get the short clips to load with and olive green line, means that it probably is the field dom. issue that is causing my difficulties. Is there an error in my logic? I'm also unclear if I am able to tell FCP not to render in interlaced mode. Is that something I can do? Does it even apply to my situation?

Jerry,
Thanks for the reply. I've been "assured" (who knows what that means) that the material was shot advanced, but it might make sense for me to do a test to see if Cinema Tool pulldown removal solves my problem. Can I use the pulldown removal option in the FCP tools menu after I've captured or do I need to use Cinema Tool.
I must say I'm still baffled about my different length clips capturing with different properties even though I never changed any settings between captures. Any hunches on your part about that anomaly?

Percentage of RAM used

Hi all
I have been playing around with memory settings for AE CS5.5 and taking some advice from here:
blogs.adobe.com/toddkopriva/2010/10/please-try-recommended-memory-settings-for-after-effec ts-cs5-and-give-feedback.html
and here:
http://forums.adobe.com/thread/734343?start=0&tstart=0
With variety different compositions, and different memory settings I have noticed my 'RAM: % used of 24GB' in my Render Queue window (at the bottom of the window) is always pretty low. Anything between a few % and 25% ish.
Is this just showing me the RAM used for the foreground CPU and not the collective CPUs?
Any info is much appreciated.
Cheers
A

What happens with MP processing is that one CPU renders a frame and at the same time the other CPU's try and render other frames at the same time. You don't get multiple CPU's working on the same frame. AE doesn't work like that. Most MP aware software doesn't either. The standard multi threading usage is to divide up the tasks and send them to a CPU to complete. AE's 'task' is to render a frame. The MP processing in AE isn't smart enough yet to divide up a frame into pieces and send the pieces all to the renderer. I've been asking for line rendering for a long time. AE builds a whole frame at a time as a single process. That's why AE's MP rendering is a little wiggie. (wiggie is almost buggy)
I'm also saying is that if your project is MP compatible that each CPU can render a frame at a time and that more than one frame may be rendered simultaneously, but if there is anything in your project that is not MP aware each CPU will try and render, get confused because the something like a codec or an effect is not MP aware, and the system will hang until it gives up and tries to render with one CPU. When that frame is rendered AE will start over with the next frame try and send multiple frames to multiple CPU's and try to render multiple frames simultaneously, get confused, fail, and finally render a frame with 1 CPU and then start the process again. This is why throwing in an effect that is not MP aware for one shot that only lasts 10 frames in the middle of a comp would, without that effect, efficiently use MP rendering will cause the render to hang up and dramatically increase render time or fail completely. That's why I seldom of ever have it turned on.

How to increase painting performance ?

First off all, i'd like to apologize for my poor english, because I'm from brazil, and even knowing very well how to speak english, my spelling sometimes comes out really nasty.
Now getting to the subject... ;^)
I study computer science here in brazil, and during a course of data structures, I once saw this stunting applet( a kind of visualization application for AVL trees ) located at: http://www.seanet.com/users/arsen/avltree.html. Since then, I've tried to make something similar to this applet, because I thought that it would be a great experience to do something like that. And I've achieved that. However, like in everything that we do, we encounter some trouble in the way.
First, i tried to develop my own visualization of AVL trees program by using the C language, toghether with the old Borland Turbo C BGI graphics library. It was fine, but i wasn't satisfied 100% with it. Then I've decided to develop it in Java too. I had to make several changes in the algorithms responsible for rendering the tree when I wrote the program in Java, because I wasn't doing the things in the C version in a very smart way. However, the Java version was really improved and is pretty efficient.
My actual problem:
I've implemented a swing component responsible for doing the visualization of any AVL tree. It extends JComponent.
My only problem, is related with the Java 2D library and it's renderer. As the size of the component, that holds the tree and paints it, grows, the performance of the painting slows down drastically. Even when the user isn't interacting with the tree, witch doesn't require recalculating any coordinates and adicional processing.
I've tried to set a clipping area in order to perform the drawing faster and improve it's performance, but it didnt worked as I expected. The wanted performance is still unachieved.
You'll know what I'm talking about if you download the program and play with it ...
I don't know what to do ... I'm thinking to create offscreen images of the tree, but I've read that the swing components already are double buffered.
I would publish the source code of the application for you to examine, but I think it wouldn't be useful, because the code is well documented, sadly, in Portuguese. So for you to get along with it, would take a long time ....
One thing thar I've noticed is that Visual Paradigm 3.0( http://www.visual-paradigm.com ) is made in java, and the diagrams sheets are nicely rendered ... what the developers of visual paradigm may have done to improve the performance of the drawing of the diagrams ? Cause they render realy fast, dont matter the size of the panel holding the diagram...
Does anyone know any documents that i can read about this stuff ? Does anyone have any suggestions ?
you can download the C version of my visualization program at: http://planeta.terra.com.br/informatica/jdesign/pessoal/AVL.zip
you can download the java version of my visualization program(executable jar) at: http://www.jdevelop.thefreeserver.com/ArvoresArvl.jar
you can view a brief explanation of the visualization program at: http://www.jdevelop.thefreeserver.com/avl_tree.html
Note: the java version has few known bugs, however they dont affect the performance of the painting and i'm working on them.
If you are brave enought and want to try analising the source code, ask me for it by emailing me at: [email protected]
Thanks in advance,
Julio Cesar de Andrade Vieira Lopes
[email protected]

i'm sorry .... the correct link to download the java program is:
http://www.jdevelop.thefreeserver.com/ArvoresAvl.jar

Tiff causes re-render

Similar Messages

Maybe you are looking for