Legend 
thanks Eric!
further to my last comment if it helps i am running a synology 718+ and having just looked at the logs the NULL .. seem to be in the logs with the old transceiver as well (although much less frequently and doesnt crash the firetv app)
I don’t often watch remotely, but I did yesterday while on the interstate. Overall, the stream was very stable, changing quality on the fly as my cell signal fluctuated. However, The audio and video were out of sync from the start and remained so throughout. It was a couple of second off. I’m on the latest release of the DVR, using the adaptive transcoder.
Is there any update on when the new transcoder will get the feature to always transcode (rather than dynamically selecting) so that users in the UK with fireTv 4k stop being forced to use the old transcoder version?
If i select new transcoder at the moment it ignores the transcode selection depending on content being played which then causes further issues in fireTv with poor deinterlacing etc
Please can we have a toggle to always force transcode!
Which fire tv model and firmware bug are you referring to?
Please see here re Erics response:
I understand the transcoder issue, but I would like to know what FireTV device you are using and why you need an always transcode option.
If i dont transcode the video the image quality for the main HD tv channels (1080i) (bbc, itv, channel 4) is horrific and virtually unwatchable.
The hardware deinterlacing does not work and whenever there is fast moving motion the picture breaks up in interlaced lines.
The app also does not switch framerate / resolution so everything is delivered in 1080p even though the non transcoded stream is 1080i
Basically forcing 720p 6mb and using old transcoder fixes all issues and plays back ok at the stuck 1080p with no artefacts (except for audio sync issues occasionally)
Using new transcoder works some times until it decides not to transcode and the all the interlacing issues return.
Regardless of source / transcoder etc, the app never switches from 1080p 60hz (even though 50hz is default here in uk)
Hope that helps
1 Like
Which fire tv model are you using?
FireTv 4k stick
(I.e the one that used to crash when playing 1080i)
Now it seems to switch to software (or no) deinterlacing instead of crashing, which is unwatchable for medium to fast motion on screen
Watching something like F1 racing is lots of interlaced lines everywhere and looks terrible
When transcoded at 720p - perfect
@timellert If you still have one of these F1 recordings with lots of interlacing artifacts, could you send the video to [email protected]? I just got a new Fire TV 4k Stick and would like to replicate what you're seeing.
Sure, i dont have any previous recordings but will send over the next one this coming saturday
I’ll even take Free Practice 1. 
Sadly we only get quali and the main gp on channel 4 here!
I will try recording the football instead tonight to see if that has the same issues and send over tomorrow if it does
1 Like
hey Eric.. some recordings winging their way to you via email... all have massive interlacing artefacts when played at normal res on fireTv 4k via channels... especially the F1 quali which is mainly a blur of interlaced lines
1 Like
This is great. I was totally able to see what you're talking about. We'll figure out what the best steps forward are for this.
1 Like
As a follow-up to this work, I've just released a new experimental setting to provide automatic bandwidth adjustment for Live TV watching. You can read about it here:
Running 2019.12.26.0206 currently (update about once a week)
I have a remote (liveTV) stream that is choppy. Is this due to the new transcoder option?
My remote site (AppleTV) is set to 720p @ 3mbps
My remote site has 100mbps download
My local site has 200mbps download/20mbps upload
My DVR server is running in a Virtualbox which has 4 cores (AMD Ryzen 2400G) and 4GB dedicated to it.
2019/12/27 07:26:35 [ENC] Starting encoder for ch6.1 in /mnt/data/apps/dvr/storage/Streaming/ch6.1-dANY-ip192.168.100.54/encoder-1-827911728 at 1 (0.000000) (encoder=libx264, resolution=720, deinterlacer=blend, bitrate=3744 segment_size=0.01)
2019/12/27 07:27:18 [ENC] Segment 29 has unexpected duration: inputs=30 expected=1.5015 actual=2.002 expected_pts=43.443399-44.944899 actual_pts=42.952444-44.921078
2019/12/27 07:27:21 [ENC] Segment 31 has unexpected duration: inputs=33 expected=1.2012 actual=1.5015 expected_pts=46.446399-47.647599 actual_pts=46.489311-47.957444
2019/12/27 07:27:26 [ENC] Segment 34 has unexpected duration: inputs=37 expected=1.234567 actual=1.5015 expected_pts=50.650599-51.885166 actual_pts=50.693511-52.161644
2019/12/27 07:27:28 [ENC] Segment 36 has unexpected duration: inputs=40-41 expected=1.5015 actual=1.568233 expected_pts=53.386666-54.888166 actual_pts=53.362844-54.897711
2019/12/27 07:27:31 [ENC] Segment 38 has unexpected duration: inputs=43 expected=1.4014 actual=1.5015 expected_pts=56.389666-57.791066 actual_pts=56.432578-57.900711
2019/12/27 07:27:36 [ENC] Segment 41 has unexpected duration: inputs=47 expected=0.533867 actual=1.735067 expected_pts=61.027632-61.561499 actual_pts=60.803611-62.505311
2019/12/27 07:27:42 [ENC] Segment 45 has unexpected duration: inputs=52 expected=0.6006 actual=1.5015 expected_pts=65.965899-66.566499 actual_pts=66.008811-67.476944
2019/12/27 07:27:44 [ENC] Segment 47 has unexpected duration: inputs=54 expected=1.8018 actual=1.9019 expected_pts=68.468399-70.270199 actual_pts=68.110911-69.979444