Quote: I loaded a 720p video and just edited it out. I added a picture to the timeline and then PD10 just fell over itself and just lagged. I managed to save and exit but now when i load the project it just kills PD10.
The Picture is 1680x1050 and a .png image (With no transparency)
Now I'm stuck with the project being unable to do anything, i can remove the picture and save it but it just won't recover. Even if i restart my computer. I can still edit other things, it's just the project doesn't want to work... any solutions other then starting again?

If you would reduce the image size of your PNG to 1920x1080 or as near that Aspect ratio (16:9) you can get, that may take the load off of PD 10.

If your project file is corrupted, you can either look for a uncorrupted pds in the Autosave folder or start a fresh project.
If you would Save As your project each time you make changes.

Give it a unique name each time Project1, Project2, ProjectN, Etc.
You can go back to a previous version.

You might check your preview resoultion, set it to High or Normal.
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:

Quote: I loaded a 720p video and just edited it out. I added a picture to the timeline and then PD10 just fell over itself and just lagged. I managed to save and exit but now when i load the project it just kills PD10.
The Picture is 1680x1050 and a .png image (With no transparency)
Now I'm stuck with the project being unable to do anything, i can remove the picture and save it but it just won't recover. Even if i restart my computer. I can still edit other things, it's just the project doesn't want to work... any solutions other then starting again?

If you would reduce the image size of your PNG to 1920x1080 or as near that Aspect ratio (16:9) you can get, that may take the load off of PD 10.

If your project file is corrupted, you can either look for a uncorrupted pds in the Autosave folder or start a fresh project.
If you would Save As your project each time you make changes.

Give it a unique name each time Project1, Project2, ProjectN, Etc.
You can go back to a previous version.

You might check your preview resoultion, set it to High or Normal.

Can you PLEASE read.

First of, The image is smaller then 1920x1080, it is 1680x1050 (16:10) as said before. However, it has been removed and the problem exists so that won't fix it.

Second, where is the Autosave folder?
I am NOT starting a fresh project, i've sent too much time on this one just to have to throw it away because of an image.
Well, I don't expect to add a picture and have my whole project die on me like that, thus this was the only copy.

The preview resolution* is set to the lowest it will go. This isn't the problem as i was able to view it fine before the picture was added.

Edit: Manged to get to the render step and recover the project HOWEVER!
You need to fix the pictures... i changed the Aspect ratio to 16:9 (1280x720) added it to the second layer and went to preview it and couldn't do it (green preview)

Quote: First of, The image is smaller then 1920x1080, it is 1680x1050 (16:10) as said before. However, it has been removed and the problem exists so that won't fix it.
Second, where is the Autosave folder?

You are correct, I misread the image size.

AutoSave is located in a hidden folder. (You can move it to a folder of your choice, change in Preferences).
C:\Users\UserName\AppData\Roaming\CyberLink\PowerDirector\10.0\AutoSave

You may need to change your Windows Explorer view to show Hidden folders.

Edit: Manged to get to the render step and recover the project HOWEVER!
You need to fix the pictures... i changed the Aspect ratio to 16:9 (1280x720) added it to the second layer and went to preview it and couldn't do it (green preview)

A green preview screen is an indication of a Video Card Driver problem. Check with the manufacturer for the latest Driver.

Be sure you have the latest Patch for PD 10. One of the patches fixed the Nvidia rendering problem.
http://www.cyberlink.com/support/powerdirector-ultra/patches_en_US.html

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:

Quote: First of, The image is smaller then 1920x1080, it is 1680x1050 (16:10) as said before. However, it has been removed and the problem exists so that won't fix it.
Second, where is the Autosave folder?

You are correct, I misread the image size.

AutoSave is located in a hidden folder. (You can move it to a folder of your choice, change in Preferences).
C:\Users\UserName\AppData\Roaming\CyberLink\PowerDirector\10.0\AutoSave

You may need to change your Windows Explorer view to show Hidden folders.

Edit: Manged to get to the render step and recover the project HOWEVER!
You need to fix the pictures... i changed the Aspect ratio to 16:9 (1280x720) added it to the second layer and went to preview it and couldn't do it (green preview)

A green preview screen is an indication of a Video Card Driver problem. Check with the manufacturer for the latest Driver.

Be sure you have the latest Patch for PD 10. One of the patches fixed the Nvidia rendering problem.
http://www.cyberlink.com/support/powerdirector-ultra/patches_en_US.html

I spent months trying to fix the green screen problem and now, it's back!
The problem is NOT a Video Card Driver problem, I have the latest and newest possible versions as they haven't changed for the past 6 months (or near enough) and considering this problem was temporarily fixed until now, this cannot be the cause.
Furthermore, installing the latest patch has done nothing along the lines of fixing this issue, i have got an Intel HD 4000 so that fix won't apply.

Here is my DxDiag:
http://pastebin.com/ikxByC97

Can we please get this issue resolved asap. I am currently needing to upload a video project to YouTube and i cannot do that if none of these video editors work... well, i can still edit and all that but without a preview and with all the freezing that has now started to happen it is becoming near impossible to be able to edit.

