Yes, that github link is what I referred to as xml2mxf, which tonywagner's code was based on.Green Lantern wrote: ↑Sun Feb 09, 2020 6:56 pmJust to make sure there's no confusion, since the names are very similar, have either of you been to:
and contacted its developer, Ray Douglass? His email is at the bottom of the page above and he does respond. You could bring the differences mentioned above to his attention and he could perhaps improve his code to provide a best-of-both-worlds solution. If you do pursue this, please post back here to let others know.
The code in https://github.com/raydouglass/xmltv-to-mxf does not work with channel numbers that contain periods. tonywagner fixed this and posted a link to his fixed code on page 5 of this thread.
tony also supplied an additional parameter that is required to run the code on a Windows machine instead of Linux.
I think it would be ideal if tony uploaded his source code to that github page so it can be included in the project. It's an essential improvement as the original command just fails on a Windows machine with an error like this: "No acceptable channel number found for..."
I so far prefer the xmltv2mxf method, for which I linked the YouTube video above. I believe that method gets us closer to a good quality guide, although still with some problems.
Here's the command I'm using for that, along with some additional batch stuff:
REM convert xml guide data to mxf format (WMC format)
cd "\Recorded TV\xmltv\xmltv2mxf_jan_2013\XMLTV2MXF"
XMLTV2MXF.exe /i xmltv.xml /o ..\guideZap2It.mxf /s Scripts\XMLTVNZ\Zap2It.xml
The YouTube video does a decent job explaining how to set this up, but uses absolute paths for everything, which gets tedious and annoying. Fortunately, we don't have to write our batch commands the same.