0
By using below command changing the channel map but after successful run input wav file header is not matching with an output
ffmpeg -i in.wav -af "channelmap=13|14|15|0|1|2|3|4|5|6|7|8|9|10|11|12" out.wav
0
By using below command changing the channel map but after successful run input wav file header is not matching with an output
ffmpeg -i in.wav -af "channelmap=13|14|15|0|1|2|3|4|5|6|7|8|9|10|11|12" out.wav
2Which software is complaining about the header? And what's the error msg? – Gyan – 2019-07-22T17:41:01.440
I am checking both the files in HexPad – Varadaraju G – 2019-07-23T06:52:41.603
ffmpeg will usually add a info chunk with encoder info. Why do the headers need to match? – Gyan – 2019-07-23T10:25:11.470
Is there any chance to avoid this? – Varadaraju G – 2019-07-23T10:41:25.280
We can avoid some metadata, yes, but since I don't know what your source header looks like, I don;t know if ffmpeg can match it. – Gyan – 2019-07-23T10:47:11.830
by using flag -bitexact, avoided some bytes. but I need to avoid all – Varadaraju G – 2019-07-23T11:26:25.590
Let us continue this discussion in chat.
– Varadaraju G – 2019-07-23T11:31:38.163