Long rendering times.

Hello everyone

Hello all
I have just taped a 2 hr. school play ( 2 cameras ) in HDV.( Sony FX1's )
I have added some b roll to this program, no special effects, when i tried to render it out it wanted a 7 hour render.
Ridiculous, i've done half hour and one hour segments before with effects and it didn't take seven hours
Settings are in HDV 1920 X 1440
Can anyone shed some light ??
Thanks
Vic

Similar Messages

HELP: I have an impossibly long rendering time after converting .MP4 files from Go Pro Camera to .MOV on Final Cut Pro 7. PLEASE ADVISE.

I am working on a project and shot guerilla style footage with a Go Pro camera, which produced .MP4 files incompatible with FCP7. When I converted the files to .MOV, I realized the rendering time in the sequence editor is impossibly long. I am working with a deadline and the rendering time exceeds the deadline, let alone editing time. Suggestions???

Telling us you converted to .mov doesn't tell us much. MOV is a container that supports a very wide range of codecs. It is the specific CODEC that matters.
You most likely did not convert the material to a FCP7 native format. ProRes is recommended and, given the compression of the GoPro, ProRes LT would be the best choice.
Use Compressor to convert everything to ProResLT and life will be much simpler.
x

FCP LONG RENDERING TIMES, MANUAL FADES J U M P I N G.... Please h e l p!

Hello
Firstly please bare with me as im trying to be thorough
I have final cut studio HD 2.
I am making a "HALO MACHINMA"(basically making a film from manipulated game footage) film for my final project at university.
My HD recorder kicks the files out a M2TS files, so since as far a sim aware FCP cannot touch these I have been converting them to HD quicktime videos using the program "Xilisoft HD converter "
Once i imported these files i was able to edit one scene fine. No issues.
However i have come back to my project a week later. I opened a NEW PROJECT so i could edit another scene without having a huge timeline. I began by using one of my clips and doing a manual opening fade with the pen tool. However rendering took far longer than usual (I have 4GB of RAM so for something so small its usually near instant), then when i went to replay it the fade kept jumping. if i manually tab the timeline bar over it using the right arrow i can see every frame, but play back jumps. (also if i export the video it doesn't jump, however i cant edit correctly like it currently is)
So my issue is, The LARGE rendering times, and the fact it jumps when played if i alter it.
Things ive tried:
I thought, well maybe if i go back to the original project i can try putting the files in there and editing, since maybe the project settings were weird on the other one. However the new files still do the same there.
SO then i thought "maybe these unedited files are corrupt or something similar" SOOOO within the original project I copied an original file that previously worked fine. HOWEVER even the old files dont work correctly. I cannot even alter the original project without HUGE rendering times, however the playback still "appears" fine on the original project.
I am also getting 2 RED rendering lines about the video and audio. where it used to only be 1. (if im correct 2 means the audio and video needs rendered)
If i place in another file like a standard quicktime or AVI i do not have a problem.
I do not understand how it once worked, now does not on these files? have some setting changed?
(when i start a new project i get the box that says the settings are wrong for this, change etc etc. I click YES -so i'm guessing its meant to work fine then)
Please help me, im running out of time on this final university project and any help will be very appreciated.
Thank you
Sam Edwards

Hi Nick
Yes the files i'm using are .MOV files. according to Xilisoft they are HD .MOV files.
although it may only claim there HD due to the high resolution. -1092x1080
ok so i clicked more info on the file and it claims its codec is MPEG-4 video, AAC.
I dont under stand that if there .MOV files then why would they have this codec?
confused.
Thank you

Extremely long rendering times

I am trying to render a 13 minute project.
FCS 2 is telling me it will take 30+ hours.
Is this normal?
Am I doing something wrong?
Best,
Evan Jacobs

So, your source clips are Quicktime Animation, and you're editing them on a "standard" timeline, whic makes me assume that it's a DV/DVCPRO NTSC timeline, with your source material residing on your internal drive.
There are a number of things here that will cause long render times:
1. The nature of the Animation codec in this situation would indeed cause longer than normal render times. Animation is a high-quality mastering codec. When used on a Sequence that is set to use a compressed codec, such as DV/DVCPRO NTSC, your clips will need to be rendered.
To check the Sequence Settings, press Command - 0 (zero).
2. It is not recommended to use your Internal drive as a scratch drive. Not only is that one hard drive reading your source files, writing render files, but it is also running your entire OS, plus any other programs that may be open. That's a LOT of work for one hard drive, so expect less than optimal performance.
Try moving your source material to an external firewire drive.

Long Rendering Time in Premiere Pro with Yosemite

The rendering time with Yosemite and Premiere Pro CC 2014 is stating hours for a 17 minute video (regardless of small or large file) I recently upgraded to Yosemite (mid project like a dodo-newbie to the editing world). I also recently installed a Neat video plug in. Don't know if that has anything to do with it. Should I revert back to Mavericks? Or is there something I can do?

I'M having the same problem, though it's inconsistent. When I first encoutered the issue it was a simple fix of switching to the Cuda renderer from the open CL/Cuda that is automatically selected. That little honeymoon lasted a week or so, but now I'll have 4 or 5 clips varying in length from 30 to 120 minutes and invariably one or more will get hung up and require many hours to export.
Also in the norning after a night of exporting, the ME will indicate the clip was successfully exported, but when the files are checked one or more will not be properly exported. Generally if I try again the clip will export properly and in a decent amount of time, but sometimes it takes seveeral attempts.
Add to that that I get dropped frame choppy playback about 70% of the time it becomes a very frustrating program to use professionally. My drive speeds are good at well over 120Mbs for read and write and this is only 1080/30P material.
Tried tech support via phone, which was a joke, even though I have received excellent support in the past this episode was not so. Tech didn't even give me a case number, and I forgot to request one as well, but after remote linking to my machine for an hour in which he was most of the time off the phone, he came back on said he would watch my machine, but was now hanging up.
Clearly there are issues with this release. The previous release worked fine. I just now need to figure out how to go back to the previous version.
Jim Watt

Choppy Video and Long Rendering Time

Just using iMovie for the first time since loading iLife 09. Two main problems:
1. Video is very choppy. Using the same camera as before loading new iLife and never had the problem before. Noted a solution posted elswhere - "Clip adjustments, click on 'convert entire clip', give it a minute to convert, click 'done'" - only I don't have a "convert entire clip" option. I can do something with stabilizing but it takes 10 minutes to process a 30-second clip.
2. Speaking of things taking a long time, I just started to share a project to iDVD - it appears it will take about 90 minutes to process a 5-minute project with a few transitions. Why is this? Not enough RAM/GHZ? It can't be the project because it's very small with very few transitions.
This is almost not worth it. Any advice on either issue? Thanks.

Hi
First have you set the Quicktime streaming setting, goto sys prefs/quicktime/streaming/streaming speed, set to 1.5mbps(if a comcast user use 500)
In ichats prefs click on video and change bandwidth limit to NONE.
Restart iChat.
Tony

Insanely long rendering time with premiere CC

My config : Hp pavilion dv 7
i7 2GHZ
ATI radeon 2Ghz
8Giga ram
So i'm trying the free trial version of premiere CC and it takes me about 4 hours of rendering a 24 minutes long video. In h.264 hd720P (only 2 video tracks and 2 audio tracks). Before that i used premiere cs 6 and it was quite long too but not that much (around 50 minutes for the same settings), what is up with that ?!
edit : It's also imossible to watch the preview window because of the insane lag even if i reduce the quality of the previsulisation.(1/4) or the size of it (10%), it's impossible to work properly.

Well software and programming and computers are definitly some magic world...with fairies and witches...yesterday morning i tried again and...it was working..perfecty....30 min rendering for a 20 min long project....i did nothing special...just tried pinnacle studio...i guess premiere sensed it Seriously i have NO IDEA what happened, thank you anyway.

Way long rendering times HDV to SD DVD

I was just at the Apple store playing with the new 2.6 MacPro and FCP. I loaded the HDV Beauty sample project and conformed it (2x real time) and went to Compressor to export to MPEG2 to make a SD DVD. A 1.5 minute timeline took 36 minutes! WHOA! Extrapolating, a 2 hour HDV timeline will take over 60 hours of compression. Outrageous! Did I miss something? I just wanted to make a SD DVD from HDV material.
Wuddup wit dat? Is there an easier solution or an economical board I could add to the MacPro to speed things along? Do I need to jump to a PC/Canopus solution?

You could go PC, but you might run into other issues with in-store encoding. Apple stores have better hours and easier access to demo computers so so I'd just start the export before the Apple store closes and come back in the morning when it's done.

Obscene rendering times on Mac G5

Should it take 4 hours to render 4 minutes of a clip? This seems ridiculous, is there anything besides a beefier machine (this is G5 Dual 2 GHz PoerPC) working this way is really frustrating

What happens when Final Cut renders is that it takes all your source media (video, titles, jpgs, psd, etc) and conforms the whole thing into the format specified by your sequence settings (DV/NTSC, HDV, etc). It's possible the render could look worse if your source media needs to be resized or is too heavily compressed to begin with (because you are in essence compressing it again). It's kind of hard to know exactly what the issue is without being able to see what's happening.
I would try recapturing your screencasts as DVCPRO at a resolution of 720x480 (or at PAL size if that's the case). This is the format that FCE normally captures DV footage with, and is a much higher quality than mpeg4 with much less compression. It should be able to play back in FCE without any rendering.
Now that I think about it, double check your sequence settings. I'd assume you had intended to make a DV/NTSC or PAL project - but if you're sequence is set to HDV, that could explain both the long rendering times and crappy render quality.

I have extended video footage taken on my ipad that I need to burn to dvd. Tried imovie and final cut. Final Cut rendering time was extremely long. What is easiest way to accomplish my goal?

I am a video technology teacher and coach at a high school in NJ. I have footage of a basketball scrimmage that I need to get from my iPad onto a DVD. I tried importing it into iMovie without success. I have imported it into Final Cut Pro but the rendering time makes the process very cumbersome with 7/8 hours of rendering time to create a quick time file to then use with iDVD. Is there a quicker way to accomplish this.

The Mac does not come with a Blu-ray burner. So you would be burning a Blu-ray compatible file to a standard DVD-5 or DVD-9. Neither of which are ideal for authoring Blu-ray content.
Do an exhaustive search online about Blu-ray authoring and disk creation. This is not something for the hobbyist video creator (and I say hobbyist in the sense that you're not creating thousands of copies for mass distribution, so no one take offense.)
Blu-ray is expensive and requires a lot of planning and prep to do it right. But you can't burn an official Blu-ray disc on a Mac as they stand. And, Compressor doesn't burn discs, it only creates files. DVD Studio Pro would be the app that would burn the Blu-ray disc, and DVDSP has not been upgraded since long before Blu-ray came on the scene.

Longer export times even though clip is rendered. I don't understand.

Just curious about this. I added a time code generator to a clip and rendered but it took 5x longer to export a ref movie as opposed to the same clip without the time code filter. If it is rendered, why the much longer export times? Everyday is a learning experience.
Thanks in advance.
Best.
Tom

Because a filter is applied, the reference file cannot just point to your source file as it normally would, it has to include the filter because the filter cannot be referenced. This means that it basically has to render the movie and the filter into the reference file.
However, since you rendered first, this leads me to the following questions:
1. Where are your source files located?
2. Where are your render files located?
3. Where are you exporting the reference file to?
4. What are your sequence settings?

How do I deal with project bloat? Long Save time is getting worse?

Here are the FB posts I have got about this issue. I tried to paste them neatly but didn't work.
To be honest I am baffled that such an advanced NLE has so many issues. There should be a warning about the Warp Stabilizer messing up a project I had no idea till now.
This was my question to a PP user group on FB.
I am cutting a 60+ minute doc with lots of source material and the project takes a dogs age to save now which is beginning to interrupt my workflow. I would have thought the save would take less time depending on how much work was done since the last save. I suppose working with Proxies might be the solution but I am already 70% done.
Here are the responses
Saving the project file on an SSD might be a good idea.
Your project size is slowing you down. Create a couple of projects, each containing a part of the footage. Organized in bins as needed. Call them footage projects. Create an other project named edit and cut in there. Use the media browser to browse the footage projects. Import what you need and use search bins to keep it organized.
If you didn't transcode your footage before you started the project it could be part of the problem. And like the other post says only having the footage you are currently working on will also help. The claim that you don't have to transcode when working in Premiere is misleading because in most cases when working with many different source codecs transcoding will always improve your computers performance.
I had the exact same experience cutting a 90 min feature with 120 hours of Pro Res 4444 footage. Long save times are caused by project bloat, either by having too many assets loaded or a lot of warp stabilizer effects applied. Transcoding will only affect playback performance and exports - it doesn't sound like it's the problem in this case.
only some codecs (4K GoPro, 6K R3D, lengthy h264/AVCHD clips for example) benefit from transcoding and will be snappier and playback smoother. But transcoding will never ever help the loading or saving time of your project
Don't apply warp stabilizsr to everything. All those coordinates get stored in project file
All I can say is that I worked on a Premiere project in November where my computer spent up to 5-7 minutes scanning through all the different directories with footage after the project was open before I could play back the sequences in my project. I ha...
some of the ftg is in need of stabilization so I did use the warp stabilizer but not excessively. 15 x 3-10 second clips. Is there a way of managing the storage of the coordinates too minimize the hit on the project size?
nope. Try importing existing project into a new project.
I usually stabilize footage in a separate project to avoid huge project files, and export the stabilized result. Then I use the stabilized version in the main project.
I also work with Nested Sequences a lot. Working in short, manageable timelines. When opening a large project, Premiere will find the footage for the active sequence first, so I can start working quickly, while Premiere is still finding the rest of the footage.
Could do your warp stabilizing in AE and export renders of them, then import those renders into your project so the are just media files instead of files with stabilizer tracking points.

I usually stabilize footage in a separate project to avoid huge project files, and export the stabilized result. Then I use the stabilized version in the main project.
That would be something like the advice I would have given
and more likely...
Save heavy duty FX application until after you have locked down your edit. (eg Blurs , Warp, 3rd party FX(MB)
I Create separate sequences or Duplicate Projects for many reasons. eg CC/Grade and
Warp Stabiliser ...definitely. Its even has a slow save impact on After Effects Projects!

Which is better 7200 RPM HDD or SSD for laptop upgrade to boost rendering times?

This is my current setup
RAM: 8GB
Processor: Intel Core i7-3630QM
GPU: Nvidia Geforce GT 635M - 2GB
OS: Windows 8.1
Storage: 1TB 5400 RPM HDD
I am going to start editing raw footage in premiere pro. I would like to update my laptop to help with rendering times. Tommorow I will be installing 16GB of RAM. Which will be better for storage a 7200rpm HDD or and SDD drive? I am seeing conflicting views on the web. I figured that this will be the best place to ask, since I am upgrading primarily for this program. I appreciate the help.

No clue what would be conflicting between the two. Both the internal operating speed of data handling and the i/o to the system over any sustained period of time are so vastly higher for a modern and large-ish SSD compared to any HDD that it is a total no-brainer. In fact, on the tweaker's page, they point out that for a really monster system, set up RAID's of multiple SSD's. Lacking that, RAID's of four or five linked fast LARGE HDD's which will be noticeably slower than the SSD option but typically better than single HDD's, even using one for each part of the process.
For both the processing of data to present a view on the monitor during editing and during rendering, it's not the "burst" speed numbers that count ... it's the sustained long-term data transfer counts that matter. Which are different from what many think they are ...
neil

MapViewer long preparation time

When MapViewer is not used for more than 1 hour it takes a very long time to produce the first map. After that the same map is produced in less than 2 seconds. In the MapViewer logfile I see a long preparation time. What can be the reason?
Wed May 28 17:28:39 CEST 2008 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] preparation time: 105344ms
Wed May 28 17:28:39 CEST 2008 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] querying/rendering time: 1031ms
Wed May 28 17:28:39 CEST 2008 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] packing time: 203ms
Wed May 28 17:28:39 CEST 2008 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] --------------- total time: 106578ms
Wed May 28 17:28:39 CEST 2008 DEBUG [oracle.lbs.mapserver.core.MapperPool] freeMapper() begins...
Wed May 28 17:28:39 CEST 2008 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] preparation time: 275343ms
Wed May 28 17:28:39 CEST 2008 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] querying/rendering time: 1063ms
Wed May 28 17:28:39 CEST 2008 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] packing time: 187ms
Wed May 28 17:28:39 CEST 2008 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] --------------- total time: 276593ms

