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: Klymins' MP3 Encoding Table (Read 1531 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Klymins' MP3 Encoding Table

Hello. I just finished an MP3 encoding table that gives the ideal (in my opinion, at least) encoding settings for every bitrate at telephony and CD sampling rates (I didn't do any tests with DVD sampling rates) (I'm currently working on the corresponding AAC-LC table). I used MP3Enc for all of the combinations, because it is apparently the best for encoding tasks with cutoff (at least for me) and I couldn't find a way to encode good quality cutoffless MP3's with other encoders too.

Two options are given for the sampling rate (they sometimes give the same settings): High and Low. High is the ideal one for most cases. Low is ideal one when the cutoff is too low for the corresponding high version or a lower sampling rate is wanted (these can be wanted when a weak interpolation method is used, which I recommend (I especially recommend linear interpolation)). Note that the Low option should be used carefully, because you can get an unnecessarily low sampling rate for the bitrate with it. I put an "L" to combinations those are probably better with the low setting.

The first frequency value gives the sampling rate (rounded), and the second one gives the cutoff. If there's only one, this is the first one.

If there's an "2x", that means this will be encoded at twice of the intended sampling rate with a cutoff point that is the half of the intended sampling rate (the quarter of the real sampling rate) and exported at the intended sampling rate (the half of the real sampling rate, and Flash can do this on it's own). This is apparently the only way to get good cutoffless MP3's for a wide range of combinations. If MP3Enc could be modified to be able to export cutoffless MP3's without using this way, please tell me, I'll be very happy.

And, "N/A" means "Not Available".

Note that I made this table for music. For speech, using GXLame with VBR is probably the best, although MP3 is not a good codec for speech but many players support nothing else (or only MP3 and WMA) as lossy codecs. For sound effects, probably so much trial and error is needed, although some musics also may need so much trial and error.

Feel free to tell me if you find a mistake or think something could be improved.

Here's the table (I'll also attach the .ods file):

edit: see Reply #14


MOD: edited by request of OP

Re: Klymins' MP3 Encoding Table

Reply #1
Oops! I found a mistake. Here's the correct version:
X



Re: Klymins' MP3 Encoding Table

Reply #4
I made another correction, here's the updated version (edit: I updated it once more):
X

Re: Klymins' MP3 Encoding Table

Reply #5
I feel quite ignorant, but I don't understand the purpose of this table. I don't think anyone wants to use MP3Enc for anything. Also those clown fonts you use make the entire table look like trolling.

Re: Klymins' MP3 Encoding Table

Reply #6
I feel quite ignorant, but I don't understand the purpose of this table. I don't think anyone wants to use MP3Enc for anything. Also those clown fonts you use make the entire table look like trolling.

This table is primarily to be integrated in a software (for example a SWF file creating program) to give the user the ability to encode good MP3's at various bitrates without having too much experience with MP3.

I think MP3Enc clearly beats LAME, at least at low bitrates (there was a topic about that (the one that had Afrowell samples) but I couldn't find it right now).

And about the font: I really like this font (Porky's, I discovered it by Flash games of EightGames) but changing it is easy.

Edit: I changed the font right now (to Rubik) and I honestly think that's much better, thanks for suggestion. (I didn't like darkalex's formatting because it had left align and changed widths.) New formatting:
X

Re: Klymins' MP3 Encoding Table

Reply #7
Regardless what the thread you cant find anymore sais tho, the respective lower right portion feels like a TOS 8 violation, even if we assume that everything that thread sais is correct here. I think you need some explaining for your choice on the higher bitrates. Consider just leaving those blank.
And so, with digital, computer was put into place, and all the IT that came with it.

Re: Klymins' MP3 Encoding Table

Reply #8
Regardless what the thread you cant find anymore sais tho, the respective lower right portion feels like a TOS 8 violation, even if we assume that everything that thread sais is correct here. I think you need some explaining for your choice on the higher bitrates. Consider just leaving those blank.

That's a good point, thanks. I chose MP3Enc also for those bitrates mainly because the original SWF creating programs (Adobe Flash Professional and Adobe Animate) uses it, and choosing one encoder for all combinations can be better for many reasons including probable consistency between the combinations and lower licensing fees. Also, I don't want to choose LAME even for high bitrates where it can do a better job as it's non-FhG.

By the way, I thought maybe I should consider limiting the bitrate to 96kbps for Telephony Mono, 160kbps for Telephony Stereo, 128kbps for CD Mono, and 224kbps for CD Stereo.

Re: Klymins' MP3 Encoding Table

Reply #9
I don't understand the purpose of this table. 
This being as useful as an ashtray on a motorbike, you're not alone on that.  ::)
• The older, the lossier
• Listen to the music, not the media it's on.
• "União e reconstrução"


Re: Klymins' MP3 Encoding Table

Reply #11
At least @Klymins has his fun. I hope nobody stopping by at Hydrogen takes these things here to serious.
Is troll-adiposity coming from feederism?
With 24bit music you can listen to silence much louder!

Re: Klymins' MP3 Encoding Table

Reply #12
I hope nobody stopping by at Hydrogen takes these things here to serious.
Now and in future searches, as all this drivel is sure to populate pollute them results.

Edit: strikethrough
• The older, the lossier
• Listen to the music, not the media it's on.
• "União e reconstrução"


 

Re: Klymins' MP3 Encoding Table

Reply #14
I improved my table even more, but I still feel like there's some inconsistencies. Feel free to give suggestions about that. The hard part is that MP3Enc also has some inconsistencies on it's own, too.

I also changed the font again (to Consolas) because I realized that Rubik is not a builtin font in Windows. Also I think using a monospace font is a better idea.

I also want to emphasize that my choice of encoder is not made purely for quality. I didn't try L3Enc because it does not work on most Windows installations, and I didn't choose Lame even for high bitrates because I thought using the same encoder for all combinations can create a consistency between the combinations while Lame or GXLame probably does a better job in cases where the bitrate is extremely low or high for the samplerate-channelconfig combination (for example a high bitrate for the combination like 11025Hz mono 40kbps, or a low bitrate for the combination like 44100Hz mono 32kbps (this can be needed for devices which don't support MPEG-2 mode which allowed the use of lower sampling rates)).

I also limited the bitrate to prevent users from using unnecessarily high bitrates, but even the current highest bitrates are unnecessarily high for many people too (including me, as 128kbps is totally transparent to me at 44100Hz stereo with most encoders), so I marked cells those have a bitrate that is more than enough to be transparent to many people with "H".

I decided to keep my files in a Google Drive folder instead of attaching them to this post (like I was doing when I was not knowing that I can attach files to my posts) as this way I can update the files without keeping the old ones if I find another mistake or a way to improve the table. But apparently Google does not show my .ods file properly so I put a .png file to there too. From now on, I will just write "Updated." when I update the files. I think I should say that the Google Drive folders those I shared in my older posts are not to be trusted anymore.

Here's the link: https://drive.google.com/drive/folders/1svjXAR2I_2FVYoJTWHs06wrcjyepeULv?usp=drive_link

I hope I can help someone.