How do I find out why something is direct streaming?

[crusher11 1101]

Dashboard doesn't say, stats for nerds doesn't say. 

[vdatanet 1617]

Direct streaming is a symptom of unsupported audio or container. If you look the remuxing you can see the reason:

TranscodeReasons=AudioCodecNotSupported

If the container is not supported, you will see something like TranscodeReasons=ContainerNotSupported

[crusher11 1101]

Look where? 

[vdatanet 1617]

2 minutes ago, crusher11 said:

Look where? 

Sorry, the remuxing log

[crusher11 1101]

There isn't a remux log, only a directstream log, and "transcodereason" does not appear in it.

 

[vdatanet 1617]

2 minutes ago, crusher11 said:

There isn't a remux log, only a directstream log, and "transcodereason" does not appear in it.

 

Can you post that log? If it's only directstream, container is most likely not supported and HLS stream is created copying audio and video.

[crusher11 1101]

I found it in the main log and yeah, it says container not supported.

But it's in an MKV, same as everything else on my server.

 

[vdatanet 1617]

15 minutes ago, crusher11 said:

I found it in the main log and yeah, it says container not supported.

But it's in an MKV, same as everything else on my server.

 

Post the log. What client device are you using?

[crusher11 1101]

LG TV. It's pretty cluttered with other irrelevant remuxes and transcodes and such, I'll generate a clean one in a bit.

 

[vdatanet 1617]

Just now, crusher11 said:

LG TV. It's pretty cluttered with other irrelevant remuxes and transcodes and such, I'll generate a clean one in a bit.

 

No, I was talking about the direct stream log, although the server log could also be useful.

[crusher11 1101]

I assume it's one of these. Or all of them, maybe I stopped and started at some point or something.

ffmpeg-directstream-2811217c-469d-4995-a662-f1f347337180_1.txt ffmpeg-directstream-35c1ff0b-e022-4be3-b965-bc2f18864414_1.txt ffmpeg-directstream-00c9fb91-d351-4fb4-908f-ebf109b06ecf_1.txt

[vdatanet 1617]

They are the typical container not supported logs, why is unknown to me, maybe the server log shows more information.

[crusher11 1101]

Here.

 

embyserver.txt

[vdatanet 1617]

I can't see the reason why not it direct plays, maybe @Luke can help

[bakes82 167]

The admin UI tells you when you click the i on the stream.

 

[crusher11 1101]

That's only true of transcoding, not of direct streaming.

 

[vdatanet 1617]

The reason is container not supported, but why? The device seems to support that container.

[bakes82 167]

Stream usually means its unpacking the original file from the container.  IE a mp4 is wrapped in a mkv, its unwrapping the mkv and streaming you the mp4.

I have TS files for DV and they transcode as non supported.  IDT ive ever seen a stream yet.

[bakes82 167]

[vdatanet 1617]

3 minutes ago, bakes82 said:

Yes, we know that the problem is why happens this when container is supported?

[bakes82 167]

Your device doesnt support something.  Probably HDR.

[bakes82 167]

I play 1917 remux on PC non HDR monitor stream, I play it on HDR/DV TV with shield, direct play.

[vdatanet 1617]

4 minutes ago, bakes82 said:

I play 1917 remux on PC non HDR monitor stream, I play it on HDR/DV TV with shield, direct play.

There's no remux here, only streaming. Audio and video is copied as is.

[bakes82 167]

Just now, vdatanet said:

There's no remux here, only streaming. Audio and video is copied as is.

Playing a REMUX version of the file ..... not a WEB-DL version.  Does the file youre playing have HDR?  Does the device your playing it on support HDR?   HDR is another "track"/"stream" of the file I believe so if the device youre playing it on doesnt do HDR it seems plausible it would just "stream" the non HDR track.

[crusher11 1101]

HDR isn't another stream, and this isn't HDR anyway.

It's saying the container isn't supported, even though it's MKV.