Reproduced problem and resent Diagnostics from client app. The previous diagnostics were from the client app also.
Is it possible to add this to the Client Settings ? So some devices can be set to always use HLS ?
1 Like
Updated to client to latest beta version on Firestick 4k Max. Just sent in diagnostics. Using the HLS option, I now get a black screen with Invalid Argument displayed. Happens whenever I watch a channel long enough for the Cache to completely fill and I move the timeline bar back in time requiring the server to fill in the client buffer.
This failure does not occur using my Chromecast Google TV device. But it happens every time so far on my Fire device.
I had all sorts of problems on my FireTV with HLS watching certain Videos. Erratic skips.
Yes, hopefully not a major OS issue. Fortunately, I don't really need to use HLS on my Firestick since I have external memory installed which I use with the released version. But I do like HLS for my other devices, although I mainly use Firesticks. Apparently, the best solution is to use the AppleTV device which a majority of users recommend. But I would like to avoid getting hooked into Apple and the extra cost just so I can watch free OTA TV. .
I do not use it either but do test for it as some of my PC Clients use it ... so have to keep them happy.
I found optimal setting is if you have enough storage and enough tuners is to not use tuner sharing or HLS. No impact on the Server when viewing LiveTV.
On my main system I have tuner sharing off, tuner priority on and HLS off on any connecting Clients I have Tuner Priority and tuner sharing automatically on.
Could you update to the latest Android beta app and see if you have any different behavior? Please submit diagnostics if you run into these problems again.
Updated and duplicated Invalid Argument problem. Sent diagnostics. As I go back on the timeline bar with statistics on, I can see the buffer getting longer until it finally exceeds the cache and then I get the black screen with Invalid Argument.
Updated to version 8.30.2122, duplicated problem and resent diagnostics from client. Just noticed a newer version with updated diagnostics that I will try out next.
Updated to 8.30.2207, but I also restarted/rebooted my Firestick 4k Max device. The problems appear to be fixed, not getting any invalid arguments, nor any issues while sweeping the timeline bar. I will continue testing, but I think it has been fixed. Yea!
1 Like
Waht exactly does this mean ... using HLS ?
Watching The Orville - Season 2, Episode 13 from 10.0.0.194 (Transcoder Ready).
1 Like
That's normal. It means there's nothing to do. Start stop is also normal. The transcoder runs on demand
OK Thanks because I see stop and start on the Criminal minds Video constantly but it runs flawlessly. Is it just extra logging ?
2022/08/30 16:48:42.685983 [ENC] Starting encoder for Criminal Minds S01E01 2005-09-22 Extreme Aggressor 2022-06-29-1459.mpg in /home/nyplayer/ChannelsDVR/Streaming/file6666-ip10.0.0.194-1990193565/encoder-2867-2102669567 at 2867 (2868.866000) (encoder=remux, resolution=720, deinterlacer=, bitrate=2732, segment_size=0.01)
2022/08/30 16:48:42.719280 [HLS] ffmpeg: file6666-ip10.0.0.194: [mpegts @ 0x7fc5700] Dropped corrupted packet (stream = 1)
2022/08/30 16:48:48.075778 [ENC] Transcoder has handled 5075 segments and will be restarted
2022/08/30 16:48:48.082637 [ENC] Stopped encoder for Criminal Minds S01E01 2005-09-22 Extreme Aggressor 2022-06-29-1459.mpg in /home/nyplayer/ChannelsDVR/Streaming/file6666-ip10.0.0.194-1990193565/encoder-2867-2102669567 after encoding 2867 to 3033
2022/08/30 16:48:59.085332 [ENC] Next segment to pre-encode of 3034 is 9m57.597s from the last request of 2437
2022/08/30 16:48:59.086538 [ENC] Starting encoder for Criminal Minds S01E01 2005-09-22 Extreme Aggressor 2022-06-29-1459.mpg in /home/nyplayer/ChannelsDVR/Streaming/file6666-ip10.0.0.194-1990193565/encoder-3034-1469778920 at 3034 (3036.033000) (encoder=remux, resolution=720, deinterlacer=, bitrate=2732, segment_size=0.01)
2022/08/30 16:48:59.120342 [HLS] ffmpeg: file6666-ip10.0.0.194: [mpegts @ 0x76bd700] Dropped corrupted packet (stream = 1)
2022/08/30 16:49:04.475791 [ENC] Transcoder has handled 5016 segments and will be restarted
2022/08/30 16:49:04.482911 [ENC] Stopped encoder for Criminal Minds S01E01 2005-09-22 Extreme Aggressor 2022-06-29-1459.mpg in /home/nyplayer/ChannelsDVR/Streaming/file6666-ip10.0.0.194-1990193565/encoder-3034-1469778920 after encoding 3034 to 3199
2022/08/30 16:49:14.884078 [ENC] Next segment to pre-encode of 3200 is 9m55.595s from the last request of 2605
2022/08/30 16:49:14.885151 [ENC] Starting encoder for Criminal Minds S01E01 2005-09-22 Extreme Aggressor 2022-06-29-1459.mpg in /home/nyplayer/ChannelsDVR/Streaming/file6666-ip10.0.0.194-1990193565/encoder-3200-420064320 at 3200 (3202.199000) (encoder=remux, resolution=720, deinterlacer=, bitrate=2732, segment_size=0.01)
2022/08/30 16:49:14.919554 [HLS] ffmpeg: file6666-ip10.0.0.194: [mpegts @ 0x731e700] Dropped corrupted packet (stream = 1)
2022/08/30 16:49:20.276069 [ENC] Transcoder has handled 5055 segments and will be restarted
2022/08/30 16:49:20.287486 [ENC] Stopped encoder for Criminal Minds S01E01 2005-09-22 Extreme Aggressor 2022-06-29-1459.mpg in /home/nyplayer/ChannelsDVR/Streaming/file6666-ip10.0.0.194-1990193565/encoder-3200-420064320 after encoding 3200 to 3367
Those logs indicate normal operation of the transcoder.
1 Like
Whoops, still having problems during playback after long pause and cache filled. Sent diagnostics. Latest beta installed. This problem has happened twice now.
Can you see if this latest build acts any better?
This build killed Channels DVR on USB Storage it will not start up. Will not startup on any device even with internal storage.
Can you try using the non-beta app to try to reinstall the latest beta? I'm not able to reproduce this issue on my own Fire TV.
1 Like
Uninstalling the Beta and reinstalling from non beta works. should I update the beta ?