Run Into a Sad Face While Playing Video

#4

@sam_nazarko I’ll reproduce the crash using the July firmware and then see if it still happens on the August. If it does, I’ll post the August firmware’s log too.

0 Likes

#5

FW 2018.07-1 log - had to run through the scene 5x before it crashed.

FW 2018.08-1 log - had to run through the scene 3x before it crashed.

On both instances, resolution stayed at 1080p after the crash. Hope this helps.

P.S. This is only related to OTA update - I ran into a sad face after update and reboot. Rebooted again and sad face didn’t appear anymore. Should I post on a new thread? Or just leave it alone?

0 Likes

#6

If you get one sad face on an update, you don’t need to worry about it.
I’ll check the logs shortly.

Sam

1 Like

#7

Tried this same video on Vero 4K+ running FW 2018-08-2 and it’s still crashed.

0 Likes

#8

Something seems to be off with the file you are trying to play or at least with the media info you posted. I found the file you are trying to play and the media info of it looks like this:

General
Unique ID : 315678901853956885238136447738850784762 (0xED7D8B84693728F91CB21B849EB335FA)
Complete name : Blue.Planet.II.2017.S01E03.Coral.Reefs.2160p.DTS-HD.MA.5.1.HEVC.HYBRID.REMUX-FraMeSToR.mkv
Format : Matroska
Format version : Version 4 / Version 2
File size : 16.8 GiB
Duration : 48 min 52 s
Overall bit rate : 49.1 Mb/s
Movie name : Blue Planet II (E03) Coral Reefs
Encoded date : UTC 2018-07-05 08:19:48
Writing application : mkvmerge v23.0.0 (‘The Bride Said No’) 64-bit
Writing library : libebml v1.3.6 + libmatroska v1.4.9

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Commercial name : HDR10
Format profile : Main 10@L5.1@High
Codec ID : V_MPEGH/ISO/HEVC
Duration : 48 min 47 s
Bit rate : 45.4 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 25.000 FPS
Original frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.219
Stream size : 15.5 GiB (92%)
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0050 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 1000 cd/m2
Maximum Frame-Average Light Level : 120 cd/m2

Audio
ID : 2
Format : DTS
Format/Info : Digital Theater Systems
Format profile : MA / Core
Codec ID : A_DTS
Duration : 48 min 52 s
Bit rate mode : Variable / Constant
Bit rate : 3 840 kb/s / 1 509 kb/s
Channel(s) : 6 channels
Channel positions : Front: L C R, Side: L R, LFE
Sampling rate : 48.0 kHz
Frame rate : 93.750 FPS (512 SPF)
Bit depth : 24 bits
Compression mode : Lossless / Lossy
Delay relative to video : 5 ms
Stream size : 1.30 GiB (8%)
Title : DTS-HD MA 5.1
Language : English
Default : Yes
Forced : No

Text
ID : 3
Format : PGS
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Duration : 48 min 10 s
Bit rate : 23.3 kb/s
Count of elements : 688
Stream size : 8.03 MiB (0%)
Title : English (SDH)
Language : English
Default : No
Forced : No

Menu
00:00:00.000 : en:Chapter 1
00:09:06.319 : en:Chapter 2
00:20:23.159 : en:Chapter 3
00:29:23.400 : en:Chapter 4
00:36:06.239 : en:Chapter 5

Sadly I don’t have a 4k tv to test.

Edit:

I was thinking about this since I can’t test it myself I can give you a sample of my file and you or someone from the osmc team can test it to see if the issue is with your file or something else.

Is only this episode affected ? Or is the whole Blue Planet II giving you problems ?

0 Likes

#9

@k2u3 so far I’ve tried 1-3, only 3 gives me that crash. On that specific scene. I also tried on a Wetek Hub (LE 8.2.5 official) and it doesn’t crash.

0 Likes

#10

Anything I can do to help?

0 Likes

#11

Will look at this soon.

0 Likes

#12

I was able to find out that the audio on the UHD disc had very noticeable compression artifacts. That’s why the people that released the remux I posted media info of used the 24bit audio from the regular German Blu-ray disc that had to be synced. The framerate of the video, subtitles and chapters had to be changed from 23.976fps to 25fps to match that of the audio. This also explains why it says HYBRID REMUX in the file name. Hybrid meaning they used multiple discs to make a the remux.

I’m just guessing but Maybe if @eagerbeaver is trying to play the Original media from the UHD those artefacts could have caused osmc to crash

0 Likes

#13

@k2u3 Does this mean there’s no fix for this?

This one still occurs on November 2018 update (OSMC_TGT_vero3_20181101.img.gz)

0 Likes

#14

Sorry for the late reply.
Can I get a small MKV sample to reproduce this?

Cheers

Sam

0 Likes

#15

Sure

0 Likes

#16

I just watched the 3rd episode in 2160p on my 1080p SDR TV and my vero 4k+ didn’t crash and I also haven’t had any other issues other then that the picture could have been a bit brighter.

0 Likes

#17

HDR -> SDR improvements are planned

Cheers

1 Like

#18

Following up on this. Using test build 2019.04-1 and problem still persists. New log

0 Likes

#19

Are you sure a part of the file you are trying to play is not just somehow corrupted and it has nothing to do with the vero ? Have you tried a different version of the same content ?

0 Likes

#20

The problem is inconsistent. Sometimes it would crash, other times it plays normally. Same file.

If it was corrupted, wouldn’t it manifest the crash 100% of the time? Tell me if I’m wrong.

0 Likes

#21

What you wrote here makes me think that If you skip over the bit of the file that is corrupted it won’t crash but if you don’t skip over it it will.

But I’m no expert let see what @sam_nazarko or someone else from the team has to say

0 Likes

#22

Hi,

If the issue is only occurring with one video, have you tried ripping again from the original source? Looks like corruption to me.

Tom.

0 Likes

#23

Will try again.

0 Likes