The .m4a files are within the specifications that is why I report them, if you see in the post that I publish all the characteristics of the m4a file in question with all the details I leave it here so you can review it again MCX8000 .m4a files and engine prime, it is not a problem of incompatibility according to the specifications of the MCX8000 but of engine prime when not recognizing it as compatible in fact the controller reproduces them if they are not analyzed with engine prime according to the data of the MCX8000 https://1d2f8a47519b3dc0b576-fff53f927840131da4fecbedd819996a.ssl.cf2.rackcdn.com/Uploads/MCX8000-UserGuide-v1.1.pdf
File Formats AAC (CBR / VBR, 44.1 kHz, stereo 64-320 kbps), the .m4a files are encoded at 320 VBR which according to the above meets the specifications, I do not understand what is referred to is not a valid standart, in that post there was a lot of debate on the subject and the final conclusion was that it was an engine prime problem because of its way of determining if the file is compatible or not.
“As and when needed” and who decides this? a bug is a bug and should be corrected in the shortest time when it is notified I do not think we should have a new computer (we have less than a year with it) with much less errors that continue to leave the factory with known bugs, is my opinion
excuse me English
regards