2023-11-19, 12:32 AM
log shows the same thing so no doubt it had the same problem
Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))
Stream #0:1 -> #0:1 (ac3 (native) -> aac (libfdk_aac))
means it's being transcoded, if direct playing it would say (copy)
since it's going h264->h264 then video codec shouldn't be the reason
since it's going ac3->aac audio channels are potential is why i mentioned the downmix setting
but most likely is bandwidth limits
there should be another log on the server than that, it should contain something that says "TranscodeReason" and that's what needs to be determined
as far as im concerned that device should not have issues with h264 or ac3, they are fairly standard
Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))
Stream #0:1 -> #0:1 (ac3 (native) -> aac (libfdk_aac))
means it's being transcoded, if direct playing it would say (copy)
since it's going h264->h264 then video codec shouldn't be the reason
since it's going ac3->aac audio channels are potential is why i mentioned the downmix setting
but most likely is bandwidth limits
there should be another log on the server than that, it should contain something that says "TranscodeReason" and that's what needs to be determined
as far as im concerned that device should not have issues with h264 or ac3, they are fairly standard