I still think your assessment of the problem is off. I think you’re just dismissing the idea out of hand and not putting any critical thought into understanding the suggestion, and as a result you are arguing against a strawman.
@cayars said:
As an example you would never be able to direct play these files so they would have to go through the transcoder in order to be remuxed properly.  What does that do to all clients and server functions currently in place that know and understand what it means to play the “original” file?
…
Not only that be we are asking them to do this every time the file is played and to do it on every client available.
Yes and no. In my example usage scenario, I have a BDrip with h.264 video and AC3/5.1 audio. These are muxed in one file that can be ‘directly played’. Browsers / web clients do not support AC3/5.1 audio, though. To prevent a transcode, I’d normally create a “plex verion”, but that would be incredibly wasteful. The source video is already compatible and doesn’t need a “plex version”, yet I’m wasting time and SIGNIFICANT disk space to duplicate that video. I would like to just take the AC3/5.1 audio track and create a “plex version”, externally, that is compatible with whatever browsers support today.
As I understand it, plex will prioritize whatever “plex versions” with codecs which can be direct played- the remux wouldn’t need happen for clients which support the source file.
Why not just fix the source file one time and be done with it?
There is nothing wrong with the source file. Why modify my archive to be compatible with contemporary limitations of today? Browsers could gain support for AC3/5.1 in a few years. The only thing that needs “fixing” here is plex, or web client codec support.
Every client would basically need a way to adjust the delay of the sound…
I agree, that would be absolutely insane to expect of users, and although it would be nice to have that functionality in plexmediaplayer (where it already exists in mpv and just needs to be exposed), I also agree it wouldn’t be worth the time to implement that in every plex client.
But!
Maybe the technical details of this are above me, but I really do not understand why you think any solution to this problem would involve the user manually syncing audio. How can mpv, vlc, mpc-hc keep an external audio track in sync? How does youtube keep its very many DASH streams in sync? Heck, how does the plex transcoder keep transcoded audio + video streams in sync? Why is it you think it can’t be done? Why is a rather old feature of mpv/vlc/mpc-hc/youtube “magic” to you?
Before we can continue this discussion, we need to separate the terms “keeping in sync” and “delay/offset”. I think up until this point, you have been using them interchangeably.
A delay/offset would only be necessary if the audio file does not match the video. Again, this is not a plex problem, it is up to the user to hardcode the delay into the file themselves. This problem will not arise if the audio file is literally a transcoded version of the source file.
Keeping in sync is, as I understand it, the player adjusting timings on the fly to correct de-synchronizations introduced by the computer itself. This is… a basic component of a video player and nothing is “magic” about it.
BTW, does anyone know of any streaming software similar to Plex that does anything like this?
YouTube’s DASH streaming system.
By all means DO put in a formal request for this feature it in the proper section of the website (request forum) and see if you can get support for it from the users. That’s the proper way to request features and to see how important features are to users so Plex knows where to spend it resources on new features.
Sorry, I thought that’s what this was (I didn’t start this topic). Also, and this is a genuine comment, I’m not being snide: I’m just used to participating in projects where features are implemented because they make sense, not by popular vote 