Bitrate Calculator and such
- RadicalEd0
- Joined: Mon Jun 24, 2002 2:58 pm
Bitrate Calculator and such
Ok, I'm aware there are plenty of bitrate calculators out there, plenty of good bitrate calculators. But I just made one myself, mostly for myself (doing those calculations is a pain :P). Buut.. its pretty simple, and it has some neat functions too. Instance, it can calculate the bits per pixel percentage of an encode, can calculate the total bitrate (with audio) and the video bitrate (total - audio), and I included a nifty little thing that converts audio bitrate for 5.1 encodes. That is... if you're used to using like 96 kbps for stereo audio and you've suddenly decided to encode in surround, just put 96 in and it will tell you the = bitrate for 5.1 audio (approximately).
You can input either megabytes, kilobytes, or both for the first part and likewise with hours, minutes, and seconds. These also have to be filled out for the bits per pixel calculations to work. Theres 2 audio inputs because mostly I use 2 audio streams (english and japanese).
You can use it to calculate the bitrate for full cd encodes, 50mb amvs, or pretty much anything else.
Btw, its visual basic meaning you need some dll from microsoft.com but chances are you already have it.
so um yea... have fun
http://www.angelfire.com/anime3/airanime/bit.html
You can input either megabytes, kilobytes, or both for the first part and likewise with hours, minutes, and seconds. These also have to be filled out for the bits per pixel calculations to work. Theres 2 audio inputs because mostly I use 2 audio streams (english and japanese).
You can use it to calculate the bitrate for full cd encodes, 50mb amvs, or pretty much anything else.
Btw, its visual basic meaning you need some dll from microsoft.com but chances are you already have it.
so um yea... have fun
http://www.angelfire.com/anime3/airanime/bit.html
NMEAMV: PENIS
NMEAMV: IN
NMEAMV: YO
NMEAMV: MIXED
NMEAMV: DRINK
NMEAMV: IN
NMEAMV: YO
NMEAMV: MIXED
NMEAMV: DRINK
- The Wired Knight
- Joined: Sun Jan 07, 2001 3:22 pm
- Status: Attorney At Law
- Location: Right next door to you
- RadicalEd0
- Joined: Mon Jun 24, 2002 2:58 pm
- klinky
- Joined: Mon Jul 23, 2001 12:23 am
- Location: Cookie College...
- Contact:
- AbsoluteDestiny
- Joined: Wed Aug 15, 2001 1:56 pm
- Location: Oxford, UK
- Contact:
OK, it would really help if you actually understood what was going on when encoding things.
1) Your bitrate calculation is completely off because you haven't taken muxing overhead into account.
2) Because there is no muxing overhead in the equation there is also no distinction between CBR and VBR overheads. Also, multiple audio streams increase this overhead.
3) it is completely unclear as to whether the audio box wasnt you to put in a bitrate or an actual size.
Everything in this calculator can be done quite easily in gordianknot and it also has millions more features. Simiarly if you dont need the bits/pixels count there is a good (and correct) bitrate calculator that comes with xvid by Nic.
Nice try, but it just doesn't work.
1) Your bitrate calculation is completely off because you haven't taken muxing overhead into account.
2) Because there is no muxing overhead in the equation there is also no distinction between CBR and VBR overheads. Also, multiple audio streams increase this overhead.
3) it is completely unclear as to whether the audio box wasnt you to put in a bitrate or an actual size.
Everything in this calculator can be done quite easily in gordianknot and it also has millions more features. Simiarly if you dont need the bits/pixels count there is a good (and correct) bitrate calculator that comes with xvid by Nic.
Nice try, but it just doesn't work.
- klinky
- Joined: Mon Jul 23, 2001 12:23 am
- Location: Cookie College...
- Contact:
- RadicalEd0
- Joined: Mon Jun 24, 2002 2:58 pm
I already know that, all of it :PAbsoluteDestiny wrote:OK, it would really help if you actually understood what was going on when encoding things.
1) Your bitrate calculation is completely off because you haven't taken muxing overhead into account.
2) Because there is no muxing overhead in the equation there is also no distinction between CBR and VBR overheads. Also, multiple audio streams increase this overhead.
3) it is completely unclear as to whether the audio box wasnt you to put in a bitrate or an actual size.
Everything in this calculator can be done quite easily in gordianknot and it also has millions more features. Simiarly if you dont need the bits/pixels count there is a good (and correct) bitrate calculator that comes with xvid by Nic.
what I said originally was that I made this for my own rudimentary use. Personally I don't use gordianknot for encodes, I simply calculate the bitrate myself using the stuff I put into this calculator.
I basically made this because I just learned how to use Basic for calculations and variables input by the user and I felt like doing something with it.
Oh yea, the bpp calculation was completely messed up in the first version, but it should be fixed now. (same url as before)
works for me :P if you dont like it, dont use it. In fact I dont recommend using it if you're versed in GK. I merely did it to aid in my own personal calculations.Nice try, but it just doesn't work.
NMEAMV: PENIS
NMEAMV: IN
NMEAMV: YO
NMEAMV: MIXED
NMEAMV: DRINK
NMEAMV: IN
NMEAMV: YO
NMEAMV: MIXED
NMEAMV: DRINK
- Lyrs
- Joined: Thu Aug 29, 2002 2:41 pm
- Location: Internet Donation: 5814 Posts
hmm....I wish I could create these things. Been trying for around 15 years just to learn this programming stuff and I still haven't gotten a bit further then when I started. I guess computers just aren't my kind of thing....
:digs into "C++ for Dummies" book:
I have no clue what is being said.....LOL!
:digs into "C++ for Dummies" book:
I have no clue what is being said.....LOL!
- RadicalEd0
- Joined: Mon Jun 24, 2002 2:58 pm
- AbsoluteDestiny
- Joined: Wed Aug 15, 2001 1:56 pm
- Location: Oxford, UK
- Contact: