Dolby Vision now possible through MP4 Mux.

[yusesope]

As I said, a short clip of the same movie worked. So either the tsmuxer is doing it wrong or exoplayer has a bug I suppose, since I have no idea why a clip of the whole movie would work. This is what I am trying to establish now.

edit: forgot to mention but yusesope's tool did not return any errors

Well with your short clip, you're not mixing in any atmos audio since you're using mp4muxer. When a video reverts to transcode on plex, it either can't handle the video or audio track. Since you've already established that a file without atmos works, then it's probably the atmos track that's causing the issue. How're you mixing in the atmos track with tsmuxer, and what does the resulting mediainfo look like?

I'm muxing it with tsmuxer as I always do, it worked so far for all atmos tracks I tried. but simply put, I take the generated hevc file and original m2ts file as inputs, but select only the atmos track in m2ts input. Finishes without errors.

Full movie made with mp4muxer and no audio works, but it crashed the first time I played it. mediainfo for full movie with DTS-HD MA track that's not working (thought it was Atmos initially):

From the client_broken_movie.txt file:

• Code: Select all

  [VideoUtils] MediaCodec found (OMX.Nvidia.DOVI.decode) for video/dolby-vision
  [ExoPlayer][EventLogger] decoderEnabled [0.88, 0.00, window=0, video]
  [ExoPlayer][EventLogger] decoderEnabled [0.89, 0.00, window=0, audio]
  [ExoPlayer][EventLogger] tracksChanged [0.89, 0.00, window=0, 
  [ExoPlayer][EventLogger]   Renderer:1 [
  [ExoPlayer][EventLogger]     Group:0, adaptive_supported=N/A [
  [ExoPlayer][EventLogger]       [X] Track:0, id=0, mimeType=video/dolby-vision, codecs=dvhe.04.06, res=3840x2160, fps=24.0, supported=YES
  [ExoPlayer][EventLogger]     ]
  [ExoPlayer][EventLogger]     Metadata [
  [ExoPlayer][EventLogger]       original_init_data: (Value: 0 Buffer: 117 bytes)
  [ExoPlayer][EventLogger]       scantype_progressive: (Value: 1 Buffer: 0 bytes)
  [ExoPlayer][EventLogger]     ]
  [ExoPlayer][EventLogger]   ]
  [ExoPlayer][EventLogger]   Renderer:3 [
  [ExoPlayer][EventLogger]     Group:0, adaptive_supported=N/A [
  [ExoPlayer][EventLogger]       [X] Track:0, id=1, mimeType=audio/vnd.dts, bitrate=0, codecs=dts, channels=0, sample_rate=0, supported=YES
  [ExoPlayer][EventLogger]     ]
  [ExoPlayer][EventLogger]     Metadata [
  [ExoPlayer][EventLogger]       block_align: (Value: 0 Buffer: 0 bytes)
  [ExoPlayer][EventLogger]       channel_layout: (Value: 0 Buffer: 0 bytes)
  [ExoPlayer][EventLogger]       original_init_data: (Value: 0 Buffer: 0 bytes)
  [ExoPlayer][EventLogger]     ]
  [ExoPlayer][EventLogger]   ]
  [ExoPlayer][EventLogger] ]
  [Player][ExoPlayer] Setting initial track selection...
  [Player][ExoPlayer] Switching video surface to use MediaCodec surface.
  [Player] onSurfaceChangeRequested
  [ExoPlayer][EventLogger] surfaceSizeChanged [1.02, 0.00, window=0, 0, 0]
  [ExoPlayer][EventLogger] timelineChanged [1.02, 0.00, window=0, periodCount=1, windowCount=1, reason=DYNAMIC
  [ExoPlayer][EventLogger]   period [5406.46]
  [ExoPlayer][EventLogger]   window [5406.46, true, false]
  [ExoPlayer][EventLogger] ]
  [Player][ExoPlayer] onTimelineChanged (Position: 0 ms)
  [ExoPlayer][EventLogger] decoderInitialized [1.02, 0.00, window=0, video, OMX.Nvidia.DOVI.decode]
  [ExoPlayer][EventLogger] decoderInputFormatChanged [1.02, 0.00, window=0, video, id=0, mimeType=video/dolby-vision, codecs=dvhe.04.06, res=3840x2160, fps=24.0]
  [ExoPlayer][EventLogger] decoderInitialized [1.02, 0.00, window=0, audio, OMX.google.raw.decoder]
  [ExoPlayer][EventLogger] decoderInputFormatChanged [1.02, 0.00, window=0, audio, id=1, mimeType=audio/vnd.dts, bitrate=0, codecs=dts, channels=0, sample_rate=0]
  [DisplayBehaviour] Mode switching has been disabled, as Dolby Vision is playing.

  the problem is the audio track.

  Code: Select all

  [ExoPlayer][EventLogger] playerFailed [1.14, 3.00, window=0]
  An exception occurred: com.google.android.exoplayer2.r: com.google.android.exoplayer2.s0.q$a: Unsupported channel count: 0
  Stacktrace: com.google.android.exoplayer2.r: com.google.android.exoplayer2.s0.q$a: Unsupported channel count: 0

