TMPGEnc + DVD-5 bitrate settings

Something wrong with my first approach so I'm trying a different method for getting the avg. bitrate for TMPGEnc transcoding. I load the project in REMPEG2 to get the diagnostic data, then plug that into the DVD-R bitrate calculator by mhammer, but that does not give the new desired avg. bitrate for TMPGEnc, so.. (Size of new Video Stream in bytes from the bitrate calc) * 8 / 1000 * (length in seconds) This gives a number that seems reasonable, and it fits in with the Scalefactor when comapred to the original Avg. bitrate. So I think this is Ok, but I'm not sure about equation 2 (first post), the Max bitrate calculation, anyone got a comment on that?

Looks good except I think the audio is "48 KiloBYTES", so it ends up being "384 KiloBITS". So you subtract the 384. I could be wrong.

A few other things. 1. Extras are not always the same size. But most of the time the difference can be minimal. 2. I think you have to divide by the number of seconds not multiply. So the more seconds the lower the bitrate. I think this is more of you just typed in the wrong symbol. 3. If you do subtitles too you have to take this into account.

Yes its is divide, just did not put all the brackets in: [(Video Stream in bytes from the bitrate calc) * 8] / [1000 * (length in seconds)]. How does one account for the subs? Is it even necessary, I think they should be nearly insignificant?

Ok this is going to sound lame, I just found the built in bitrate calc in TMPGEnc.:stupid: It gives numbers that are sort of close to but not equal to the numbers that I get from ReMPEG data., for example: ReMPEG data + mhammer bitrate calc : 4941 Kbit/s TMPGEnc: 4.33 Mbps, where 4.33 Mbps is either 4330 or 4434 Kbit/s (depending on whether you use 1000 K or 1024 K in 1 M). So far I have been getting file sizes that are very close to the 4.7 GB limit with the ReMPEG data, so I'm happy with that. However I am curious about this other calculation method, is it reliable? Am I interpreting the data properly (that the resulting Mbps is Mega bits / sec and not Mega Bytes /sec etc.. etc..

As long as you take into account the subtitles. They are small but have an effect on the resulting bitrate. I'm not exactly sure how big they are, but IfoEdit's 'Bitrate Calculator' takes them into account. The calcs look good, so do the units after fixing the 48 to 384 glitch. But I always usually subtract about 50 from the result to save me from a second encode.