Posts by sYCO

After the not so fine working 8.0.1g I went back to 8.0.1e
and realised, it still seems to have problems with the TV
streaming. As if pandora's box was opened now.

I will try c or d today and see, where this leads to.

Quote from Notna

No idea how your set up is, but works flawlessly here with an MXQ Pro 4k (P212 model with S905x socket) on practically anything I throw at it. Any examples of files that always fail? More than happy to test a few to see if it is hardware, software or otherwise related.

Maybe they talk about TV streaming, which is fucked
since f or g (purple lines, banding, resolution reset, ...).

Quote from Poida

You horrible person! ( kidding)

Haha, noooooo, that was not meant in a bad way.

It is just safe to say now, that something went wrong along the builds with the TV streaming in 8.

Btw, I tested a PS4 with my beamer and also the box at another TV set. I am very happy, that expensive beamer is not dead, yet.

Quote from boot2k3

The same issue on S912 for me. I have one liveTV channel with the same color problem on f version.

Sorry, sorry, I totally forgot to mention my box.

So, I have this purple issue on a Nexbox MXQ Pro 4K (S905, 1 GB RAM).

Quote from afl1

I found the same issue on S905X/S912. It starts red and green color flaring in bands with equal width. Simple switching liveTV channel fix this flaring. But after a while it appears again. This issue has nothing with overheating. I opened box and kept CPU temperatute < 60°C and the behavior was same. This flaring has never happended on S905 boxes..

I am happy to hear, I am not the only guy with that issue.

Btw, my beamer is totally going crazy with refocusing and
resizing the screen with this problem.

I went back to c and now it seems to work again without
that purple lines and flaring and resizing issue. I will test
more today/tomorrow.

With the f version I was watching some minutes/hours
of stream TV (official public TV channels), when I got
some purple lines and disturbings into the picture and
also sometimes the resolution reseted to 4:3 and went
back to 16:9.

So, I thought ... okay, shit, my beamer is dying.

Well, then I switched to play local files (movies in mp4
format) and the normal quality was back. No problems.

I will do some testing later to rule out, if my beamer is
dying. I just went back to c and also I will do use the
PS4 to determine, if the beamer is the issue.

Quote from kubrickdave

I experience frame drops about 30 minutes into seemingly every H264 file I play. I then skip back 10 seconds and the passage plays flawlessly. If I pause playback at anytime that 30 minute "timer" gets reset. Meanwhile the Kodi log shows this:

Code

WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer

So there's some kind of buffer underrun it seems. This is playback over NFS with dec_control set to 4.
During the runtime of this particular file (full-length movie), I also got this (log time stamp does not correlate with stutter, appears later):

Code

NOTICE: CActiveAEStream::AddData - messy timestamps, increasing interval for measuring average error to 6000 ms

I'll try to get a full debug log later.

Same here, I think, but I can not say for sure, because I just watched one file.

Quote from x-kent

Hi Kszaq.

