[fandangos]

removed the link, made a mistake that I need to fix before posting it.

[fandangos]

Ok, I think this will work out better. 

I'm only having problems if the source of the remuxes is too slow. 
If I access those remuxes on my NAS, no problem, if it's on a cloud storage, it may or may not work. 

Same with the previews build: delay set to zero if using change refresh.
Try with buffer 2 and 3.

https://mega.nz/file/XEdm2LAZ#efDt63w4JU...apxFvQ2Oeg

What I think it's happening is that Kodi is hammering the shield (bugged firmware) with requests to set mode. 
So, what I simply did is that, if an error is present, wait 1 second, reset, wait 1 second.

I don't think I have as much problem like you guys are having on my setup so that's hard to replicate here.

[JGrana01]

I agree that the problem/crash occurs before any part of the video is displayed. I should have been clearer on the crashes. The spinning wheel happens, the upper part of the display shows the name of the file and the "play" icon, but the display dims, wheel spins and....when you press "Stop"...crash.
BTW, this only happens with .mkv files. The .mp4's seem to play just fine.

Did you simply try to press the "Back" button on the remote?

I use the default remote which doesn't have a "Stop" key. When I am in the same situation with the spinning wheel and press the "Back" button, it is possible to choose another file, for example the P81.mkv to "repair the faulty start". 

Regards Hoppel

No, I pressed Stop. Shortly after, Kodi crashes. The next time I get the spinning wheels of death I will try Back.
BTW, things are still inconsistent as far as P4. I set the Shield back to 30 hz refresh (left Kodi at 29.97 hz), put the Shield to sleep and tried again this morning.
P4 started fine... No P8 needed.

[hoppel118]

The next time I get the spinning wheels of death I will try Back.

SWOD = spinning wheels of death

Fantastic!!! 

[rexian]

Ok, I think this will work out better. 

I'm only having problems if the source of the remuxes is too slow. 
If I access those remuxes on my NAS, no problem, if it's on a cloud storage, it may or may not work. 

Same with the previews build: delay set to zero if using change refresh.
Try with buffer 2 and 3.

https://mega.nz/file/XEdm2LAZ#efDt63w4JU...apxFvQ2Oeg

What I think it's happening is that Kodi is hammering the shield (bugged firmware) with requests to set mode. 
So, what I simply did is that, if an error is present, wait 1 second, reset, wait 1 second.

I don't think I have as much problem like you guys are having on my setup so that's hard to replicate here.

Tried the new build and here is how it went -

1. Kodi Settings > Display > refresh rate set to 29.97 - 1st screenshot
   
2. Kodi Settings > Player > Adjust display refresh rate set to OFF - 2nd screenshot
   
3. Played P5 / 60Hz sample (since it gave me most trouble before) and it played fine - 3rd screenshot
   
4. Played P4 / 23Hz sample - got spinning wheel. Pressing back repeatedly didn't help. Had to go to the Shield Home by pressing Home button on Shield remote and then kill it. Forgot to take the screenshot but was able to replicate later.
   
5. After killing Kodi, again started it. Went to play P4 / 23Hz sample with Kodi still set to 29.97 - it played fine this time - 4th screenshot
   
6. Tried playing P81 / 59Hz sample and it played fine too - no screenshot
   
7. Went back to Kodi Settings > Display > refresh rate and set to 23.98 - 5th screenshot
   
8. Tried P5 / 60Hz sample again and it still played fine - 6th screenshot
   
9. Next tried P4 / 23Hz sample and this time it played fine without any issues - 7th screenshot
   
10. Then tried P7 FEL and got the spinning wheel - 8th screenshot
    
11. Waiting a few seconds or pressing back didn't help and had to exit to Shield Home screen with Home button. And then killed Kodi from Shield home - 9th screenshot
    

Screenshots here. Will try with adjust refresh rate to "on start/stop" later.

[yop16]

Ok, I think this will work out better. 

I'm only having problems if the source of the remuxes is too slow. 
If I access those remuxes on my NAS, no problem, if it's on a cloud storage, it may or may not work. 

