Post-Render time waste for H264 & ProRes Export on Windows?

There is one thing that bothers me all the time.
If i render to some 1 Gbit/s windows network location, everything is fine until multiplexing starts, and it goes like this:
1. Premiere CC creates .m4v file for video and .aac file for audio - thats OK.
2. Then multiplexing starts and some temp file like "s3r4." is created - no problem.
3. After that Premiere creates desired ".mp4" file with suffix ".mp4._00_" and copies "s3r4." to that file
4. Than it renames ".mp4._00_" to ".mp4" and render is finished
The thing i don't get here is why Premiere have to copy already multiplexed file "s3r4." to "_00_" file
and than rename it back to mp4? This procedure takes a lot of extra time if you have some huge file size (4GB? 8GB?)
The other thing: i have also installed Drastic MediaReactor for Direct ProRes export from Premiere CC on Windows.
Files are huge, no multiplexing in this case, but still after render Premiere starts
it's unneeded copy process of ".mov" file to ".mov._00_" and than back to ".mov".
I've tried to "end task" and just use the uncopied ".mov" which is available immediately
after render and it works fine and has no problems at all. I have also contaceted
Drastic Tech on this case and they said they have nothing to do with this copy/pasting.
That's why i don't know why Premiere has to copy/paste post-render files to the same location after render.
In case of ProRes they can reach ~20GB and you can imagine how long does it takes to copy/paste
such file especially to a network location.
Why instead of "copy" Premiere can't just use a "rename"? That could be blazing fast!

Try exporting to a local hard drive instead of one on a network.

Similar Messages

Render time. Is 11 hours render time reasonable for a 90 minute file?

I started with a 120 minute AVI file, trimmed the last 30 minutes off and am rendering it to an identical format AVI file. Is 11 hours render time reasonable? Have I set something improperly?

More information needed for someone to help... please click below and provide the requested information
-Premiere Pro Video Editing Information FAQ http://forums.adobe.com/message/4200840
AVI is a wrapper, what is inside YOUR wrapper?
Exactly what is INSIDE the video you are editing?
Codec & Format information, with 2 links inside for you to read http://forums.adobe.com/thread/1270588
Report back with the codec details of your file, use the programs below... A screen shot works well to SHOW people what you are doing
http://forums.adobe.com/thread/592070?tstart=30 for screen shot instructions
Free programs to get file information for PC/Mac http://mediaarea.net/en/MediaInfo/Download
What effects have you applied to the video?

PRORES Exporting on Windows 7 machine

Is it possible? Maybe there is on option to use FFMPEG library to export diectly somehow?

I've found out that there is another PRORES Encoder on windows 7. That is Harmonic ProCoder. Version 3.19 and it has all PRORES presets.
I can imagine that with help from FrameServer (if it still works in CS6) we can export to PRORES directly from timeline.
But this method needs testing, i will report back if it succeeds

Render times different for FLV?

I've set up a virtual cluster for Compressor and witnessed the astounding speed increase using Activity monitor. I'm wondering though- the render jobs were using an .mov being rendered to .mp4 (and other formats) and I was able to see all 8-cores being utilized. When I try to render to flv (using Quicktime Export Components) performance drops to ONE core, and takes much longer.....is flv just processed differently in Compressor or does Qmaster not process all jobs the same?

Only certain codecs can be segmented, h264 can, flv can not.

Render times differing for same composition

I'm trying to render a composition and the first time I tried it said 7 hours. So I shut the Mac down, went home and set it going over night. But it only took 40 mins to create a Lossless render. Great, I thought.
So today I'm trying to export the same Comp and it's saying 4-5 hours! I've cleaned the Cache, enabled multiprocessing etc and it's still saying 4-5 hours.
Any idea why that would be?
All the settings are the same. Output codec, output location etc.
Stumped.