Quote: Here is my DxDiag:
http://pastebin.com/ikxByC97

I have a question,
I have read many Dxdiag.txt files on the Intel i7 and HD graphics, Many have dedicated memory of 64 Megabytes, I notice yours has 32 Megabytes of dedicated memory.

My question: Is that configurable in BIOS?

Intel does have updates for the HD graphics. Have you tried the Intel site for downloads?

https://downloadcenter.intel.com/default.aspx

The Preview in Powerdirector is directly dependant on the Graphics Driver. If the driver fails, so does the Preview. The most common failure is a Green Screen. Or pauses in the video.

A Video Editor is directly dependant on the whole computer system, if any part fails, it shows in the result of the Produced Video.
Nothing puts as much stress on a computer as editing High definition Video.

If I was trying to find the cause of your problems, I would get a set of bench mark and stress test software and run the tests multiple times to find out where the weak points are in your computer system.

You can find that sofware online and usually for free.

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:

Quote: Here is my DxDiag:
http://pastebin.com/ikxByC97

I have a question,
I have read many Dxdiag.txt files on the Intel i7 and HD graphics, Many have dedicated memory of 64 Megabytes, I notice yours has 32 Megabytes of dedicated memory.

My question: Is that configurable in BIOS?

Intel does have updates for the HD graphics. Have you tried the Intel site for downloads?

https://downloadcenter.intel.com/default.aspx

The Preview in Powerdirector is directly dependant on the Graphics Driver. If the driver fails, so does the Preview. The most common failure is a Green Screen. Or pauses in the video.

A Video Editor is directly dependant on the whole computer system, if any part fails, it shows in the result of the Produced Video.
Nothing puts as much stress on a computer as editing High definition Video.

If I was trying to find the cause of your problems, I would get a set of bench mark and stress test software and run the tests multiple times to find out where the weak points are in your computer system.

You can find that sofware online and usually for free.

First and foremost, i have an Intel i5 and HD graphics, and although it's base amount of dedicated memory is 32mb it is auto scaling up to 1.7gb. This is unchangeable in the bios.

I will download the update from Intel then, HP haven't updated them in a while... I'll post here once that is done.

But the preview works when nothing is in the timeline, when content is added to the timeline the whole thing dies... which it hasn't done for the past 3 months since i fix this issue last time (i say fixed i mean it fixed itself somehow) And for this problem to re-occur just because of adding an image is odd... It makes me thing that either PD10 has corrupted a codec only it uses or that a config files has changed... or something alone those lines as it work 100% fine in the months between the occurrences of this problem...

If updating my GPU drivers don't fix it i will try the codecs... which one's do i need to reinstall?

Quote: First and foremost, i have an Intel i5 and HD graphics, and although it's base amount of dedicated memory is 32mb it is auto scaling up to 1.7gb. This is unchangeable in the bios.

I will download the update from Intel then, HP haven't updated them in a while... I'll post here once that is done.

But the preview works when nothing is in the timeline, when content is added to the timeline the whole thing dies... which it hasn't done for the past 3 months since i fix this issue last time (i say fixed i mean it fixed itself somehow) And for this problem to re-occur just because of adding an image is odd... It makes me thing that either PD10 has corrupted a codec only it uses or that a config files has changed... or something alone those lines as it work 100% fine in the months between the occurrences of this problem...

If updating my GPU drivers don't fix it i will try the codecs... which one's do i need to reinstall?

The i5 and i7 both have HD graphics, some models have HD 3000 some models have HD 4000 graphics.

I have no idea why some have 64 MB allocated and some have 32 MB allocated.

To eliminate any corrupted Codec in Powerdirector, you would have to uninstall, delete the Powerdirector program folder, then re-install powerdirector.

The Codecs used on the timeline are built into the program. There is a different set of Codecs used in the media library.

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:

Quote: First and foremost, i have an Intel i5 and HD graphics, and although it's base amount of dedicated memory is 32mb it is auto scaling up to 1.7gb. This is unchangeable in the bios.

I will download the update from Intel then, HP haven't updated them in a while... I'll post here once that is done.

But the preview works when nothing is in the timeline, when content is added to the timeline the whole thing dies... which it hasn't done for the past 3 months since i fix this issue last time (i say fixed i mean it fixed itself somehow) And for this problem to re-occur just because of adding an image is odd... It makes me thing that either PD10 has corrupted a codec only it uses or that a config files has changed... or something alone those lines as it work 100% fine in the months between the occurrences of this problem...

If updating my GPU drivers don't fix it i will try the codecs... which one's do i need to reinstall?

The i5 and i7 both have HD graphics, some models have HD 3000 some models have HD 4000 graphics.

I have no idea why some have 64 MB allocated and some have 32 MB allocated.

To eliminate any corrupted Codec in Powerdirector, you would have to uninstall, delete the Powerdirector program folder, then re-install powerdirector.

The Codecs used on the timeline are built into the program. There is a different set of Codecs used in the media library.

In which case I'll uninstall and reinstall... but it still makes no sense why this problem has just started because of such a stupid cause...