Hello, I have a TVHeadEnd server and I see channels with LG smartv
Until now I used LG 47LB710V with webos 1.0 and the operation is correct.
Currently I have purchased for LG 28MT49S bedroom with webos 3.5 and the performance difference is remarkable.
The two TVs connect by cable ethernet
With webos 1.0 I select the channel and the playback is instantaneous.
With webos 3.5 I select the channel, the video is fixed for a few seconds, in an icon lower left is shown animation of arrow going down, I suppose it indicates that it is loading buffer and after 4 or 5 seconds starts the video in motion.
Why this difference in performance? It is uncomfortable changing channels with 3.5 webos because the delay is very large.
Any solution?
Thank you.
Different operation with LG webos 1.0 and 3.5
Re: Different operation with LG webos 1.0 and 3.5
I am with the same problem, SSIPTV and LG SMART IPTV and all Applications for IPTV work too slowly while switching channels...
Only Kodi works fine and perfect but with dedicated device, in my case I use my orange PI PC Plus and it is not good hardware and while switching channels kick me out... maybe cpu issue... the cpu is not have enought power to handle with switching...
Only Kodi works fine and perfect but with dedicated device, in my case I use my orange PI PC Plus and it is not good hardware and while switching channels kick me out... maybe cpu issue... the cpu is not have enought power to handle with switching...
Re: Different operation with LG webos 1.0 and 3.5
I think SSIPTV and all IPTV Players for Web os not support TVHEADEND stream types.
If you convert the TVHEADEND streams into HLS I think channel switching will be fast.
Using CPU:
fmpeg -reconnect 1 -reconnect_at_eof 1 -reconnect_streamed 1 -reconnect_delay_max 2 -y -nostats -nostdin -hide_banner -loglevel quiet -fflags +genpts -user_agent HLS -i http://tvh,ip:9981/stream/channelid/12345 -strict -2 -dn -vf yadif -vcodec h264 -acodec aac -preset superfast -profile:v baseline -level 3.0 -b:v 2048k -b:a 128k -minrate 1024k -maxrate 3072k -bufsize 2048k -crf 19 -aspect 16:9 -r 50 -ar 44100 -ac 2 -scodec copy -hls_flags delete_segments -hls_time 10 -hls_list_size 6 /var/www/html/streams/1_.m3u8
Using NVIDIA GPU:
ffmpeg -fflags +genpts -user_agent "GPU Transcode" -nostats -nostdin -hide_banner -loglevel quiet -hwaccel cuvid -c:v h264_cuvid -resize 960x720 -deint 2 -i http://tvh.ip:9981/stream/channelid/119400202 -map 0:v -c:v h264_nvenc -preset slow -profile:v main -level 3.1 -rc vbr_hq -b:v 2000k -minrate 1000k -maxrate 3000k -bufsize 5000k -map 0:a -c:a libfdk_aac -ac 2 -b:a 128k -hls_flags delete_segments -hls_time 10 -hls_list_size 6 /var/www/html/streams/1_.m3u8
https://github.com/streamlinevideo/streamline
https://github.com/t-mullen/hls-server
Good luck, for me is too complicated.
If you convert the TVHEADEND streams into HLS I think channel switching will be fast.
Using CPU:
fmpeg -reconnect 1 -reconnect_at_eof 1 -reconnect_streamed 1 -reconnect_delay_max 2 -y -nostats -nostdin -hide_banner -loglevel quiet -fflags +genpts -user_agent HLS -i http://tvh,ip:9981/stream/channelid/12345 -strict -2 -dn -vf yadif -vcodec h264 -acodec aac -preset superfast -profile:v baseline -level 3.0 -b:v 2048k -b:a 128k -minrate 1024k -maxrate 3072k -bufsize 2048k -crf 19 -aspect 16:9 -r 50 -ar 44100 -ac 2 -scodec copy -hls_flags delete_segments -hls_time 10 -hls_list_size 6 /var/www/html/streams/1_.m3u8
Using NVIDIA GPU:
ffmpeg -fflags +genpts -user_agent "GPU Transcode" -nostats -nostdin -hide_banner -loglevel quiet -hwaccel cuvid -c:v h264_cuvid -resize 960x720 -deint 2 -i http://tvh.ip:9981/stream/channelid/119400202 -map 0:v -c:v h264_nvenc -preset slow -profile:v main -level 3.1 -rc vbr_hq -b:v 2000k -minrate 1000k -maxrate 3000k -bufsize 5000k -map 0:a -c:a libfdk_aac -ac 2 -b:a 128k -hls_flags delete_segments -hls_time 10 -hls_list_size 6 /var/www/html/streams/1_.m3u8
https://github.com/streamlinevideo/streamline
https://github.com/t-mullen/hls-server
Good luck, for me is too complicated.