Michel Bardiaux wrote:
Baptiste Coudurier wrote:
Hi,
Michel Bardiaux wrote:
Baptiste Coudurier wrote:
Michel Bardiaux wrote: [time for a big snip]
Michael has reported 13200 in aiff, do you also see 13200 for mov? Then accepting (OK, silently) 0, 13000 and 13200 when decoding solves your problem while leaving some safety. Yes. OK then, my proposition is that on decoding, all 3 are accepted silently, anything else causes a warning (but is accepted); on encoding, anything else than 13000 elicits a warning and is forced to 13000.
Ok with this spec, or is it necessary to tolerate 13200 on encoding too because some muxer sets 13200 before init is called?
Well you can check in the code, that is mov and aiff, I guess.
But I can't find a way to know, in libgsm_init, whether it is called for enc or decoding. My mistake or is there none?
You can check with AVCodecContext->AVCodec symbol I think.
You mean, compare AVCodecContext->AVCodec->encode vs. NULL, right?
That is one solution if it works. -- Baptiste COUDURIER GnuPG Key Id: 0x5C1ABAAA SMARTJOG SAS http://www.smartjog.com Key fingerprint 8D77134D20CC9220201FC5DB0AC9325C5C1ABAAA Phone: +33 1 49966312