Tuner dvb_fe_set_parms failed

[baj1]

NextPVR failed to start recording "the game" today.  Granted we had a lot of recordings going but in theory we should have been fine.  Adapter 0 and 1 are the two tuners on my Hauppauge 2250, I also have a dual tuner HDHR we in theory we should be able to handle 4 recordings simultaneously.

There were 3 recording going before 12pm today and 4 scheduled for 12pm.  Three of those 4 were on the same channels recording before 12pm.  The recording on the "new" channel, my game, failed to start.  Based on the device-adapter1.log.1 file it appears the tuner was inactive prior to 12pm but then threw error "dvb_fe_set_parms failed" when it attempted to start.

I also noticed there were no log entries prior to 12pm, but it should have been 11:59am with the 1 minute pre-padding, so not sure what happened there.

The file was created in the NFL Football folder, but is 0 bytes.

So aside from not scheduling so many recordings around important things like football games, any thoughts?

Thanks,
Brad

[mvallevand]

I think your statement is wrong when NFL started I see the same thing I have been seeing NextPVR is tuning before stopping when there are back to back recordings.

12:00:00:395 [INFO] Tuning: 189028615 Hz
12:00:00:395 [INFO] Changing frequencies
12:00:00:395 [INFO] Stopped recording (/home/bmserver/Video_HD/Video_HD/A Cinderella Christmas (2016)/A.Cinderella.Christmas.(2016).ts)
12:00:00:395 [INFO] Stopped recording (/home/bmserver/Video_HD/Video_HD/Christmas With the Andersons (2016)/Christmas.With.the.Andersons.(2016).ts)
12:00:00:396 [INFO] Tuning: 189028615 Hz
12:00:00:396 [ERROR] dvb_fe_set_parms failed
12:00:00:396 [INFO] Creating writer for: /home/bmserver/Video_HD/Video_HD/NFL Football/NFL Football_20201129_12001500.ts

[baj1]

So is this a bug in NextPVR recording service for all of v5 or just a Linux thing?

[mvallevand]

What part of "Stopped recording" means unused to you. You have two 2hr Christmas movies start at 10am on that tuner and they get stopped without their 2 minutes of post padding.

Ok so you removed the post. Sub would have to comment on how he is handling this in linux.

Martin

[sub]

It is sounding like a bug in NextPVRs handling of multirecord in Linux. I’ll take a look at the logic a bit later today.

[baj1]

What part of "Stopped  recording" means unused to you.  You have two 2hr Christmas movies start at 10am on that tuner and they get stopped without their 2 minutes of post padding.

Ok so you removed the post.  Sub would have to comment on how he is handling this in linux.

Martin

Yeah, I mis-read the log file and somehow missed the recording start so I was thinking those were idle messages before noon.  I thought I was quick to delete but you are quicker!

[mvallevand]

I only have one tuner configured on my dual tuner but the logging is similar with no error.

19:00:00:265 [DEBUG] starting stream: /home/martin/recordings/LOL -)/Season 10/LOL -).S10E06.ts
19:00:00:265 [DEBUG] slip seconds: 1200
19:00:00:265 [DEBUG]
CHOT HD
19:00:00:267 [INFO] Tuning: 581028615 Hz
19:00:00:267 [INFO] Changing frequencies
19:00:00:268 [INFO] Stopped recording (/home/martin/recordings/Global National/Global National_20201129_18301900.ts)
19:00:00:483 [INFO] Tuning: 581028615 Hz
19:00:00:483 [INFO] using demux 'dvb1.demux0'
19:00:00:483 [INFO] using dvr 'dvb1.dvr0'
19:00:00:483 [DEBUG] waiting for signal lock

[baj1]

We had issues again tonight with back-to-back recordings.

Sub, have you had any time to look for possible causes in the code?

[sub]

I've just been looking at the code, and cant see anything obvious at fault. I've also had a couple of tries at reproducing the issue, but haven't seen it happen here

[mvallevand]

Since I have the same tuner, I just configured the second tuner for digital (I was using svideo) and setup a back to back recording to see if I see the same thing.

Martin