The good news is that the Dolby Vision decoder is being successfully initialized.
At this point I assume that the FEL stream is correctly decoded.

[shawnc22]

The DTS-MA track could definitely be the issue. One last thing you might want to try is create a TS file with TSMuxer with only the video tracks. If that works, then it's probably the DTS track causing the issue.

edit: oops yusecope beat me to it!

[1000010]

Well with your short clip, you're not mixing in any atmos audio since you're using mp4muxer. When a video reverts to transcode on plex, it either can't handle the video or audio track. Since you've already established that a file without atmos works, then it's probably the atmos track that's causing the issue. How're you mixing in the atmos track with tsmuxer, and what does the resulting mediainfo look like?

I'm muxing it with tsmuxer as I always do, it worked so far for all atmos tracks I tried. but simply put, I take the generated hevc file and original m2ts file as inputs, but select only the atmos track in m2ts input. Finishes without errors.

Full movie made with mp4muxer and no audio works, but it crashed the first time I played it. mediainfo for full movie with DTS-HD MA track that's not working (thought it was Atmos initially):

From the client_broken_movie.txt file:

• Code: Select all

  [VideoUtils] MediaCodec found (OMX.Nvidia.DOVI.decode) for video/dolby-vision
  [ExoPlayer][EventLogger] decoderEnabled [0.88, 0.00, window=0, video]
  [ExoPlayer][EventLogger] decoderEnabled [0.89, 0.00, window=0, audio]
  [ExoPlayer][EventLogger] tracksChanged [0.89, 0.00, window=0, 
  [ExoPlayer][EventLogger]   Renderer:1 [
  [ExoPlayer][EventLogger]     Group:0, adaptive_supported=N/A [
  [ExoPlayer][EventLogger]       [X] Track:0, id=0, mimeType=video/dolby-vision, codecs=dvhe.04.06, res=3840x2160, fps=24.0, supported=YES
  [ExoPlayer][EventLogger]     ]
  [ExoPlayer][EventLogger]     Metadata [
  [ExoPlayer][EventLogger]       original_init_data: (Value: 0 Buffer: 117 bytes)
  [ExoPlayer][EventLogger]       scantype_progressive: (Value: 1 Buffer: 0 bytes)
  [ExoPlayer][EventLogger]     ]
  [ExoPlayer][EventLogger]   ]
  [ExoPlayer][EventLogger]   Renderer:3 [
  [ExoPlayer][EventLogger]     Group:0, adaptive_supported=N/A [
  [ExoPlayer][EventLogger]       [X] Track:0, id=1, mimeType=audio/vnd.dts, bitrate=0, codecs=dts, channels=0, sample_rate=0, supported=YES
  [ExoPlayer][EventLogger]     ]
  [ExoPlayer][EventLogger]     Metadata [
  [ExoPlayer][EventLogger]       block_align: (Value: 0 Buffer: 0 bytes)
  [ExoPlayer][EventLogger]       channel_layout: (Value: 0 Buffer: 0 bytes)
  [ExoPlayer][EventLogger]       original_init_data: (Value: 0 Buffer: 0 bytes)
  [ExoPlayer][EventLogger]     ]
  [ExoPlayer][EventLogger]   ]
  [ExoPlayer][EventLogger] ]
  [Player][ExoPlayer] Setting initial track selection...
  [Player][ExoPlayer] Switching video surface to use MediaCodec surface.
  [Player] onSurfaceChangeRequested
  [ExoPlayer][EventLogger] surfaceSizeChanged [1.02, 0.00, window=0, 0, 0]
  [ExoPlayer][EventLogger] timelineChanged [1.02, 0.00, window=0, periodCount=1, windowCount=1, reason=DYNAMIC
  [ExoPlayer][EventLogger]   period [5406.46]
  [ExoPlayer][EventLogger]   window [5406.46, true, false]
  [ExoPlayer][EventLogger] ]
  [Player][ExoPlayer] onTimelineChanged (Position: 0 ms)
  [ExoPlayer][EventLogger] decoderInitialized [1.02, 0.00, window=0, video, OMX.Nvidia.DOVI.decode]
  [ExoPlayer][EventLogger] decoderInputFormatChanged [1.02, 0.00, window=0, video, id=0, mimeType=video/dolby-vision, codecs=dvhe.04.06, res=3840x2160, fps=24.0]
  [ExoPlayer][EventLogger] decoderInitialized [1.02, 0.00, window=0, audio, OMX.google.raw.decoder]
  [ExoPlayer][EventLogger] decoderInputFormatChanged [1.02, 0.00, window=0, audio, id=1, mimeType=audio/vnd.dts, bitrate=0, codecs=dts, channels=0, sample_rate=0]
  [DisplayBehaviour] Mode switching has been disabled, as Dolby Vision is playing.

  the problem is the audio track.

  Code: Select all

  [ExoPlayer][EventLogger] playerFailed [1.14, 3.00, window=0]
  An exception occurred: com.google.android.exoplayer2.r: com.google.android.exoplayer2.s0.q$a: Unsupported channel count: 0
  Stacktrace: com.google.android.exoplayer2.r: com.google.android.exoplayer2.s0.q$a: Unsupported channel count: 0

