Tvheadend - Bug #1295 Record fail: "Waiting for Stream". Debug output says "GracePeriod Expired" 2012-10-03 18:15 - Guillaume B Status: Rejected Start date: 2012-10-03 Priority: Normal Due date: Assignee: Sutton % Done: 0% Category: PVR / DVR Estimated time: 0.00 hour Target version: Found in version: 3.3.7.gbe6c0 Affected Versions: Description Hello, My recordings seem to fail in a reproducible manner, with the error "Waiting for stream". I catched one failing just right now. Enabling debug output shows some errors: oct. 03 18:04:27 Service: Realtek DVB-T RTL2832/TNT COFDM BB: 482,000 khz/france 5: Status changed to [Graceperiod expired] oct. 03 18:04:29 Service: Subscription "DVR: C dans l'air": Adding adapter oct. 03 18:04:32 Service: Subscription "DVR: C dans l'air": Adding adapter oct. 03 18:04:32 Service: Subscription "DVR: C dans l'air": Probing adapter "_dev_dvb_adapter0_realtek_dvb_t_rtl2832482000000" without stealing for service "Realtek DVB-T RTL2832/TNT COFDM BB: 482,000 oct. 03 18:04:42 Service: Realtek DVB-T RTL2832/TNT COFDM BB: 482,000 khz/france 5: Status changed to [Graceperiod expired] oct. 03 18:04:43 Service: Subscription "DVR: C dans l'air": Adding adapter oct. 03 18:04:46 Service: Subscription "DVR: C dans l'air": Adding adapter oct. 03 18:04:46 Service: Subscription "DVR: C dans l'air": Probing adapter "_dev_dvb_adapter0_realtek_dvb_t_rtl2832482000000" without stealing for service "Realtek DVB-T RTL2832/TNT COFDM BB: 482,000 I went to the Adapter tab and saw that the DVB-T tuner was tuned to the correct frequency (482MHz): http://i.imgur.com/o2otu.png The signal quality is top notch: http://i.imgur.com/htr5ml.png ( HiRes: http://i.imgur.com/htr5ml.png ) So, I don't know. I'm pretty sure I can reproduce the problem on my RPi, it looks like immediately off a fresh start of tvheadend, any record will work; but after that the next record will fail. If you need more information, I can provide. 2018-08-26 1/6
History #1-2012-10-03 18:20 - Sutton It suggests, though can't be sure yet. That nothing is being received. Just being tuned to a frequency does not indicate an ability to receive the stream. Also do you have signal quality monitoring enabled? If not everything will be 100%. #2-2012-10-03 19:07 - Guillaume B Yes, signal monitoring is enabled. I agree with you, it could be that I receive nothing from the adapter: I'm using the RPi with a powered hub, but it seems that it still doesn't like USB peripherals that much. Is there a way that I can I test if the adapter receives something with tvheadend? #3-2012-10-03 19:12 - Guillaume B After restarting tvheadend, I still have the problem, so I guess you're right: the problem comes from the tuner. SAD FACE. #4-2012-10-03 19:47 - Ronald van Eijck grace-period expired hints at a new smart card that has all channels enabled for the first couple of weeks.if you use a smart card in your tuner check if it works correctly in your TV or some other device. A grace-period is common on smart cards to make sure you have some time to register the card but can still view all channels without waiting. #5-2012-10-03 19:50 - Sutton The grace period mentioned here simply refers to how long TVH allows before it will timeout the subscription due to lack of data. In other words this implies TVH is not receiving any information from this transponder. Can you receive services on other transponders? Or even services on that transponder (which would indicate a definite software bug). #6-2012-10-04 18:03 - Sutton - Status changed from New to Rejected I'm rejecting this, I'm pretty sure the issue here is the tuner and not TVH. Though this does seem to be being reported by a few people recently so I won't rule out that TVH is doing something odd. But until someone can demonstrate a reasonable explanation as to why this is not the tuner I'm not going to investigate further. 2018-08-26 2/6
#7-2012-10-23 04:44 - Joe Cruz - File Screenshot - 10222012-10_39_26 PM.png added This is happening to me. I can't record. It says that it can't steal the service but the adapter is not in use. Debug: Service: Subscription "DVR: uy": Adding adapter "_dev_dvb_adapter0_hdhomerun_atsc575028615" for service "HDHomeRun ATSC/575,028 khz/wogx-dt" Oct 22 22:38:41 Service: Subscription "DVR: uy": Adding adapter "_dev_dvb_adapter0_hdhomerun_atsc575028615" for service "HDHomeRun Oct 22 22:38:41 Service: Subscription "DVR: uy": Probing adapter "_dev_dvb_adapter0_hdhomerun_atsc575028615" without stealing for service "HDHomeRun Oct 22 22:38:43 dvb: "575,028 khz" on adapter "HDHomeRun ATSC", status changed to OK Oct 22 22:38:45 dvb: "575,028 khz" on adapter "HDHomeRun ATSC", status changed to No signal Oct 22 22:38:46 dvb: "575,028 khz" on adapter "HDHomeRun ATSC", status changed to OK Oct 22 22:38:48 dvb: "575,028 khz" on adapter "HDHomeRun ATSC", status changed to No signal Oct 22 22:38:51 Service: HDHomeRun ATSC/575,028 khz/wogx-dt: Status changed to [Graceperiod expired] Oct 22 22:38:53 Service: Subscription "DVR: uy": Adding adapter "_dev_dvb_adapter0_hdhomerun_atsc575028615" for service "HDHomeRun Oct 22 22:38:55 Service: Subscription "DVR: uy": Adding adapter "_dev_dvb_adapter0_hdhomerun_atsc575028615" for service "HDHomeRun Oct 22 22:38:55 Service: Subscription "DVR: uy": Probing adapter "_dev_dvb_adapter0_hdhomerun_atsc575028615" without stealing for service "HDHomeRun Oct 22 22:38:57 dvb: "575,028 khz" on adapter "HDHomeRun ATSC", status changed to OK Oct 22 22:38:59 dvb: "575,028 khz" on adapter "HDHomeRun ATSC", status changed to No signal Oct 22 22:39:00 dvb: "575,028 khz" on adapter "HDHomeRun ATSC", status changed to OK Oct 22 22:39:02 dvb: "575,028 khz" on adapter "HDHomeRun ATSC", status changed to No signal Oct 22 22:39:05 Service: HDHomeRun ATSC/575,028 khz/wogx-dt: Status changed to [Graceperiod expired] Oct 22 22:39:07 Service: Subscription "DVR: uy": Adding adapter "_dev_dvb_adapter0_hdhomerun_atsc575028615" for service "HDHomeRun Oct 22 22:39:07 dvb: /dev/dvb/adapter0 closing frontend 2018-08-26 3/6
Oct 22 22:39:07 dvb: /dev/dvb/adapter0 stopping thread Oct 22 22:39:07 dvb: /dev/dvb/adapter0 stopped thread Oct 22 22:39:09 Service: Subscription "DVR: uy": Adding adapter "_dev_dvb_adapter0_hdhomerun_atsc575028615" for service "HDHomeRun Oct 22 22:39:09 Service: Subscription "DVR: uy": Probing adapter "_dev_dvb_adapter0_hdhomerun_atsc575028615" without stealing for service "HDHomeRun Oct 22 22:39:09 dvb: /dev/dvb/adapter0 opened frontend /dev/dvb/adapter0/frontend0 Oct 22 22:39:09 dvb: /dev/dvb/adapter0 started dvr thread Oct 22 22:39:09 dvb: "/dev/dvb/adapter0" tuning to "575,028 khz" (Transport start) Oct 22 22:39:15 dvb: "575,028 khz" on adapter "HDHomeRun ATSC", status changed to OK Oct 22 22:39:18 dvb: "575,028 khz" on adapter "HDHomeRun ATSC", status changed to No signal Oct 22 22:39:19 Service: HDHomeRun ATSC/575,028 khz/wogx-dt: Status changed to [Graceperiod expired] Oct 22 22:39:20 Service: Subscription "DVR: uy": Adding adapter "_dev_dvb_adapter0_hdhomerun_atsc575028615" for service "HDHomeRun Oct 22 22:39:22 Service: Subscription "DVR: uy": Adding adapter "_dev_dvb_adapter0_hdhomerun_atsc575028615" for service "HDHomeRun Oct 22 22:39:22 Service: Subscription "DVR: uy": Probing adapter "_dev_dvb_adapter0_hdhomerun_atsc575028615" without stealing for service "HDHomeRun Oct 22 22:39:24 dvb: "575,028 khz" on adapter "HDHomeRun ATSC", status changed to OK Oct 22 22:39:26 dvb: "575,028 khz" on adapter "HDHomeRun ATSC", status changed to No signal Oct 22 22:39:27 dvb: "575,028 khz" on adapter "HDHomeRun ATSC", status changed to OK Oct 22 22:39:29 dvb: "575,028 khz" on adapter "HDHomeRun ATSC", status changed to No signal Oct 22 22:39:32 Service: HDHomeRun ATSC/575,028 khz/wogx-dt: Status changed to [Graceperiod expired] Oct 22 22:39:34 Service: Subscription "DVR: uy": Adding adapter "_dev_dvb_adapter0_hdhomerun_atsc575028615" for service "HDHomeRun Oct 22 22:39:36 Service: Subscription "DVR: uy": Adding adapter "_dev_dvb_adapter0_hdhomerun_atsc575028615" for service "HDHomeRun Oct 22 22:39:36 Service: Subscription "DVR: uy": Probing adapter "_dev_dvb_adapter0_hdhomerun_atsc575028615" without stealing for service "HDHomeRun Oct 22 22:39:38 dvb: "575,028 khz" on adapter "HDHomeRun ATSC", status changed to OK Oct 22 22:39:40 dvb: "575,028 khz" on adapter "HDHomeRun ATSC", status changed to No signal 2018-08-26 4/6
Oct 22 22:39:41 dvb: "575,028 khz" on adapter "HDHomeRun ATSC", status changed to OK Oct 22 22:39:43 dvb: "575,028 khz" on adapter "HDHomeRun ATSC", status changed to No signal Oct 22 22:39:46 Service: HDHomeRun ATSC/575,028 khz/wogx-dt: Status changed to [Graceperiod expired] Oct 22 22:39:48 Service: Subscription "DVR: uy": Adding adapter "_dev_dvb_adapter0_hdhomerun_atsc575028615" for service "HDHomeRun Oct 22 22:39:50 Service: Subscription "DVR: uy": Adding adapter "_dev_dvb_adapter0_hdhomerun_atsc575028615" for service "HDHomeRun Oct 22 22:39:50 Service: Subscription "DVR: uy": Probing adapter "_dev_dvb_adapter0_hdhomerun_atsc575028615" without stealing for service "HDHomeRun Oct 22 22:39:52 dvb: "575,028 khz" on adapter "HDHomeRun ATSC", status changed to OK Oct 22 22:39:54 dvb: "575,028 khz" on adapter "HDHomeRun ATSC", status changed to No signal Oct 22 22:39:55 dvb: "575,028 khz" on adapter "HDHomeRun ATSC", status changed to OK Oct 22 22:39:57 dvb: "575,028 khz" on adapter "HDHomeRun ATSC", status changed to No signal Oct 22 22:40:00 Service: HDHomeRun ATSC/575,028 khz/wogx-dt: Status changed to [Graceperiod expired] Oct 22 22:40:00 subscription: "DVR: uy" unsubscribing from "WOGX-DT" Oct 22 22:40:00 dvr: "uy" on "WOGX-DT": End of program: Time missed Oct 22 22:40:07 dvb: "575,028 khz" on adapter "HDHomeRun ATSC", status changed to OK Oct 22 22:40:07 dvb: /dev/dvb/adapter0 closing frontend Oct 22 22:40:07 dvb: /dev/dvb/adapter0 stopping thread Oct 22 22:40:07 dvb: /dev/dvb/adapter0 stopped thread At some point it complained of signal quality but see the screen shot taken at the time. #8-2012-10-23 08:24 - hanza hanza sometimes it happens to me too. can be resolved by switching to other channel and then back to recording channel, then it can lock and recording starts #9-2012-10-23 10:43 - Sutton This does not indicate its failing to use the adapter (the without stealing, just indicates it was able to use the adapter "without stealing" from another subscriber, i.e. its not in use). The problem you're having is "Grace Period Expired", which means TVH failed to receive any data from the adapter within the expected period of time (several seconds). This does occasionally happen with various DVB adapters due to various problems with the DVB API and/or hardware. The 2018-08-26 5/6
problems are usually transient (and not related to signal level, though its worth checking that in case that is also a factor). This does seem to happen more often with some adapters (HDHomerun included) than others. Unfortunately there isn't much TVH can do about this, apart from possibly re-sending the tuning request, but it seems to be doing this (but I can check that it is actually re-sending the request). I think its quite telling that the signal level keeps jumping from OK to no signal, clearly something is wrong with the adapter. Though as pointed out above its probably a transient firmware failure that will go away later. #10-2012-10-23 16:26 - Joe Cruz Thanks. Your information made me think of another option and it worked. I am using wireless between where the HDHR is located and the computer doing the recording. It puzzles me that if I click on a channel from the HDHR config gui VLC plays it immediately. However when I click on the same channel from the TVheadend browser it fails. It seems like there is a difference between what one does vs the other in calling the same channel. My solution was to use wired connection between the two points. I did a test recording lasting 2 minutes and it worked fine. That solves it for now but does not answer why over wireless VLC plaays the channel when clicked on HDHR config gui but not from TVheadend in browser. #11-2012-10-23 16:31 - Sutton Well if I had to hazard a guess I'd have to say its probably down to the hdhomerun DVB API wrappers. We get no end of complaints about HDHomerun, and it almost always relates to the DVB API interaction. Presumably this HDHR config UI you're using is written by the manufacturers and uses their official API that they fully understand, yada yada, so you'd expect that to work. I'd try bugging whoever provides the hdhomerun dvb api wrappers. However if we can find some simple solution in TVH to workaround such problems I'm open to suggestions. #12-2012-10-23 17:09 - Joe Cruz Thanks again. I understand. Just a though though, is it possible for TVH so act as if I was manually clicking on the HDHR config gui and actually let the HDHR gui send the request? Sorry if I sound ignorant but I'm just and end user with no programming skills. Files Screenshot - 10222012-10_39_26 PM.png 361 KB 2012-10-23 Joe Cruz 2018-08-26 6/6