Jump to content

Emby records an unwatchable ".TS" file


Recommended Posts

Posted

With a routine scheduled Live-TV recording, every few months Emby will create a recording that is unwatchable on any device or player.  On August 22, Emby recorded the NBC News with Lester Holt at 6:30PM.  With any viewing attempt, this file won't play, just hangs on a black screen, or spinning circle depending on the device or PC.  The file length is 1.7GB, typical for the half-hour show.

Logs attached.  Thanks for the help!

-Don

embyserver.txt

Posted

Also... I don't know if it is relevant but appears my PC (Emby Server) updated the system time at 18:36, soon after the show started recording.  This it did on its own.  Lots of entries in the server log after that happened.

Thanks, -DJ

Posted (edited)

That log file is from the 23rd (00:00 to 01:38) showing ‘The Late show…’ ending and ‘After Midnight..’ being recorded.

Please attach the correct log when the bad recording was made.

But the most common cause of this problem would be a poor OTA signal or a bad IPTV feed.

Edited by TMCsw
sp.
Happy2Play
Posted

Probably need to see the ffmpeg log also.

2024-08-22 20:48:09.766 Info App: CodecValidation: The color format (Unknown) is not supported)
2024-08-22 20:48:09.766 Info App: CodecValidation: Encoder is not compatible with 'D3d11va' decoders

 

Posted

ffmpeg-transcode-47c68487-9e41-4887-81bf-41ff32c4024f_1.txt

This is the ffmpeg log produced when we first tried to watch the program using the Nvidia Shield.  Later went directly to the server PC and couldn't watch it there either.  Couldn't FF or Rewind to find a better spot, video would never start.

Thanks -Don

  • 3 weeks later...
Posted

embyserver (1).txt

It just happened again.  Emby appeared to record "NBC news with Lester Holt", and it produced a ".ts" file that cannot be played on any device, including the Emby server PC.  Can't jump forward, etc., just hung screen.

Log is attached, but I find it interesting that the server PC appears to have updated its time setting about 18:38 into the recording.  This is the same thing I saw in the logs the last time this occurred.  Not sure if it is significant..

Thanks!

-Don

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...