Cybergy 4 Posted August 10, 2018 Posted August 10, 2018 (edited) I've had 2 runaway recordings in as many days. I set 2 different shows/channels to record via the EPG (first was a single episode, second was a series recording). In both cases the recording looked bad (HEAVY pixellation, blank screen at times, technicolor "banners" across the screen, etc). The recordings were supposed to be 1 hour but both ended up near 1,500 minutes. In another case, when I set a show to record 1 minute early, the recording appears to have started when I wanted, but stopped at the turn of hour, one minute later. Do bad feeds cause runaway recordings? Does the extra minutes added before and after the recording normally end at the hour or 1/2 hour? Edited August 10, 2018 by Cybergy
Luke 42083 Posted August 11, 2018 Posted August 11, 2018 Hi there, please attach the emby server log so that we can look closely at an example. thanks.
Cybergy 4 Posted August 22, 2018 Author Posted August 22, 2018 Hey Luke, Sorry for the late response. Here's a recording example; - The Pacific War in Color - 21 Aug 2018 - 492 mins (ends at 3:03pm) I have my recordings set to run an extra minute if possible. I have others, but no log files due to a windows re-install. I'll provide more later if needed. embyserver-63670492799.txt
Luke 42083 Posted August 22, 2018 Posted August 22, 2018 According to the log it completed after 59 minutes like it was supposed to.
Cybergy 4 Posted August 22, 2018 Author Posted August 22, 2018 Interesting. Maybe I need to read some of the wiki but unless the tiles in recordings are a summary of minutes, it is misreporting the recording length. I’ll read up.
Cybergy 4 Posted August 22, 2018 Author Posted August 22, 2018 I used a utility called MediaInfo to look at 3 recordings of the same show. All are approximately the same size, but the duration in MI as well as Emby shows vastly different run-times. Screen Caps of MediaInfo on the 3 episodes attached.
Luke 42083 Posted August 23, 2018 Posted August 23, 2018 That's just the duration that ffprobe is giving us. We may need to look at repairing the headers of the .ts file after completing the recording. thanks.
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now