Dafydd, hi, the other files are much bigger than that tiny 8gb file. That was just a sample for the export

I will be doing more extensive testings now that I've gotten to a point where it will function. I do appreciate your time and may need your assistance again when I find the culprit causing the problem.

"Camera uses a heck of lot less bitrate." I know. The thing is, I only want to process the clips once and not multiple times degrading the quality. I'm looking for the highest fidelity I can get out of these productions. I am noob at video editing to be honest and am still learning about it, but I know when something looks great and when it doesn't!

Good news indeed Thanks for the update.
Dafydd

Everything seemed stabled for that setup. However, that Nvidia driver 358.91 is totally unusable for me and my games, it totally tanks the FPS to where it's not even playable. This driver is NOT an option for me.

Discovered HEVC M2TS files rendered at maximum settings will plackback except when you try to skew forward or in reverse with a player. It hangs for a very long time. M2TS it the only format that does this, every time. HW on or off doesn't matter - hw off took way longer to process!

Rendering in HEVC MKV produced an oddball. It rendered a two part clip on the timeline, but it only rendered the first clip of the two correctly. When it got to the second clip it was VERY poor quality like a potato rendered it. I rendered it exactly the same way again a couple of times more and it worked fine.

Stable, no crashes and those tests were 1080p 60 FPS HEVC 38800

---------------

Stage two:

Installed PD14 patch 2303a

Installed Nvidia 361.43 minus EXPERIENCE!

Since the stock Nvidia is not an option I went back to a driver I know plays my games well on my 980ti.

Same tests as before. I'm able to work for a while and render some tests. I can't predict it, but it will randomly crash. I used to have a debugger installed on the the old Win10 install so I could see errors popup, but now I don't so PD14 just quits instantly with no messages when it crashes. Luckily, event viewer shows this actual error message:

Faulting application name: PDR.exe, version: 14.0.2302.0, time stamp: 0x5636e474
Faulting module name: d3d9.dll, version: 10.0.10586.0, time stamp: 0x5632d381
Exception code: 0xc0000005
Fault offset: 0x00000000000124d0
Faulting process id: 0x1c50
Faulting application start time: 0x01d160450b5a9b66
Faulting application path: C:\Program Files\CyberLink\PowerDirector14\PDR.exe
Faulting module path: C:\Windows\SYSTEM32\d3d9.dll
Report Id: c6f7a9ca-caca-427d-b3da-e67c0c0c1a43
Faulting package full name:
Faulting package-relative application ID:
--------
Faulting application name: PDR.exe, version: 14.0.2302.0, time stamp: 0x5636e474
Faulting module name: d3d9.dll, version: 10.0.10586.0, time stamp: 0x5632d381
Exception code: 0xc0000005
Fault offset: 0x00000000000124d0
Faulting process id: 0x704
Faulting application start time: 0x01d1604472679e69
Faulting application path: C:\Program Files\CyberLink\PowerDirector14\PDR.exe
Faulting module path: C:\Windows\SYSTEM32\d3d9.dll
Report Id: 65de15e6-7beb-4cbf-9a5c-de25c807ced8
Faulting package full name:
Faulting package-relative application ID:

Those are two separate crashes. I also find it odd that Directx9 file is being utilized in today's modern systems and, even worse, failing in the application. Only one positive note, since I still haven't installed any additional codecs, Fraps has continued to work on the updates until the random crashes occur.

This issue needs to be addressed and resolved. I simply can not use OLD drivers as those particular drivers do NOT work for me elsewhere where I rely on it the most.

You should do your rendering to H.264 instead of the HEVC H.265 format. H.264 is a lot more common, More players support H.264 AVC than H.265 HEVC.

In Powerdirector 14 Produce module H.264 is H.264 AVC. The dropdown gives choice of M2TS, MP4 and MKV, at several resolutions. 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.

Quote: You should do your rendering to H.264 instead of the HEVC H.265 format. H.264 is a lot more common, More players support H.264 AVC than H.265 HEVC.

In Powerdirector 14 Produce module H.264 is H.264 AVC. The dropdown gives choice of M2TS, MP4 and MKV, at several resolutions.

