Note also, that almost NO encoder would be giving you an EXACT size that you intend (though they can get close). So maybe you should give us some info about what you consider to be a comfortable bitrate (and possibly WHY you think so, since you may be surprised to find fallacies in your assumption). IOW, 320x240 using 1Mbps of AVC is usually plenty of bitrate to give good quality, while 1280x720 using 1Mbps of AVC might be OK but it might not, and 1920x1080 using 1Mbps of AVC is going to be showing some weakness (or a lot, depending on content type). Understand, however, that the higher your resolution is, the higher your bitrate will need to be to maintain quality without increased artifacts. Choose your resolution, but also choose your bitrate. Another important rule: for most types of lossy encoding, Bitrate is Irrespective of Resolution. You just have to have a complete understanding of what you really want.Īlso, you refer to resolution but then also talk about "size", but the way you are throwing that term around makes me believe you are actually wanting info on BITRATE. Code: 1280 / 720 * 1.0 (square pixel AR) = 1.777777777777 (aka 16:9) This can be used with ANY app, once you are used to the formula and once you know which variables the app is referencing (they can use slightly different nomenclature).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |