home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
HTPC Projects
Software
Tools and other software
EPG-Buddy a new EPG Tool with easy usage.
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Lehmden" data-source="post: 1257881" data-attributes="member: 109222"><p>Hi.</p><p></p><p>No need to. Missing "" are a real possible cause for the observed behavior. </p><p> </p><p></p><p></p><p>Those files are indeed identical and this for a good reason. The first one is named as the CLI grabber tool that runs and grab the data in background on a daily schedule, needs it to be named. The second one is how you configure the output so it can be recognized by your TV engine easily. The first file is copied to the new name and location instead of moved as if it would be moved no "old" EPG data is there to start with the next day...</p><p></p><p>[ATTACH=full]201183[/ATTACH] </p><p></p><p>This is the file you will use in your TV engine and you can name and place as you like... </p><p></p><p></p><p></p><p>This is one of the cache files used in EPG-Buddy. This file hold relationships between series names as in EPG- data and on TVDB. Those is not always the same, especially if your EPG data is non in English... This file can be used to manually "map" a series name from EPG to a series name on TVDB, if they are not identical and EPG-Buddy don't match the series by itself.</p><p>This file is read on every start and it is modified always as every day new series will appear in the EPG data. But it is not wiped out before it is read into the program so the data is used on every run... The main cache for TVDB data is the folder "EPG-Grabber.Cache". Here all data downloaded from TVDB is stored for later usage. My own cache folder contains data for 2700 series recently...</p><p></p><p></p><p>Maybe DVB-Viewer or TVHeadend are able to use extra fields (I don't know). But ArgusTV, NextPVR and MediaPortal are only make use of movie, series and episodes name, season and episodes number and description. Adding other fields only is a waste of resources and time as you can't use them. Theoretically you can append those fields to the description so you can see the actors, writers, year and country at the end of the description. Not too nice, if you ask me...</p><p></p><p>Aside this, EPG data is "temporal". After 14 days max they are gone and lost. There is no real sense in putting too much effort into those temporal data... In the beginning we were thinking about using the TVDB/TMDB routines from Media-Buddy for EPG-Buddy too. Those routines are very complex to get the best possible data with no user interaction. For .nfo files that stays with the video "forever" it makes sense to invest time and effort to get a perfect result. And this would have been lot easier to re-use instead of writing the routines from scratch. But in EPG-Buddy this would need way to much time. An average grabbing as it is now takes about 30 minutes here for 14 days and 60 channels where 40 channels are compared with TVDB. IF we use the Media-Buddy routines the same grabbing process will last about 6-8 hours... It would be similar to enriching 5.000 to 10.000 episodes at once in tMM or Media-Buddy... A bit too much time, if you ask me. Especially as this needs to be done every day...</p><p></p><p>The main use case is for recurring recordings of series where the (most often missing in original EPG data) season and episodes numbers are very important. Those numbers are used and added to the recording file name if EPG-Buddy could identify the series and episode. Very helpful if you want to cut, transcode and enrich the recordings with .nfo file and fanart for usage in the "real" media library...</p><p></p><p></p><p>Oh, it is possible to use more than one XML file already. You can e.g. use data from TVSpielfilm and WebGrab++ as I do it every day. 58 out of my 60 channels are grabbed from TVSpielfilm as it is very fast and easy. The 2 channels that are not available on TVSpielfilm I grab with the included WebGrab version. In my case the resulting files are named "TVGuide_1.xml" and "TVGuide_2.xml". As I'm using MediaPortal as TV solution I've also created the tvguide.lst file that directs the MP- XMLTV plugin to use both of my XML files. This way both files are treated as one inside the XMLTV plugin. Here I can't see any longer from which of both data sources the data for a specific channel is from...</p><p>Only the usage of two or more external XML files is not possible atm. due to the known bug in EPG-Buddy... Once this is fixed the data from both (all) external XML will be listed together at once inside the EPG-Buddy GUI...</p></blockquote><p></p>
[QUOTE="Lehmden, post: 1257881, member: 109222"] Hi. No need to. Missing "" are a real possible cause for the observed behavior. Those files are indeed identical and this for a good reason. The first one is named as the CLI grabber tool that runs and grab the data in background on a daily schedule, needs it to be named. The second one is how you configure the output so it can be recognized by your TV engine easily. The first file is copied to the new name and location instead of moved as if it would be moved no "old" EPG data is there to start with the next day... [ATTACH=full]201183[/ATTACH] This is the file you will use in your TV engine and you can name and place as you like... This is one of the cache files used in EPG-Buddy. This file hold relationships between series names as in EPG- data and on TVDB. Those is not always the same, especially if your EPG data is non in English... This file can be used to manually "map" a series name from EPG to a series name on TVDB, if they are not identical and EPG-Buddy don't match the series by itself. This file is read on every start and it is modified always as every day new series will appear in the EPG data. But it is not wiped out before it is read into the program so the data is used on every run... The main cache for TVDB data is the folder "EPG-Grabber.Cache". Here all data downloaded from TVDB is stored for later usage. My own cache folder contains data for 2700 series recently... Maybe DVB-Viewer or TVHeadend are able to use extra fields (I don't know). But ArgusTV, NextPVR and MediaPortal are only make use of movie, series and episodes name, season and episodes number and description. Adding other fields only is a waste of resources and time as you can't use them. Theoretically you can append those fields to the description so you can see the actors, writers, year and country at the end of the description. Not too nice, if you ask me... Aside this, EPG data is "temporal". After 14 days max they are gone and lost. There is no real sense in putting too much effort into those temporal data... In the beginning we were thinking about using the TVDB/TMDB routines from Media-Buddy for EPG-Buddy too. Those routines are very complex to get the best possible data with no user interaction. For .nfo files that stays with the video "forever" it makes sense to invest time and effort to get a perfect result. And this would have been lot easier to re-use instead of writing the routines from scratch. But in EPG-Buddy this would need way to much time. An average grabbing as it is now takes about 30 minutes here for 14 days and 60 channels where 40 channels are compared with TVDB. IF we use the Media-Buddy routines the same grabbing process will last about 6-8 hours... It would be similar to enriching 5.000 to 10.000 episodes at once in tMM or Media-Buddy... A bit too much time, if you ask me. Especially as this needs to be done every day... The main use case is for recurring recordings of series where the (most often missing in original EPG data) season and episodes numbers are very important. Those numbers are used and added to the recording file name if EPG-Buddy could identify the series and episode. Very helpful if you want to cut, transcode and enrich the recordings with .nfo file and fanart for usage in the "real" media library... Oh, it is possible to use more than one XML file already. You can e.g. use data from TVSpielfilm and WebGrab++ as I do it every day. 58 out of my 60 channels are grabbed from TVSpielfilm as it is very fast and easy. The 2 channels that are not available on TVSpielfilm I grab with the included WebGrab version. In my case the resulting files are named "TVGuide_1.xml" and "TVGuide_2.xml". As I'm using MediaPortal as TV solution I've also created the tvguide.lst file that directs the MP- XMLTV plugin to use both of my XML files. This way both files are treated as one inside the XMLTV plugin. Here I can't see any longer from which of both data sources the data for a specific channel is from... Only the usage of two or more external XML files is not possible atm. due to the known bug in EPG-Buddy... Once this is fixed the data from both (all) external XML will be listed together at once inside the EPG-Buddy GUI... [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
HTPC Projects
Software
Tools and other software
EPG-Buddy a new EPG Tool with easy usage.
Contact us
RSS
Top
Bottom
