Attn: Doom9, change to the Nandub Guide?

[LotionBoy]

I started to wonder about the apparantly random choice of 270 for the high-pass value and that started me thinking (always a dangerous thing). Setting the high-pass to 270 can lead to file-size deviation because Nandub is correcting for the min. bitrate, but not registering that correction in the gauge at all. Since 270 seems to be a random number, I would suggest setting the high-pass to the min. bitrate. This way, the curve is scaled perfectly to how if it is going to be encoded, and should make hitting the desired filesize easier. Just a thought.

LotionBoy

[Doom9]

we're talking about the nandub reference guide here.. it's nandos parameters, not mine really. I think he had his reasons.. and I talked over these params with some of the initial nandub betatesters.. they all used the same value here and never had any problems (neither did I).

[LotionBoy]

agreed that 270 does work, but I think that setting it to the min. bitrate is much more precise. Unless 270 is some sort of magic number for Nandub? I'd be interested in knowing why 270 came to be the accepted value and if there is any benefit to using it. So, anyone know?

LotionBoy