Login at Kodi Home

jfabernathy · 2020-10-10, 12:40

(2020-10-10, 12:36)DarrenHill Wrote: I'll try and find a suitable programme to record and will see on my system (Pi4 + LE 9.2.5 + TVH server + HDHomerun - so not so different to yours).

Thanks, and I'm setting up a test case on a Ubuntu 20.04 system with TVHeadend 4.2.8-36~g5bdcfd8ac and see if I can record something longer than 2hr on that system.

**DarrenHill** · 2020-10-10, 13:01

I've set up a 2h30m programme this afternoon via the Kodi EPG and a 6hr programme in parallel via the TVH web dashboard.

Will report back this evening once both have finished what lengths I get.

jfabernathy · 2020-10-10, 13:07

(2020-10-10, 13:01)DarrenHill Wrote: I've set up a 2h30m programme this afternoon via the Kodi EPG and a 6hr programme in parallel via the TVH web dashboard.

Will report back this evening once both have finished what lengths I get.

Thanks, what's key is to compare the reported lengths vs. the actual lengths.

mcelliott · 2020-10-10, 14:39

(2020-10-10, 11:19)jfabernathy Wrote: Well, I was hoping that someone else who uses Kodi and the TVHeadend addon on any device, and specifically a Raspberry Pi 4 could confirm that they had every recorded a program longer than 2 hours. For me it's key to find out if I'm dealing with TVH only issue or a is it specific to Raspberry or LibreELEC.

All the time, SD and HD. There is no fundamental problem.

Next time you provide logs, you need to provide TVHeadEnd logs, not Kodi logs. All Kodi will show is playing the recordings.

jfabernathy · (This post was last modified: 2020-10-10, 18:38 by jfabernathy.)

(2020-10-10, 14:39)mcelliott Wrote:
(2020-10-10, 11:19)jfabernathy Wrote: Well, I was hoping that someone else who uses Kodi and the TVHeadend addon on any device, and specifically a Raspberry Pi 4 could confirm that they had every recorded a program longer than 2 hours. For me it's key to find out if I'm dealing with TVH only issue or a is it specific to Raspberry or LibreELEC.

All the time, SD and HD. There is no fundamental problem.

Next time you provide logs, you need to provide TVHeadEnd logs, not Kodi logs. All Kodi will show is playing the recordings.

Sorry if this is a dumb question, but where is exactly the tvheadend log located. I know about the one you see if enabled in the Web interface at the bottom of the screen, but can't find the actual file.

EDIT:
I finally found the location of the log file: /storage/.kodi/userdata/addon_data/service.tvheadend42/service.log

I'll post it after I complete my 4 hour record tests running today if the previous problem is repeated

**DarrenHill** · (This post was last modified: 2020-10-10, 23:02 by DarrenHill.)

First recording is finished (set up via Kodi) - should be 2.5 hours, and that's what it recorded and played back as (Star Trek JJ Abrams version film). Length reported by Windows file manager for the film is 2:30:17, and that's what also plays via VLC on my Windows machine as well accessing the file directly.

Second recording is currently an hour in and ongoing (set via the web dashboard), but thusfar everything is working exactly as it should.

HTS Tvheadend 4.2.8-36 ~ LibreELEC Tvh-addon v9.2.0.123 running on a LE 9.2.5 Pi4, taking input from a HDHR Quatro.

jfabernathy · 2020-10-10, 23:12

Well now I know what causes the problem, but not why. Here's what I know:

The setup for my previous system that could not record shows longer than 2 hours.

Raspberry Pi 4 4GB RAM, LibreELEC 9.2.5 image installed to USB3-SATA SSD with Raspberry pi Imager app.
HDHR Connect tuners (2) setup as IPTV Network Automatic.
EPG using Schedule Direct SD4TVH grabber

Today I rebuild as follows:

RPI4 with LibreELEC 9.2.5 installed on microSD card with USB3-SATA SSD for recording storage only.
HDHR Connect Tuners (2) setup using DVB inputs -> TV Adapters with ATSC-T Network with US ATSC-T center freq.
EPG using Internal XMLTV tv_grab_file.

Using the TVH web interface I setup to record two 4hr football games and I got all 4 hours of both games.

So the problem is caused by one of the changes. My guess is the use of IPTV vs. DVB TV adapters.

I doubt the EPG method would matter. And it doesn't make sense to me that booting off of microSD vs. USB SSD
would matter.

On my other test today:

I used an Ubuntu 20.04 PC and installed TVHeadend from the PPA and configure it's
HDHR Quatro tuners (only 2 of them) as IPTV Network Automatic.
The EPG this time was XMLTV: Multinational (Schedules Direct JSON web services with SQLite DB)

On this test I recorded the same 2 football games and both were only 2 hours long. I'll dig through the log files and post those later.

So it seems pretty obvious to me that using HDHR tuners as IPTV inputs somehow limits your recording time to 2 hours.

I prefer the IPTV method because it's share tuners. So 2 tuners could be used by TVH and 2 could be used by a Smart TV
running the HDHomerun App.

**DarrenHill** · 2020-10-10, 23:19

Mine are all set up as DVB-T inputs, so that would fit perfectly with your thinking.

jfabernathy · (This post was last modified: 2020-10-10, 23:26 by jfabernathy.)

on the Ubuntu system that used IPTV for HDHR I looked at the log and didn't see much. the recordings started at 12N and should stop at 4PM but the recordings were only 2 hr long

xepajamaza (paste)

jfabernathy · 2020-10-11, 00:27

I think I'm getting closer. when you use IPTV Network Automatic you need a .m3u file. Mine had entries like:

Code:

#EXTM3U

#EXTINF:-1 tvg-name="UNC-TV" tvh-chnum="4.1",UNC-TV

http://192.168.0.21:5004/auto/v4.1?duration=7200

#EXTINF:-1 tvg-name="ROOTLE" tvh-chnum="4.2",ROOTLE

http://192.168.0.21:5004/auto/v4.2?duration=7200

#EXTINF:-1 tvg-name="UNC-EX" tvh-chnum="4.3",UNC-EX

http://192.168.0.21:5004/auto/v4.3?duration=7200

#EXTINF:-1 tvg-name="NCCHL" tvh-chnum="4.4",NCCHL

http://192.168.0.21:5004/auto/v4.4?duration=7200

Note the duration=7200 which is 2 hours. I'm going to make the edits as in:

Code:

 #EXTM3U

#EXTINF:-1 tvg-name="UNC-TV" tvh-chnum="4.1",UNC-TV

http://192.168.0.27:5004/auto/v4.1

#EXTINF:-1 tvg-name="ROOTLE" tvh-chnum="4.2",ROOTLE

http://192.168.0.27:5004/auto/v4.2

#EXTINF:-1 tvg-name="UNC-EX" tvh-chnum="4.3",UNC-EX

http://192.168.0.27:5004/auto/v4.3

#EXTINF:-1 tvg-name="NCCHL" tvh-chnum="4.4",NCCHL

http://192.168.0.27:5004/auto/v4.4

and see what happens.

jfabernathy · 2020-10-11, 11:23

Solved! the ?duration=7200 in the .m3u file for the IPTV Network Automatic was the issue. I can't remember where I got the m3u file, but clearly that parameter was causing the problem and I have no idea why it was ever used.

Thanks all for helping.

**DarrenHill** · 2020-10-11, 12:01

Thread marked solved.