Xbox One X Movies slowly get to the point they freeze

[BurntTech 6]

It appears the FPS slowly drops until it goes below 1x speed and then won't play at all. This happens at different times based on movies (Guessing movie size). By switching from atmos/7.1 to 5.1 the issue is no longer an present. The log file attached is the 7.1 movie doctor strange. Also attached 5.1 log it appears to also be dropping fps over time.

embyslowfreeze.log

embyslowfreeze.log

embyslowfreeze51.log

[Luke 37060]

@@softworkz

[softworkz 3335]

@@BurntTech

 

The log files look fine. What kicks in here is the transcode throttling feature, thus it is expected behavior that the speed is approaching 1.0x over time.

 

I just got no idea right now, why playback would freeze. Does it work when you disable throttling from the Transocding settings page?

[BurntTech 6]

The part that is weird is we tried the same movie from scratch few times and it freezes within the minute. For doctor strange it was 52 mins I think. This made me think its about movie size. 

[softworkz 3335]

It's never about size, but I guess you still meant the right thing, which would be bitrate. (both, input and output rate can be relevant depending on the case)

 

Does it happen with all videos or just specific one(s)?

Did you try to disable throttling?

 

The only thing I can imagine would be an issue with timing calculation.

The throttle feature is targeting for a 120s ahead buffer.

You video is 114min and the buffer seems to approach zero length after 52min which is approximately the half of it...

 

When you look at the seekbar during playback, does the displayed timing appear to be correct?

 

Does it happen with other clients (e.g. the web client) or does that occur with the Xbox only?

[BurntTech 6]

During the first freeze for this log was stopped, I started it and it did the typical bouncing back between a 15 seconds. The server dashboard shows the same thing of bouncing times. You can't seek while this issue is happening. When switching from 7.1 to 5.1 it would create a new remux so that would explain why it works. The bitrate must just be same enough. Would out of diskspace or ram be logged any where? Last Idea I had was speed writing to cache? 

[Luke 37060]

Can you try performing the test that he requested? Thanks.

[softworkz 3335]

During the first freeze for this log was stopped, I started it and it did the typical bouncing back between a 15 seconds. The server dashboard shows the same thing of bouncing times. You can't seek while this issue is happening. When switching from 7.1 to 5.1 it would create a new remux so that would explain why it works. The bitrate must just be same enough. Would out of diskspace or ram be logged any where? Last Idea I had was speed writing to cache? 

 

@@BurntTech - I'm afraid, I don't understand most of your reply.

 

Would you mind answering the following questions:

1. Does it happen with all videos or just specific one(s)?
2. Did you try to disable throttling?
3. When you look at the seekbar during playback, does the displayed timing appear to be correct?
4. Does it happen with other clients (e.g. the web client) or does that occur with the Xbox only?

One, two, three, four.... :-)

[BurntTech 6]

Got some testing done during the holidays

1. No doesn't happen during every movie (trying to determine if its 7.1 audio movies) Angry birds also has which is also a MKV but direct streams also has 5.1 audio and works

2. Disabled throttling didn't fix the freeze but it did allow me to seek past it (Movie completed direct steaming red bar a few minutes after the movie started )

3. The times seem correct, noting when it does freeze it goes back forth between a few seconds

4. When I used windows desktop app the movie direct plays (doesn't direct stream) and works correctly for dr strange. 

 

If it would be helpful I can try to get the remux log of Doctor strange with throttling disabled.

[Luke 37060]

@@softworkz, any idea why turning the throttle on/off would affect seeking?

[softworkz 3335]

@@softworkz, any idea why turning the throttle on/off would affect seeking?

 

 

The only thing I can imagine would be an issue with timing calculation.

The throttle feature is targeting for a 120s ahead buffer.

You video is 114min and the buffer seems to approach zero length after 52min which is approximately the half of it...

[softworkz 3335]

Got some testing done during the holidays

1. No doesn't happen during every movie (trying to determine if its 7.1 audio movies) Angry birds also has which is also a MKV but direct streams also has 5.1 audio and works

2. Disabled throttling didn't fix the freeze but it did allow me to seek past it (Movie completed direct steaming red bar a few minutes after the movie started )

3. The times seem correct, noting when it does freeze it goes back forth between a few seconds

4. When I used windows desktop app the movie direct plays (doesn't direct stream) and works correctly for dr strange. 

 

If it would be helpful I can try to get the remux log of Doctor strange with throttling disabled.

 

Thanks very much for testing these things.

 

for #4 - could you try to force transcoding with the desktop app (e.g. by reducing the max bandwidth)

 

Back to the Xbox - during playback, when you look at the server dashboard from a browser, you're seeing card(s) indicating the client connections and ongoing playback sessions.

When you look at the playback position time on the dashboard and compare it to the playback position displayed on the xbox, are you seeing the same values at both places?

When you take a stopwatch and watch the time progress, is that approximately realtime? (no need to check precisely, just check that it's not half or double speed)

[BurntTech 6]

I forced 720p on dr strange and everything worked fine. I suspect that it brought down the audio 5.1 is why that worked. I set the max bitrate to 4mbps and said play movie in 7.1. I'll get the timings when I get back to see if the timings are off.

 

Output #0, segment, to '/var/db/emby-server/transcoding-temp/88015f079413ad2eaf6c2b95416b2a9a%d.ts':

  Metadata:

    encoder         : Lavf58.12.100

    Stream #0:0: Video: h264 (libx264), yuv420p, 1280x720 [sAR 1:1 DAR 16:9], q=-1--1, 23.98 fps, 90k tbn, 23.98 tbc

    Metadata:

      encoder         : Lavc58.18.100 libx264

    Side data:

      cpb: bitrate max/min/avg: 3616000/0/0 buffer size: 7232000 vbv_delay: -1

    Stream #0:1: Audio: ac3, 48000 Hz, 5.1, fltp (24 bit), 384 kb/s (default)

    Metadata:

      encoder         : Lavc58.18.100 ac3

[Luke 37060]

Thanks for the info.