Background rendering on load

Hi,
I'm using PE8 and am quite new to it, so apologise if I'm asking something obvious. However, I've got a strange problem. I've started two seperate PE projects, using different media files. The timeline of both projects is fully rendered (The bar is completely green) and I've also outputted both to several formats such as MPEG. So all is good. However, every time I open one of the projects, parts of the timeline bar goe back to red and it begins background rending those clips. So, I let it (Eventually) finish, the bar is all green again, save and re-open - guess what - same clips are back to red and background (re-)rendering starts again. Happens every time and on both projects. Always the same clips (Which on one project are 3 x title clips next to each other at the end and on the other project is 1 x .m2ts video clip, 3 x titles next to each other, and 1 x title at the end). I've also tried rendering by pressing enter rather than leaving it to background render but this hasn't made any difference. The work area bar covers the whole length of both movies. The disk has plenty of disk space so it's not that it's filling up.
Could anyone offer any advice on this? I realise I can turn off backgroud rendering, but it seems like a really good thing to have and so wish it worked right.
Thanks very much for reading,
Simon

Hi Hunt,
I was indeed using QuickTime 7.6.x. I've uninstalled it, but it has not helped. I've also, as mentioned above, used the option to clear the cached files from within Adobe, manually deleted the media cache and manually deleted the Preview Files of one of the projects. All of this was done seperately and test inbetween. None have helped.
Additionally, I just tried to get into Organiser and it won't start. It just bings and then brings up the 'Crash Report' screen (Which I'd bet money that they don't read - I've submitted about 30 since buying Premier Elements a couple of weeks ago). So, Organiser won't start at all any more (I've tried launching it from within Premiere Elements and from the popup launcher, and yes, I've tried rebooting). Also, the program crashes pretty much every single day that I use it, for one reason or other. Usually I'm just using it for an hour or two in the evening. Over the weekend, I used it for a number of hours but had a number of crashes. I'd say it's crashing on about a 2 hour basis.
I apologise if this is coming over a bit negative, particularly as I'm in an Adobe forum and am writing something thats going to be read by Adobe fans. However, I came into this pretty provider neutral. I choose Adobe because it has a good brand name and based on the brief demo'ing I did of it's product and a couple of rivals. I am pretty shocked with what I've found. Premeiere Elements 8 comes across as unfinished. It's clearly bug ridden - intermittently crashing on a 2 hour basis, and some functions (Organiser, saving rendered files) completely not functioning. I admit I'm working with AVCHD files, which are relatively new, but in that case Adobe shouldn't have released the product until it was up to the task. Then there are lots of areas that simply seem like they need a bit more polish - not being able to type directory names in when creating/importing/exporting files, but having to go through the click, click, click file tree explorer for example.
Anyway, sorry to rant. I've just started uninstalling, so I'll see how things are after I've re-installed. If not, I'm pretty close to asking for a refund or simply writing this purchase off. I've been told that Final Cut Express is very good and I've wanted an excuse to 'need' a Mac for a while, so perhaps this is the push I wanted?!
Thanks for your help, I'll post an update just to let you know if the re-install solves the problem, but I don't expect any further troubleshooting - unless it's from an Adobe developer and he wants to personally apologise to me!
Simon

Similar Messages

Background rendering.

Hi, I've started using the trial version of Final Cut Pro X and have a question...
Background rendering is taking up LOADS of disk space.
Why isn't the rendering overwriting itself?
A 5 minute film shouldn't have to fill over 65GB of disk space, should it?
And, is it possible to delete a clip in iPhoto, that has been imported to
the project in Final Cut Pro X without it dissapering in the project as well?
Best regards,
Adam.

adji00 wrote:
And, is it possible to delete a clip in iPhoto, that has been imported to the project in Final Cut Pro X without it dissapering in the project as well?
As Tom said, this depends how you imported it. If you're not sure, select the clip and press Shift+Cmd+R to reveal the clip in Finder.
Depending how you imported the clip, the one you see here may be an alias (just a few bites in size). Right-click the clip in Finder and if you see the option to 'Show Original', the one you're lookinng at is indeed, an alias. Select 'Show Original' - it will probably be in an iPhoto folder.
If you don't see the option to 'Show Original', and the finder clip is more than just a few bites in size, then it's the original that FCP X is using and if deleted, will go offline in FCP X.
Andy

Background rendering when iMac is in standby mode

After I have imported a video file from my Sony HDR Z1 FCP X starts to render in background mode, when I am using the iMac all is fine but if I leave it overnight and the iMac "goes" to sleep" the rendering also stops. Is there a way to stop this so I can leave the machine to complete what it is doing before it goes to sleep?