The good news is that the Dolby Vision decoder is being successfully initialized.
At this point I assume that the FEL stream is correctly decoded.

I figured that, muxing it now with LPCM. Weird though, mediainfo looks good. And also the original file with the same audio track works fine.

[yusesope]

From the client_working_clip.txt file:

Code: Select all

Track:0, id=0, mimeType=video/dolby-vision, bitrate=65110539, codecs=dvhe.05.06, res=3840x2160, fps=24.0, supported=YES

Are you sure you have set the --dv-profile switch with the value 4 in mp4muxer?
The Shield received a track with profile dvhe.05.

[shawnc22]

Have you also tried using makemkv to just make a HDR10/DTS-MA mkv file to see how that plays? The only disk I have with DTS-MA is planet earth 2 (no DV unfortunately), and the mkvs I've made out of those play just fine in DTS on plex. The mediainfo for the audio tracks looks just like yours also:

Code: Select all

Audio #1
ID                                       : 2
ID in the original source medium         : 4352 (0x1100)
Format                                   : DTS XLL
Format/Info                              : Digital Theater Systems
Commercial name                          : DTS-HD Master Audio
Codec ID                                 : A_DTS
Duration                                 : 53 min 4 s
Bit rate mode                            : Variable
Bit rate                                 : 2 301 kb/s
Channel(s)                               : 6 channels
Channel layout                           : C L R Ls Rs LFE
Sampling rate                            : 48.0 kHz
Frame rate                               : 93.750 FPS (512 SPF)
Bit depth                                : 16 bits
Compression mode                         : Lossless
Stream size                              : 873 MiB (5%)
Title                                    : Surround 5.1
Language                                 : English
Default                                  : Yes
Forced                                   : No
Original source medium                   : Blu-ray

If the mkv you make works, then TSMuxer may be doing something funky with the audio track, or it may be a combination of a DV track and DTS audio in the same container that Plex doesn't like.

[1000010]

From the client_working_clip.txt file:

Code: Select all

Track:0, id=0, mimeType=video/dolby-vision, bitrate=65110539, codecs=dvhe.05.06, res=3840x2160, fps=24.0, supported=YES

Are you sure you have set the --dv-profile switch with the value 4 in mp4muxer?
The Shield received a track with profile dvhe.05.

I used profile 5 and it still triggered DV. Tried now with 4 and got the same result.

[variant]

A .ts file of the Shining triggered DV and the DTS track worked just fine on the shield’s internal player.

[Deihnyx]

I used the method described in the past threads.

• ffmpeg to decode the BL + EL layer

  Code: Select all

  ffmpeg -i bluray:H:\ -map 0:0 -c copy D:\output\BL.hevc -map 0:1 -c copy D:\output\EL.hevc
  

