(2016-10-19, 10:12)Milhouse Wrote: Not a FULL debug log, you've snipped useful and potentially relevant information. No idea if what remains is likely to solve the issue.

(2016-10-19, 10:12)Milhouse Wrote: Not a FULL debug log, you've snipped useful and potentially relevant information. No idea if what remains is likely to solve the issue.

(2016-10-19, 17:45)Memphiz Wrote: You must have done something else to it. The complete log file header is missing ... but yeah - turn on debugging, restart kodi and reproduce your issue.

• Includes newclock5 patches
  
• Excludes the LibreELEC linux-01-RPi_support patch in favour of sourcing these and possibly more recent patches directly from kernel branch rpi-4.8.y
  
• Includes latest bcm2835-driver master (597c662a)
  
• Includes latest kodi-platform master (c8188d82)
  
• Includes latest libcec master (c559955d, ahead +17)
  
• Includes latest libnfs master (2edbd147)
  
• Includes latest p8-platform master (041a8c6c, ahead +1)
  
• Includes latest addons: inputstream.mpd (4c8013f6), inputstream.rtmp (70cb86f6), inputstream.smoothstream (081c6c43), peripheral.joystick (c89326e3, +24), pvr.argustv (87cb6780), pvr.demo (01c68c88), pvr.dvblink (043aa892, +1), pvr.dvbviewer (f72c62ff), pvr.filmon (675c2b4e), pvr.hdhomerun (eef1bd15), pvr.hts (c091da30), pvr.iptvsimple (adee8a7f, +3), pvr.mediaportal.tvserver (845479b6), pvr.mythtv (2f3dfcdc, +2), pvr.nextpvr (6a2128d8, +1), pvr.njoy (b5d65655), pvr.pctv (d6d969fe), pvr.stalker (168e35f7), pvr.vbox (c966c5fd), pvr.vdr.vnsi (dd95edef), pvr.vuplus (7ab30d34), pvr.wmc (d9eac84f)
  
• Exclude [env] libcec-PR208.patch: merged upstream (libcec)
  
• Include [env] patch: Add kodi binary addons (pvr, adsp, other)
  
• Include [env] patch: Don't build ADSP addons
  
• Include [env] patch: linux: use in-tree rtl8192cu for RPi/RPi2
  
• Include [env] patch: Bump included addon versions to prevent online updates
  
• Include [env] patch: Add experimental splash video for RPi
  
• Include [env] patch: HACK: Disable multiple PVR addons during migration. Always enable inputstream.* and os.*
  
• Include [env] PR:837: lcdd: initial addon
  
• Include [env] PR:849: samba: fix browsing and clean up smb.conf
  
• Revert [env] 46b9b7b3: rtmpdump (Reason: use newclock5 bump)
  
• Include [pkg] patch: [skin.estuary] Hide watched items on home (kodi-theme-Estuary)
  
• Include [pkg] PR:33: bye bye lcdproc (service.libreelec.settings)
  
• Include [pkg] PR:34: system update - fix cross-device linking (service.libreelec.settings)
  
• Include [pkg] PR:8824: videodb: fix smart playlists not honoring "Show empty TV shows" setting.
  
• Include [pkg] PR:10370: Add settings to control notification rumble duration and strength
  
• Include [pkg] PR:10714: AESinkAUDIOTrack: Don't false alarm with m_offset
  
• Include [pkg] PR:10731: Change splash db upgrade logic
  

1. VideoPlayer: fix aspect ratio for matroska containers for stereo modes
   
2. PR:10731: Change splash db upgrade logic
   

1. LibreELEC.tv:
   • linux: backport Avermedia TD110 support to iMX6 4.4 kernel (6a0a3616)
     
2. XBMC:
   • Fix deadlock introduced by #10690 (PR:10726, 1 commit, 1 file changed)
     
   • Fix Music Standard Roles Nodes (PR:10717, 1 commit, 7 files changed)
     
   • [peripheral API] Fix unitialized variable (f4cb6526)
     
3. peripheral.joystick:
   • [cmake] Cleanup and modernize (e5ee9467)
     
   • Remove unused member variable in CSettings (c89326e3)
     
4. newclock5:
   • New commits in this build:
     • VideoPlayer: fix aspect ratio for matroska containers for stereo modes (762a727c)
       
5. Additional commits/pull requests/changes not yet merged upstream:
   • Added: [pkg] PR:10731: Change splash db upgrade logic
     