Welcome to the wonderful weird wacky world of After Effects renders. Do you have multiprocessing turned on? How much RAM do you have? How many cores? What's your source footage? What resolution & codec are you rendering to?
I've run into the same situation. Even though I have gobs of RAM (32GB), sometimes rendering with fewer cores and less assigned memory results in faster rendering. I'm sure Todd will be along to provide the link for tuning your RAM/Core settings (I don't have it offhand). I find usually my Mac is fastest after a fresh reboot and not running anything else.
So you are saying you got 40 minutes with multiprocessing turned *off*?
40 minutes vs 7 hours seems a little extreme. You sure it completed rendering? You did it at full rez at full frame rate?

Since the last update, every time we start Firefox, it quits responding. If we wait long enough it will fix itself. This is a big time waster for sure.

When I start the program, it will hang. Bringing up Task Manager it shows that Firefox is not responding. Also if I click anywhere on the screen, the screen will lighten up and also show "not responding."
I have tried closing the program and reloading but this does not help. The only thing I've been able to do is wait and wait and wait. Then suddenly it will start working again.
What to do? I have had this problem a few times in the past but do not recall how it was fixed and I'm lost on what to do except to accept this or go back to using Explorer.

Which security software (firewall, anti-virus) do you have?
It is possible that your security software (firewall, anti-virus) blocks or restricts Firefox or the plugin-container process without informing you, possibly after detecting changes (update) to the Firefox program.
Remove all rules for Firefox and the plugin-container from the permissions list in the firewall and let your firewall ask again for permission to get full unrestricted access to internet for Firefox and the plugin-container process and the updater process.
See:
*https://support.mozilla.org/kb/Server+not+found
*https://support.mozilla.org/kb/Firewalls
*https://support.mozilla.org/kb/fix-problems-connecting-websites-after-updating

Time machine for Mac OS X and Windows Server 2008 R2

Hello,
I am using Mac OS X Lion (Maciontosh HD) and i am using Windows Server 2008 R2 (BOOTCAMP) through Bootcamp.
Now i am trying to change my 320 GB HDD to 750 GB HDD. So, i back up my mac data (Maciontosh HD excluding BOOTCAMP part) through Time machine and backup the WS Server (BOOTCAMP part) by windows backup management.
Now i am able to restore both, but the interresing thing is i can not see the data of Windows server while i am using Mac OS. Anybody can help me?
Is there any suggestion regarding the backup and restore of like dual booting?
Regards,
Huq.

Hi, did you end up finding a solution to this? I'm looking for the same thing. Thanks a lot

FCPro Render times - much longer with different Sequence?

Has anyone else noticed this? For many years I have worked with just a few Sequences in FCPro, and the render times seem to be similar in them all - at least that I've noticed. When I slow motion scenes, or render simple graphics - I kind of have a feel for how long I have to wait for various things. Both with my MacBook Pro (2010) and Mac Tower (2 years old). I've always found render times, not excessive. Usually I've worked with DVCProHD.
BUT NOW . . . I'm noticing I'm waiting 2 to 3 times longer for any render. By NOW, I mean since I bought the XF300 and am natively importing 50mbs 12x720 footage into FCPro. (I overcrank a lot, so I tend to stay with 720.) It can now be done after the firmware upgrade a few months back. I love how much faster "native" import is, and I love it using 50mbs as it should, not 70mbs, which it did using ProRez import.
BUT I'm noticing much longer times to render in the XDCAM 422 720p30. Render screen says "conforming edited MPEG-2." Of course, this takes away some of the excitement, and is downright annoying! Has anyone else noticed this, or is it just me? Can render times change significantly, depending simply on the timeline Sequence setting? If they do, I'll just live with it - but I need reassuring that it's normal to take much 2 or 3 times the time - or I'm kinda hoping I'm doing something wrong!
Thanks,
Larry

OK Shane, I've done a bit of work here - this might surprise you? Maybe you'll learn something, we'll find out. But you've certainly been helpful to me!
OK, I took a 5 minute Sequence, shot with the Canon XF300, imported natively into FCPro. The test here is to now render in XDCAN vs. render in Prorez. I LOVE Logging & Transferring in NATIVE as the files are 30% smaller (50mbs vs. 70mbs - and that goes for the ProRez exports as Self Contained movies, too - 70 vs. 50mbs.)
So now it gets interesting . . . to render the 5 minute movie using XDCAM HD rendering (same codec) as importing footage = 5 minutes to render the timeline. Not much rendering was needed. Coincidentally, 5:00 even to render about a 5 minute movie. The total render "space" it used was 932meg.
Now . . . I did the same render (after I deleted all renders) but this time I had it render in ProRez instead. It took 3:30. Soooo, it saved 1:30 in the rendering process. GOOD! So we "learned" FCPro renders faster in ProRez as compared with XDCAM, which is exactly what you said! Oh, it ony used 832 meg for the ProRez renders, which means not only is ProRez faster to render, but it uses about 10% less space to actually "do"it.
But here's the GLITCH I can't explain. I then exported to self contained movie (which we normally do in our workflow, master to a self contained movie to save). In the XDCAM render sequence, it takes 1:35 to export to self contained movie, about normal for a 5 minute movie. But the ProRez render took almost 6 minutes to export!!
WHY would it take over 3 times longer to export the ProRez sequence compared to the XDCAM sequence? This is what didn't make sense to me. (I'm wondering maybe in the export process, FCPro doesn't "see" the (ProRez) renders and has to rerender it just to export it? And that's why the export time is so much longer with ProRez? What do you think?
So to sum up, NATIVE import is faster and smaller files. Then ProRez render is faster and smaller files. So I'll do that! BUT then it takes longer to export the "ProRez" rendered Sequence You just can't win!!! If you have a 60 minute timeline, it's seriously longer!
Do your findings parallel mine? Anyway, thanks for your time, and if you can't tinker with this, I certainly understand. I'm just trying to setup a workflow here. I've tested this 3 times, my results are consistent.
Thanks again,
Larry

EX cam footage render time?

I have EX1 footage captured as EDcamEX.
I placed it in a pro res time as recommended for faster renders.
The footage was an event- low light. The gain was high.
I applied a BCC Denoise filter.
The filter cleaned it up nice but,
The timeline is about 90 minutes and The render out is taking 11 hours (?)
Is this render time correct for this type of filter on this length timeline?

Hi -
Couple of things:
1) When dealing with XDCam and Ex footage, I routinely get very long estimates for renders that rapidly drop as the render progresses.
2) I am not sure what advantage you got by editing the Sequence with the Codec set differently from the source. I routinely edit Ex footage on sequences that have the same codec (XDCAM EX 1080p30) and the renders, while not zippy, are not outrageously long. If you think about it, now FCP has to convert all the footage used in the sequence to Pro Res as well as rendering any effects or transitions. This is probably quite CPU intensive.
Don't know if you want to consider this, but you might want to create a new sequence that has the same codec and frame size and frame rate as you source material, and copy all the clips from your ProRes Sequence and paste them to the new sequence and try a render there.
Hope this helps.