When the machine is asleep, it is asleep, period.
If you want to give it time to finish rendering before it goes to sleep, open System Preferences->Energy Saver,
click on the "Schedule..." button and set a time for it to go to sleep.
Note: Depending on your mac and the content you are editing, you may not need background rendering at all. Many people prefer to leave background rendering off, and only render specific portions if the playback is not smooth (for instance if you have some effects on a given clip, that your mac cannot play well without rendering, you may want just to render that clip).

Background rendering? Oh REALLY? Who's Apple kidding?

One of the things I was looking most forward to, was - to quote the infamous Supermeet presentation: "Never ever have to wait for rending no more!"
It's just that, to my best knowledge, there really is absolutely NO background rendering going on NOR is it any different from the auto rendering we had in FCP 7. Just at bit more automatic, perhaps.
To me, the definition of af background task is something that continues while you continue your work. I'm positive that most people hear this in FCP X as in "so it will do the rendering in background, so you don't have to wait for it".
But wait........
- If it's a background process, while does it stop when we continue working ? That's no background task to me! Is it?
- If it's something so new, that it has to be accompaniet with "never have to wait no more", why is it almost 100% the same as we already had in FCP 7?
Two me, there seems to be only two very small differences:
- in FCP X you can set the time limit where in FCP 7 you had to stick to the, what, 15 minutes delay in this process starting automatically
- in FCP X you can pause the rendering temporarily just by doing anything in FCP X, where as in FCP 7 you had to click cancel to halt it
So the conclusion to is, that you most definately still have to wait for rendering, as you cannot finish you project before you completed the wait........
Background rending? Oh REALLY? Who's Apple kidding, anyway?

why is it almost 100% the same as we already had in FCP 7?
This is just incorrect. First, the technology in FCP is vastly superior to 7. The speed is substantially faster. It is not analogous in any meaningful sense to auto render. In addition, once render initiates, it does not actively have to be stopped by the user to continue working, nor does it have to be re-initiated. The process is seamless.
Indeed calling it background rendering is marketing hype and it is not in background in any true sense. However, it's relationship to what happens in 7 is zero. The two differences are minor. The real differences are in the processes ability to access new techology, using more RAM, more processor power, more graphics processing, and more modern OS technolgies. That's the real difference.

Background Rendering in FCP 10.2 is not working

Is anyone else having an issue with background rendering not working in the new FCP 10.2 version?
In fact even the render all function doesn't seem to be working properly since I upgraded. It only appears to be rendering small pieces at a time.
It won't render the whole project out like it's supposed too. Have to keep pressing the Control, Shift, R keys over and over to get it to completely render out the sequence.

Try turning off BG Rendering and turning it back on.
If you have multiple projects in a single library, try another existing project or create a test project; (add some clips with effects to get render bars). If they render, select the first project and choose Delete Computer Generated Project Files.
Russ

Background in table load delay, or slow load

I just put together this page and things are working pretty
well, but I'm not happy with how the background image loads last.
First you see the text on the screen, and then you see the image
load in from top to bottom.
The image is only 96kb, so it shouldn't be a problem where
the file size is having to download.
I've made other pages with larger background images that load
instantly.
I'm thinking it may be the order of my code - which I'm very
new to.
I thought maybe I could just post the link to the page and
maybe someone could give me a hint as to why it's loading like
this?
http://www.covalt.net/resume
Thanks!

I just put together this page and things are working pretty
well, but I'm not happy with how the background image loads last.
First you see the text on the screen, and then you see the image
load in from top to bottom.
The image is only 96kb, so it shouldn't be a problem where
the file size is having to download.
I've made other pages with larger background images that load
instantly.
I'm thinking it may be the order of my code - which I'm very
new to.
I thought maybe I could just post the link to the page and
maybe someone could give me a hint as to why it's loading like
this?
http://www.covalt.net/resume
Thanks!

Background Rendering - Any way to curb the percentage of processor that Final Cut uses when rendering?

When Final Cut X tires to render something on my machine it literally maxes out all 8 cores, sometimes it takes 15-20 mins to process edits I make to the frames, making my wholemachine freez up. Is there a way to cap the amount of processor the FCX is using for rendering? It wiould be ideal if I could set this at 50% or something, so i could at least work on other projects while my machine is rendering. I made global edits to the whole video I am working on that involve keying and transforms on the frames, so everytime i make an edit early on in the movie, it seems to be re-rendering the transform and key effects through the whole movie. Its a pain!
Next time, I'm going to have to use proxy media. Hopefully that will help.

