Recording Error: No errors, but no data delivered.

[jksmurf]

Hmmm

Been getting these errors recently. Lots of them.

Code:

Just Recording Error: No errors, but no data delivered. This is usually because the device failed to lock a signal.

Then

Code:

Recording Error: Device failed to start

Is the computer not waking NextPVR to record do you think?
I ask as when I go into the Channel manually it has a stream which seems to work fine and the show ts and ts map file show fine.

netstat -an | find /i "listening" >LISTEN.txt

Code:

TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2869           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3689           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5040           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5357           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5916           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:7680           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:7969           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:8337           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:8866           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:8968           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49664          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49665          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49666          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49667          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49711          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49730          0.0.0.0:0              LISTENING
  TCP    127.0.0.1:5939         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:27015        0.0.0.0:0              LISTENING
  TCP    127.0.0.1:28380        0.0.0.0:0              LISTENING
  TCP    127.0.0.1:28385        0.0.0.0:0              LISTENING
  TCP    192.168.1.10:139       0.0.0.0:0              LISTENING
  TCP    [::]:135               [::]:0                 LISTENING
  TCP    [::]:445               [::]:0                 LISTENING
  TCP    [::]:2869              [::]:0                 LISTENING
  TCP    [::]:5357              [::]:0                 LISTENING
  TCP    [::]:7680              [::]:0                 LISTENING
  TCP    [::]:8866              [::]:0                 LISTENING
  TCP    [::]:49664             [::]:0                 LISTENING
  TCP    [::]:49665             [::]:0                 LISTENING
  TCP    [::]:49666             [::]:0                 LISTENING
  TCP    [::]:49667             [::]:0                 LISTENING
  TCP    [::]:49711             [::]:0                 LISTENING
  TCP    [::]:49730             [::]:0                 LISTENING

[EDIT]I recently changed both pre and post padding to 0, would this have had any affect?
[EDIT]Ref this thread https://forums.nextpvr.com/showthread.ph...gnal/page9 I don't have a <HDHRBasePort> setting in config.xml so assume it's not needed any more.

k.

[sub]

Those are two different errors. Neither are typically NextPVR issues. I can't let you much more than the what the error says:

"No errors, but no data delivered. This is usually because the device failed to lock a signal."

"Device failed to start"

To get anything more than this, you'd probably look for patterns. For example, with the "No errors, but no data delivered" maybe check if it's always the same channel(s). You might get a week signal on these channels, or the broadcaster has moved these channels and it'll never managed to lock onto a channel (and you'd need to rescan to find the new tuning).

For the "Device failed to start". It's either in use elsewhere, or the driver has shat itself (probably requiring reboot before it comes right)

[jksmurf]

Those are two different errors. Neither are typically NextPVR issues. I can't let you much more than the what the error says:

"No errors, but no data delivered. This is usually because the device failed to lock a signal."

"Device failed to start"

OK

To get anything more than this, you'd probably look for patterns. For example, with the "No errors, but no data delivered" maybe check if it's always the same channel(s). You might get a week signal on these channels, or the broadcaster has moved these channels and it'll never managed to lock onto a channel (and you'd need to rescan to find the new tuning).

It's Digital TV over an IPTV Box so can't see why it would be a weak signal right?

For the "Device failed to start". It's either in use elsewhere, or the driver has shat itself (probably requiring reboot before it comes right)

. Right. Off to clean up that nasty mess then.

k.

[sub]

HDMI from your Colossus? Maybe some channels have HDCP? This can cause a colossus to not deliver any data.

[jksmurf]

HDMI from your Colossus? Maybe some channels have HDCP? This can cause a colossus to not deliver any data.

I have a splitter that seems to work when I run it manually but yes a good possible reason all the same.