VS10 Create Disk with Split File

bm · Post by bm » Fri Jun 15, 2007 1:12 pm

Hello,

I edited my master video file and saved as a new file but it was over the 4gig XP Fat32 limit so VS split it into 2 files. How do I do "Create Disk" with the 2 files and have it put them back together and not create 2 menu items?

Thanks!!

Post by **Ken Berry** » Fri Jun 15, 2007 1:31 pm

...ummmm .... why are you still using FAT32?

bm · Post by bm » Fri Jun 15, 2007 3:01 pm

VS8-10 won't allow me to save a video file to my NTFS drives because they're mapped (path) and the mapping drive doesn't have enough space. I wrote to VS about this and they didn't care and gave me a bogus response. I sent them doc on what mapped drives or paths are and why they're used. Mapped drives have been around for quite awhile and starting VS8, they check the mapping drive not the actual drive itself.

All of the applications I use that access the paths or mapped drives have no problem with it including the Hauppauge software that created the video files.

Please don't make this a "why are you still using Fat32" thread instead of what my original question is.

Thanks

Post by **Ken Berry** » Fri Jun 15, 2007 11:07 pm

But I am afraid it IS a matter of FAT32. That is a limitation of your operating system which is imposed on all your programs. It is not a Ulead problem. So how do you expect Video Studio to get around a limitation which is not of its making but which it has no choice but to respond to.

I had thought that in such circumstances, the cut that is made is seamless. But translating that into a seamless DVD is another matter. If you insert the two files into the burning module, the program will, logically, treat them as two separate files. And though you can set the menu to play the next video automatically after the first, in practice there is always a second or two break in continuity at that point.

You could finalise your editing and try going straight to the burning module with your project file. But this means that the project still has to be converted during the burning process (which often causes other problems). The 4GB limit also applies, so in practice the rendering occuring there will also involve a split in the project. However, since the menu has already been made, there is the chance that the cut made will in fact appear to be seamless in the final DVD. However, I stress that I am merely theorising here. I have never tried this since I migrated all my various hard disks to NTFS once I moved on from Windows ME many years ago now... It could be that the program may simply spit the dummy and tell you the file is too big...

Another option, of course, would be to slightly reduce the bitrate used in your project so that the final overall size is less than 4 GB...

bm · Post by bm » Sat Jun 16, 2007 12:37 am

Ken,

Thanks for the thoughts. I think you misunderstood my comment about what the problem is. I'm very well aware of FAt32 splitting files and the limititation associated with Fat32. I also am aware that there is a gap when the file gets split. In my case it doesn't matter as there is silence at the part where it was split. You had asked why I'm still using FAT32.

Your comment:
"But I am afraid it IS a matter of FAT32. That is a limitation of your operating system which is imposed on all your programs. It is not a Ulead problem. So how do you expect Video Studio to get around a limitation which is not of its making but which it has no choice but to respond to."

The problem I described why I can't write to NTFS IS VS's problem as they don't know what a path or mapped drive is. It's not something new. I'm sure Ulead thinks people only have a C: drive on their computer and everyone is a computer novice. Msoft wanted to allow more volumes than A-Z so they created paths or mapped drives like Unix. VS is the only software I own that has a problem with it. Nero's video creation creates files to it with no problem as does everything other than VS.

Writing to a path has nothing to do with Fat32 as the main drive must be NTFS. A common procedure is to create a small NTFS drive then use it to map several partitions inside it thus not using up drive letters. Go to Administrative Tools > Computer management > Disk Management > select drive then "Add Drive Letter or Path"

sjj1805 · Post by **sjj1805** » Sat Jun 16, 2007 1:51 am

I cannot see why you have a problem with mapped drives.
Even with NTFS you can give a path a drive letter.

The easiest way is to make the path a network share and then simply using Windows Explorer goto tools, map network drive. There are other methods of course.

Please view:
Converting your hard drive from FAT32 to NTFS.

Also...

How to connect and disconnect a network drive in Windows XP

Another way is to partition your hard drive(s) and then they will have a permanent drive letter anyway.

etech6355 · Post by **etech6355** » Sat Jun 16, 2007 4:32 pm

VS8-10 won't allow me to save a video file to my NTFS drives because they're mapped (path) and the mapping drive doesn't have enough space.

Did you mis-type this statement? Or, the program thinks there isn't enough space when there is. Are you assigning a drive letter to your shares or trying to use the unix method. VidesStudio can only use the enumerated drives passed to it from the windows operating system (drive letters), not true unix mappings.

At present my Operating System is XP_SP2 Fat32, I have VS10+ and 2 mapped drives referenced as R & T drive. These drives are network shares from other computers & servers.
I'm using 4 video files as the source located on the R: Drive and rendering all 4 videos out to a new single video on the T: Drive.
My working folder is on the Fat32 OS drive and Preview files is also the local drive.
I think maybe your referring to true drive mappings similar to Unix/Linux? Such as //server/videos and all.

I don't know if you can map the drives to a physical drive letter or not but that should work then.
If you do have a drive letter mapped to a windows share on a MAC/UNIX/Linux computer running the SMB protocol and windows cannot read the disk information of the shared drive then it's a protocol or user rights issue on your network. Make sure the firewall isn't blocking the ports windows uses for it's shares and lookups.

I'm not sure how your mapping your drives. I can either use the windows interface or the command line.
If I use the command line then this is the command I'll use to connect to a SMB windows share that is a Raid0 configuration.
Net use H: \\Suse-server\raid (This creates my H: on the windows computer which shows 180Gig and 49Gig Free, this is correct usage for that shared drive)

To remove the H: I use this command
Net use H: /delete (But you can do this all from windows graphical user environment).

To be honest with you my system runs XP faster with the OS instaled on a fat32 drive versus ntfs drive. My internal video/audio drives are Ntfs though.

sjj1805 · Post by **sjj1805** » Sun Jun 17, 2007 6:51 pm

Another method of assigning a drive letter to a Windows Folder is to use the SUBST command.

I used to use this quite extensively with Windows NT4 and also Windows 98. but haven't had the need to recently.
I just checked and to my surprise it works with Windows XP on a NTFS hard drive.

How to use the SUBST command