• yusesope's script to merge the layers (all counters to 100%)

  Code: Select all

  python src\bl_el_rpu_builder.py -bl D:\output\BL.hevc -el D:\output\EL.hevc -of D:\output\Full.hevc
  

• tsmuxer to remux the new hevc + truehd atmos to TS

Everything seems OK to me.

To try to understand where the problem lies, I recommend you:
Download version_0.0.3_revision_1 of my tool and start it with the command:

Code: Select all

python bl_el_rpu_builder_v0.0.3_rev_1.py -bl D:\output\BL.hevc -el D:\output\EL.hevc -of D:\output\New_Full.hevc

It is important that all the counters reach 100%, that the total number of BL AUDs is equal to those of EL Layer and that the program ends with the invitation to "press a button to exit".

If everything was ok, I recommend, before using tsMuxeR, to test only the video with mp4muxer (HERE) by trying both profile 4 and profile 7 (it takes some time).

Code: Select all

mp4muxer -i D:\output\New_Full.hevc --dv-profile 4 -o D:\output\New_Full_dvhe04.mp4

Code: Select all

mp4muxer -i D:\output\New_Full.hevc --dv-profile 7 -o D:\output\New_Full_dvhe07.mp4

If the video is displayed correctly on your devices then add the audio with tsMuxeR (as you did previously).
If that doesn't work, try creating a BL + RPU file by adding the "-mode 2" switch to my script.

Code: Select all

python bl_el_rpu_builder_v0.0.3_rev_1.py -mode 2 -bl D:\output\BL.hevc -el D:\output\EL.hevc -of D:\output\BL_RPU.hevc

Thank you,
Trying your new revision and the patched tsMuxer for profile 4 DV is recognized on my C7 and C9 while using a TS file.
However, it stutters terribly. Maybe these tvs can't handle dual layers natively?

While using the shield, it works (DV detected on the team, Atmos detected on my Denon) but only with Plex, and it crashes at start sometimes. I was never able to get DV to work with Emby on Shield.
The EL file generated by "Us" was almost 10GB, I suppose that's FEL?

Thanks

[Mortenjorstad]

You need
Eac3to 3.34
Tsmuxer
Yusesope tool v.0.0.3

First you have to make bl.hevc and el.hevc

Eac3to path to folder with DV movie 2:bl.hevc 3:el.hevc

Know you have made 2 files bl.hevc and el.hevc

Start yusesope tool and drop first bl.hevc and then el.hevc
This will make a new hevc fIle

Start tsmuxerGui
Add the file you made With yusesope tool
Add Blu-ray movie and just select the soundtrack
Mux the files together in Ts.

You will know have a movie that is DV with Atmos that will play on shield 2019

I followed the exact same steps but the final file only has 1 video stream (hdr10).

You must use this tsmuxer, if you use wrong only hdr10 is copyed

https://mega.nz/#!9m4FDJjT!1276qfyWM_tU ... 5SqsVORvSg

[shawnc22]

Thank you,
Trying your new revision and the patched tsMuxer for profile 4 DV is recognized on my C7 and C9 while using a TS file.
However, it stutters terribly. Maybe these tvs can't handle dual layers natively?

While using the shield, it works (DV detected on the team, Atmos detected on my Denon) but only with Plex, and it crashes at start sometimes. I was never able to get DV to work with Emby on Shield.
The EL file generated by "Us" was almost 10GB, I suppose that's FEL?

Thanks

The TV player cannot play Atmos audio. I'm assuming you're using Plex because the internal player would not play the audio to begin with. The stuttering is probably caused by tv plex player trying to transcode that atmos track into something playable.

[Deihnyx]

Thank you,
Trying your new revision and the patched tsMuxer for profile 4 DV is recognized on my C7 and C9 while using a TS file.
However, it stutters terribly. Maybe these tvs can't handle dual layers natively?

While using the shield, it works (DV detected on the team, Atmos detected on my Denon) but only with Plex, and it crashes at start sometimes. I was never able to get DV to work with Emby on Shield.
The EL file generated by "Us" was almost 10GB, I suppose that's FEL?

Thanks

The TV player cannot play Atmos audio. I'm assuming you're using Plex because the internal player would not play the audio to begin with. The stuttering is probably caused by tv plex player trying to transcode that atmos track into something playable.

