Wanted to circle back around on this.....
1st, yes, I do understand what a grabber does. What I needed to do was figure out how all the pieces worked/fit together from the grabber to the xml file to OSMC. Once I had that down, I figured out changes (typically directory pointers) I needed to make to get it working.
So far, it all looks good. Just did an update test to see what shows up in the xml file, and I found Program, Episode, description, etc. all sitting in the file. The system I'm working from is upstairs and the RPI 3/OSMC system is downstairs so it'll be a bit till I can verify OSMC is seeing what it's supposed to see. However, I'm fairly confident at this point.
Anyways, thx bunches for the help and insight. I truly appreciate it.
1 last question...I edited "[Solved]" into the title of my 1st posting. Is there a button somewhere that I missed that would do this automatically?
Cheers....
Robert Cameron wrote:
> I think you've misunderstood what a grabber actually is.
>
> The "grabber", connects to a service/website, looks up channel/program information for a specific carrier/channel/timespan/country/&c, and then downloads that information to your computer.
>
> XMLTV is a format that many grabbers adhere to. Similarly, the XMLTV project also publishes a number of grabbers that also output their information in the XMLTV format.
>
> All of the grabbers published by the XMLTV project (in general, they are all named
tv_grab_*@) all respond to certain arguments/parameters/configurations in the same manner. In Tvheadend, when it starts up, it looks for programs in your @$PATH
that generally start with @tv_grab_*@and respond to the proper commands; it will then make these available to you as EPG modules. However, you almost always need to configure these grabbers outside of TVH, and almost always as the user that TVH also runs as.
>
> If your grabber does not output directly to XMLTV, or is not recognized by TVH, there are a few other options for getting your guide data into the program. The most popular of those options is with xmltv.sock, which is a socket that listens for XMLTV data.