Workshop 2.0 reports only 4 gb needed for 6+ GB file. Why?

[jlietz]

I have 1 file that is approx 6.2 gb. It is Mpeg2 with PCM audio. I opened Workshop to see if I was going to be able to fit it onto DVD, with Workshop converting the audio to AC-3 (256 kb/s). I didn't create a menu or anything as it was just my intention to verify that the file would be small enough. I forgot to check "Convert to disc template" on the audio tab, but the funny thing is that Workshop reports that the required disk space is only 4.0 gb! To clarify, both the video and audio tab have the "Convert to disc template" option unchecked and the file is 6+ gb.
Am I missing something here?

[canadateck]

It will convert the files if they are not DVD compliant , even if you dont click "Do not convert".

[thecoalman]

Possibly your file is a non compliant format which would have to be converted regardless if the boxes were checked or not?

[jlietz]

Yes, but they are DVD compliant. The "Convert to disc template" box would be greyed out, I believe, if they weren't.
I'm creating a disc image right now just to see if Workshop is misreporting the file size. I'll post the results in about 10 minutes.

[thecoalman]

I'll post the results in about 10 minutes.

If it has to convert it you won't be back in 10 minutes..... Unless of course your using the computer Cap has at his work place then you would be back in .00000003 seconds.

[canadateck]

Yes it would be greyed out.But if you are telling Workshop to Put this "6Gb" File onto a 4gb DVDr then it would have to convert,If you try it by just making a dvd file then it would not.

Edit:What I mean is tell it to save the DVD file to your harddrive, Then it would not try to Convert.

[jlietz]

I guess I need to e-mail Ulead (as if they don't know about the bug already ) because the disc image was approx 6.2 gb. Still a great authoring tool though.

[canadateck]

I guess I need to e-mail Ulead (as if they don't know about the bug already ) because the disc image was approx 6.2 gb. Still a great authoring tool though.

There is no bug. Where would you get that?

[canadateck]

If it said you need 4Gb for an "image file" "DVD Folder" then that would be a bug i guess,But not if you are trying to put it to "DVD".

[thecoalman]

because the disc image was approx 6.2 gb. Still a great authoring tool though.

You disc image shouldn't be 6.2 if you converted it to AC3 from PCM it should be smaller, losing 2.2 gigs seems to be an awful lot though. How long is your video?

[jlietz]

Your disc image shouldn't be 6.2 if you converted it to AC3 from PCM it should be smaller, losing 2.2 gigs seems to be an awful lot though. How long is your video?

For the test I just left it as PCM. The point of the test was to determine if Workshop was misreporting the destination file size, which it was. The video length itself was about 2 hrs 2 min.

If it said you need 4Gb for an "image file" "DVD Folder" then that would be a bug i guess,But not if you are trying to put it to "DVD".

Workshop claimed I only needed 4.0 gb for the DVD and 4.0 gb for the disc image (well, actually it said 8.0 gb for the disc image, but we know Workshop reports double the amount of the final image size). But in reality it needed 6.2 gb, thus it is a bug. Perhaps the bug only manifests itself when the project size exceeds 4.7 gb???? I don't know. I just don't want to waste 30 minutes writing an image that Workshop says will be small enough when in reality it may end up too large for the DVD.

[thecoalman]

For the test I just left it as PCM.

.

Is that DVD compliant PCM? Possibly it's allowing you to create a non-compliant image but won't allow you to burn the disc? Just a suggestion. If I remember correctly 1 hour of PCM is about 1 gig so that's possibly an answer.

I only have 1.3 so I can't test out what your doing, guess I'll have to upgrade. 8)

[jlietz]

Yes, it is compliant PCM. But, whether or not Workshop is creating a non-compliant image is not what I'm concerned about. It is simply the discrepancy between reported and actual size, which it seems, is a bug.
I appreciate all the help.