-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EPG import fails for xmltv.info #57
Comments
Well actually it seems to work as intended despite of the warning: P.S. You may also want to try out TV Browser, which is a free and nice desktop EPG guide supporting (via plugin) tvstreamrecord. |
Thanks for the quick reply. I had deleted all my channels before importing, so I guess that's why it didn't work. I was under the impression that channels would be created by the import. Yes, I've been using TV Browser for years and actually installed the plugin after the import failed. Works like a charm :) |
What do you mean with import? Importing channels and importing EPG data are two separate processes. Channel info contains URIs of the streams and XML data contains... well XML data only. Sure you can (and actually have to in this case) have two channels with the same URI, where one channel is named after XML source and the other one after TV Browser. Please be aware though that there is no concurrency check: if you schedule both channels at the same time and your stream source can provide but one stream at a time, one or both of them will probably fail. |
Thank you for the clarification, I think I've figured it out now! Keep up the good work 👍 |
Hi, I've recently discovered the xmltv.info that offers EPG data for German channel. Not sure how reliable it is, but I want to give it a try. However, the EPG import fails with
Unknown XMLTV generator 'XMLTV.info', please contact me if it fails
I downloaded the XML file, and at first glance it looks fine to me, at least it's valid XML ;)
tv_validate_file epg.xml
(from the xmltv package) throws validity errors, however, but maybe those can be ignored?Is there anything I can do from my side to make the import work? I'm running TSR from the Docker image on my NAS.
The text was updated successfully, but these errors were encountered: