I don't the issue. (I was just confused since you mentioned anamorphic in a way that is seemed wrong to me.)
Anamorphic encoding was introduced since people had a fixed number of pixels, in for example on DVD (720x480 for NTSC, 720x576 for PAL), and wanted to save for example 1024x576 content with a minimum of black borders around it. So anamorphic signaling was introduced which meant, that the one of the dimensions (usually the width) was saved in a compressed/stretched way and the decoder had to stretch/compress the content on decoding.
Thus having 1024x576 pixels were compressed to 720x576 encoded and signaled with a PAR of 1.25 (=1024/576) which told the decoder that on playback the content needed to be stretched to 1024x576 again. (iirc. http://www.widescreen.org has a decent introduction to the history of anamorphic encoding)
Cu Selur
Anamorphic encoding was introduced since people had a fixed number of pixels, in for example on DVD (720x480 for NTSC, 720x576 for PAL), and wanted to save for example 1024x576 content with a minimum of black borders around it. So anamorphic signaling was introduced which meant, that the one of the dimensions (usually the width) was saved in a compressed/stretched way and the decoder had to stretch/compress the content on decoding.
Thus having 1024x576 pixels were compressed to 720x576 encoded and signaled with a PAR of 1.25 (=1024/576) which told the decoder that on playback the content needed to be stretched to 1024x576 again. (iirc. http://www.widescreen.org has a decent introduction to the history of anamorphic encoding)
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.