3 replies to this topic

[Scott Melbourne Australia]

HI

i am using Roxio with Eye TV. I have no problem importing the EyeTV video into Toast and preparing the video files to burn a DVD. However every time I click 'burn' it says "theres not enough free space on this disc - 4.45gb are needed but 4.38gb are available".

This error happens with any brand single layer dvd disk. Toast doesn't seem to be compressing the files to the right size. Indeed, it shouldnt even need to be compressing it - because the video is only 1hr 30 mins. How can I tell Toast it should be working to a max of 4.38GB on single layer DVD disks?

Cheers

Scott

ps Toast customer service is TERRIBLE! I used the ticket system to ask the question above.

Response #1 - COMPLETELY unrelated to my question. It was telling me how to export from TIVO. TIVO is not even available in Australia!

Response #2 - Told me to ask the User Groups!!! Shouldn't Roxio know their own product?!!

If anybody from Roxio reads this I would encourage them to check ticket 449165 for proof of the terrible customer service.

[tsantee]

It would be helpful to know more about the EyeTV file such as its size and whether it is from a digital source or was MPEG encoded by the EyeTV. Given the small difference in size required maybe you could trim off a few seconds of the video using EyeTV's editor.

Otherwise, here is something to try.

Choose Save as Disc Image instead of clicking the burn button. When the disc image is finished select it using the Image File setting in the Toast Copy window. Now click the burn button. If the disc image is too big for a single-layer disc Toast will give you the option to have it compressed to fit. By the way, if Toast says it is encoding the video when you are saving the disc image then abort the process, go to the custom encoder window and choose Never next to re-encoding. That way Toast should only multiplex the video which should go much faster. If the multiplexing goes very slowly let me know and I'll tell you a workaround to speed that up.

[AustinHam]

tsantee's suggestion on Sep 23 2007, 06:39 AM of "something to try" worked for me. Many thanks!

But I have a question. I've been burning some EyeTV video recordings onto single-layer DVDs. Toast 7 burned several 15.6GB files (2.5 hours each) with no problems, but balked at a file of only 4.9GB (1.5 hours), complaining that there wasn't enough space on the blank DVD. Presumably the 15.6GB file was automatically compressed to fit; why wasn't that automatic compression invoked for the 4.9GB file?

Does Toast have a hidden compression setting which can be tweaked without the extra step of disk-image creation and compression?

[tsantee]

tsantee's suggestion on Sep 23 2007, 06:39 AM of "something to try" worked for me. Many thanks!

But I have a question. I've been burning some EyeTV video recordings onto single-layer DVDs. Toast 7 burned several 15.6GB files (2.5 hours each) with no problems, but balked at a file of only 4.9GB (1.5 hours), complaining that there wasn't enough space on the blank DVD. Presumably the 15.6GB file was automatically compressed to fit; why wasn't that automatic compression invoked for the 4.9GB file?

Does Toast have a hidden compression setting which can be tweaked without the extra step of disk-image creation and compression?

You must be recording at a custom bit rate setting to have such large files for videos of that length. In any case here is what I'm guessing is happening. Toast knows it can fit 2.5 hours of video to a single-layer DVD when it is doing the encoding. It also knows that 15.6 GB exceeds the capacity for DL media so encoding is required regardless of how you set the Custom Encoder options. Since a 4.9 GB file can fit DL media then Toast doesn't need to re-encode the EyeTV MPEG in order to fit those discs. So it is telling you to insert a DL disc, or save as disc image OR go to the custom encoder settings window and select Always for re-encoding. The latter option will result in Toast encoding a new MPEG file that fits the single-layer disc. But it won't save any time compared with my two-step disc image method and will result in a slightly lesser-quality encoding.