That’s odd. I always encode my videos with a 29.97fps frame rate because there used to be a problem with 24fps way, way back. I haven’t seen any problems with 7.1 firmware, so I wonder if it’s something else. As a test, you might want to re-encode the original with ffmpeg to 29.97fps and see what happens. Maybe the frame rate change is a red herring and it was just re-encoding it that “fixed” it.
I tried re-encoding the original to the same resolution, profile, and frame rate as the original. Still the same result of it not playing. ffprobe says:
Using roVideoScreen instead of a scene graph video node gave me a little more information.
showHomeScreen | msg = Service does not support range requests. | index = 0
Video status: 0 0
showHomeScreen | msg = Unspecified or invalid track path/url. | index = 0
Video status: 0 0
While it’s true that Range requests aren’t supported by this simple web server I’m using locally, the 24fps stream will play and 29.97 will not. Not even if I run it through ffmpeg to “sanitize” it first. I’ll try again with a different server which supports Range requests, but I’d love to know what the correlation is for requiring Range support vs. frame rate.