If your system can handle native rendering, then turn off background rendering and only render when you need to.
If you system is stuggling with native rendering, convert to Pro Res, again keeping background rendering off.

Background rendering question...

I have several 30 minute FCPX projects and all of them have lots of background rendering to do still. (color corrections and the like)
Do I have to open each project and render them one at a time before sending to Compressor?
OR...when I send to Compressor, somehow it completes the rendering before it exports?
Just wondering what the fastest workflow is.
I don't see a way to say "Render all my unrendered files in all my projects" while I'm sleeping overnight.
Advice?
Thank ya!

Ooooohhhhhhhh....... so it just knows what to do when it exports? So, if I did color correcitng, it will just be there on export? That's interesting... ok. Cool.

Stalling:Error in background rendering so switching to foreground rendering after 0 frames completed

Our facility is running AE CS6 ver 11.0.0.378 on 8 core Mac Pros with 32 Gb ram running OSX10.6.8
using Thinkbox Deadline 5.2 for distributed rendering to other 8 Core Mac Pros with 32 Gb ram.
The issue is that we are in crunch mode trying to deliver 4K comps (soon to be 8k comps) and we are experience substantial
delays 10-20 minutes after the AERENDER starts, but before it starts doing any fruitful rendering.
We are reading from and writing to Quicktime movie files (which normally works just fine for us) and thus the entire frame range needs
to get computed on a single host.
The symptom is that many comp jobs (but not all) stall for a while with no apparent actibity before spitting this messgage, but then happily
and swiftly complete each frame in a second or less with no errors:
0: STDOUT: PROGRESS:   There is an error in background rendering so switching to foreground rendering after 0 frames completed out of total 576 frames.
0: STDOUT: PROGRESS: 00001 (1): 20 Min, 16 Sec
0: STDOUT: PROGRESS: 00002 (2): 1 Seconds
0: STDOUT: PROGRESS: 00003 (3): 0 Seconds
0: STDOUT: PROGRESS: 00004 (4): 1 Seconds
0: STDOUT: PROGRESS: 00005 (5): 2 Seconds
0: STDOUT: PROGRESS: 00006 (6): 1 Seconds
Given that the delay, seems to be related to the number of frames (350 frames creates a 10 min stall and 576 frames creates a 20 minute stall), it seems like it's trying to do something for every frame in background mode, before it gives up and does them quickly
in foreground mode. During this time, there doesn't seem to be any signficant CPU or Network or IO activity. I looked for command line args that might force AERENDER to foreground mode, but didn't find anything.
Here's what the digested submission args look like.
0: INFO: Startup Directory: "/Applications/Adobe After Effects CS6"
0: INFO: Process Priority: BelowNormal
0: INFO: Process Affinity: default
0: INFO: Process is now running
0: STDOUT: PROGRESS: 12/6/12 10:37:54 AM PST: Starting composition sc20_assem_R_v57 .
0: STDOUT: PROGRESS: Render Settings: Best Settings
0: STDOUT: PROGRESS: Quality: Best
0: STDOUT: PROGRESS: Resolution: Full
0: STDOUT: PROGRESS: Size: 1200 x 860
0: STDOUT: PROGRESS: Proxy Use: Use No Proxies
0: STDOUT: PROGRESS: Effects: Current Settings
0: STDOUT: PROGRESS: Disk Cache: Read Only
0: STDOUT: PROGRESS: Color Depth: Current Settings
0: STDOUT: PROGRESS: Frame Blending: On for Checked Layers
0: STDOUT: PROGRESS: Field Render: Off
0: STDOUT: PROGRESS: Pulldown: Off
0: STDOUT: PROGRESS: Motion Blur: On for Checked Layers
0: STDOUT: PROGRESS:
0: STDOUT: PROGRESS: Solos: Current Settings
0: STDOUT: PROGRESS: Time Span: Custom
0: STDOUT: PROGRESS: Start: 00001
0: STDOUT: PROGRESS: End: 00576
0: STDOUT: PROGRESS: Duration: 00576
0: STDOUT: PROGRESS: Frame Rate: 23.976 (comp)
0: STDOUT: PROGRESS: Guide Layers: All Off
0: STDOUT: PROGRESS: Skip Existing Files: Off
0: STDOUT: PROGRESS:
0: STDOUT: PROGRESS: Output Module: APR_422HQ - Millions
0: STDOUT: PROGRESS: Output To: /Volumes/Renders/Scenes/20/sc20_assem_R_v57_r1_2k.mov
0: STDOUT: PROGRESS: Format: QuickTime
0: STDOUT: PROGRESS: Output Info: Apple ProRes 422 (HQ)
0: STDOUT: PROGRESS: Output Info: Spatial Quality = 100
0: STDOUT: PROGRESS: Include: Project Link
0: STDOUT: PROGRESS: Output Audio: Off
0: STDOUT: PROGRESS: Channels: RGB
0: STDOUT: PROGRESS: Depth: Millions of Colors
0: STDOUT: PROGRESS: Color: Premultiplied
0: STDOUT: PROGRESS: Resize: -
0: STDOUT: PROGRESS: Crop: -
0: STDOUT: PROGRESS: Final Size: 1200 x 860
0: STDOUT: PROGRESS: Profile: -
0: STDOUT: PROGRESS: Embed Profile:
0: STDOUT: PROGRESS:
0: STDOUT: PROGRESS: Post-Render Action: None
We're under the gun to get this production delivered, and these delays are killing us. I worry when we switch to 8K comps
that the "fruitless delay time" will just get longer.
I'm currently trying to correlate the plug-in assortments in effect for the shots that exhibit this behaviour. Clearly in "foreground mode" the machines are capable of rendering the shot quickly.   We've speculated, that posibly some plugins may be GPU or OpenGL accelerated (these machines have ATI Radeon HD 5770 cards) despite the fact that AERENDER probably doesn't require special graphics cards).
Anyone have any ideas, especially if there is some way for force the foreground mode from the start?
Regards,
Jay Production IT Support.

