I recorded a program using my PC tuner card that was 7.9GB. Using VideoReDo I cut off the head & tail of program bringing the size down to 4.7GB. I imported the progam in DMF 4 & added chapter points every 5 minutes. I didn't creat a menu. When I went to burn it said that the file was too large so I used the fit to disk settings.
Once the final disk was burned I checked it by using Windows Explorer properties. I was astoonded to see that the size was only 2.8GB. What happened? Why could it not fit before using fit to disk? I'm struggeling to understand what happened. Before I burned the disk I had checked to see if any other streams had been recorded at the same time of the air. VideoReDo didn't display any other streams.
What's happening with file size?
-
keithm
Well the first point is you can't fit 4.7gb on a dvd r! I think the maximum is 4.38 but I never go beyond 4 gb.
Secondly the DVD menu will take up some disk space.
But the message you got might have related to the working folder for ulead. I still think there is an issue trying to create a large DVD if you are running fat 32 hard disks. I can't fast export a DVD over 2gb at the moment and I believe that to be an issue with FAT 32. If you can partition part of your disk to NTFS (what OS are you runnng) and point ulead's working folder to the NTFS partition it might be ok.
Secondly the DVD menu will take up some disk space.
But the message you got might have related to the working folder for ulead. I still think there is an issue trying to create a large DVD if you are running fat 32 hard disks. I can't fast export a DVD over 2gb at the moment and I believe that to be an issue with FAT 32. If you can partition part of your disk to NTFS (what OS are you runnng) and point ulead's working folder to the NTFS partition it might be ok.
I've never used the fit to disc feature, and I don't understand why it compressed it to 2.8GB. Maybe the size-estimation algorithm is lousy?
This extra compression is your reducing video quality. If it is notiecably worse than the original recording, you might try starting-over and adjusting the bitrate manually. A Bit Rate Calculator will make this easier.
I have had good results with DVDshrink. It seems to shrink the file by exactly the right amount ('Burn" the project to hard drive instead of a DVD-R, shrink it, and then copy the shrunk VIDEO_TS and AUDIO_TS folders to a DVD-R.)
If you must capture in MPEG, ideally you should guess the "correct" bitrate at capure-time, and avoid re-coding the MPEG.
The 4.7GB vs. 4.35GB issue is caused by marketing nonsense! The following is from DigitalFAQ.com:
This extra compression is your reducing video quality. If it is notiecably worse than the original recording, you might try starting-over and adjusting the bitrate manually. A Bit Rate Calculator will make this easier.
I have had good results with DVDshrink. It seems to shrink the file by exactly the right amount ('Burn" the project to hard drive instead of a DVD-R, shrink it, and then copy the shrunk VIDEO_TS and AUDIO_TS folders to a DVD-R.)
If you must capture in MPEG, ideally you should guess the "correct" bitrate at capure-time, and avoid re-coding the MPEG.
The 4.7GB vs. 4.35GB issue is caused by marketing nonsense! The following is from DigitalFAQ.com:
Quick note: "4.7 GIG" vs 4.38GB disc size
Many people wonder why there 4.7 GIG discs are "defective" and "only" write 4.38 GB at maximum capacity. This is not an error of any kind, but rather an industry inconsistency. The 4.7 "GIG" that is calculated is actually 4.7 billion bytes. But on a computer, it takes 1024 bytes, not merely 1000, to make up a full MB.
The 4.7 GIG discs = 4.38 GB = 4489 MB (for DVD-R) and 4483 (for DVD+R)
This kind of inconsistency is found in many other areas. For example, the 120GB hard drive will format to about 112GB, requiring 8GB for file system and other settings. A 6-hour video tape is about 6:05 in length. And let's not forget the most famous one: hot dogs come in packs of 10 while buns come in packs of 8.
[size=92][i]Head over heels,
No time to think.
It's like the whole world's
Out of... sync.[/i]
- Head Over Heels, The Go-Gos.[/size]
No time to think.
It's like the whole world's
Out of... sync.[/i]
- Head Over Heels, The Go-Gos.[/size]
-
The Old Timer
Yes I also have had great results with DVDShrink. I just thought that since the chapter points were added by DMF 4 it would be just as well to have it burn the disk. If one can set the bitraetes for recoding in this program I must have missed it. Are you sure this can be done?
In any event the point that I was making was whether or not the original file was too large or much too large is beside the point. If the program thought that the file size was too large to fit in a disk then the fit to disk option should have produced a file size just under the maximum allowable size not 2/3 of this figure. As I said if I knew what the results were going to be before the disk was burned I could have had more on the disk.
In any event the point that I was making was whether or not the original file was too large or much too large is beside the point. If the program thought that the file size was too large to fit in a disk then the fit to disk option should have produced a file size just under the maximum allowable size not 2/3 of this figure. As I said if I knew what the results were going to be before the disk was burned I could have had more on the disk.
-
jcc
I have used the fit-to-disk feature and found it to behave as expected. I suspect that the error would have been in the initial estimation of the size of the project. ie it was always going to end up at 2.8G. The fit-to-disk result would not have ended up significantly less than 4.7G
If you still have the project, try exporting the video and reimporting it. That may resolve the confusion.
If you still have the project, try exporting the video and reimporting it. That may resolve the confusion.