|
|
Just to follow up on this, no crashes todate which I am happy about.
I think the solution was to remove the temp files and I think it was linked to temp files left over from PD10 when I upgraded to PD11.
Perhaps worth noting for anyone else upgrading from PD10 with the software download purchased PD11. 
|
|
|
Hi Dafydd
Liek I mentioned above, I managed to get it done without a crash last night, so no worries. http://www.youtube.com/watch?v=xOlDQE5sfAs
I've attached a clip of 720/100fps similar to that used in both the successful and unsucessful projects....
I'll keep an eye on things to see if it crashs again. Thanks for the help thus far
|
|
|
|
OK, my first observation.
1. Switch OFF shadow edit files, you don't need them and they are wasting your resources. Find all the shadow files and delete them, see 1jpg.
2. Observation: If you use shadow edit files they MUST generate before you start editing - causes problems if the aren't.
Your system doesn't need Shadow File generation.
Shaddow files are now turned off.
3. Preferences/Confirmation - see options/image.
The two in the red boxes are unticked.
4. Preference/General - see options/image.
5. Preferences/Project - Browse if you want to change, mine is pointed to C drive/address
6. what's your Preferences/Hardware Acceleration selections - not sure they would have any impact.
See attached images.
Thanks for the images. I wasn't sure the Drive was SSD but suspected it was. Still curious to know what spare capacity you have after removing unwanted data.
21M! Not a huge reduction.
More snow today, looking much better out there, I'm planning on working from home for the next few days...
|
|
|
OK, I did some digging around (easier to do without yesterdays red mist! )
PD is storing its files in a roaming directory on my D drive.
D:\Users\Jason.Jason-PC\AppData\Roaming\CyberLink\
And in the PowerDirector\11.0\AutoSave directory I was able to recover one version of the project, so attached is the screenshot you asked for The autosave file after this one crashes PD11 (its 10mins or so later on in the day). Its irrelevant now as I have re-mastered the video when I thought the original work was all lost... It would be interesting to see if I can get this version of the autosave to crash as often as it was yesterday!
|
|
|
Hi Dafydd,
I cant increase the C: drive as its a 120GB SSD with Win7 64bit on it, so short of not having an OS, I am a bit stuck there. All my programme files / user directory locations are the D drive (with 169GB of free space).
I cant take a snapshot of the workspace with the project insitu because every time I try and load the project, PD11 crashes.
I've attached a screen capture of the subsequent project I finished after the one I have had issues with... This one uses the same files and suffered no crashes in its creation....
Is there a text config file for PD11 which shows the paths it is using for the cache etc?
|
|
|
Hi Jim - I had some success last night I had cleared the temp files and it seemed to let me get through 2 hours of editing without a crash!.
Looking at the manual delete temp files, they are being stored on the D drive (which is where the user directories are located)
All references to file locations fields are pointing to the D drive in the settings dialog.
I dont think there is a way to attach the PD settings as a text file is there?
|
|
|
|
Thanks Jim, I checked the C drive, but surely 35Gb of free space (out of 120gb) should be enough shouldnt it?
|
|
|
I have been experiencing crashes on PD11 since I upgraded from PD10 about 2 weeks ago.
Todays 17 in a row crash session has resulted in a project file which crashes PD11 as soon as it trys to open the file (other project files are OK). Its 5 hours of lost work, so I am trying to keep calm!
None of the crashes were fatal to the PC, they all resulted in an exit to teh desktop and the cyberlink crash report tool.
There seems to be no pattern to the crashes other than once they start they continue as though there is a memory leak, but if I reboot and restart editing this doesnt resolve the issue. It could be when I am adjusting audio levels, adding transistions or moving clips around the timeline... no particular pattern.
I rolled back my gfx driver and cleaned up all cache files to no avail.
I'm running PD 11 Ultimate 11.0.0.2418 on Win 7 64bit. Video files today were a mixture of gopro 720/100fps and pal dvr footage. but prior to that (with slightly less crashes) they were 720/25fps and PAL dvr footage.
Hopefully the attached dxdiag is of use.
Previous projects open fine but todays seems to initiate a crash as soon as it has loaded.
I'm off down the pub for a beer before I create a monitor shaped hole in the window!
Any thoughts on a resolution would be most appreciated.
|
|
|
Hi Kath, Thanks for finding this solution!
I have a similar problem, if I have a lot of splits but want to apply something to the whole track, at present I have to apply it to each individual split section at a time. I can't select all and then apply. (eg, change the volume across the whole video track 1).
Yes you can group them, this is useful for if you want to move the whole lot in one go, but still wont let you alter the parameters for all the split sections on the track.
I have tried what you suggest Kath and it works, hover close to the right edge so the mouse pointer turns to a film reel with 2 arrows and then drag as described to the end of all the footage you wish to join, select overwrite and bingo!
Thanks Kath
Cheers
Jason
|
|
|
So not too much to report at present, a couple of emails have been exchanged, the usual passing of information to assist in understanding the issue.
I did upload a short clip for them to see the proceses
https://vimeo.com/45867582
|
|
|
I have had a prompt responce back, not to dissimilar to what we have alread discussed on here, account level related (basic account only allowing 1 HD movie per week etc). I still dont think this to be the issue, I am well under my 500MB per week quota and its not a HD movie, and more importantly this is before the file is produced, so there is no info to give about if the file is HD, SD or its size.
I have provided my DXDiag details and also a step by step to reproduce the issue. The good news is that in producing the step-by-step instructions, I have managed to narrow the internet temp file down to one particular token file which if deleted solves the problem. Problem is that it needs deleting each time you want to upload to Vimeo!
Thanks Chetan,
Following through your recommendations in order:
My 'basic' vimeo account is 500MB/week, in the last 3 weeks I have uploaded 1x 250MB HD video and this error was found whilst trying to upload a 90Mb SD video. Thus I am within the account limitations.
In relation to your points:
1. Tried
2. Latest stable NVidia driver is installed (see attached dxdiag file)
3. Latest DirectX is installed (see attached dxdiag file)
4. See point 2 and attached DXDiag file.
5. Currently set to 8GB
I would note that the error I refer to happens *before* any video has been rendered and is the stage where the application to upload direct from PD to Vimeo is being authorised. There is therefore no file size information at that stage to pass on to Vimeo.
As previously informed, if I delete all temporary internet files related to Vimeo and re-try it then works for that one try, subsequent attempts require the internet files to be deleted again to work.
To recreate the issue:
1. Create a video in standard definition.
2. Go to produce, select Online/Vimeo.
3. Select standard quality
4. Vimeo Authorisation screen pops up, select authorise
5. Log in to vimeo when prompted
6. Select 'Allow' when prompted to allow PowerDirector to access your account.
7. PD will now start to produce the movie and then proceed to upload the movie.
8. Now retry the operation (can be same video file or a new one) - repeat points 1 through 4 inclusive.
9. Pop up screen now shows "Uh oh, something went wrong" message.
10. On the pop-up window, click settings shows a script error "https://secure-a.vimeocdn.com/js_v6_opt/vimeo/controllers/user_settings.min.js?f216206"
11. Cancel script error, note that the PD uploader is still authorised.
12. Go to IE, internet options, browsing history settings, view files.
13. Delete vimeo.com token file "http://vimeo.com/oauth/request_token"
14. Repeat steps 2 through 7 inclusive, video will now upload to Vimeo.
15. Try and repeat step 14 will result in another error, repeat step 13 resolves the error untill the next upload.
So this issue is repeatable as shown above.
Looking forward to your comments.
|
|
|
Yes - will certainly share.
The Youtube one works fine, but I prefer Vimeo sometimes
Will comment further when I get a responce
|
|
|
Quote:
Quote:
I wonder why Vimeo allowed me to upload 2 HD videos through PD earlier today?
I don't know. The above image was a screen capture of Vimeo's Terms Of Service page, captured about 45 minutes ago. So I just thought I'd throw it out there, in case it may be part of the equation, with regard to jiberjaber's issue.
Maybe you've found a way (by cleaning temp files?), to beat the system. 
But uploading to my Vimeo Basic account (outside of PD), has never allowed me to upload more than one HD (1920x1080 / 1280x720) video, within a 7 day time period. Which meant that my glaring "typo" had to remain there for a whole week. 
Yep - fully agree with what you say about the account limits, but the first time I came across this issue was with a SD recording after some time from uploading the last one. We are at the part of the process where the error occurs which is before Vimeo actually knows what video you are going to upload as it hasnt been rendered at the point where you authorise the upload tool within the Vimeo account.
Though I dont want to rule out the account limits 100%, I think they might be a red-herring here
I've raised a ticket (Question ID = CS001163260) so will see what comes of it.
|
|
|
Its a Basic account, I also had the same thoughts but it isnt the account limit thats the problem, if I clear the temp files out, I can upload. (managed an SD video last night)
The problem is independant of the type of video file (HD or not).
I think it is either a change to the VIMEO API or a file permissions issue as I noted that if I go to the settings section through the PD10 pop up browser windo, I get a script error. (only noticed on re-trying after posting this thread).
|
|
|
No support ticket yet, I wanted to confirm it wasnt a permissions thing or some such issue... will raise on today
|
|
|
I appear to have an issue uploading to Vimeo direct from PD10Ultra. (Win7 64bit / IE9)
When I produce a movie to upload direct o Vimeo, it displays the pop-up screen for me to authorise the 'app' then starts the production and upload.
However, if I try again, I keep getting an error
If I go to my settings page I can see that the app is authorised already.
The only way I am able to get it to work is to go in to my temp internet files and delete all references to vimeo that reside in there... I am then prompted for my log in to vimeo rather than the error screen and it all works for the one upload!
Any idea how to solve this, at the moment I am limited to uploading to Youtube but can't get anything on vimeo without a load of hassel! 
Thanks in advance.
|
