I don't have Movie Studio Platinum so I tried Vegas Pro 9 with your settings and a 1 hr 55 min project. The rendered video file was 4.1 GB.

4684 kbps average and 1 hr 55 mins works out at 4.03 GB.

I don't understand why MSP should have produced a rendered video of 5.3 GB. Did it include audio as well, or only video? (Check with Mediainfo).

If you still have problems, take it up on the Movie Studio forum.

OK ... I found an issue .. when I looked at Render with Media Info it was too long (time wise)

Traced that down to fact I had a spurious marker out at 3.5 Hrs ... so was rendering 3.5 nor 1.55

So run it again first off audio is run at Dolby stereo ac3 192 Kb ... gives file of 160,165Kb
Entered run time & audio deatils in Marks Bit Rate Calculator
Selected MainConcept DVD Architect PAL Widescreen
Set to VBR 2 pass and entered the Calculator settings - (no audio stream)
Settings are as shown:
http://tinyurl.com/pbdvgbj
Rendered and results in Video file size 4,347,808 Kb

Audio + Video = 4,507,973 Kb

So we are better as no longer 6Gb ... but when I try to put this into DVD Architect it again gives me an 'oversize error File size of 4.8Gb'

So back to same issues why does DVD architect claim, this to be oversized ?
No menus or anything else being added.

The whole point of using DVD Calculator was to ensure it would fit with 5% safety margin.
Keen to understand where its going wrong ... Sony app feeding Sony app - would expect it to work happily.

>>>Sony app feeding Sony app - would expect it to work happily.<<<
Indeed, but this happens, read here
"Why does DVD Architect sometimes incorrectly report file sizes? (It usually says it’s too large even though it isn’t).."

A DVD calculator for VBR is an educated guess at best. How much compression is applied depends entirely upon the type of footage. If there is a lot of detail or movement, compression is less, if there is a lot of static shots, them there is more compression.

Yes, DVD Arch seems to get it wrong sometimes about whether a project will fit on a disc or not. If you think that it should fit, author to a folder only, without burning. Then check the folder size. If it is less than 4,700,000,000 bytes, then burn the folder to the disc.

Note. I find it best to work in bytes rather than Kbytes or whatever to avoid confusion between kibibytes (multiples of 1024, as reported by Windows Explorer and other software) and kilobytes (multiples of 1000). Microsoft has a lot to answer for, for introducing this unnecessary problem!

DVDAS will only estimate the size (as has been said). What I used to do when authoring DVD projects was to use one of the many bit rate calculator methods available, prepare the project into a HDD folder then, if it was marginally too large for a DVD, I'd use the excellent DVDShrink to create a burnable folder. With DVDShrink you can compress quite a lot with not much visible degradation. I've recently compressed to about 75% and the result was perfectly respectable.

I'm having a similar issue. I have a file thats 5.35gb. I had rendered it through Vegas Movie Studio last night and it came out at 20gb. However when I went into DVD Architect 5.0 and placed the video in there and went to burn, it was able to 'Fit to Disc' when I selected that option in 'Optimize'. Eventually though I aborted the rendering process because it was late and I didn't wanna leave my computer running during the night. This morning however I decided to delete the rendered file mainly due to its size and go with the original 5.35gb file. However the 'disc space used' in DVDA5.0 says 6.1gb and when I select 'Fit to Disc' in 'Optimize' I get the 'Media file(s) is too big and could not fit to disc' pop up. This puzzles me immensely especially when this window did not appear when the file was 20gb. Should I just ignore it and try burning anyway?? Is it possible its due to the file type?? The 20gb version I think was an AVI while the 5.35gb file is .mpg. Should I perhaps adjust the Default video bit rate??

I personally will adjust the video bit rate during rendering so it fits exactly without any further processing.

I still follows Adobe's Bit Budgeting guide for the bitrate planning:

https://helpx.adobe.com/encore/using/project-planning.html#bit_budgeting

and to make more safe, I count the disc size as 4.5GB instead of 4.7GB - plus safe 4%.

Don't forget a 4.7GB disc only holds 4.377gb in computer language.

Currently I'm rendering the video again through Sony Vegas under another setting. Should I revert back to the original file what would be my best method for changing the bit rate?? I tried adjusting it under 'Optimize' but I don't think it had any effect. Is there a work around so it'll just be able to simply Fit to Disc my video?? I just find it strange it I didnt get the pop up when I used the 20gb video but I get it with the 5gb video. I tried twice rendering in DVDA5.0 to see if it would burn either way. It did not.

I'm honestly stumped here. I have my settings in Sony Vegas as MainConcept and DVD NTSC. I used a Bitrate calculator to get an estimate but when I go into Custom to put these numbers in they just revert back to what they were set as before in this case 192,000. What do I do?? I'm really no expert with bitrates and all that and really would appreciate some assistance. I even rendered my 5gb video twice as an .mpg in Sony Vegas and I still get the 'file is too big to fit to disc' when I select 'Fit to Disc' in DVD Architect. Help!

when I go into Custom to put these numbers in they just revert back to what they were set as before in this case 192,000.

Try typing your numbers like this: 8000000, not 8 000 000.

when I go into Custom to put these numbers in they just revert back to what they were set as before in this case 192,000.

Try typing your numbers like this: 8000000, not 8 000 000.

Before I do that, I may have fixed something. Under Optimize in DVDA5.0, in the video section there was a listing that said Recompress and the drop box next to that was set on 'No'. I changed this to 'Yes' and did not get the popup when I selected 'Fit to Disc'. Currently in the process of burning a disc.

Good. Note that it's another recompression.

I understand. ;) At the time that I am typing this it is now at the burning stage and there's so far been no issues.