Same with the previews build: delay set to zero if using change refresh.
Try with buffer 2 and 3.

https://mega.nz/file/XEdm2LAZ#efDt63w4JU...apxFvQ2Oeg

What I think it's happening is that Kodi is hammering the shield (bugged firmware) with requests to set mode. 
So, what I simply did is that, if an error is present, wait 1 second, reset, wait 1 second.

I don't think I have as much problem like you guys are having on my setup so that's hard to replicate here.

hello is possible compili any version for shield stick?

[fandangos]

Ok, I think this will work out better. 

I'm only having problems if the source of the remuxes is too slow. 
If I access those remuxes on my NAS, no problem, if it's on a cloud storage, it may or may not work. 

Same with the previews build: delay set to zero if using change refresh.
Try with buffer 2 and 3.

https://mega.nz/file/XEdm2LAZ#efDt63w4JU...apxFvQ2Oeg

What I think it's happening is that Kodi is hammering the shield (bugged firmware) with requests to set mode. 
So, what I simply did is that, if an error is present, wait 1 second, reset, wait 1 second.

I don't think I have as much problem like you guys are having on my setup so that's hard to replicate here.

hello is possible compili any version for shield stick?

Let's wait.
The things I did might have no impact at all.


The problem testing this is that we have "this file works but suddenly it does not".

What we need is a methodology that ALWAYS results in a problem.
Like: play this file, play that file and it will always hang.

And this has to be true without refresh rate change so it's 100% shield's fault and we can think on a workaround because I doubt nvidia will care at this point.

[hoppel118]

Hi @fandangos,

I also checked your new build now. It was better for the P7FEL mkv test file. I had the chance to play that file 25 times in a row without an error, but then Kodi "crashed". It was still possible to navigate in Kodi, but not possible to start any mkv test file again. It was also not possible to repair the Kodi player by starting the P81 mkv test file. For the P4 and the P7MEL mkv test files it was the same as before. I could start/play3secs/stop it two or three times and Kodi Player died (I call it a "faulty start" in my github post).  
 

The problem testing this is that we have "this file works but suddenly it does not".

What we need is a methodology that ALWAYS results in a problem.
Like: play this file, play that file and it will always hang.

And this has to be true without refresh rate change so it's 100% shield's fault and we can think on a workaround because I doubt nvidia will care at this point.

Yes, absolutely! Everybody has a different understanding in how to test. I tried to describe my test cases, but now you wrote that it must be without refresh rate changes:

https://github.com/xbmc/xbmc/pull/18965#...-753479715

We can try to find the test cases always resulting in an issue again. But before we do this, we need to know the right settings for Android and Kodi.

Can you please copy and paste my settings from my github post and correct/delete wrong options/values?

Thank you very much.

Best regards Hoppel

[fandangos]

Hi @fandangos,

I also checked your new build now. It was better for the P7FEL mkv test file. I had the chance to play that file 25 times in a row without an error, but then Kodi "crashed". It was still possible to navigate in Kodi, but not possible to start any mkv test file again. It was also not possible to repair the Kodi player by starting the P81 mkv test file. For the P4 and the P7MEL mkv test files it was the same as before. I could start/play3secs/stop it two or three times and Kodi Player died (I call it a "faulty start" in my github post).  
 

The problem testing this is that we have "this file works but suddenly it does not".

What we need is a methodology that ALWAYS results in a problem.
Like: play this file, play that file and it will always hang.

And this has to be true without refresh rate change so it's 100% shield's fault and we can think on a workaround because I doubt nvidia will care at this point.

Yes, absolutely! Everybody has a different understanding in how to test. I tried to describe my test cases, but now you wrote that it must be without refresh rate changes:

https://github.com/xbmc/xbmc/pull/18965#...-753479715

We can try to find the test cases always resulting in an issue again. But before we do this, we need to know the right settings for Android and Kodi.

Can you please copy and paste my settings from my github post and correct/delete wrong options/values?

