Posts by Ftelf

    K1 Plus Combo on latest test build. 201706201320-g45271ec-I.

    After some 20hours of continous on one channel there was a crash. Seems like a driver issue.

    kodi.old.log

    Code
    18:25:39.272 T:4078957472   ERROR: CAESinkALSA - snd_pcm_writei(-32) Broken pipe - trying to recover
    18:26:10.711 T:3561821088   ERROR: Previous line repeats 1 times.
    18:26:20.075 T:3561821088  NOTICE: CAMLCodec::Decode: Stuck, try to get more buffer
    18:26:25.843 T:4078957472   ERROR: CAESinkALSA - snd_pcm_writei(-32) Broken pipe - trying to recover
    18:26:42.835 T:3561821088  NOTICE: CAMLCodec::Decode: Stuck, try to get more buffer
    18:26:50.982 T:4078957472   ERROR: CAESinkALSA - snd_pcm_writei(-32) Broken pipe - trying to recover

    service.log

    Code
    2017-06-21 18:22:14.891 [WARNING] linuxdvb: Availink avl6862 : DVB-S #0 - read() EOVERFLOW
    2017-06-21 18:22:15.753 [WARNING] linuxdvb: Availink avl6862 : DVB-S #0 - read() EOVERFLOW
    2017-06-21 18:22:18.551 [WARNING] linuxdvb: Availink avl6862 : DVB-S #0 - read() EOVERFLOW
    2017-06-21 18:22:19.659 [WARNING] linuxdvb: Availink avl6862 : DVB-S #0 - read() EOVERFLOW

    Can you please let me know you upgraded tvheadend to 4.2.2-49? The latest version I see in LibreELEC add-ons repo is 4.2.2-32

    Well, all I did was blindly forced tvheadend update which I have set to manual. The tvh web says: HTS Tvheadend 4.2.2-49 ~ LibreELEC Tvh-addon v8.1.112 rjwfju. Now I'm upgrading to 201706201320-g45271ec-I.tar .

    20170619172911 Was stable for 23hours of live tv on DVB-S2. But after that 23hours when I checked TV, the audio was out-of-sync. But this could be a problem of timeshift which is not recommended, but I use it anyway because I think that it works flawlessly.

    EDIT:

    tested: LibreELEC-S905.arm-8.0-8.0.2-devel-201706201320-g45271ec-I.tar

    not sure what it suppose to fix, but survived 16 hours of live TV without any problems. AV sync was OK when I checked.

    The only maybe interesting log items.

    Test build with fix for live tv playback stuck.

    LibreELEC-S905.arm-8.0-8.0.2-devel-20170619172911-g45271ec-I.tar

    Pls, report testing results.

    Upgraded yesterday in the evening (21:20), also tvheadend from the official repo (4.2.2-49). Watched favourite shows till 22:10, left playing a Live TV through the night (with shifted timeshift ~ -5minutes). Checked after 7 and half hours, Live TV is still ON. None of the symptoms present in 8.0.2b observed. I had audio stuttering, ocassional video freeze and kodi frontend crash.

    tvheadend service.log is clean, only EPG searches

    kodi.log has few buffering issues, nothing serious. kodi.log

    K1 Plus Combo, upgraded to latest 8.0.2b-I + service.tvheadend42-8.1.111a

    previous version 8.0.2a-I + tvheadend42-8.1.112 (not sure why, but it was this version I believe).

    2 days from upgrading and I got 1 kodi crash a several freezes of Live TV (DVB-S2/DVB-T2). This never occured in the previous versions. In fact the 8.02a-I combo was very stable.

    kodi_crashlog_20170617111300.log

    kodi.old.log

    Tvheadend service.log (should be from the moment when Live TV crashed)


    Simple as your LE setup is obviously configured to set display rate the same as the video frame rate (recommended setting). Easy to rectify and a one off operatioon. Just go through all the refresh rates for your chosen resolution and calibrate your box to the TV screen for each and every refresh rate. There are several of them with KODI 17 as we now have all the fractional rates too. I of course also had that problem y ou mention but of course now it is fixed. If you decide to use a different resolution liek changing from 1080i to 1080p then you will need to do the same again as I understand it but I just stick to 1080p on my FHD 5 year old Samsung Series 7.

    I had an impression that screen-size calibration is only last resort fix because it will distort the image in the worst possible way (crop-resize). He obviously have problem with overscan, which is a TV problem not a S905 nor LE. All he have to do is to made TV works in 1:1 pixel mode. Ie. on my Samsung UE46F6650SB I had to change HDMI label to PC, problem fixed.


    TVHeadend fails at scanning 2 of our 5 local DVB-T muxes. It failed in 7.x, and still fails in 8.x.
    VDR worked as an alternative in 7, but that seems to be basically dead now (in the first 8.x build I tried, it would work once then lock, and in the latest build, it just doesn't find any channels).
    And for reference, all channels worked correctly in the Android firmware.

    But... I found a Realtek USB tuner I've had for years, and plugged that in. TVHeadend works fine with that.

    So the question: Is that due to the built in tuner having a crappy kernel module? Is it something the community gurus are working to improve, or something that's stuck because it's closed source?

    Also, overall, I love how this exists - it's what these boxes should have been built with to start with :)


    I have just did rescan for dvb-s and dvb-t networks and all works just fine in the latest 8.0.1k release as well as in the previous ones. 4 muxes are dvb-t 1 dvb-t2 and about 14 dvb-s2. About the tuner driver, it's said here in the thread how it works, don't be shy and read.

    It happen every movie what i see. I tried with 23.97 and 24 fps movies, with or without subtitles.
    I cannot give you sample, because the official sample to small (only 1 minute), and the movie is big.
    Operation.Mekong.2016.1080p.x264.TrueHD.5.1 14.69 GB

    I have K1 plus Combo @8.0.1j-test.
    I have tried first 10 minutes of the ^^^ movie. Not a single glitch. If this happens with "every movie" I'll search for a problem elsewhere. In your setting, TV, network, NAS, etc... I have also tried some 30GB mkv I found and still no problems. I have a windows NAS server with intel RAID5.


    How do i repair it ? any idea ? which one and where can i order it and replace ?
    Thanks for replying.


    is it working in android ?
    have you tried to lsmod ?
    is your wifi chipset RTL8723BS as google suggests ?
    do you have proper module in your system ?
    have you tried google ? as I have found similar problem ?
    [Mini M8S] Realter RTL8723BS Module Driver - Amlogic - Armbian forum

    edit: it was quite time consuming to read all of your posts to find out what device are you actually talking about. its Mini M8S pro.

    K1 plus combo @ 8.0.1g S2/T2
    Channel switching is indeed faster. I have observed two frame freezes on T2 (qHD, h.265) withing 10 minutes after channel switch. Another 30 minutes was fine. Than at least 45 minutes fine on S2 (HD, h.264). Using permanent time-shift if that matters.
    It's really interesting how those boxes became more stable and problems-free because of hard work of few enthusiasts. Wish I could help more. Thanks.

    I'm on the 801f and I did never see this hopping before. I did not change any of my settings since Jarvis. It is quite hard to see and I strongly believe that most people just do not see it. You need a strong vertical line like text on a quite steady background. I was thinking someone else would see it so that I do not have to go back to 801e or earlier to figure out when it started :) Maybe I find some minute at the weekend.


    So it's regression in 801f what you see than. That's why it's a good idea to mention what version are you using etc.. 10155052560281661
    4:3 channel, SD I assume, what codec, mpeg2, h264, h265 ? What decoder HW/SW ? Have you tried to record this video and check on another device/PC ?
    I have just checked few SD channels broadcasting in 4:3 h.264. HW decoder for all formats and codecs. HDMI output as FHD. All channels perfectly still (according to logo), checked also some other, no problem. K1Plus Combo @ 8.0.1f

    A small bit on DVB-S2. DVB-S2 is working pretty well so far, but I'm trying to get DVB-T/T2 port to work without any luck. It recognizes its there driver wise but it fails to find muxes and there is no signal strength or SNR displayed.


    Not sure what device and version you are using because you didn't mentioned. But I have been using k1 plus combo on dvb-s2 since jarvis builds, actually on 801f and never seen such issue. Also tried dvb-t few days ago without single issue. Today dvb-t2 starts in our area so I'll also check that. Have you read through the all or at least first ? Maybe some tvh setup tutorial, there are many on youtube etc.

    K1 Plus Combo @ 8.0.1f
    Anybody else having a problem with video playback when jumping back over timeline ? There is about 20 percent chance that the video got stuck and will remain still, audio continues. Only way to fix it is to stop playing the video fine and open again. It happens randomly, sometimes it's ok within the same video file, sometimes it got stuck. Playing files through NAS (SMB).
    ie:
    Video: MPEG4 Video (H264) 1280x720 23.976fps 1206kbps [V: h264 high L4.1, yuv420p, 1280x720, 1206 kb/s]
    Audio: AAC 48000Hz stereo 156kbps [A: aac lc, 48000 Hz, stereo, 156 kb/s]

    I observe this behavior since 8.0.1b, never seen with previous versions and I have seen it with every following version up to 8.0.1f

    K1 Plus Combo 8.0.1a -> 8.0.1c [DVB-S2]
    I'm not sure that I had any buffering issues with 8.0.1a version, at least I cannot remember any, but with the "1c" it's present. I had been using "1a" since release for 1-3 hours a day.

    today

    Code
    19:14:21.781 T:3631215520 WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer
    19:14:23.929 T:4121042400  NOTICE: Display resolution ADJUST : 1920x1080 @ 50.00 - Full Screen (16) (weight: 0.000)
    19:18:14.621 T:3631215520  NOTICE: Previous line repeats 1 times.
    19:18:14.621 T:3631215520 WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer

    Yesterday 7 times according to log. I remember few times.
    logs

    K1 Plus Combo 8.0.0f from Internal upgraded to 8.0.1a [DVB-S2] 1TB USB HDD for TS+REC
    upgrade smooth, seems no regressions. Checked DVB and media playbec briefly, both OK.

    Checked bug present also in 8.0.0f, possibly also in previous builds.

    • Watching Channel for a minute or longer, active Time Shift.
    • Reverse playback [<<]
    • Now the screen is stuck, cannot resume the playback. Switching channel brings only the audio. Video has the same image all the time.
    • Closing the TV and opening channel again brings the same video image, audio is OK.


    Nothing serious, I just have to pay attention not to press Reverse during the TV on. Ordinary left and right arrows to jump over time works fine.

    PS: Thanks for your effort guys. Really appreciate it.

    EDIT:
    After about and hour of testing. Several channel changes (10+) on the another channel change the video stuck, there is tons of following log entries:
    [ 5007.337429@0] DI: check_di_buf: Error 17, di_buf is NULL
    [ 5007.337477@0] DI: check_di_buf: Error 17, di_buf is NULL
    [ 5007.347469@0] DI: check_di_buf: Error 17, di_buf is NULL
    [ 5007.347513@0] DI: check_di_buf: Error 17, di_buf is NULL
    [ 5007.357484@0] DI: check_di_buf: Error 17, di_buf is NULL
    [ 5007.357517@0] DI: check_di_buf: Error 17, di_buf is NULL
    [ 5007.367574@0] DI: check_di_buf: Error 17, di_buf is NULL
    [ 5007.367617@0] DI: check_di_buf: Error 17, di_buf is NULL
    [ 5007.377436@0] DI: check_di_buf: Error 17, di_buf is NULL
    [ 5007.377470@0] DI: check_di_buf: Error 17, di_buf is NULL
    [ 5007.387562@0] DI: check_di_buf: Error 17, di_buf is NULL
    Never seen this before, video never stuck on channel change before. Seems a HW decoding issue IMHO. Had to reboot, stopping TV do not help, Opening TV again shows last video image, audio was OK. TVH still works fine on background. logfile

    afl1 I'm confused about the wrong remote.conf bundled in the first build of 8.0.0d.
    I assume the remote.conf placement directory /etc/amremote
    remote.conf posted separately as a fix has 1167B and it is the very same file as in 8.0.0a,b,c, even in older beta6a.
    In the first build with the wrong remote.conf it has 1203B, but there is also a correct remote.conf in /flash

    In the corrected second build if 8.0.0d the /etc/amremote.remote.conf has 1163B and it still differs from the previous ones and the currently attached one.

    On the left is this one
    On the right is /etc/amremote/remote.conf from the corrected build
    bxwfpq
    [code=php]
    Line83 0x01 30 #27 #audio <=> 0x01 27 #audio

    [/php]