(2020-03-29, 07:24 PM)sub Wrote: chris4824 are you using the current release? I renamed one of my channels A&E, and it is working ok, and the xml did not end up with the problematic "&" character.
Yes latest release. it works fine until it creates the next ts file. then it errors.
(2020-03-29, 05:35 PM)sub Wrote: I'll check the A&E thing when I've had my breakfast.
(2020-03-29, 03:56 PM)chris4824 Wrote: I have a wintv 885 digital tuner and with ver4 I was able to get all my channels but with ver5 it didn't seem to pick up all my channels so to fix the issue I copied my npvr.db3 from ver4 to ver5 and everything is good now
The usually reason for this is the tuning files being out of date for your area. If you try scanning All Countries / All Regions, does it then find all your channels?
No. I have tried all of them and it finds the same ones every time. When I replaced the file from v4 it has all my channels. No big deal since I was able to get them back from replacing the file. Just thought you may wanted to know. If you need anything from me to help let me know.
If you want to let me know what frequency channels were missing from your v5 scan, then post the logs showing a scan in v5, I'll check what happened.
/
I'll run a scan and post the logs. its quite of few of channels thats missing. could I post both npvr.db3.. would you be able to see the channels missing from that file?
(2020-03-29, 07:24 PM)sub Wrote: chris4824 are you using the current release? I renamed one of my channels A&E, and it is working ok, and the xml did not end up with the problematic "&" character.
Yes latest release. it works fine until it creates the next ts file. then it errors.
I just checked that, and it's still fine here.
Can you restart your recording service, then reproduce the problem and post the logs again - so I can see the service startup, and the stream starting, which were missing from your previous log.
2020-03-29, 08:11 PM (This post was last modified: 2020-03-29, 08:13 PM by chris4824.)
(2020-03-29, 07:57 PM)sub Wrote:
(2020-03-29, 07:35 PM)chris4824 Wrote:
(2020-03-29, 07:24 PM)sub Wrote: chris4824 are you using the current release? I renamed one of my channels A&E, and it is working ok, and the xml did not end up with the problematic "&" character.
Yes latest release. it works fine until it creates the next ts file. then it errors.
I just checked that, and it's still fine here.
Can you restart your recording service, then reproduce the problem and post the logs again - so I can see the service startup, and the stream starting, which were missing from your previous log.
edit. forgot the log
renamed it back to A&E and did the same. here is the log from start of service to end of service. Gonna change it back and get a log of scanning channels for you.
In your earlier logs, it referred to files like: E:\NPVRBuffer\live-A&E-18.ts. Do you actually have a filename in that directory with the "&" character? The current version added logic to strip these invalid characters when deciding on the file name, so you'd instead get files with names like "live-AE-18.ts"
Where are you trying to watch these streams? Web app? NextPVR.exe? Kodi? somewhere else? It's possible I missed some specific case.
(2020-03-29, 08:29 PM)sub Wrote: In your earlier logs, it referred to files like: E:\NPVRBuffer\live-A&E-18.ts. Do you actually have a filename in that directory with the "&" character? The current version added logic to strip these invalid characters when deciding on the file name, so you'd instead get files with names like "live-AE-18.ts"
Where are you trying to watch these streams? Web app? NextPVR.exe? Kodi? somewhere else? It's possible I missed some specific case.
Yes there was one with that filename. I first had the channel names A & E. So I thought it was the spaces so I changed it to A&E and it still didn't work. Once I took out the & it worked fine but yes both times it had a filename with &.
I have the logs for the scan but I'll wait to post them if you like.