hshah 19 Posted April 8, 2019 Share Posted April 8, 2019 Thanks for the info. Is stuff like this tracked somewhere? If it helps, I don't mind logging my findings with all the details Link to comment Share on other sites More sharing options...
matty87a 6 Posted April 11, 2019 Share Posted April 11, 2019 i've just stumbled across this thread after noticing 41GB of files in temp after switching to using the xml url (which is a gz file). reverted to using a local gunzipped xml file generated by the script i posted here: https://emby.media/community/index.php?/topic/68368-emby-xtream-editor-epg-xml-does-not-work/?p=685215 The temp files are now where they should be but the same data is present. May be worth trying till the .gz issue is fixed Link to comment Share on other sites More sharing options...
hshah 19 Posted April 13, 2019 Share Posted April 13, 2019 i've just stumbled across this thread after noticing 41GB of files in temp after switching to using the xml url (which is a gz file). reverted to using a local gunzipped xml file generated by the script i posted here: https://emby.media/community/index.php?/topic/68368-emby-xtream-editor-epg-xml-does-not-work/?p=685215 The temp files are now where they should be but the same data is present. May be worth trying till the .gz issue is fixed It is down to what I mentioned above - the .gz file gets saved as .xml and basically re-extracts it for every channel. If your XMLTV feed is .xml then you are fine, but if its .gz then something like your script is the best option until @@Luke and co. manage to implement a fix Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now