Large files on NTFS after render
 

okies, heres a strange one, i have 2x 120gb WD drives bother with the 8mb cache, and 1 whichis 80gb same spec but a system and resources drive...

now recently ive been doing some really long (and short) edits, however when i try to play them back in media player (from raw DV Avui files made form Vegas) i can only view4.42 seconds when it goes for something like 40 mins.. the file size IS correct and when i open it in Vegas, i can see and mess with the full file, but when i open the SAME file in Pinnacle Studio7 (or meida player and PowerDVD to preview, i get teh same 4.42.. its as if the file locks up...

now when i render this to the master drive, which has compression turned off in the drive attributes, the file plays thruout with no issues...

funny thing is i can SEE the file in vegas (ie the FULL edit with sound and all) and i can see the file size in Explorer and they all look ok, the duration however shows 4.42mins in explorer

this is on any file which goes over 4mins and 42 seconds...

i never had this prob in the past, but for some reason, i get it now...

I am attempting to change the attirbutes of the drives to be set to non compressed, and seeing how that goes, but so far my atempts to view the file in media player, even with this compression turned off isnt working...

any ideas? Or shoudl i jsut clean the drives, format and start again?

I dunno if its vegas thats doing it or what, but i think its teh HDD archiving routines or somthing...

All drives are NTFS, a i HAVE been able to view larger loooooong files (were talking 40gb files here) without issues before...

any ideas?

First, you should have posted this in the "What Happens in Vegas" forum.

Second, what settings did you use for rendering and have you made any changes to the preferences?

One place to check, when you go to options - preferences, there is an option on whether or not to use Open DML. Did this get changed?

it is set to on being avi2 conformed file...

see, i didnt know if it was a Vegas issue, as it looks like a HDD file system issue as well.. :(