Universal Media Server | Forum

Nice find

f: is format - which is often, but not always, the same as file extension. MP4/M4A is an exception, where a "special rule" designates MP4 to "format M4A" if the MP4 file contains only one audio track and no video. UMS classified these files as MP4 from the start (regardless of the extension, this is...

f:acc m:audio/x-m4a ..is invalid too. Luckily, since "acc" files doesn't exist, it never gets a match, which would have resulted in strange results, sending a non-existing format without transcoding using "audio/x-m4a" :lol: I've found mentioned on the net that M4A files are "sometimes" using the "...

Feed both files into a diff application, for example https://www.diffchecker.com/, and you will see what has been modified.

Doesn't do what you think. It matches all M4A (MP4 with only one audio track) files AND all AAC files. It accepts any codec. The problem is that there is no "AAC format", AAC is an audio codec, not a file format.

I don't remember all the "flags" myself, but f:, a: v: and m: are pretty clear to me. "f:" is the (file) format/container, "a:" is the audio codec, "v:" is the video codec (where relevant) and "m:" is the MIME type to send. There are others, but I don't remember them all. The expressions after ":" a...

The trace log is needed to see the ProtocolInfo UMS serves the TV, which decides what the TV does with a given media. The closest thing to documentation of the "supported" lines is found in DefaultRenderer.conf. The supported line relevant for M4A that you listed is: Supported = f:m4a|alac m:audio/m...

The way I described is really simple once you have done it once or twice ;) No installation necessary, just Git check out and F5 (refresh) and F11 (debug run) in Eclipse. It just sounds more complicated when I try to explain :roll: I don't know if you installed TortoiseGit or not, but if you did, si...

Read the red text above for how to create useful logs.

Still no log.