USELESS ONLINE HELP FACILITIES For all the amazing productivity aids that APPLE offers the world I have to report that their online support service is worse than useless and has recently been the source of immense time wasting and irritation.

USELESS ONLINE HELP FACILITIES
For all the amazing productivity aids that APPLE offers the world I have to report that their online support service is worse than useless and has recently been the source of immense time wasting and irritation.
Incident 1. Since many months attempts to download new and updated APPs produced a response – Apple ID Disabled. I had no time to consult an APPLE Store due to work in distant lands. When I finally visited yesterday I was told that as my IPAD has been reported as stolen, and APPLE in its wisdom had blocked its usage! I am not sure how they became so misinformed and nobody every advised me while with a few swift moves APPLE could have located me by email address or SKYPE.
Incident 2. Once the above anomaly had been fixed I tried to down load a newspaper and diligently input my address, credit card number and personal data. Repeatedly I was advised that my Credit Card was invalid and my postal code was incorrect! Really!
I was left to guess that having moved from UK to the US I should have advised APPLE! Not being told of this requirement brought about a second visit to APPLE Store in the same day to waste both mine and their time with a routine anomaly. How parochial in the context of a globalized world!
In each case I tried to resolve the issues using online access to a help line and by calling by phone at the numbers on the APPLE Website. In each of four separate occasions I diligently went through the routine and ended up with a message that thanked me for contacting Apple followed by a polite ‘Good Bye’!
In desperation I went to an Apple Store for the second time in a day as it is close to where I live when I am not working. On both occasions I was courteously attended to by Apple Staff.
However, my work is usually far away from the US and it is generally many thousands of miles to the nearest Apple Store therefore online help is viewed as imperative if one is to resolve issues away from home.
Why can Apple not provide a clearly marked EMAIL address and Telephone number at a Help Desk with real people to respond to requests for help? It would cost nothing in relative terms and might restore my high level of anti-APPLE sentiment that these two recent events have provoked.
Peter Hanney
Miami, Fl.

Why can Apple not provide a clearly marked EMAIL address and Telephone number at a Help Desk with real people to respond to requests for help?
If that is your question, the answer is at the bottom right of this web page. It is clearly marked "Contact Us" and is the best way, really the only way, to contact Apple.
If there were a publicly posted email address for concerns such as yours, it would be quickly filled with spam in about three minutes, thereby becoming instantly useless to you and everyone else. Apple would need to change it hourly, if not more often. That is also the reason you ought not to post your name, location, and what appears to be your iPad's serial number on this publicly viewable website.
Apple does not respond here and I can find no other questions for your fellow Apple users to answer.

Help with configuring Qmaster for optimal render times.