(2016-10-19, 21:31)mezo Wrote: milhouse maybe you can help me with my question. i recently tried to run libreelec completly on usb, which the rpi3 allows. but after booting from usb i only have 120mb ram aviable... after switching back to sd card i get 753mb. i have no clue why this happen.

(2016-10-20, 00:04)Milhouse Wrote:

(2016-10-19, 21:31)mezo Wrote: milhouse maybe you can help me with my question. i recently tried to run libreelec completly on usb, which the rpi3 allows. but after booting from usb i only have 120mb ram aviable... after switching back to sd card i get 753mb. i have no clue why this happen.

The firmware in these builds (specifically, bootcode.bin, I believe) doesn't yet fully support the network and USB boot functionality - this is still considered experimental. If you're using firmware from branch=next then the 120MB issue has already been fixed, but may remain unfixed in the current branch=master firmware. You could try using the bootcode.bin from branch=next, and everything else from these builds, but if you have issues then wait until net/USB boot changes land in master.

(2016-10-19, 20:38)the_jaguar Wrote:

(2016-10-19, 10:12)Milhouse Wrote: Not a FULL debug log, you've snipped useful and potentially relevant information. No idea if what remains is likely to solve the issue.

(2016-10-19, 17:45)Memphiz Wrote: You must have done something else to it. The complete log file header is missing ... but yeah - turn on debugging, restart kodi and reproduce your issue.

Ok, I enabled debug log using Advanced Settings and restarted my Pi3 and went through the entire sequence of starting the movie and hitting "fast forward", etc. Here is the log - http://pastebin.com/H6jM1Dyc

Nothing in the log has been edited or snipped. Let me know if this works. Once again, thanks much for looking into this.

(2016-10-20, 00:08)mezo Wrote: thanks for your replay. i replaced start.elf and bootcode.bin from the next branch with the files from libreelec (would there even a usb possible without that?). or does libreelec somehow overwrite it with the old files on boot?

(2016-10-20, 05:06)smp1 Wrote: I was running build 1010 for a few days now and tonight I noticed a weird issue - one of the CPU cores - "CPU 2" was stuck at 100% load. No idea what triggered this or how to reproduce. I ran "top" via ssh, kodi.bin was using ~120% of the cpu.

(2016-10-20, 08:43)Milhouse Wrote:

(2016-10-20, 00:08)mezo Wrote: thanks for your replay. i replaced start.elf and bootcode.bin from the next branch with the files from libreelec (would there even a usb possible without that?). or does libreelec somehow overwrite it with the old files on boot?

LibreELEC will overwrite the firmware from branch=next each time you upgrade so you'll need to restore the branch=next bootcode.bin and start.elf after every upgrade (these are the two files that allow the RPi3 to boot from USB). However as start.elf includes the GPU firmware you're basically installing non-standard GPU firmware that doesn't include all the updates from branch=master, which is the version we're testing in this thread, so expect problems nobody using the branch=master firmware can reproduce.

As such, please do not be report issues (playback/deinterlace problems, random crashes, GPU hangs etc.) in this thread if your GPU firmware is from branch=next.

Edit: it's possible you need the bootcode.bin/start.elf firmware from branch=next only to program the "program_usb_boot_mode" OTP bit, after which the current firmware provided by LE may allow you to boot from USB, but with only 120MB as that issue is not yet fixed in branch=master. Depending on whether the 120MB issue is in bootcode.bin or start.elf, try replacing only bootcode.bin from branch=next and see if that fixes the memory issue, but avoid using start.elf from branch=next with these test builds - if you do you're on your own...

(2016-10-20, 12:27)mezo Wrote: i tried it a second time by replacing bootcode.bin/start.elf from branch=next, but somehow i get only 120mb ram after.

(2016-10-20, 15:28)Milhouse Wrote: What happens if you only replace bootcode.bin with the version from branch=next, and keep the current LE start.elf? You should have the full memory allocation, what I'm not sure of is whether USB booting will be possible with the start.elf from branch=master.

(2016-10-18, 18:23)popcornmix Wrote: The VC-1 and MPEG-2 files are detected as deinterlaced correctly.
They look fine to me. The file is a deinterlace torture test, so it is intended to be hard to deinterlace.
We produce the same output as, say VLC using yadif x2 (which is considered a very good deinterlacer).