I normally use Emby. Both Emby and Plex trigger DV on the TV player. It shows both the ATMOS track and the AC3 "Core" track. Both of them stutter. Transcoding anything in Emby will strip DV anyway, so I'm confident it's not the problem.
My only conclusion is that the C7/C9 needs DV in single layer in order to work. But from what I understand if I do produce single track single layer track I won't be able to play them with devices that can only play regular HDR, correct? Otherwise, what's the drawback in producing single track single layer files?

Emby on shield just doesn't trigger DV for some reason, but I'm guessing that's something I'll need to ask the Emby team.

[shawnc22]

Thank you,
Trying your new revision and the patched tsMuxer for profile 4 DV is recognized on my C7 and C9 while using a TS file.
However, it stutters terribly. Maybe these tvs can't handle dual layers natively?

While using the shield, it works (DV detected on the team, Atmos detected on my Denon) but only with Plex, and it crashes at start sometimes. I was never able to get DV to work with Emby on Shield.
The EL file generated by "Us" was almost 10GB, I suppose that's FEL?

Thanks

The TV player cannot play Atmos audio. I'm assuming you're using Plex because the internal player would not play the audio to begin with. The stuttering is probably caused by tv plex player trying to transcode that atmos track into something playable.

I normally use Emby. Both Emby and Plex trigger DV on the TV player. It shows both the ATMOS track and the AC3 "Core" track. Both of them stutter. Transcoding anything in Emby will strip DV anyway, so I'm confident it's not the problem.
My only conclusion is that the C7/C9 needs DV in single layer in order to work. But from what I understand if I do produce single track single layer track I won't be able to play them with devices that can only play regular HDR, correct? Otherwise, what's the drawback in producing single track single layer files?

Emby on shield just doesn't trigger DV for some reason, but I'm guessing that's something I'll need to ask the Emby team.

No, the problem is that the TV player cannot play Atmos audio, it's been said here many times. The AC3 Core track you're trying to play is not an actual audio track. Here're a couple tests you can do:

1) With the same HEVC video track you've been using from yusecope's tool, use TSMuxer to add in a different audio track from the original m2ts file, or add no audio tracks at all and see if that plays on the TV player without stuttering.
2) Use makemkv to create an mkv with the Atmos track and just the HDR10 layer. Try playing that on the Plex TV player and see if it stutters (it will).
3) Lastly, if you open the TS file that's been stuttering on the barebones internal tv player (by browsing to it through the Photos and Videos app), you'll notice that it plays perfectly in DV while you get a message saying that the Audio track is not supported.

[eblackadder]

Using MXPlayer on the shield i havent got any method to work, ive tried several in this thread (all using yusesope tool), is it supposed to work? If so please teach me, i feel like theres 10 different TSMuxer mentioned and some mentioning mp4muxer instead (which is the correct version btw? i believe there are several different programs when u google mp4muxer)

I don't get it to work as well. When i start a file(made with yusesope's tool 0.3 and the modified TS Muxer) i chose HW decoder. It works and my tv triggers Dolby Vision and my Denon receiver triggers Atmos. Then after awhile i get a message that HW decoder isn't supported. Then it goes to HW+ decoder and it triggers HDR and only Stereo on my receiver.

On Plex it runs pretty well but subs with PGS enabled made the video stop. I can solve that with an external srt file. I also feel that there is sometimes a micro stutter after awhile. Maybe that has something to do with the Shield Tv pro that i'm using? Can someone tell me when i watch a dv movie what the setting of the AI upscaler? Can i turn it off for 4k movies?

[ragico]

I have made several m2ts DV adding also the atmos/dts hd master audio tracks and all play flawlessly in the shield 2019 using Plex app.
Among them Braveheart, Cold Pursuit, The Doors, Earth: One Amazing Day (all FEL). All made using Yusesope tool v.003
There is one remaining problem to be sorted out and this is the pgs subtitles.
Any time in any movie I try to enable the subtitles the movie either stops or does not start.
May be is a Plex problem.

[1000010]

The DTS-MA track could definitely be the issue. One last thing you might want to try is create a TS file with TSMuxer with only the video tracks. If that works, then it's probably the DTS track causing the issue.

edit: oops yusecope beat me to it!

right so I made a couple of additional tests:
* ts with LPCM sound didn't work
* mp4 without sound worked
* ts short clip without sound worked
* ts full movie without sound didn't work

