SAT>IP tuner does not work with NextPVR

[sub]

jcjefferies, are you able to PM me a download link to your npvr.db3?

[mvallevand]

jcjefferies, are you able to PM me a download link to your npvr.db3?

He posted them last week.  His custom XMLTV file provides just the CRID.  NextPVR use Title/CRID

Martin

[jcjefferies]

So far  it has worked far better than I expected! The first channels I tried were all SD which were given two entries in the EPG. The first of the two entries  each channel has was the original entry which used the XMLTV created by EPG Collector which I have been using for around 10 years. The second entry uses the DVB EPG used by Freesat and Terrestrial Freeview in UK with the Unique ID in the format "Title-Unique ID" which is now the standard ID format used to "Avoid Duplicate Recordings"

I was expecting to have to cancel the recording in the original first EPG entry and recreate it in the second entry but all so far all have appeared in the second entry using the DVB EPG. So far it has worked well on the first 4 channels which were all SD. It is not working correctly yet on two channels where one entry is SD and the other HD channel.

The server now only has one DVB-S2 tuner after one failed several months ago and NextPVR does not fully recognise my SAT>IP tuner on the live server. However my Test NextPVR server works with the SAT>IP tuners. If I copy the live server database to the test server the SAT>IP server no longer works. I did try and copy the recurring-backup to the test server but could not find a way to import the data!!

Chris

[mvallevand]

Once you and sub can figure out why your existing SAT>IP tuner isn't working my utility to update the recordings and deleted recording should be able to fix the duplicates issue I thought sub posted that there was a change to the tuning string for SAT>IP https://forums.nextpvr.com/showthread.ph...#pid588052 not sure if that is the issue.

You probably should start with the zipped logs with the beta software running with your production npvr.db3.

Martin

[jcjefferies]

Unfortunately I had to abandon my "Bright Idea" with two entries for the channels I regularly record!!! The four channels I used for the initial test were all recording New material so gave a false impression of working. When I added one of the channels I record most I was inundated with pending recordings including some I watched a few days ago! So have returned my Live server to its previous settings!!

I dont like playing with the live server settings which is why I have a test server. It had a clean install of Windows and NextPVR and my SAT>IP tuner has always worked as expected. Its currently running the "external"  V6.1.6 beta.

I just copied the database and config file from the live server to my test server running V6.1.6 and attempted to scan two of my SAT>IP tuners. Both scans failed almost immediately. Logs enclosed!

Chris

[mvallevand]

I don't know how your production server is working with SAT>IP since it is using device IP 192.168.1.95 and failing (confirmed with the npvr.db3) you sent earlier. However since your production database is set to use DVB-S not SAT>IP it hard to compare directly.

For the copy test it looks like you know how to use sqlite since there are extra tables in your database I would run these two command on the copy.

Code:

DELETE FROM SATIP_RECORDER WHERE capture_source_oid < 123;

UPDATE SATIP_RECORDER SET base_url = REPLACE(base_url,".95:",".225:");

Until you run my utility to fix your recordings you will get duplicates because of how your custom XMLTV created them. I would also change test config.xml to not remove missing files and keep the deletion history to ensure duplicate check work

Code:

.
    <DeletionHistoryDays>10000</DeletionHistoryDays>
    <AutoRemoveMissingRecordings>false</AutoRemoveMissingRecordings>
    <CheckForRenamedRecordings>false</CheckForRenamedRecordings>

I you want seen the production npvr.db3 and I can quickly make these changes However you would still need to change your recurring recordings to use the SAT>IP channels, after the working scan you might be able to merge them and then remove the DVB-S channels. Alternatively DVB-S will still work with the beta and also use the new OpenTV guide so you would only need to use SAT>IP later.

Martin

[jcjefferies]

Martin

I dont know the significance of IP 192.168.1.95 but it was last used by a RPi3 running LibreElec as a NextPVR client probably last year! It was more recently setup as a client for for my test server but uses a different IP address. The SAT>IP server is 192.168.1.225 (Static)

I have made changes to the database using an editor which ran in a web browser back in 2016. More recently I have used SQLite Studio to view the database but dont think I made any actual changes recently!

As a former Sysadmin before I retired I dont like messing about with live server so I want to try it on my test NextPVR Server first if I get you to make the changes for me please!

The three Config settings you suggested changing are currently set to 1 - 730  2&3 - True!

Latest database enclosed!

Chris

[mvallevand]

The .95 was in your production database (4 times) that is why I asked for you to remove the extra records and change the last one to .225 Potentially a legacy error from when .225 wasn't static.

Resend the zipped current "live' database and I will make the changes.

Martin

[mvallevand]

OK try this on your test server, I merged in the SAT>IP from the last scan. I kept the DVB-T that you had there before.

Remember to make those config.xml changes or you could lose the history.

There is still going to be an issue with "Bangers & Cash" since NextPVR doesn't always URL encode it as part of the unique_id

Martin

[jcjefferies]

Martin

Just a quick report as have to go out but it scans and finds the channels which it has not done with that database!

Chris