Replies: 3 comments 3 replies
-
I just noticed that you had changed the order back to the perl script 2 commits ago. I am using the most recent commit in docker that I can tell. |
Beta Was this translation helpful? Give feedback.
-
Alright so I just looked at the output the current output is:
I had an old perl output that was like this:
I think there was an option name first that output like this
I think I should be able to just add an extra display name to make the output as
|
Beta Was this translation helpful? Give feedback.
-
First update was to make it like my last example
Then from another request use
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I am switching over to your setup because I have recently started having troubles with the historic perl script. I will be posting over there soon.
What I see with your setup and the older perl setup is a slight change in the channel id's. (This is using OTA)
WUTVDT2 ROAR 29.2Yours is as such:
The historical perl is:
1
2 29.2 WUTVDT2
3 29.2
4 WUTVDT2
Using xteve to provide my epg to plex and tivimate.
What I notice is that xteve must have it hard coded to grab line 3, then line 2, then channel id.
So when I am setting up my channel mappings with the old per script, I see:
29.2 (29.2 WUTVDT2) (I29.2.42947.zap2it.com)
When I use your script I see:
ROAR (WUTVDT2) (42947)
My question here is, would it be ok to bring your setup back in line with the old way? When trying to map the way your script has them listed, I don't see the channel number which makes it quite difficult to map as not all channels call signs in the guide match what the hdhr is producing. I am also not sure if this change would break other setups.
Hope this makes sense.
Beta Was this translation helpful? Give feedback.
All reactions