Thank you very much.

Best regards Hoppel

That's the thing... there's no right setting. 
There are settings that may/may not overcome a problem.

A good starting point would be: with kodi with all default settings, play a file:
it works? good.
Change a setting. It works? It does not work.

So the problem is how the settings interact with the video file and not the video file or kodi itself. 

Starting and stopping a player 25 times in a row is not a a real world use case. 
A car can drive fine but if you turn it on, drive 2 meters, turn it off, turn it on, drive 2 meters repeat.. this is not how you drive a car and it may fail LoL

Not sure if that makes sense but I don't think it's something worth pursuing to fix.

What I think it's worth investigating is P7MEL, that's a profile used for remux correct?
Can you name one movie that has this profile so I can hunt it and test here?

Also does P7MEL crashes/hangs if you just start the shield and play?

[hoppel118]

That's the thing... there's no right setting. 
There are settings that may/may not overcome a problem.

A good starting point would be: with kodi with all default settings, play a file:
it works? good.
Change a setting. It works? It does not work.

So the problem is how the settings interact with the video file and not the video file or kodi itself. 

Ok, that’s something we can work with. We have to start with Kodi default settings.

Starting and stopping a player 25 times in a row is not a a real world use case. 
A car can drive fine but if you turn it on, drive 2 meters, turn it off, turn it on, drive 2 meters repeat.. this is not how you drive a car and it may fail LoL

Not sure if that makes sense but I don't think it's something worth pursuing to fix.

Yes, I am aware of it not being a real world use case. That’s my final point/question in my GitHub post.

But sometimes I had the problem that a file was not starting, even though it was the first file I played after an HDMI reset and a Kodi restart.

What I think it's worth investigating is P7MEL, that's a profile used for remux correct?
Can you name one movie that has this profile so I can hunt it and test here?

We have to investigate in P7FEL and P7MEL. MakeMKV gives us both in relation to the source content.

Let me look for real movies in P7FEL/P7MEL. Will post them later.

Also does P7MEL crashes/hangs if you just start the shield and play?

Yes, that brought me to my test cases (start/play3secs/stop). I didn’t see this with any kind of file format in the past.


Regards Hoppel

[hoppel118]

Here is a "complete" list of DV movies with FEL/MEL information: https://forum.blu-ray.com/showthread.php?t=276448

Maybe it's also possible to determine this information with latest MediaInfo. But I don't know where to look.
 

• Download and install latest MediaInfo (version: 20.09): https://mediaarea.net/de/MediaInfo/Download 
  
• Open MediaInfo, configure "View - Tree"
  
• Drag and drop a movie to the MediaInfo window
  

Here you see some DV information under "Video - HDR format", for example something like this:

Dolby Vision, Version 1.0, dvhe.07.06, BL+EL+RPU, Blu-ray compatible / SMPTE ST 2086, HDR10 compatible


Do you or anybody else here know where to look at for FEL/MEL information? 

Regards Hoppel

[fandangos]

Ok, I was testing here with Lord of The Rings, I have some FEL mkv files, I'll try it during the next few days.

[hoppel118]

Yep, both triologies "lord of the rings" and "hobbit" are MEL. I recognized some discussion of it not being FEL.

[hoppel118]

@fandangos How does your test case looks like?

Should we wait for a new build from you or should we test with Kodi default settings?

What I don’t understand is... Why the hell does Emby such a good job in playing P7FEL and P7MEL files? Where is the difference in file handling between Exoplayer and FFmpeg?

Regards Hoppel

[fandangos]

@fandangos How does your test case looks like?

Should we wait for a new build from you or should we test with Kodi default settings?

What I don’t understand is... Why the hell does Emby such a good job in playing P7FEL and P7MEL files? Where is the difference in file handling between Exoplayer and FFmpeg?

Regards Hoppel

Well.. Exo Player got a proper support to dv mkv.

We are using a implementation that we had to cherry pick by the plex team on ffmpeg.
FFmpeg does not support dv mkv yet.