You are right, the -sameq option -sameq deprecated and then removed from avconv, there were many reasons for this. Last but not least, there are different quantizers, and it makes little sense to talk about the same quantizer parameters when transcoding between different codecs.
Most people when reencoding are looking for quality, not quantifiers. Therefore, they should use -qscale n , where n is between 1 and 31, representing quality from best to worst.
In a sense, if you are used to the -sameq option, you are the victim of a tool that should have been at best for testing purposes. It does not give anything reasonable and can be rooted in an attempt to put the "same metadata" into a container that does not support it, or to "copy the stream" into an archaic file format (which leads to things like AVI with vorbis audio that donβt even can be played). You can hack something together, which does all of this, but it has no place in the video encoding tool.
I suggest that if you are going to do a lot of stress testing of different containers and codecs, then you install ffmpeg , which has more tools to create frankensteins. If you transcode in order to actually store the files you create or distribute them, you can create another question explaining your situation and what is your desired result.
In short: "How can I create a transcoding process with exactly the same quantizer?" Only "No" can be answered.
source share