v5.0.5 not recording: failed to start stream

[sub]

If that doesn't get your going, can you go to the Settings->Channels screen, and hit the trash can icon top/right to delete all the channels, then restart NextPVR (to reset the logs), then go back in and just scan the legacy device, and just try watching one of those channels, then post the logs again.

[rkulagow]

I deleted the devices and restarted the VM. Went to devices, selected the legacy device, declined the copy of existing sources. Ran a scan.

Went to the EPG, and selected to record "The Bold and the Beautiful" on 2.1. Failed with Connection Refused.

[mvallevand]

If you disable the newer device with ctrl does that help I see the line

2020-05-28 12:52:08.607 [DEBUG][8] source@1

which I don't get.

Martin

[sub]

If you disable the newer device with ctrl does that help  I see the line

2020-05-28 12:52:08.607 [DEBUG][8] source@1

which I don't get.

Martin

This message is indicating it didn't have <freq> in the tuning request, so wasn't treated as a legacy tuning.

rkulagow, this identifies that your problem is happening earlIER, when the channels were scabbed, rather than at the time you go to watch the channel.

[sub]

When you did the scan in that previous log, where there any channels in the database already? (like on the other HDHR)

[rkulagow]

There may have been other channels. I'm juggling a lot of things right now!

What's the equivalent of nuking from orbit? Should I delete all the devices, restart, then come back in, perform the scan on the legacy OTA device and try scheduling again?

[sub]

What's the equivalent of nuking from orbit?

You can stop NextPVR, delete the npvr.db3 file, then restart. It'll create a new empty database.

[rkulagow]

Only the legacy devices are defined. I tried to record "Hot Bench", and the recording failed.

[sub]

Ok, I can see at scan time it's not correctly identifying the device as a legacy device. I'm checking why.

[sub]

Can you try that clean scan again with this version, then post the logs again?