Not normal. Try producing to disk - which later can be burned to DVD using a various commercial and free programs.

Thank you for the reply. It was my understanding that large files work better when "produced" first (otherwise, why even have the option?). This is a large file with many awesome effects, etc.... but 100 hours?!?! I am hoping my Support Ticket yields better answers/solutions and I will share here for those who run into similar problem.

westwalker999,
please supply a dxdiag (computer diagnostic) to better understand your computer's hardware.
http://forum.cyberlink.com/forum/posts/list/29701.page
See Part A and Part B. Attach the dxdiag, it will be VERY helpful.
Also, the type of video files you are using.
Thank you HP Envy Phoenix/4thGen i7-4770(4@3.4GHz~turbo>3.9)
Nvidia GTX 960(4GB)/16GB DDR3/
Canon Vixia HV30/HF-M40/HF-M41/HF-G20/Olympus E-PL5.
Tape capture using 6 VCR, TBC-1000, Elite BVP4+, Sony D8 camcorder with TBC.
https://www.facebook.com/BarryAFTT

westwalker999,

Along with BarryTheCrab's request for Diagnostic info, Tell us about the format of the source Video.

What is the source of your video, what is the resolution, what is the file type?

Carl312: Windows 10 64-bit 8 GB RAM,AMD Phenom II X4 965 3.4 GHz,ATI Radeon HD 5770 1GB,240GB SSD,two 1TB HDs.

Your 1 hour project with many awesome FX may be overwhelming your machine, but 100 hours does seem crazy-long.
When you say "many awesome FX", well, if that includes stabilization, color correction, cropping, speed changes, lighting correction, or any combination of those, plus any other FX from the FX library, all those things make a computer work like a dawg.
Many folks buy HD cameras, only to find they're trusty computers choke on them.
The dxdiag will enlighten us. HP Envy Phoenix/4thGen i7-4770(4@3.4GHz~turbo>3.9)
Nvidia GTX 960(4GB)/16GB DDR3/
Canon Vixia HV30/HF-M40/HF-M41/HF-G20/Olympus E-PL5.
Tape capture using 6 VCR, TBC-1000, Elite BVP4+, Sony D8 camcorder with TBC.
https://www.facebook.com/BarryAFTT

Boy as a novice it would be difficult to track down all of those diagnostic questions! lol. I did use a combination of HD video and cell phone video, plus picture (total images/video file is 4.5 GB) AND loaded in music everywhere. I used FX and transitions everywhere, and more... much more..and added title and subtitles.. I did notice warnings that the videos were not the right frames per minute? but it played okay when I inserted it anyway! ok..sounds like there is a large learning curve needed to get things cleaned up for future productions. Maybe this one will go through! 32 hours and 32% done so far!!

..actually I saw jpegs and MP4 as the most common extension

could not find the 64 bit.


The PD is being used now (in Production/redering) so I do not want to mess with it. But it is literally days old (just purchased/upgraded).

westwalker999, I agree with everyone else that you shouldn't be seeing produce times anywhere near what you're seeing.

I'm glad you uploaded the DXDiagfile, because there are a couple of things that concern me. One is fairly minor, in that you have an older driver for your built-in HD4000 graphics. Yours is dated 12/21/2013, while the current version came out 5/24/2014. You can download it here.

The main thing I'm concerned about is that you've had 9 BSODs (Blue Screens). If you only upgraded a couple of days ago, this is very serious. It's possible that these errors occurred before your CPU upgrade, so please tell us when you saw the errors.

To be honest, I'd scrap the producing that's now going on so you can run some diagnostics and hopefully get PD12 working properly. Like Barry said, it is possible to throw so much stuff onto your clips that it will take several seconds to produce each frame, but even then it would be hard to exceed 3-4 hours for a video that's your length.

I'd suggest two things once you've clicked on the Cancel button: first, run the System File Checker from an elevated prompt. Since you're running 8.1, right-click on the Start button and choose Command prompt (Admin), then type in "sfc /scannow" (without the quotes) and hit <Enter> to let Windows run a quick diagnostic of the protected OS files. That might be enough to find and repair the issues with your Blue Screen crashes.

After you update your video driver, maybe you could save your project as a different name, and delete everything in the timeline past the first minute, or first couple of clips, then try producing it.

If it's still really slow, please use the Pack Project Materials option on the File menu to save your mini project, then zip it and attach it to your next post so that we can see what kind of effects you've got there. Other members can then see how fast or slow producing takes on different machines.

You should also take a look at the settings you have for Hardware Acceleration and Produce under Project Preferences (gear icon). I can't see from your previous screenshot, but it would be nice to know what settings are available to you on the Produce tab before you hit Start. Do you see the option for Intel QuickSync, and is it checked/available?

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°