I am trying to "create a new video file" from 4 clips which together come to 20GB. Each time I set it up an error message comes back saying "disc too full" - yet I have 165GB of free space.
My capture is from an analogue Hi8 source converted through DV.avi through a Canopus ADC55 A>D converter.
In the past I have captured from this source and device before with great results BUT they where whole clips - this is the first time I have tried editing and creating a new video file. My format is PAL.
I have re-loaded VS9 twice and re-captured twice to no avail.
What gives - any ideas ?
thanks Vince
165GB and VS says "not enough space" !
Moderator: Ken Berry
-
Vincej
-
heinz-oz
You will also find that you will get the same effect after a while with VS 11, unless you changed the virtual memory settings in your preferences. It worked now because VS 11 has set a new location for your temp files and virtual memory. You need to make your own folder, better still, a separate drive for these files and keep this location clean and defragged. If it is big enough you won't have such problems.
Just because you have a biggish HDD doesn't mean that VS can automatically use all the free space. How much free space do you have and where does VS keep the working folder? What are your preference settings?
Just because you have a biggish HDD doesn't mean that VS can automatically use all the free space. How much free space do you have and where does VS keep the working folder? What are your preference settings?
-
Phil S
- Posts: 66
- Joined: Fri Nov 18, 2005 10:34 am
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Gigabyte GA-EX58-UD3R v1.6
- processor: QuadCore Intel Core i7 2933 MHz
- ram: 6gb
- Video Card: NVIDIA GeForce 210
- sound_card: Realtek High Definition Audio
- Hard_Drive_Capacity: 1640gb
- Location: London
I had the same thing happen, What annoyed me was that VS11 spent nearly an hour rendering my file and then gave me this message - not enough disk space when I knew I had at least 120Gig free. You are then stuck and have to start again. Rather poor I thought. Never had it happen with VS10.
Heinz-Oz - could you be a little more specific on what to set up to prevent this happening again. I already have working folders set up. With regard to virtual memory, are you talking about Windows preferences or VS preferences. What should it be set at?
Thanks
Heinz-Oz - could you be a little more specific on what to set up to prevent this happening again. I already have working folders set up. With regard to virtual memory, are you talking about Windows preferences or VS preferences. What should it be set at?
Thanks
-
Vincej
-
heinz-oz
I don't have VS installed on this machine and cannot be more specific. Just started my working day
In VS, under the "File" menu you will find a setting for preferences. There you can set the way VS deals with virtual memory and where the working folder resides. Make sure there are not restrictions on either.
In Win XP (don't know about Vista) in Control Panel>System>Advanced>Performance>Advanced>Virtual memory you should set your swapfile to be about 2 to 2.5 times physical RAM memory. To do that, select custom and set the minimum and maximum size to the same value, click set and you are done.
Provided there is enough contiguous file space on your HDD which hosts your swap file and/or the working folder for VS, this error should not come up again.
In VS, under the "File" menu you will find a setting for preferences. There you can set the way VS deals with virtual memory and where the working folder resides. Make sure there are not restrictions on either.
In Win XP (don't know about Vista) in Control Panel>System>Advanced>Performance>Advanced>Virtual memory you should set your swapfile to be about 2 to 2.5 times physical RAM memory. To do that, select custom and set the minimum and maximum size to the same value, click set and you are done.
Provided there is enough contiguous file space on your HDD which hosts your swap file and/or the working folder for VS, this error should not come up again.
-
BrianCee
Vincej - when you say you have 165Gb free on your hard drive that is storage space not memory.
Memory basically comes in two types - real - which is your RAM size - and 'virtual' which although it is on your hard disk is not directly accessible to the user - it is used by programmes like VideoStudio to carry out the actions you have requested.
The setting for virtual memory do have to be correct though for the applications you are running and any video editor - not just VideoStudio - needs a bit more 'virtual' memory than basic computing.
just follow the instructions already given to you by Heinz.
Memory basically comes in two types - real - which is your RAM size - and 'virtual' which although it is on your hard disk is not directly accessible to the user - it is used by programmes like VideoStudio to carry out the actions you have requested.
The setting for virtual memory do have to be correct though for the applications you are running and any video editor - not just VideoStudio - needs a bit more 'virtual' memory than basic computing.
just follow the instructions already given to you by Heinz.
