2020-01-18, 05:58 PM
Thanks to a great and very useful option, I MUST test it tomorrow
2020-01-18, 05:58 PM
Thanks to a great and very useful option, I MUST test it tomorrow
2020-01-18, 06:14 PM
@Paulo thank you, but be aware this is still not accepted code and I am still trying to work around some unexpected behaviour in Kodi. I am very interested in user feedback.
Martin
2020-01-18, 10:29 PM
Here is an updated link https://jenkins.kodi.tv/blue/organizatio.../artifacts with some changes that won't impact how this addon works. The win32 build did build in this go round, the build system is hit & miss but it is great for me working in Ubuntu and testing in Windows.
Martin
@mvallevand
Thanks, I can see that these are fresh compilations, I will leave them for the morning I couldn't stand it and I had to check it hls - fast test, 720p / bitrate 2500 encoding a small clip that lasts a few seconds and works - I will do it with log tomorrow MPEG-TS (M2TS) - completely suspends kodi on various variants - I will do it tomorrow with log ![]() some channels turn off when stop recording
2020-01-19, 12:06 AM
On startup Kodi does block for about 5-10 seconds while the server buffers but after that playback should normalize. I don't really understand your comment so I will wait for the logs to help me relate.
Martin
Found the option in the Live Stream, thanks for the hint.
So far I tested on Windows 10 Pro 64bit with latest Kodi 19 nightly and Nxtpvr addon: 4.3.0 (My NextPVR Server is a Beelink BT3 Pro TV Box (Intel Atom X5-Z8500 4GB/64GB ) with Windows 10 Pro 64bit and latest V5 Server) over WAN: 1080p (4000 kbps) and it worked originally but soon it introduces pauses and at some point in time Kodi froze and ffmpeg at the server-side crashed (ffmpeg.exe 32bit 89% - 96% CPU) on transcoding 1920x1080i50 lines H.264 channel -- uploading logs but didn't manage to reproduce the ffmpeg crash 720p (2500 kbps) and it works (ffmpeg.exe 32bit 85% - 95% CPU) on transcoding 1920x1080i50 lines H.264 channel 480p (1000 kbps) and it works (ffmpeg.exe 32bit 80% - 90% CPU) on transcoding 1920x1080i50 lines H.264 channel 360p (750 kbps) and it works (ffmpeg.exe 32bit 65% - 85% CPU) on transcoding 1920x1080i50 lines H.264 channel So some comments below: 1. I am totally ignorant on how pictures and streams work and best possible value combinations for lines and bitrates, but assuming that google are quite expert on those I would suggest that we add: minimum option: 240p for lines supported and lowest bitrate 300kbps and maximum bitrate to 6000 kbps (so far maximum that can be set for 1080p is 4000 kpbs) 2. As many people like me will be totally ignorant on the combination of those two, I would suggest to automatically suggest default bitrate that matches the lines selected as per Google recommended values below: Lines 240p 360p 480p 720p 1080p Resolution 426 x 240 640 x 360 854x480 1280x720 1920x1080 Video Bitrates Maximum 700 Kbps 1000 Kbps 2000 Kbps 4000 Kbps 6000 Kbps Recommended 400 Kbps 750 Kbps 1000 Kbps 2500 Kbps 4500 Kbps Minimum 300 Kbps 400 Kbps 500 Kbps 1500 Kbps 3000 Kbps 3. I see as per analysis done by Android Authority (see table at https://www.androidauthority.com/how-muc...se-964560/ picture uploaded) That frame rate may also be varying, should we also exposing the frame rate for selection? 4. Of course if we can make all this work together with timeshift it would be awesome! I hope that helps, let me know if you want me to do any other test...
2020-01-19, 10:38 AM
Hi, thanks for the feedback,
First is the ffmepg usage is way too high for a good experience. Changes in the next version might help, For comparison my small main 2 core linux server is about 25% and my i5 test box is 9%. I am concerned about the PC since especially as it is fanless, it is probably throttling on top of high CPU. Your kodi log is set for maximum resolution and bandwidth. Why would you want that or higher Internet? A better test is mid range at 576 1000kbps. The horizontal resolutions in the picklist 360, 480, 720, 1080 values work out to be the same as what google recommends. Sub offers two more 504 and 576. I agree that a lower option would help, but again the issue for the WAN uses is bitrate more than scaling I didn't put the vertical resolution in the pick list to make it easier to code. Martin
2020-01-19, 10:45 AM
Dear Martin,
Thank you for your reply.I know indeed I need a box with a more powerful CPU but as usual...my budget is very low ![]() The logs were provided for the test of 1080p that was pausing and eventually crasing (although not reproduced) ffmpeg.exe. As such I set to the highest bitrate that addon allows me as it is closer to the 4500 kbps that is google recommended value..... Otherwise, yes, I will most likely use the lowest values during travel so that I get no pausing during streaming Thanks and regards
2020-01-19, 03:41 PM
(2020-01-18, 11:30 PM)Paulo Wrote: @mvallevand The issue with the files in the logs you sent me are not the same but they both seem backend related. Can you watch them in the browser interface? 1- The file you indicate was m2ts failed likely because NextPVR directly downloaded it, I am guessing sub needs to use different command line for m2ts packet size. 2020-01-19 14:57:05.078 [DEBUG][63] Incorrect stream type...will fail 2 - The hevc file is failing because your PC isn't close to being powerful enough able to software decode it in real 2020-01-19 15:16:50.868 [DEBUG][69] [FFMPEG]: frame= 29 fps=7.2 q=25.0 size=N/A time=00:00:00.66 bitrate=N/A speed=0.163x Martin
2020-01-19, 03:49 PM
(2020-01-19, 10:45 AM)aderlopas Wrote: Thank you for your reply.I know indeed I need a box with a more powerful CPU but as usual...my budget is very low Ok thanks I thought you weren't able to stream. I use a sub $200 PC to an well understand the budget issue. The budget impacts my ability to use this feature when travelling, I always seem to get the room with the worst wifi. I don't see why you are having trouble with selecting the resolution in Kodi though, it seems to be the same as YouTube. Is it just because I don't show the p? Martin |
|