Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Some more bitrate graphs ... (Read 2908 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Some more bitrate graphs ...

(Part 2 of my quest to use Ogg Vorbis to help me learn Python scripting  )

I've written a little tool which takes the output from ogg123, hits it with a rock, and generates nice graphs of bitrate-vs-time for Vorbis audio files. It's nothing complicated, but it's possible that some of you may like to play with it.

I've generated two example graphs - they both involve Vorbis encodes of 'Radiohead - Everything In Its Right Place' from 'Kid A'. Both were generated with a datapoint smoothing value of 10.

http://www.maths.warwick.ac.uk/~jingram/og...tyvsmanaged.png
This demonstrates quite well the differences between quality mode and managed bitrate mode. The track was encoded three times:
1) with -q 5, which averaged 181kpbs
2) with -b 160, which averaged 160.1kpbs
3) with -b 160 -M 160, which averaged 152kpbs.
As you can see, -M enforces the bitrate limit very strictly, -b less so.

http://www.maths.warwick.ac.uk/~jingram/og...yingquality.png
This shows how bitrate increases throughout the track as you increase the quality setting.

As with my previous graphs, there are postscript versions, which will be of higher quality for those of you on OSes that understand them . These, along with the Python script I used to generate the graphs, can be found in the obvious place:
http://www.maths.warwick.ac.uk/~jingram/ogg/bitrate-time/

(Edit: added some explanation for the first graph).

Some more bitrate graphs ...

Reply #1
Looks like managed bitrate could still use a bit of work... but I guess it's hard without 2-pass encoding