I find the last two points interesting. I think there might be a bug in tsmuxer that messes some things up. I will try tomorrow with m2ts if it perhaps makes a difference (I don't know either format in detail).

Client log with ts full movie without sound:

Code: Select all

03-22 21:59:14.684  e: [ExoPlayer][EventLogger] playerFailed [4.93, 0.00, window=0]
03-22 21:59:14.684  e: An exception occurred: com.google.android.exoplayer2.r: [Open]com.plexapp.plex.ff.data.FFException: Demuxer failed to open input.
03-22 21:59:14.684  i: [FF] Loading canceled (released: true)
03-22 21:59:14.685  e: Stacktrace: com.google.android.exoplayer2.r: [Open]com.plexapp.plex.ff.data.FFException: Demuxer failed to open input.
	at com.google.android.exoplayer2.v.handleMessage(SourceFile:29)
	at android.os.Handler.dispatchMessage(Handler.java:102)
	at android.os.Looper.loop(Looper.java:193)
	at android.os.HandlerThread.run(HandlerThread.java:65)
Caused by: [Open]com.plexapp.plex.ff.data.FFException: Demuxer failed to open input.
	at com.plexapp.plex.ff.FFDemuxer.open(SourceFile:31)
	at com.plexapp.plex.ff.source.FFLoadable.load(SourceFile:3)
	at com.google.android.exoplayer2.y0.a0$d.run(SourceFile:4)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
	at java.lang.Thread.run(Thread.java:764)

03-22 21:59:14.685  e: [Player][ExoPlayer] Playback error detected
03-22 21:59:14.685  e: An exception occurred: com.google.android.exoplayer2.r: [Open]com.plexapp.plex.ff.data.FFException: Demuxer failed to open input.
03-22 21:59:14.686  i: [FF] Releasing demuxer.
03-22 21:59:14.686  e: Stacktrace: com.google.android.exoplayer2.r: [Open]com.plexapp.plex.ff.data.FFException: Demuxer failed to open input.
	at com.google.android.exoplayer2.v.handleMessage(SourceFile:29)
	at android.os.Handler.dispatchMessage(Handler.java:102)
	at android.os.Looper.loop(Looper.java:193)
	at android.os.HandlerThread.run(HandlerThread.java:65)
Caused by: [Open]com.plexapp.plex.ff.data.FFException: Demuxer failed to open input.
	at com.plexapp.plex.ff.FFDemuxer.open(SourceFile:31)
	at com.plexapp.plex.ff.source.FFLoadable.load(SourceFile:3)
	at com.google.android.exoplayer2.y0.a0$d.run(SourceFile:4)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
	at java.lang.Thread.run(Thread.java:764)

03-22 21:59:14.686  i: [Player][Timeline] Handling player error
03-22 21:59:14.686  i: [Player][Timeline] Playback stopped (error: true)
03-22 21:59:14.686  i: [Player][Timeline] Unable to report progress to server as duration is unavailable.

server log:

Code: Select all

Mar 22, 2020 21:59:23.247 [0x7f5f8911f700] Error — MDE: video has neither a video stream nor an audio stream
Mar 22, 2020 21:59:23.247 [0x7f5f8911f700] Debug — MDE: received PLEX_PROTOCOL_ANY from client, but could not determine best protocol. Defaulting to HTTP
Mar 22, 2020 21:59:23.247 [0x7f5f8911f700] Debug — MDE: analyzing media item 23682
Mar 22, 2020 21:59:23.247 [0x7f5f8911f700] Error — MDE: video has neither a video stream nor an audio stream
Mar 22, 2020 21:59:23.247 [0x7f5f8911f700] Error — Streaming Resource: Cannot make a decision because either the file is unplayable or the client provided bad data
Mar 22, 2020 21:59:23.248 [0x7f5fcb088700] Debug — Completed: [192.168.0.18:34090] 400 GET /video/:/transcode/universal/decision?audioBoost=100&autoAdjustQuality=0&directPlay=0&directStream=1&directStreamAudio=1&fastSeek=1&hasMDE=1&location=lan&maxVideoBitrate=200000&mediaBufferSize=209664&mediaIndex=0&partIndex=0&path=%2Flibrary%2Fmetadata%2F13354&protocol=*&session=2344769d6696a1ac-com-plexapp-android&subtitleSize=100&videoBitrate=200000&videoQuality=100&videoResolution=3840x2160 (14 live) TLS GZIP 590ms 384 bytes (pipelined: 5)