Filtering "Illegal characters in path"?

[notasage]

I'm running a very basic NextPVR 3.6.6 setup to record OTA shows. Just basic scheduling with no meta data. Occasionally the schedule seems include odd characters so I get failed recordings like:
The Big Burn: American Experience
Wildfire across the Northern Rockies.
Recording Error: Illegal characters in path.

How can I get NextPVR to filter out any illegal characters before it tries to create the file so my recordings are not missed? Schedule data is not perfect so a little sanity cleanup on NextPVR's part would probably benefit everyone.

Log snippet of the event attached (it does show the odd characters). If you need more, let me know.

Thanks!

[sub]

Hmm, it should already be filtering these characters.

If you can supply your NPVR.db3 database file, with the name of a show that has this problem, I'll try reproducing it and fix for the next release.

[mvallevand]

Hmm, it should already be filtering these characters.

If you can supply your NPVR.db3 database file, with the name of a show that has this problem, I'll try reproducing it and fix for the next release.

Look's like some non-ASCII junk in the beginning of the name can't post it but it shows in logs

2016-04-26 20:00:00.187 [DEBUG][9] Advanced manual recurring recording is using name: American Experience

Probably from an OTA EPG update.

Edit: Nope from the name of the Rule.

Martin

[notasage]

File attached as requested.

The recording was triggered by recurring entry with a filter of:
title like '%American Experience%'
In this case the show title was "The Big Burn: American Experience".

While I do most of my management work through the web interface, I believe this was entered through the GUI because there are still differences between what you can do on the web and in the GUI.

Let me know if you need anything else.

Thanks!

[notasage]

Running 3.7.7 now and still seeing an occasional failed recording with:
Recording Error: Illegal characters in path.

New npvr.db3 attached.

[sub]

Can you also post your logs, so I can see what happened when it tried to record 'American Experience' (earlier today/yesterday)?

[notasage]

Can you also post your logs, so I can see what happened when it tried to record 'American Experience' (earlier today/yesterday)?

Notepad++ is showing a couple SYN characters (23 dec / 0x16 hex). Same as my first report.

I've checked the TVGuide.xml and can find no SYN characters in the entire file and nothing odd about the American Experience entries.

Search the entire log for "American Experience", they seem to be present in the recurring log references also. They will probably get filtered in this paste, but look at this area of the log:

Code:

2016-07-30 02:15:08.688    [INFO][10]    UpdateRecurringRecording(121, '
American Experience'):
<Rules>
  <ChannelOID>7259</ChannelOID>

Could they have gotten into the recording rule maybe? The GUI and web interface don't show anything unusual.

I've attached my entire NRecord.log and TVGuide.xml.

[sub]

Could they have gotten into the recording rule maybe?

Yeah, this is the problem. The name of the show when you created the season recording included these characters. It looks like the affected shows are 'American Experience', 'Film School Shorts' and 'Curling'.

ie, basically you had some extra garbage in your zap2xml xmltv file when you created these recurring recordings. It doesn't look like the current xmltv file has this problem so you can probably just cancel those recurring recordings, and recreate them then is should be ok.