Am able to duplicate problem I had on previous machine running VideoStudio 8. Have new machine (Windows XP, core2, 2Gig memory, 800G disk dedicated to video postprocessing) and upgraded to VS 10 with service pack 1.
Did 11 movies of 30-90 minutes on new machine no error outputting .avi file. movie today I outputted and then realized I hadn't muted a couple of slices so I hit escape, muted slices and then output as .avi and gave new file name. crash at 99%. movie is 42 minutes. on my old machine only way around was to output in shorter segments. Seems like VS10 is having a problem closing the file but I don't know why.
I am technically savy. Run | %temp% and deleted all temporary files after restart. renamed output .avi file and ran again, same thing, crash on final write to disk at 99%. Very frustrating. Ideas appreciated.
crash crash crash
Moderator: Ken Berry
- Ron P.
- Advisor
- Posts: 12002
- Joined: Tue May 10, 2005 12:45 am
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Hewlett-Packard 2AF3 1.0
- processor: 3.40 gigahertz Intel Core i7-4770
- ram: 16GB
- Video Card: NVIDIA GeForce GTX 645
- sound_card: NVIDIA High Definition Audio
- Hard_Drive_Capacity: 4TB
- Monitor/Display Make & Model: 1-HP 27" IPS, 1-Sanyo 21" TV/Monitor
- Corel programs: VS5,8.9,10-X5,PSP9-X8,CDGS-9,X4,Painter
- Location: Kansas, USA
Are you outputting to DV or uncompressed AVI, or some other codec (divx, mov) ?Did 11 movies of 30-90 minutes on new machine no error outputting .avi file. movie today I outputted and then realized I hadn't muted a couple of slices so I hit escape, muted slices and then output as .avi and gave new file name. crash at 99%. movie is 42 minutes. on my old machine only way around was to output in shorter segments. Seems like VS10 is having a problem closing the file but I don't know why.
Ron Petersen, Web Board Administrator
hi vidman - simple .avi output. i did notice since i posted that output folder and folders upstream were read only. very odd as i have changed no security settings and confirmed default output directory exists.
i am under production deadline so am cutting 10 minute segments and will try rerender entire 40 minutes tonight/tomorrow and update post. something is amiss though as have been using for production since december '06 with no problems. it was killing the output and then reoutputting that started this machine tumbling as happened on other machine I used to use for production. input appreciated - steve
i am under production deadline so am cutting 10 minute segments and will try rerender entire 40 minutes tonight/tomorrow and update post. something is amiss though as have been using for production since december '06 with no problems. it was killing the output and then reoutputting that started this machine tumbling as happened on other machine I used to use for production. input appreciated - steve
-
sjj1805
- Posts: 14383
- Joined: Wed Jan 26, 2005 7:20 am
- System_Drive: C
- 32bit or 64bit: 32 Bit
- motherboard: Equium P200-178
- processor: Intel Pentium Dual-Core Processor T2080
- ram: 2 GB
- Video Card: Intel 945 Express
- sound_card: Intel GMA 950
- Hard_Drive_Capacity: 1160 GB
- Location: Birmingham UK
What is your final output destination - internet or DVD disc or somewhere else?
You could try outputting to the format required by the final destination rather than creating an avi file. If you're creating a DVD disc then render to MPEG2 using either PAL DVD or NTSC DVD.
If some partly rendered files are still hovering about somewhere on your system and causing the error, changing the output format might well clear it.
You could try outputting to the format required by the final destination rather than creating an avi file. If you're creating a DVD disc then render to MPEG2 using either PAL DVD or NTSC DVD.
If some partly rendered files are still hovering about somewhere on your system and causing the error, changing the output format might well clear it.
output
no, I am not changing my workflow after almost three years using VS. I go straight from .avi to windows media encoder set at best quality. nothing really 'hovers about' my systems lol. I sell thousands of clips a year and pretty much have process down. other production houses laugh but I stick with VideoStudio and keep things simple. thanks for suggestion though. I suspect some sort of Windows permission problem when VS barfs. cuts fine in 10 minute increments so it seems a final write problem or file closure over X mbs.
-
sjj1805
- Posts: 14383
- Joined: Wed Jan 26, 2005 7:20 am
- System_Drive: C
- 32bit or 64bit: 32 Bit
- motherboard: Equium P200-178
- processor: Intel Pentium Dual-Core Processor T2080
- ram: 2 GB
- Video Card: Intel 945 Express
- sound_card: Intel GMA 950
- Hard_Drive_Capacity: 1160 GB
- Location: Birmingham UK
No I'm not asking you to change your tried and tested workflow.
What I am suggesting is that you got this particular error after you killed the process whilst it was still in progress.
You have tried clearing anything you have managed to find such as temporary files etc. but still have the problem. I am suggesting you try a one off by creating your video in a different format to 'clear the buffers' as it were. Providing you save your vsp file you can then go back and try again with your tried and trusted method.
It is important that when you find a method that works for you that you stick to it.
What I am suggesting is that you got this particular error after you killed the process whilst it was still in progress.
You have tried clearing anything you have managed to find such as temporary files etc. but still have the problem. I am suggesting you try a one off by creating your video in a different format to 'clear the buffers' as it were. Providing you save your vsp file you can then go back and try again with your tried and trusted method.
It is important that when you find a method that works for you that you stick to it.