I'm trying to retain as much quality as possible for the final render to burn to bluray. Then, after I have that first master rendered at the highest bitrate, I can delete the source files that are way too big to keep and are just useless cuts. This way can I have the best master render for my library. If and when I'm going to post on online I WILL render/convert it again (264) to degrade the quality and to compact the file size.

Make sense?

Hi Terminal,
You are showing your inexperience with what you're doing. STOP maxing everything, all you're doing is generating large cumbersome files with exaggerated bitrates.

I worked out a few days ago that your small SSD's would take less than 63 minutes of avi (container) video before they were full and that is without anything else stored. Start looking at what is a sensible bitrate rather than maxing your video capture on the software.

Sorry to "go on".

Dafydd

2 x 1TB SSDs will be very soon. Space is not even an issue at this point, it's about the application handling the situation.

The application not handling the files: it is the files that are the problem, the selections being made to create them in the first place. You have to carry out your task within the confines of the capability of the software that is operating on a home computer.

OK, I'll stop banging on*... what do I know?

Dafydd

Quote: The application not handling the files: it is the files that are the problem, the selections being made to create them in the first place. You have to carry out your task within the confines of the capability of the software that is operating on a home computer.

OK, I'll stop banging on*... what do I know?

Dafydd

The software allows for the option to be made in the settings. My hardware is competent enough to do and does do the job. My available options to choose the best quality possible from within alloted fields in the software using HEVC are features I purchased. Even at 38800 or 38000 bitrate in HEVC, whether it be MP4, M2TS or MKV it's my choice and it should work every time not just a couple of times before the application decides to crash on its own.

IT CAN DO THAT JOB, IT WILL DO THAT JOB and, IT DOES DO THAT JOB, except PD14 will crash randomly sitting there doing nothing while not even processing anything. PD14 will crash randomly after a couple of rendered productions after being patched to 2302. I don't know why you can't understand that there is an issue with Powerdirector.

I really can't make it any clearer than that. The question is is Cyberlink going to fix it or not? Are they even acknowledging a problem or are they blaming it on the end user like you are.

Yep, I'm blaming you the inexperienced end user for creating your issue.
As for CyberLink fixing issues that they can replicate - that's their call.
Best of luck, I have editing to do on a system that doesn't crash, that doesn't get overloaded with bloated files.
Dafydd

Quote: Yep, I'm blaming you the inexperienced end user for creating your issue.
As for CyberLink fixing issues that they can replicate - that's their call.
Best of luck, I have editing to do on a system that doesn't crash, that doesn't get overloaded with bloated files.
Dafydd

Thanks for verifying the prediction. Again, it's PD14 software*, not system that is crashing. Everything else runs like a charm here.



P.S. 11000 bit does the same exact thing. So your theory of over bloat is busted.

"Bust"??? Not really, as none of us here have the same issue as you do. Nobody has yet replicated your issue - strange that isn't it.

I guess you're still trying to render those avi files you initially captured, not sure as you haven't mentioned it. Data transfer processing of bloated files can be problematic and can cause programs to hang.
RE:
Video Bit rate : 584 Mbps
Audio Bit rate : 1 536 Kbps
2minutes 2 seconds = File size : 8.35 GiB
These are really OTT screen capture rates.

As I said before, best of luck with whatever you're trying to achieve, here's the CyberLink Support link.
http://www.cyberlink.com/support/index.html
Bye
Dafydd

Quote: "Bust"??? Not really, as none of us here have the same issue as you do. Nobody has yet replicated your issue - strange that isn't it.

I guess you're still trying to render those avi files you initially captured, not sure as you haven't mentioned it. Data transfer processing of bloated files can be problematic and can cause programs to hang.
RE:
Video Bit rate : 584 Mbps
Audio Bit rate : 1 536 Kbps
2minutes 2 seconds = File size : 8.35 GiB
These are really OTT screen capture rates.

As I said before, best of luck with whatever you're trying to achieve, here's the CyberLink Support link.
http://www.cyberlink.com/support/index.html
Bye
Dafydd

PD14 v2303 is problematic. FRAPS AVI is irrelevant at this point, 2303 has random crashes with any files loaded. This forum is peppered with the same conclusion as I have determined with the software who have the same issue of PD crashin.

I still have some more Frap related tests to do that may be beneficial to others so please leave this thread open.





Thanks for your time none the less,

T.M.