Rendering in Vegas 2.0a

Modi wrote on 10/31/2000, 1:35 AM
Hi:
Each time I was trying to render a video file it started
the proccess then stoped in about 12% and always recieved a
message saying: "There is no file access or not enough
free space."
I bought a 7200 40 GB Ultra ATA drive and it has 35 FREE GBs
It was used only by Vegas. I tried everything but without
results.
Does anyone out there had the same experience and found the
reason for it?
I have 450 Hz with 400 MB RAM.
Thank you for your help.
Mordecai

Comments

mcooper wrote on 10/31/2000, 3:31 PM
I haven't run into that problem, but here's a couple of ideas:

What operating system are you using? There may be a file size limit
if you are using an older version of Windows or filesystem (not FAT32
or NTFS). (Although I guess this may not be the problem since you
are able to mount the 40GB drive as a single partition).

I'm sure you are specifying the right target drive for the rendered
file, but check that. Could you be running out of temp space on your
system drive?

--Mark

Mordecai Shehori wrote:
>>Hi:
>>Each time I was trying to render a video file it started
>>the proccess then stoped in about 12% and always recieved a
>>message saying: "There is no file access or not enough
>>free space."
>>I bought a 7200 40 GB Ultra ATA drive and it has 35 FREE GBs
>>It was used only by Vegas. I tried everything but without
>>results.
>>Does anyone out there had the same experience and found the
>>reason for it?
>>I have 450 Hz with 400 MB RAM.
>>Thank you for your help.
>>Mordecai
SonyEPM wrote on 11/1/2000, 9:11 AM
Is it possible you are rendering "uncompressed"? That would account
for the huge file size.

Mark Cooper wrote:
>>I haven't run into that problem, but here's a couple of ideas:
>>
>>What operating system are you using? There may be a file size
limit
>>if you are using an older version of Windows or filesystem (not
FAT32
>>or NTFS). (Although I guess this may not be the problem since you
>>are able to mount the 40GB drive as a single partition).
>>
>>I'm sure you are specifying the right target drive for the rendered
>>file, but check that. Could you be running out of temp space on
your
>>system drive?
>>
>>--Mark
>>
>>Mordecai Shehori wrote:
>>>>Hi:
>>>>Each time I was trying to render a video file it started
>>>>the proccess then stoped in about 12% and always recieved a
>>>>message saying: "There is no file access or not enough
>>>>free space."
>>>>I bought a 7200 40 GB Ultra ATA drive and it has 35 FREE GBs
>>>>It was used only by Vegas. I tried everything but without
>>>>results.
>>>>Does anyone out there had the same experience and found the
>>>>reason for it?
>>>>I have 450 Hz with 400 MB RAM.
>>>>Thank you for your help.
>>>>Mordecai
Modi wrote on 11/2/2000, 12:21 PM
Dear Mark:
I am running Windows 98 second edition, all my files are fat 32,
About compression: where do I find if I render the files compressed
or not? Thanks for your suggestions.
Mordecai

Dave Hill wrote:
>>Is it possible you are rendering "uncompressed"? That would account
>>for the huge file size.
>>
>>Mark Cooper wrote:
>>>>I haven't run into that problem, but here's a couple of ideas:
>>>>
>>>>What operating system are you using? There may be a file size
>>limit
>>>>if you are using an older version of Windows or filesystem (not
>>FAT32
>>>>or NTFS). (Although I guess this may not be the problem since
you
>>>>are able to mount the 40GB drive as a single partition).
>>>>
>>>>I'm sure you are specifying the right target drive for the
rendered
>>>>file, but check that. Could you be running out of temp space on
>>your
>>>>system drive?
>>>>
>>>>--Mark
>>>>
>>>>Mordecai Shehori wrote:
>>>>>>Hi:
>>>>>>Each time I was trying to render a video file it started
>>>>>>the proccess then stoped in about 12% and always recieved a
>>>>>>message saying: "There is no file access or not enough
>>>>>>free space."
>>>>>>I bought a 7200 40 GB Ultra ATA drive and it has 35 FREE GBs
>>>>>>It was used only by Vegas. I tried everything but without
>>>>>>results.
>>>>>>Does anyone out there had the same experience and found the
>>>>>>reason for it?
>>>>>>I have 450 Hz with 400 MB RAM.
>>>>>>Thank you for your help.
>>>>>>Mordecai
Modi wrote on 11/4/2000, 12:49 AM
Hi:
I tried your suggestion and rendered the file in compressed mood and
it did finish the proccess fine. Thank you. My questions are: in
what situation one would render "un compressed" ? because it will
obviously end up without space even with a big file?
Secondly, does the copression lower the quality of the images?
Thanks,
Mordecai

Dave Hill wrote:
>>Is it possible you are rendering "uncompressed"? That would account
>>for the huge file size.
>>
>>Mark Cooper wrote:
>>>>I haven't run into that problem, but here's a couple of ideas:
>>>>
>>>>What operating system are you using? There may be a file size
>>limit
>>>>if you are using an older version of Windows or filesystem (not
>>FAT32
>>>>or NTFS). (Although I guess this may not be the problem since
you
>>>>are able to mount the 40GB drive as a single partition).
>>>>
>>>>I'm sure you are specifying the right target drive for the
rendered
>>>>file, but check that. Could you be running out of temp space on
>>your
>>>>system drive?
>>>>
>>>>--Mark
>>>>
>>>>Mordecai Shehori wrote:
>>>>>>Hi:
>>>>>>Each time I was trying to render a video file it started
>>>>>>the proccess then stoped in about 12% and always recieved a
>>>>>>message saying: "There is no file access or not enough
>>>>>>free space."
>>>>>>I bought a 7200 40 GB Ultra ATA drive and it has 35 FREE GBs
>>>>>>It was used only by Vegas. I tried everything but without
>>>>>>results.
>>>>>>Does anyone out there had the same experience and found the
>>>>>>reason for it?
>>>>>>I have 450 Hz with 400 MB RAM.
>>>>>>Thank you for your help.
>>>>>>Mordecai