2017-02-17, 10:41
(2017-02-14, 21:05)Milhouse Wrote:(2017-02-14, 17:58)esco Wrote: Thank you Milhouse. I have tested 4.10-rc8 build #0213x build and unfortunatelly the same behavior occurs.
Can you provide log information? "journalctl -a", "dmesg" and "kodi.log"?
Is #0101 the last build that has this working mux, or just the last working build you've used? Can you identify when this mux problem started in the normal daily builds?
We switched to using the media_build package in #0108 so you might be able to confirm that is when the problem started (ie. #0107 works, #0108 doesn't).
#0107 is fine, no issues at all. With #0108 I am able to scan muxes (however some "poll timeout" errors appear) but unable to watch TV - the log is full of MPEG2AUDIO/ H264 "Invalid start code" and "Continuity counter" errors. Am I supposed to send the logs with the latest #____x build?
Thank you.