I am getting a weird picture freeze with all the LE8 builds. Including the latest "c".
I am playing TV using Simple IPTV PVR client. After a couple of hours (usually 4-5 hours) I have the below in log and the picture just "freezes".
From the log, I can see that sometimes it does recover from it but then it just gets "stuck" with the "stream stalled" message and I need to manually stop the play, switch the channels a couple of times(just stop/play doesn't work after freeze!) and only then the video playback returns. There is no "buffering" circle, nothing. The picture just freezes.

Is it related to running on s905 ? Is there any workaround to detect and restart the stream ?
My box is S905x 2g/16gb (x96). The below happens both in your builds and builds that I did compile manually from your code.
In the below log, the freeze happened at 05:38. I have came back to TV at around 11am and it was still showing a frozen picture.
Can I somehow debug the problem further ? Looking at the KODI source where the log message is printed doesn't really help as I am not familiar with how it works and there is a "sleep(10)" in the code that doesn't make a lot of sense.

Thank you for your work.

Code

00:40:26.399 T:3658511264  NOTICE: CVideoPlayerAudio::Process - stream stalled
00:40:42.355 T:3930067872 WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer
01:32:49.247 T:3658511264 WARNING: Previous line repeats 4 times.
01:32:49.247 T:3658511264  NOTICE: CVideoPlayerAudio::Process - stream stalled
01:32:58.030 T:3930067872 WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer
02:36:04.393 T:3658511264 WARNING: Previous line repeats 1 times.
02:36:04.393 T:3658511264  NOTICE: CVideoPlayerAudio::Process - stream stalled
02:36:23.489 T:3930067872 WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer
05:38:09.192 T:3658511264 WARNING: Previous line repeats 1 times.
05:38:09.192 T:3658511264  NOTICE: CVideoPlayerAudio::Process - stream stalled

Display More

"Same" here. I go to bed and let the stream run
over night. In the morning the picture is frozen
(at some point some hours later).

On earlier versions like Jarvis the stream was still
running in the morning, when I turned on the TV.

Actually, it was even running one or two days
later, when not stopped manually.

Quote from zed85

Hi Kszaq,

I'm running [7.0.3.012j] LibreELEC 7.0 for S905/S905X on my S905 devices right now.
Do you advice to step over to 8.0.0e right now? I don't think the mentioned issues in post #1 are a problem for me.

Thank you!

I would not do it (again). I changed up last week and find
Libreelec 8 way inferior to 7.

It is slower and unstable. With Jarvis I had no crashes and
buffering problems and the response time was brilliant.

With Krypton that all went bad, I think. It is still usable, of
course, but stability and speed in Jarvis is unmatched. Also,
simply moving forward/backward in a movie file is smooth,
while it is a stuttering and buffering issue in Kodi 17.

Unfortunately, I cannot go back without doing a new installation,
which is just too much work again. If I consider to buy another
box, I will use Jarvis for now.

Quote from zed85

What kind of NAS are you owning? Synology?
What kind of share method are you using on our Synology? HTTPS WebDav?

There is a problem with Synology not accepting the SSL connection what LibreELEC 8.0 is using. See thread-4075-post-30202.html
You can fix that by using a HTTP WebDav connection from LibreELEC 8.0 to your Synology.

Exactly, a Synology NAS I am owning. Using Samba, I guess.

Still I managed to get it running again. I deleted the database files again and also removed the sources and add them again, while setting the content anew.

Now it is scraping/searching movies/series again.

Quote from bubblegum57

I know it's a pain, change sources to none, let it clean up the library then reset source to movies & scan again.

Failing that, browse storage\.kodi somethere is the videos.db delete that, it might be myvideos.db

I did the second, already. I deleted the myvideos.db files in kodi/userdata and restarted the box.

I do not know, what happened, but from one day to another
all my movies/series were not shown anymore in Kodi.

So, I tried to update/scan again all the files, but it says, there
is nothing new.

Then I read about deleting the database files, which I did, but
even after a reboot I cannot update/scan the files with success.

Anyone else having an issue like that or knowing a solution?

Thank you in advance.

PS The NAS is working fine, I could even play a movie on Kodi with
using the stream plugin (Yatse). So, it has no access limitations and
it was working the last twelve months, too.

I am about to order another cheap box as second device (for a fullhd beamer).

I found the MXQ 4K Pro and the A95X the cheapest in the market with 30 and 35 bucks.

One question: What to prefer, S905 or S905x?

Also, I could not find a cheap box with 2 GB RAM. I guess, they start at 50/60 bucks. :\

Quote from zed85

Hi Kszaq,

I'm running [7.0.3.012j] LibreELEC 7.0 for S905/S905X on my S905 devices right now.
Do you advice to step over to 8.0.0e right now? I don't think the mentioned issues in post #1 are a problem for me.

Thank you!

Five minutes ago I went from the latest 7 to the latest 8 and everything was running fine.

Even my skin AppTV (I love simple minimalistic styles) was working immediately.

Estuary looks fine, but is just not showing enough or showing too much. I reduced the list on the left side (navigation), but AppTV is still nicer, I think.

Quote from kszaq

mmpp is 100% correct. In my opinion Jarvis builds are almost 100% working and I am backporting hardware-related fixes from time to time.

If you want a new box, get S905 or S905X. Do not buy S912. My S912 builds are a proof that it's possible, not something recommended to use.

I am using your latest Kodi 16/Libreelec 7 with a MXQ 4K Pro (S905).

Is there any reason or even recommendation (from you) to use Kodi 17/Libreelec 8 (on a S905 box) or should we rather stay on Kodi 16/Libreelec 7?

Are there pros and cons for Libreelec 8, even regarding addon support?

Thanks, 012j seems to work fine.

Quote from rrol

Hi everyone, I just joined the thread. I would like to report a problem related to NAND appeared in the last 7.0.3.012h release. I use a NexBox with S905 (1GB/8GB). When booting with SD card, the NAND driver starts correctly but the system does not load the aml_nftl_dev module. Consequently, /dev/boot, /dev/system and others are not populated in the file system. And the script used to write LibreElec to the NAND fails.
I think this issue may be due to one of the latest commit named "load NAND module only when needed" which disable automatic loading of aml_nftl_dev.
This problem did not occur in 7.0.3.012g release.

Thank you for your support (and above all for your hard work!)
Regards,
RR

Maybe that is why my update from 012f to 012h went totally wrong and
destroyed my installation. :\

Quote from sYCO

kszaq ... do you have a clue/solution maybe?

greetings

Guys, does nobody have an idea, how to solve that? I mean,
it was a standard update, which lead to that issue.

I have no access to the internal side, of course, but I still have
a working external SD card installation with 012f and I could maybe
access the internal side with this.

Maybe it just helps to copy the old system files from 012f to the internal
SD to overwrite what went wrong in 012h, so that it boots up normally
again?