Just to follow up, Our compositing supervisor was still convinced that running with MP was the way to go, so I worked
with him to run some benchmarks on medium and heavy shots that we determinied would trigger the issue in -MP mode.
The test scene was about 50 frames in length, and we ran it on the same hosts with -MP on and -MP off, and also ran a
version of bundled frames (10 frames per host/task) and another where we did all 50 frames on a single host (with and without MP).
Interestingly, in every scenerio of these 4 cases, the version with -MP on, was 2-15% faster (despite the 10-11 minute delay at the start in MP mode).
His conclusion was it's still faster with -MP mode ON, and requested that I continue to explore for patches or theories how we might get around the delay.
Have read links:
http://forums.creativecow.net/thread/2/1025525
http://helpx.adobe.com/content/help/en/after-effects/using/memory-storage1.html
Regards,
-Jay-

What is background rendering? Should I use it?

Sorry for the probably very basic question, but I recently started using Premiere Elements 8 (was using 3 before) and I am not totally clear on the purpose of background rendering even though I have read the faq's and Adobe help descriptions of it.
Is it just for viewing the clips once they are in the movie? Or does it actually affect the final product? Do I need to wait for background rendering to complete or do it by pressing entere before I watch a clip that I have just placed into the sceneline or timeline? Just would like to know what the general purpose of this is and whether I should use it.
(Right now I am working with some old Motion Jpeg files which I have convereted to DV-AVI, but later I plan to use mostly mts files from my camcorder.)
Thanks in advance for your help.

Tech_Savvy,
Good explanation on Rendering.
Some folk do it constantly for that smooth playback. Personally, I will only Render small sections (by setting the WAB), when I am working on Keyframes, of custom animations and Transitions. These, I want to see as smoothly as playback will allow.
The drawback to Background Rendering is that it does take resources. On a fast computer, the user might never even know that it's going on. With a slower computer, the GUI will seem to hang, while this Background Rendering is going on, and any change will trigger it. I do not have PrE 8, but would turn this off, even on my very fast workstation, and manually Render, just the sections I need to preview, when I need to do so. That's just me.
Going back many years, Pinnacle added this feature to Studio. It caused so many problems, though I have to admit that computers were a lot slower then. Most users could do nothing in the program, while the Timeline was being Rendered. Everyone, who I knew, turned it off and never looked back.
Thanks for the inclusion,
Hunt

Corrupted clip freezing FCP X during background rendering.

When I open a particular project, the background rendering starts up and gets to 35% where it then freezes the whole job.
Had to do a Force Quit.
This first occured during colour/exposure modifying, btw.
On start up of FCP I can review the video in the project window and see that a small part of one clip is corrupted, but as soon
as I open FCP (10.0.7) it attempts the backgound render before I can stop it, there-upon freezing.
Can the particular offending clip be successfully removed before I open FCP?
15" MBP with retina display, OSX 10.8.2
Thanks in advance.
Andrew

BenB
Thanks for that - "selected", but not "opened" I see.
Also, I reckon they should change the confusing menu item "Project Properties" to straight "Projects" Yes-No?
RussH
The particular clip would jump around - black frames-out of position frames -staccato playback.
As I said, this was after I'd tried colour adjustments that wouldn't render beyond a certain point.
Thanks for that lead to Pro Maintenace Tools. Does it work specifically with FCP X? Will check it out.
I do have the very handy Event Manager X.
Thanks all