Which MapViewer version are you using?
You may have more log messages before the preparation time log. If you have, please post the previous lines of log.
Joao

Long "packing time" in some requests

Hi everyone,
We are having issues with MapViewer performance. Sometimes there are delays due to "packing time" so we are running test with the same request repeated every minute and the delay occurs on occasion without following a definite pattern (requests can range from 900 ms to several minutes for a png image)
Our version of MapViewer is OracleAS MapViewer Version: Ver10131_B061023 working with Oracle Spatial 10g
Log file is written as follows:
+Fri Jun 22 13:11:52 CEST 2012 DEBUG [oracle.lbs.mapserver.core.MapperPool] freeMapper() begins...+
+Fri Jun 22 13:11:52 CEST 2012 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] preparation time: 5ms+
+Fri Jun 22 13:11:52 CEST 2012 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] querying/rendering time: 520ms+
+Fri Jun 22 13:11:52 CEST 2012 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] packing time: 31171ms+
+Fri Jun 22 13:11:52 CEST 2012 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] --------------- total time: 31696ms+
+Fri Jun 22 13:11:52 CEST 2012 DEBUG [oracle.lbs.mapserver.core.MapperPool] freeMapper() begins...+
+Fri Jun 22 13:11:52 CEST 2012 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] preparation time: 4ms+
+Fri Jun 22 13:11:52 CEST 2012 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] querying/rendering time: 907ms+
+Fri Jun 22 13:11:52 CEST 2012 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] packing time: 60841ms+
+Fri Jun 22 13:11:52 CEST 2012 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] --------------- total time: 61752ms+
+Fri Jun 22 13:11:52 CEST 2012 DEBUG [oracle.lbs.mapserver.core.MapperPool] freeMapper() begins...+
+Fri Jun 22 13:11:52 CEST 2012 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] preparation time: 2ms+
+Fri Jun 22 13:11:52 CEST 2012 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] querying/rendering time: 292ms+
+Fri Jun 22 13:11:52 CEST 2012 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] packing time: 57423ms+
+Fri Jun 22 13:11:52 CEST 2012 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] --------------- total time: 57717ms+
+Fri Jun 22 13:11:54 CEST 2012 DEBUG [oracle.lbs.mapserver.core.MapperPool] getMapper(MAPVIEWER_BSIT_SIVA_DS) begins...+
+Fri Jun 22 13:11:54 CEST 2012 DEBUG [oracle.lbs.mapserver.core.MapperPool] getMapper() succeeded.+
Thanks in advance.

It's a bit of a long shot but you could try doing a Parameter RAM reset - hold down command/option/p/r keys at start up and wait for three chimes before releasing the keys.
Probably wouldn't hurt to reset the SMC too (remove power and battery and hold down power button for 5 seconds then put everything back)

Long rendering times.

Similar Messages

Maybe you are looking for