Announcement: Our new CyberLink Feedback Forum has arrived! Please transfer to our new forum to provide your feedback or to start a new discussion. The content on this CyberLink Community forum is now read only, but will continue to be available as a user resource. Thanks!
CyberLink Community Forum
where the experts meet
| Advanced Search >
Quote:
It really doesn't matter what software it happens with - video encoding or not - no software should ever be able to drive the CPU temperature up to the point of the computer shutting down. The job of the cooling system is to keep the temperature in check. You simply can't blame the software for what's happening on your system.


Yes, I can blame the software if the software manufacturer does not require any special eqipment to operate it, by selling me the entire thing with ability to produce hi def output with minimum requirement that are much lower than my HW the supplier guarantees that the software will not require any additional resourves. Which is not true in this case.

Quote: I will check the bios version later and will run the Prime95 as you suggest. Will post results later.


My MB is rev 1.1, so the latest stable BIOS is F9, which I already had installed for a couple of years. GIGABYTE does not recommend going to F10e, which is a beta version. The F10e contains a fix for FX CPUs , but not the one I have.

I ran PRIME95 for 23 hours and some minutes. The CPU temp has not exceeded 61.25 C. I had it on Small FFT, which is a max heat. So going back to my original statement, something is wrong with PD

Quote:
FYI, I just downloaded the Open Hardware monitor software.

I created a project with a 4K clip , inserted 10 times on the timeline. Total project duration - 10 minutes.

I then did a software encode to H264 MP4 AVC 4K 3840x2160/30p with PD13 (latest patch, 3130).

I have attached a screen capture that includes PD13 in the middle of this encoding, the task manager showing 100% utilization, and open hardware monitor.

As you can see, 3 minutes into the encoding, the CPU temp did not exceed 59°C on my system.

We both have the same CPU, and the same motherboard, same temperature monitoring software, and running PD13.

Only difference is my system is OC which should drive the CPU temps even higher than yours. But it does not, because I have an adequate cooling system.

If you have a project that reproduces the problem on your system, I can run it on mine and measure what the temps are, too.

I will even reboot my computer and disable my OC to make it even closer to your system, and show you what the temps are for that case on my system.

As I type this, the encoding has been going on for 16 minutes, and CPU temp peak was 60.9°C. Still nowhere near your 80°C. There are 8 minutes to go and I fully expect it will finish without issue, but I will let it finish. Edit: it completed. The peak temp was 63.6°C. I actually saw this peak as it occurred when I started using a few other applications while the encoding was still running (no mean feat when PD is using 100% of the CPU). The peak was only for a few seconds. I kept an eye on the Open hardware monitor and for the most part, temp was in the 58-60°C range for the 25 minute encode.


My original input file is about 45 minutes, res 600x400, if I make the output of the same res the temp go above 70, but it manages to complete the work, and it takes about 40-45 minutes. The problem occurs when I attempt to make a high def, 1900x700 or something, the time it is supposed to take grows from 40-45 minutes to about 1.5 hour, which is not an issue. But about 15-20 minutes into the work the temps go way above normal.
With all due respect temperatures going up does not mean my cooling system is not working fine. It only happens with PD. It never happens with any other video editing software, paid or free.
My test with Pinnacle was exactly the same rendering as with PD. same settings same technique, same input file even, both SW encoding.
Only PD is taxing my CPU.
Don't get me wrong, I am not complaining that my GPU temp is not going up. I am fine with it. My problem is that this software is too taxing for a simple action I am trying to accomplish. And apparently I am not the only one.
My HW is well within specs that Cyberlink requires for the software. And my "old GPU" is well above minimum specs required:
"Graphics Card
128 MB VGA VRAM or higher (1 GB or higher VRAM and OpenCL capable are recommended)."

My CPU is not overclocked, never has been.

I will check the bios version later and will run the Prime95 as you suggest. Will post results later.

thanks
I disagree about the HW problem. my cooling system is working fine.

As I wrote I used Pinnacle studio on the same PC, same input file and creating same format output file and had no issues.
I have a similar problem, computer just shuts down when PowerDirctor 13 is producing high quality video output.

To measure temp on components i use Open Hardware Monitor. So I traced the shutting down to significant CPU temp rising. It went above 80 C.
That is not normal, I compared PD 13 video producing to Pinnacle Studio same quality video producing. With Pinnacle my CPU temp did not go above 50 C on the HD video

An interesting thing that only CPU temperature went up, not the graphics card or the motherboard.

These are my PC specs:
Gigabyte GA-990FXA-UD3
AMD FX-8350 8-core
NVIDIA GeForce 9500 GT
24 GB DDR3 memory
liquid cooling system with 3 120mm fan and 1 180mm fan.


Go to:   
Powered by JForum 2.1.8 © JForum Team