|
|
Hi,
I have had experience of this problem before IMO its not specifically related to PD8. It's to do with the Windows Installation Manager. I suggest you do the clean "uninstall process" described by Dafydd, paying particular attention to clearing out all bits of Powerdirector from the Registry and also any "odd" DLL's it has left behind in its old folders. If you then do a clean install you should be OK.
PD8 gets "blamed" for a lot of things its not really guilty of - it is however a very demading but worthwhile application.
Good Luck.
Don
|
|
|
Hi Mike,
Processing "raw" video does take a lot of horsepower. One of the solutions I used in the past was to "preprocess' the video clips before putting them in a movie - its painful and longwinded but it might get around your problem - I will see if I can find the original posting on this in the forum
REgards,
Don
|
|
|
Your very welcome.
Don
|
|
|
Hi,
Did you install the contents pack??
Don
|
|
|
Hi Mike,
If your version is 3022 you already have the latest version of PD8. Regarding driver updates, whilst your system maybe new it could have been sitting in Dells warehouse for a while AND not have the latest drivers on board. My wife has a DELL and I think there is a facility where it will auto update its drivers. If you go on the DELL site and put in your service code Dell will tell you whether you have the current drivers or not.
I have actually used PD8 on my media PC (Dual Core Atom 330) and it will work though it is very very slow.
Good Luck,
Don D
|
|
|
Hi Mike,
Not sure I can help too much on this - I have very little first hand experience of the onboard graphics, however checking on Intels site I note that you do not appear to have the latest driver set for the Mobile 4 chipset. Have you ched on the DELL site for driver update ( I did and there seem to be some graphics driver updates). Yours is a fairly modest system and might be struggling with PD8 - it is a bit resouce hungry. If you resrta the playback from the time line does it clear up and also if you look in the Task Manger under processes (click on CPU) is there anything using lots of CPU resource?
And lastly when you updated PD8 did you restart the system after the update was completed?
Don
|
|
|
Hi Lee,
I downloaded your 00018.mts file and played it with no problem with PD8 on my system. because I am set up to process PAL standard and your file was NTSC PD8 automatically converted it - it played like a treat. Looking at your DXdiag file I see your machine has onboard Intel G45/43 graphics. Your driver is out of date - 6.14.0010.4977. The latest drive on the INTEL site is 6.14.0010.5284. The Intel site talks about problems with high res on the older drivers. I should update the drivers.
Hope this helps,
Don
|
|
|
Hi Melanie, you are using a very old version of PD8 - Version 1930. It had lots of "features" relating to disc burning. I suggest you upgrade to 3022 - you should then be OK.
Don
|
|
|
Paul,
A number of us run I7 with 64 bit win7 - its fine. I am unable to access your DXdiag, but could I ask why you rebuilt your system?
My thoughts on this would be as follows (based on this really (now) being a new system):
1. Are all the drivers OK (I am including the system borad drivers)
2. Did you do an absolutely clean install of PD8 that is get rid of any old Cyberlink folders/PD8 dll etc?
I had problems with PD8, if I install it AFTER I have changed the Video drivers. I always have to reinstall the Nvidia drivers
(I use a 4870 GPU)
Version 3022 in my experience is pretty solid. I now very rarely get crashes.
I agree with your comments regarding first line support - thay can be "difficult" ![]()
I am very wary of all code that messes with the registry (cccleaner, regmechanic etc.)
they have caused me terrible problems in the past by deleting keys that were needed!
Good Luck,
Don
|
|
|
Hi Darren,
What kind of files are you processing? 1GB is certainly a bit lean BUT your system would appear to meet Cyberlink's requirements spec as long as you are NOT processing HD.
Can you please say what your system spec is - the bios revision doesn't mean much unless we know what the PC/motherboard is and what the graphics card is. Also what have you got installed and what was active when it crashed. What does the event log say about the lack of system resource?
Sorry to be a bit nerdy BUT if we don't have the detail you will simply get opinions and peoples thoughts that might or might not help.
Don Maybe you could let us see the dxdiag?
Don
|
|
|
Hi Darren,
Could you please tell us what your system configuration is and what version of windows you are using: This link is usefful http://msdn.microsoft.com/en-us/library/aa366778%28VS.85%29.aspx#physical_memory_limits_windows_xp and a google search on ": Windows XP 3GB Startup switch "
32 bit Windows can use more than 2GB for Apps. However I suspect that this has nothing to do with it. If you could do a DXdiag for us AND read Dafydd's entry on what info we need to help. Where all flying blind just now. I am using PD8 Ultra 3022, with absolutely NO problems to process HD clips from my Panasonic (but I DON'T use PD8 to do the capture of the M2ts files from the Camera).
One of the updates to PD8 did change some of the program headers to enable it to address >2GB can't remember which.
Don
|
|
|
Hi Tim,,
No evidence provided BUT (IMO) I have not personally seen any situation where PD8 will damage a disc. It is of course possible that by the very nature of the work the PC is being asked to do it is uncovering a weakness in your system. What version of windows are you using and is the system up to date driver and BIOS wise. Please follow the advice given in the links in Dafydd entry.
Regards,
Don
|
|
|
Hi Jerry, unfortunately you are not giving us anything to work on. We don't know your system, what you were running etc etc.
This is a very dramatic - if you could do the "please read" from Dafydd someone should be able to help
Don
|
|
|
The following experience may be useful to anyone new using PD8. I recently reinstalled PD8, and being a masochist I decided I would do it by going back to version 2508 then updating this to 2704 and then 3022. Prior to carrying out the reinstall the system and registry were cleared of any reference to Cyberlink and ALL its products (see Dafydd entry on this). Having completed the install and restarted the system I configured PD8 with NO shadow files OR Rich video processing.
I have two monitors on my system and I had problems with PD8 locking up when introducing the second monitor as a (High Resolution) preview screen (PD8 would NOT pick up the second screen, whislt Sony Vegas would!) or if I used a single monitor, whilst it didn't crash the preview stuttered and paused.
The solution to the problem was to delete the ATI drtivers (release 10.6) restart the sytem and then reinstall the ATI drivers (plus AVIVO) from scratch. I then had to restart the system again and now it all works superbly.
I have also tried a complete download of 3022 (courtesy of Tech support) and their doesn't appear to be any difference btween the patched versions and the complete versions, on the limited testing I have carried out.
What I find particularly interesting is the need (in my case) to have to completely reinstall the ATI Video drivers/software after an install of PD8.
I hope someone finds the above useful.
Don
|
|
|
Hi me agin!,
Clicking on support tickets will only show you the history of your support requests.
Don
|
|
|
Hi Alan,
Use "Contact Technical Support" Depending on how you fill in the proforma it presents you with - you will get pointed to the right place - BUT make sure you have your licence number.
Having said the above I am finding it impossible to get responses from either Tech Support OR Customer support. I get acknowledgements of my submissions but no resolution responses - sad really.
Don
|
|
|
Hi Richard,
Sorry to hear about your acident, I know PC's can be frustrating but geting into a confrontati!on wth tecnology would
hurt your head! - Sorry bad taste - I do hope you are now fully OK. Good news about the PC, but the journey to reslution was painful. Still glad you are now good on all fronts - happy editing.
Regards,
Don
|
|
|
Hi, How is this problem going - if it is fixed I would really like to know what happened and what the solution was.
Don
|
|
|
Hi Richard,
from your response i deduce that whilst this runs everything (and has done for 5 months) - it has NEVER actually run PD8 without problems. I understand you are using "safe" BIOS settings but that is not the same as a) slowing the machine clock b) closing Cores down. I note you are also running SSD (very nice and very fast!).
The only problem i did have at one time was with (at the time) a "latest ATI driver" on my 4870 (not crossfire) reverting back a version fixed it, and then ATI issued a further update.
I also note that you can get PD8 to start with no problem, so its only when you load the time line with your *.mov files that you have issues. Do you have any other input media you can try.
Good Luck,
Don
|
|
|
Hi Richard, This does sound very hairy. Could you please clarify the following for me:
1. Has this system EVER run PD8 without problems?
2. Does simply opening PD8 cause the crashes?
I am a great follower of the "something has changed" approach to diagnosis - DXdiag doesn't seem to indicate anything nasty. The only thing I have found with PD8 is that it really does thrash hardware so any memory/hardware "weakness" will be highlighted.
I too have an I7 (only a 920) and at one time I used to overclock it with PD8 up to 3.8GH, now if I do that it will crash but only with PD8. Have you tried slowing the system clock and/or running fewer cores.
I personally think this is a sytem shortfall being exposed by PD8, but with out getting up close and personal and some meaningful diagnostics I am at a complete loss - sorry, but good luck with the problem.
Regards,
Don
|
|
|
Hi again - I don't use shadow editing at all but I do use the ATI AVIVO rendering engine.
Could you please tell me what voltage settings you are using to overclock your CPU - since I downloaded the latest video driver update I can't get my system to go above 3.17Gh
Thank you,
Don
|
