[TS_RECV] Command timedout

Anyone know what “[TS_RECV] Command timedout means on rec_tcvid log”?
@TabloSupport

99% sure it isn’t reception or drive issue.
Professional antenna stack with a signal specs of -31 dBm 32.5 MER and 1.5 EVM, Enterprise grade hard drive.
Issue could be reception caused by spurious noise, Tablo didn’t give any indication of reception errors on the App.

The issue is at 17:30 consistently on a program recorded this evening.

The Android Web App will freeze and not play past the point.
Same when Chromecasting.
Windows Chrome will freeze, but it can be skipped over the issue point and continue playing.

I have seen reception issues before on other channels with out the superior reception but the Tablo/Chromecast had been really good at playing through them. (Great work Tablo Team, thankyou)

Won’t play through this issue though.

ffprobe of all frames on the corresponding program playlist.m38u reveals that the transport stream jumps from 1051.283067 seconds to 0.700200 (same 17:30 issue point)

What the heck (attempting to sound Canadian) :wink:

Again, anyone know what [TS_RECV] Command timedout means?
Reception issue (funky one), Hard Drive burp, Tablo resource issues, Broadcast stream corruption passed onto Tablo?

Just had to be the Wife’s show too, and Bachelorette of all shows, uggggggggggggggg.

FYI, the recording right after it on the same channel was flawless.
Not saying it wasn’t a reception issue, but it would be nice to know what [TS_RECV] Command timedout means so I can pull the hard drive and check for issues or grab the spectrum analyzer and check the reception and broadcast transport stream compliance or just wait for the next update to resolve an intermittent software hiccup?

[FRAME]
media_type=video
key_frame=0
pkt_pts=94615476
pkt_pts_time=1051.283067
pkt_dts=54009
pkt_dts_time=0.600100
best_effort_timestamp=94615476
best_effort_timestamp_time=1051.283067
pkt_duration=3003
pkt_duration_time=0.033367
pkt_pos=433774656
pkt_size=38969
width=1280
height=720
pix_fmt=yuv420p
sample_aspect_ratio=1:1
pict_type=P
coded_picture_number=31489
display_picture_number=0
interlaced_frame=0
top_field_first=1
repeat_pict=0
[/FRAME]
FRAME]
media_type=video
key_frame=0
pkt_pts=63018
pkt_pts_time=0.700200
pkt_dts=63018
pkt_dts_time=0.700200
best_effort_timestamp=63018
best_effort_timestamp_time=0.700200
pix_fmt=yuv420p
sample_aspect_ratio=1:1
pict_type=P
coded_picture_number=31489
display_picture_number=0
interlaced_frame=0
top_field_first=1
repeat_pict=0
[/FRAME]
[FRAME]
media_type=video
key_frame=0
pkt_pts=63018
pkt_pts_time=0.700200
pkt_dts=63018
pkt_dts_time=0.700200
best_effort_timestamp=63018
best_effort_timestamp_time=0.700200
pkt_duration=3003
pkt_duration_time=0.033367
pkt_pos=433874296
pkt_size=16404
width=1280
height=720
pix_fmt=yuv420p
sample_aspect_ratio=1:1
pict_type=P
coded_picture_number=31497
display_picture_number=0
interlaced_frame=0
top_field_first=1
repeat_pict=0
[/FRAME]

I don’t know what TS_RECV means, but I am jealous that you have a spec analyzer available at home.

1 Like

@ChrisWilkes

Command timeout from TS_RECV means that no packets were sent to the Tablo to transcode at all. If this is a reliable station, it’s possible the transmission was off the air during this scheduled recording. The channel couldn’t even be probed at the time.