Stavros Avramidis

How do you know the encoder will be `MQAEncode v1.1, 2.3.3+800` ? Also I don't think anyone would run that on android :P

The only problem i have is the MQAEncode Encoder version. If it's fixed and tag modification is passed as argument I'm oke to merge this

Just to be clear the MQA program get's those parameters (if missing) from the MQA metadata buried in the stream. I don't like the idea of just putting unaccurate metadata...

Yes, I get it. My problem is that the mqa encoder version is hardcoded. Not validated to be accurate. The purpose of this repository is to provide tools /& reverse...

I'm bit confused. So you checked an MQA-CD file from 2018. And the MQA's app put an encoder with version of 2022 ?

Ok, I see. So the whole string is the same ? and the checksums ? In that case I recommend the following suggestion `MQAEncode v1.1, 2.4.0+1053 (278f5dd), E24F1DE5-32F1-4930-8197-24954EB9D6F4, MMM DD...

I meant the checksum on the string of it belongs to the decoder. If so with the datetime suggestion fixed I'm okay to merge

Yes roon is in .NET. I have decompiled it with dotPeek and didn't found something. Although my C# knowledge stops when the \# starts so there might be more there....

I don't find a good reason why they would :P

@moodmosaic Please stay on topic. The issue here is to reverse engineer the mqa soft decoder, not a forum to discuss what MQA has to do.