probably, but my english is quite good. I'm half english, half dutchI think Flip was being very polite and patient in his reply.
I also assume it was a language issue that caused the mix up
When somebody says an MPEG2 file contains only MPEG1/2, than I interpret that as an MPEG2 container that can only contain MPEG1/2 formats. This is just plain wrong, MPEG2 is not a container. This is probeably what Flip intended to say, but my reaction was not incorrect. If somebody says it's safer to let windows determine what codecs to use (even though sometimes that also doesn't work) than I HAVE to disagree, I'm sorrybut a lot of what flip said was responded to incorrectly in kkendals post, which Flip pointed out.
But enough about language issues
As for the effort required to change the code to individually select codecs, I guess this could be an easy task technically, but quite lengthy in the time it would take. As flip said, MP checks the extension not the contents of the container. This would need to be changed as well as adding in all the drop down boxes for every codec (and maintaining as new ones are made) which would take bit of time.
Whao, is this really true? But for example, an avi or mkv can contain so many formats, from h264 to mpeg2 and from vc-1 to xvid. Than how can MP determine what codec to take if it only looks at the container??
And how is it possible that it can determine h264 and mpeg2 within a container if it only looks at the extension? ...It's just really hard to swallow...
what was the thought behind this, to just look at the file extension, not the actual needed format within the container? Could somebody please explain this?
As I'm not a programmer, I know squad about interpreting source codes so I can't check it but this really changes the perspective on things...
Oh and Flip, if I offended you, I'm sorry. That's just my Dutch side acting up I guess.