Why turn on background rendering?

So I have a 16gb ram macbook pro retina. I am editing native avchd 720p video in my timeline. This computer will pretty much play back anything with no hickups, even if it needs to be rendered. My question is, if in the end I am going to DVD, why does FCP even need to render if it isn't rendering to mpeg2 format? Is there any reason I wouldn't want to turn off background rendering since I want to export to MPEG2? Thanks!

If you computer is fast enough for realtime playback without rendering you don't need to render before exporting.

Does background rendering stop all waiting for it?

I have some "pre-sales" questions about Final Cut Pro X.
1. I have a Sony HDR-XR500 camera, and so when I import it into FCP X, the video would be transcoded to QuickTime on import, and optimized to ProRes.
Using the type of video described above, if I were to apply a green screen effect to it, as well as adjust the video's lows/mids/highs, would I immediately be able to play back the green screen video without waiting for any rendering, and without any jumpiness in the video?
You see, I am used to waiting long periods of time with Final Cut Express 4 for rendering to finish, before I can smoothly see the green screen effect. But reading about background rendering etc. with Final Cut Pro X sounds very good, and I was just wondering if it is really true that I no longer need to wait for rendering to complete to see the green screen effect run smoothly?
Note: I have a 64-bit Intel Core 2 Duo Mac.
2. Is Final Cut Pro X's green screen filter as good as Final Cut Express 4 was or better?

Hello Hope4You,
In reply to your question, "So would you recommend FCPX at this point?" Ahhhhh.....now there's the million dollar question. It's a question that has sparked some very heated debates, some with over 120,000 views!
All I can give you is my experience. This is where I'm coming from: I've been editing on a "prosumer" level for about 4 years with FCE. I bought FCPX about a week after it first came out. I've been "experimenting" with it for over 30 hours. I run FCPX on my iMac (10.6.8 with a 3.06 GHz processor, Intel Core 2 Duo with 4 GB of memory). I use a LaCie external hard drive.
In those 30 hours I have never had the system crash, no spinning beach ball and everything has worked the way it should (there are others on this forum who have had problems but I don't know what their specs are).
For me FCPX is not buggy. It is missing some key "pro" features that were in FCP7. In my opinion probably most if not all of these features will be added over time with updates. Coming from FCE4 you are going to really like some of the more powerful features in FCPX that were not in FCE4. If you are like me I think you will find the UI (mainly the timeline) to be odd at first, it's really more like iMovie. As the world is full of change these days (remember the good old days when banks had customer service?) it's a good thing to learn new things.
Based on that I would go for it. I believe for you it will be a great step up.
MIke

Background Rendering is slowly killing me

I'm working on an unusual project in FCPX. I have a multi-track project 14 minute project. Each of these tracks has a duration of 7 to 14 minutes. There is one full screen background track and the others are scaled and tiled over it.
The problem I'm having is that every time I make a small trim, adjustment or add some titles Background rendering kicks in and tries to re-render the entire project. Once started, it's nearly impossible to stop the Background rendering and it takes over an hour to complete.
What is the negative impact of turning Background Rendering off?
Does anyone have any suggestions on how to better approach this project to make the editing quick and painless?

The problem I'm having is that every time I make a small trim, adjustment or add some titles Background rendering kicks in and tries to re-render the entire project. Once started, it's nearly impossible to stop the Background rendering and it takes over an hour to complete.
It is strange what you are saying about being difficult to stop background rendering - unless you are not actually aware of what background rendering is. Actually, "background" rendering in FCP X is more "idle" rendering, in that it is supposed to stop when you are actually working on your project; so "nearly impossible to stop" it should not be. Move your playhead, skim, open the inspector, do just about anything and it should silently stop for you, so as to not interrupt your work.
Also you should have no problem if you choose to disable it. You can either render it manually before export, or not at all. Contrary to popular misconception, you don't have to explicitly render before exporting. It may or may not take longer to export, but it will export correctly, even if the timeline is not rendered beforehand.

Turn off background rendering

Hi, new to this software. Just moving over from PC! I am using iMovie 06. How do I turn off background rendering? Its annoying. I dont mind rendering at the end but it slows my system down? I am very new to this and apologise if I seem a little stupid! Many thanks.

Excellent - many thanks. I do not use 08 though but it is good to know for when I do make the move. Many thanks.

Background rendering on load

Similar Messages

Maybe you are looking for