+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: recorded file does not match recording time (/t-recorded-file-does-not-match-recording-time)
recorded file does not match recording time - lawrenceacraig - 2025-07-05
Hi there,
I experienced an issue today where I recorded a 4-hour programme, and the recorded file ended up being only 1h35 long. The logs don't make note of any failures or issues. It shows the recording starting and finishing on time (4 hours in total).
Any idea what might have happened? Or how I can investigate further?
Code:
2025-07-05 09:59:58.970 +01:00] [INF] [3] Jellyfin.LiveTv.Recordings.RecordingsManager: Writing file to: "/Volumes/Media Hub/Recordings/Live British & Irish Lions Tour/Live British & Irish Lions Tour 2025_07_05_10_00_00 - NSW Waratahs v British and Irish Lions.ts"
[2025-07-05 09:59:59.294 +01:00] [INF] [30] Jellyfin.LiveTv.Recordings.RecordingsManager: Copying recording stream to file "/Volumes/Media Hub/Recordings/Live British & Irish Lions Tour/Live British & Irish Lions Tour 2025_07_05_10_00_00 - NSW Waratahs v British and Irish Lions.ts"
[2025-07-05 09:59:59.298 +01:00] [INF] [30] Jellyfin.LiveTv.Recordings.RecordingsManager: Triggering refresh on "/Volumes/Media Hub/Recordings/Live British & Irish Lions Tour/Live British & Irish Lions Tour 2025_07_05_10_00_00 - NSW Waratahs v British and Irish Lions.ts"
[2025-07-05 13:59:59.984 +01:00] [INF] [55] Jellyfin.LiveTv.Recordings.RecordingsManager: Recording stopped: "/Volumes/Media Hub/Recordings/Live British & Irish Lions Tour/Live British & Irish Lions Tour 2025_07_05_10_00_00 - NSW Waratahs v British and Irish Lions.ts"
[2025-07-05 13:59:59.987 +01:00] [INF] [55] Jellyfin.LiveTv.Recordings.RecordingsManager: Triggering refresh on "/Volumes/Media Hub/Recordings/Live British & Irish Lions Tour/Live British & Irish Lions Tour 2025_07_05_10_00_00 - NSW Waratahs v British and Irish Lions.ts"
[2025-07-05 14:00:00.011 +01:00] [INF] [55] MediaBrowser.MediaEncoding.Encoder.MediaEncoder: Starting "/Applications/Jellyfin.app/Contents/MacOS/ffprobe" with args "-analyzeduration 200M -probesize 1G -i file:\"/Volumes/Media Hub/Recordings/Live British & Irish Lions Tour/Live British & Irish Lions Tour 2025_07_05_10_00_00 - NSW Waratahs v British and Irish Lions.ts\" -threads 0 -v warning -print_format json -show_streams -show_chapters -show_format"RE: recorded file does not match recording time - theguymadmax - 2025-07-05
What did the guide data have it set to? My guess is that it was only scheduled for an hour and a half.
RE: recorded file does not match recording time - lawrenceacraig - 2025-07-06
I thought that myself so I checked the EPG and it was also for 4 hours. Plus if you look at the logs I have provided, you can see the time stamps starting at [2025-07-05 09:59:58.970 +01:00] and the recording stopping at [2025-07-05 13:59:59.984 +01:00] which is the 4 hours.
RE: recorded file does not match recording time - EPG Tech Talk - 2025-07-22
This issue, where a recorded file's length differs from the recording log, often points to a problem with the source signal or how Jellyfin processed it. Even if logs show a recording started and finished on time, silent failures can occur.
First, check the EPG (Electronic Program Guide) data for the specific program. Verify that the broadcast schedule matched the actual recording duration. Sometimes, broadcast times shift without EPG updates, or a program ends early.
Next, examine the stream itself. If possible, play back the recorded file in a different media player to confirm its actual length. This can rule out a display error within Jellyfin.
Consider the LiveTV source. Was there any interruption to the signal during the recording? Brief signal drops, even if not explicitly logged as errors, can cause data loss and result in a shorter file. This is especially true for unstable network connections or antenna issues.
Finally, review Jellyfin's transcoding settings for recordings. Incorrect settings or insufficient system resources could lead to corruption or incomplete files, even if the recording process itself appears to run for the full duration. Look for any warnings or errors in the system logs that might relate to transcoding or disk write operations around the time of the recording.