You are viewing an archive of the old fxhome.com forums. The community has since moved to hitfilm.com.

HArd disk Space error Vision LAB

Posted: Sat, 13th Nov 2010, 4:48pm

Post 1 of 7

FXhomer42293

Force: 400 | Joined: 6th Dec 2008 | Posts: 3

VisionLab User PhotoKey 3 Pro User

Gold Member

Hey guys,

I'm working with some simple particle effects bursts in Vision Lab studio, its just a short 5 second or so burst that I'm trying to render out as an image sequence.

But it says this:

There is not enough room on the drive you selected to export this project.

The drive I have selected is showing 2.35 TB Free (of a total 2.72)

I can render out much bigger files to this drive from other programs,

Any thoughts?

Grant smile
Posted: Sat, 13th Nov 2010, 7:06pm

Post 2 of 7

RigomrtsFX

Force: 1516 | Joined: 14th Apr 2006 | Posts: 267

VisionLab User

Gold Member

i have had this happen to me before i was down to about 1.13 of
hard drive space then i cleaned out my backups of what i rendered before
and my vegas was saving everything that i burned for long ago.

and i was careful what i removed i only removed my dvd folders
that i didnt need or wanted any more but you may have alot
of things on your pc alot of clips ? or big files .... i have 5 hard drives on my pc and 2 on 2 ex on the other pc just in case this happens
all my clips are saved on the ex hard drives
Posted: Sat, 13th Nov 2010, 8:06pm

Post 3 of 7

FXhomer42293

Force: 400 | Joined: 6th Dec 2008 | Posts: 3

VisionLab User PhotoKey 3 Pro User

Gold Member

thanks, yeah tis a strange one, by 1.13 do you mean TB?

I have a bunch of media on my drive and I'm working on some edits that may have some rendered clips that could be streamlined/deleted but it doesn't seam to explain the basic error to me that Vision Lab seems to read my drive as not being big enough for the file im rendering.

Considering I have enough space to render the file over and over and over and over and so on...

it won't even let me do it once?

I'm pretty sure a tiny image sequence shouldn't eat up 2 TB of data :-p

I don't see what salvaging a few extra meg here and there will do,

still confused but appreciate the conversation

Grant smile
Posted: Sat, 13th Nov 2010, 9:39pm

Post 4 of 7

Axeman

Force: 17995 | Joined: 20th Jan 2002 | Posts: 6124

VisionLab User VideoWrap User PhotoKey 5 Pro User MuzzlePlug User PowerPlug User PhotoKey 3 Plug-in User FXhome Movie Maker FXpreset Maker MacOS User

SuperUser

That is odd. How does the drive connect to your computer? Can you try selecting a different drive to see if that makes a difference?
Posted: Sun, 14th Nov 2010, 12:25pm

Post 5 of 7

FXhomer42293

Force: 400 | Joined: 6th Dec 2008 | Posts: 3

VisionLab User PhotoKey 3 Pro User

Gold Member

Its an internal 2TB drive, I'll try a test with a USB external later but obviously would like to be able to write to my main media drive.

Do the FXhome Tech people ever post on here or is there a way I can contact them directly?

thanks
Grant smile
Posted: Mon, 15th Nov 2010, 3:15am

Post 6 of 7

Axeman

Force: 17995 | Joined: 20th Jan 2002 | Posts: 6124

VisionLab User VideoWrap User PhotoKey 5 Pro User MuzzlePlug User PowerPlug User PhotoKey 3 Plug-in User FXhome Movie Maker FXpreset Maker MacOS User

SuperUser

They do post here on occasion, but if you want direct support, the Support tab at the top of the page takes you where you need to be. Submit a ticket and they'll get back to you.

Of course you want to be able to write to your main drive, we want you to as well. If its an internal drive there's absolutely no reason it shouldn't work. My suggestion to try another drive was just a step to try isolate the problem.

Do you have the drive partitioned at all, or is there anything out of the ordinary about the drive?
Posted: Mon, 15th Nov 2010, 4:21pm

Post 7 of 7

Simon K Jones

Force: 27955 | Joined: 1st Jan 2002 | Posts: 11683

VisionLab User VideoWrap User PhotoKey 5 Pro User MuzzlePlug User PowerPlug User PhotoKey 3 Plug-in User FXhome Movie Maker FXpreset Maker Windows User

FXhome Team Member

Do you get the error is you try to render with different settings? To a Quicktime video, for example?