I have a 6 machine Qmaster cluster. All machines in the cluster are PowerPC based and I have set up the cluster manually through Qadministrator. I personally like to have everything set up manually so no changes can be made for any reason to this cluster. I have processed a 2.5GB video in the cluster and in an Intel based Mac Pro.
Using Compressor, my output for the file is H.264 for iPod video and iPhone 640x480. The source was placed on an external Firewire 800 drive and destination is to the local disk on the Intel machine.
For the cluster, the source, also from the external Firewire 800 drive, is connected to the cluster controller, which has full read write access to all nodes in the cluster and is not a node in the cluster itself, just set to be the cluster controller. ( I saw this setup on a Qmaster setup page here, http://www.eventdv.net/Articles/News/Feature/Distributed-Network-Encoding-with-A pple-Compressor-37923.htm ) Also, I am using the same output settings, H.264 for iPod video and iPhone 640x480, and output is being written to the cluster controller local disk.
Once the batch is completed, it takes 23 minutes to render the video in the cluster as opposed to 25 minutes on the Intel machine. Not the difference in render time that I hoped for.
Here are the specs for the machines,
Cluster nodes:
1.6 Ghz Powerpc g5 1.25 GB
1.8 Ghz PowerPC G5 4GB
Quad 2.5 Ghz PowerPC G5 2.5 GB RAM
Dual 2.0 Ghz PowerPC G5 2.5 GB RAM
Dual 2.0 Ghz PowerPC G5 6 GB RAM
Dual 2.7 Ghz PowerPC G5 2.5 GB RAM
Cluster Controller:
Dual 2.0 Ghz PowerPC G5 2.5 GB RAM
Intel Machine:
2 x 2.26 quad core Intel Xeon 6GB RAM
Now I know these machines in the cluster are old but all machines, except for the cluster controller, have gotten fresh installs of Leopard 10.5.8, all relevant updates applied and fresh installs of FCP6, Qmaster and Compressor. I still cannot figure out how to speed up rendering. Is there something in this setup that I am doing wrong or is it the limitations of the old hardware. In theory, it should break up this video into segments across all machines in the cluster but it doesn't. The chunk of segments are sent to the Quad G5 and yes I have enabled multiple cores in the Qmaster prefs pane. So I figured i'd only enable 2 instances on the quad core machine and then it started to send segments to other machines but render time is still slow.
Also, even though all machines had read/write access to each other, I would scroll through the log files and see that it could not read the segment from the source media, but I could clearly see the activity light flickering.
After all of this trial and error, I still cant get the render time under 23 mins for this video.
If there's anyone out there with some advice, it would be much appreciated. Also, I forgot to save a copy of the log file, so my fault on that one but I will post once I get a chance to get back to working on that cluster.
Thanks.

Update:
So I have been able to get the cluster working. I've used Compressor and have the source media located in the shared folder that the controller mounts as cluster storage on all of the machines. The problem that I can't figure out now is why the cluster won't read the source media from any other location. I've read through Qmaster documentation and the permissions are supposed to be bypassed when you are using Qmaster.
I have both the mac HD and clusterstorage drives mounted for each machine, on each machine. Still, the cluster won't transcode the file unless I drop the media into the shared folder first. Every sharing option I could think of has been enabled. I have enabled file sharing, appletalk, set read & write permissions for each drive in each machine for all users and It still won't work any other way.
It just seems impractical to have to first copy the source media to the shared folder mounted by the controller since all locations on each machine have been totally opened up.
If anyone has some advice about this issue, it would be greatly appreciated.

Dramatically slower encode/render times from Premiere Pro CC 2014 via both AME 2014 and direct export via PP

My recent update to Adobe CC 2014 apps has been an unmitigated disaster. Was running the 2013 version until last week and everything was just dandy. Very good performance and excellent render/encode times even for stuff with lots of filters and fx.
Since update 1-2 min videos with no fx or filters (or even transitions) have gone from exporting in under two minutes to well over 25 minutes. These exports are with the same presets I regularly use (Vimeo 720HD H.264).
I've been poking around the forums here for two days looking for answers and can't find anything that works. Tried the whole "App Nap" toggle as well as a few other tips. Didn't do squat. Looking for any hints/answers. Thanks.
Mac Pro Mid 2012
2 x 2.4 GHz 6-Core Intel Xeon
32 GB 1333 MHz DDR3 ECC
ATI Radeon HD 5870 1024 MB
OS X 10.9.5 (13F34)
System SSD 500GB
Cache SSD 500GB
Media HD 1TB

Hi MXSw,
MXSw wrote:
All right. More experimentation has been done. Seems like the renaming of Adobe folders fix prescribed in the link below might have helped a bit.
Premiere Pro CC 2014 renders are painfully slow.
You can rename folders, but I prefer to do it this way: Premiere Pro CC freezing on startup or crashing while working (Mac OS X 10.9, and later)
MXSw wrote:
Kicked out a 1 minute edit with some color/fx in under 10 minutes. Not as fast as in the past but at least the CPU seemed to be cranking at 500% and above per Activity Monitor. Its barely gone over 250% in previous attempts.
That sounds a lot better.
MXSw wrote:
Same 1 minute edit took 35 minutes however when I exported from a PP timeline using MXF clips instead of QTs. I assumed the QTs would speed up the process but in the past I've gotten great performance on big old RED raw files so still a bit of mystery why I can't approach the speeds I had prior to most recent CC update.
Maybe updating your project file has something to do with it. I'll keep my eye on this issue. Thanks for reporting.
Regards,
Kevin

Exporting HD in FCX - massive render times issues

Hello,
Reading the FCP X Help topics etc I think I have a good understanding of import/export criteria. However, I have it from some peers that I could do much better with regard to reducing the massive render times I am experiencing.
Currently the render time for an 8minute clip is 26 hours using Compressor 4 using preset 'HD 1080 Video Sharing (H2.64) - AAC
BACKGROUND:
OS X 10.8.3 (12D78)
17-inch, Late 2008 MacBookPro
2.5 GHz Intel Core 2 Duo
4 GB 667 MHz DDR2 SDRAM
FCX 10.0.8
Raw footage is 1920 - 1080 from Canon D7 card - copied to an external HD.
Import settings: both proxy and optimised - both with huge export times as above.
Destination to Movei folder or desktop
The 8 minute sequence includes filters which I know will increase processing time, but by this much is pretty horrendous. (a 'preset' colour correction + sharpen + manual colour correction)
My understanding is that if I import - or later convert all footage - into optimised files - these become ProRes222 files which will give me much faster render and export times. But this does not seem to be happening.
It simply is not efficient or practical to myself or any clients to have 25 - 30 hour export times for 8 minute sequences
My impression is that this computer is simply not up to faster rendering/export processing - but my peers tell me my currrent render/export times are rediculously long.
Can any one advise please.
Thank you.

This is the Final Cut Studio forum.
You need to ask your questions here: Final Cut Pro X

Rendering Hundreds of Audio Previews Upon Export, Long Render Times

Hi everyone,
I have an assembly cut of a feature, with footage and a timeline at 422 ProRes HQ, 24 fps, 96kHz audio.
When I try to export any length of a clip, I get exorbitant render times and hundreds of audio previews to render.
Video alone is rendered almost instantaneously.
There are some audio files on the timeline (music and SFX) at 48k sample rate.
Any ideas what the problem is?
Thanks.
Premiere CC 2014
OSX Mavericks
2 X 2.66 Quad Core Xeon
32 GB memory
NVIDIA Quadro 4000 w/ CUDA
3 tB 7200 RPM - RAID 0

Thanks, Ann. I'm thinking that may be a factor because this is the first time I've had to work with audio recorded at 96 and I've never had this problem.
Can anyone else elaborate more?

Render time taking 1 hour for 4 seconds

I am trying to render a 4 second clip of 3d text doing a 360° turn, I export in H.264 and have okay computer specs.
3.04 GHz Quad core
12 gigs of ram
I'm new to this and want to start exporting more video for a project, but I can't do it with this render time.
Brandon

LilTunchiB8 wrote:
What would be a conventional, frame-based codec? Thank you so much for the help!
Uncompressed AVI is one, but the file sizes are going to surprise you. Quicktime with the PNG codec is usually smaller, but still huge. Quicktime with the PhotoJPEG codec is even smaller. Some popular choices that are even smaller are DNxHD and Cineform (either MOV or AVI). They're still going to be much larger than the H.264, but that's okay!
For many (most) professionals, the usual workflow is to render a lossless file (or nearly lossless) out of AE and then use the Adobe Media Encoder or Premiere to create the final deliverable. There are several reasons, but one is that AE is not very good at rendering h.264 files (and there are some very technical reasons for this). Anyway, the AE team deprecated the h.264 rendering in the latest version of After Effects because of it.
In your case, I would suggest rendering into a TIFF sequence (or something similar). This way, if there is a crash or something, you can pick your render up at the last frame it rendered rather than having to start at the beginning. I always do this when I'm doing 3d work and the render is going to be over an hour. Then you can bring that TIFF sequence into Premiere as if it's a video file, put your audio and everything to it, and send your final H.264 render from Premiere.

Post-Render time waste for H264 & ProRes Export on Windows?

Similar Messages

Maybe you are looking for