v1.3.1 Release with HDHR2MXF

[gzarzycki]

I have that not checked and it still tries to run it. I have it set to get the epg123.mxf file from my server but it seems to ignore the setup.

As you see in my config, I don't have it set to run the HDHR program but it does, then gets a quick command window with the error that is in the log. but you can't get out of your error window, I click to ignore that but it keeps loading it, and endless cycle that you can't get out of.

[gzarzycki]

BTW, now WMC seems to have an issue and hangs trying to get it back to the default WMC for my zip code.

[gzarzycki]

I am not using it, but it keeps trying to run it, I have checked as Client install with the config to get ithe mxf file from my server as I posted, but it runs the HDHR program. When I can get WMC working again, as it appears damaged now, I will post a capture of the errors. The loop occurs, has done it several times now when I try to exit, it just loops again, over and over again.

[garyan2]

1) When you upgrade to a newer version, you do not have to run client setup or do anything special. It will simply copy over the executable files and you are done.

2) You have created a new task as note by the task status of "Ready. The task has not yet run. Exit: 0x00000001". It looks to me you deleted your existing task and created a new task, Full Mode, with either epg123.exe or hdhr2mxf.exe, as part of your client task. Since you have no configuration file for epg123.exe on your client it is having issues.

Delete your task and create it again for Client Mode and point to the mxf file on your Exodus machine. Remember you will have to change the credentials of the task to gain access.

[gzarzycki]

I am not doing an update, I am doing a new install. I give up.

[garyan2]

I'm just not following what you are trying to describe. Pics will help... you have my email.

[garyan2]

Okay, I believe I recreated what you are seeing. You did install HDHR2MXF along with the Client Only files. When you perform a [Client Setup], with hdhr2mxf.exe installed, it will automatically run that for Step 3. Since you do not have an active DVR Service subscription with SiliconDust, it will not create the C:\ProgramData\GaRyan2\epg123\output\epg123.mxf file. When it goes to import the epg123.mxf file at the end of Step 3, it will fail. Since you probably had the default 'Automatically proceed to next step' enabled, it would continually try to run Step 3 because it never completed it in the first place. I guess I'll need to find a way to stop that behavior.

Run the epg123Setup_v1.3.1.20 again and de-select installing hdhr2mxf.exe. You can then run through the routine without worrying about it and it will be a client only install.

EDIT: added description of the continuous loop behavior.

[gzarzycki]

Gary, thanks for all the help, but this version is not ready for prime time. It has issues which after a dozen tries has pretty much wiped out my WMC to the point I have to do a total re-install of my Windows install.

[garyan2]

Whatever. I told you what you did wrong and how to fix it. I told you what I did wrong which will be fixed and released soon. The only thing EPG123 could have done, and does do, is delete your WMC database... in your case multiple times. It does nothing with your Windows system that would even remotely require a system re-install.

You do your troubleshoot and I'll do mine. I, of course, have the advantage of understanding exactly what EPG123 does and how it does it.

[garyan2]

Sorry, everyone. Version 1.3.1.30 is up to correct the infinite loop described by gzarzycki. If you don't plan to do a client setup, no need to update.

[adam1991]

I'm running out of popcorn, but can't tear myself away to get more...

[StinkyImp]

Gary, thanks for all the help, but this version is not ready for prime time. It has issues which after a dozen tries has pretty much wiped out my WMC to the point I have to do a total re-install of my Windows install.

You have previously mentioned that you're computer savvy a technological genius. Updating a current EPG123 install is as simple as extracting the nine files inside the current zip file into your existing installation.

There is absolutely no way EPG123 corrupted your system, no less trashed it. Once an EPG123 installation is set up and running (which Garyan2 spent a TON of time helping you accomplish), it's trivial to upgrade or downgrade. I do it routinely because it only takes seconds. If your system is trashed... it's operator error.

You need to stop blaming Gary for your lack of skill and understanding.

I'm running out of popcorn, but can't tear myself away to get more...

Yep... It's like watching a pig try to knit.

[garyan2]

It looks like he may have been doing a new install, not an update. I thought we had gotten all his clients up and running already, but he may have a new computer, new client, or just started with a fresh OS. Dunno.

[adam1991]

It looks like he may have been doing a new install, not an update. I thought we had gotten all his clients up and running already, but he may have a new computer, new client, or just started with a fresh OS. Dunno.

yeah, but it won't be for another week and a half that he admits that fresh OS is WinXP.

[StinkyImp]

It looks like he may have been doing a new install, not an update.

Let's say that's true... There's no way that EPG123 trashed his system. Especially not to the point of having to reinstall the OS. I still maintain it's a lack of basic understanding, and operator error.

I think what ticks me off about this guy is he continues to blame you and EPG123 when it's virtually impossible for EPG123 to trash an OS.

[adam1991]

It looks like he may have been doing a new install, not an update.

Let's say that's true... There's no way that EPG123 trashed his system. Especially not to the point of having to reinstall the OS. I still maintain it's a lack of basic understanding, and operator error.

I think what ticks me off about this guy is he continues to blame you and EPG123 when it's virtually impossible for EPG123 to trash an OS.

It's not that he blames Gary and EPG123; it's when he puts the cherry on top by proclaiming to the world that he's a retired systems expert and knows these things like the back of his hand, and that everyone else must be a moron, that really gets things going.

Oh--and then a week later he magically reveals hoary details about his system or his processes that are crucial to the discussion, items that if only he'd revealed at the beginning would have helped everyone help him.

But regardless, it's the world's fault that simple and flawless software doesn't work for him, and in fact actually trashes entire computers for him. Just give up.

[007]

Great work on EPG123. I am trying to get EPG123 to work with HDhomerun Prime. Using the latest HDHR2MXF it fails to create mxf file:

Found HDHomeRun PRIME HDHR3-CC (13113A38) with firmware 20190621.
Found HDHomeRun RECORD () with firmware .
HDHomeRun DVR Service is active.
Using available 14-day XMLTV file from SiliconDust.
Exception Thrown:
Index was out of range. Must be non-negative and less than the size of the colle
ction.
Parameter name: index
at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argu
ment, ExceptionResource resource)
at hdhr2mxf.XmltvMxf.BuildProgram(String tmsId, XmltvProgramme program)
at hdhr2mxf.XmltvMxf.BuildScheduleEntries()
at hdhr2mxf.XmltvMxf.BuildMxfFromXmltvGuide(List`1 homeruns)
at hdhr2mxf.Program.DetermineUpdateMethod()
at hdhr2mxf.Program.Main(String[] args)

Generated .mxf file contains 1 lineups, 182 services, 2888 series, 15389 program
s, and 0 people with 4704 image links.
Execution time was 00:00:10.6860188

[garyan2]

Great work on EPG123. I am trying to get EPG123 to work with HDhomerun Prime. Using the latest HDHR2MXF it fails to create mxf file:

Found HDHomeRun PRIME HDHR3-CC (13113A38) with firmware 20190621.
Found HDHomeRun RECORD () with firmware .
HDHomeRun DVR Service is active.
Using available 14-day XMLTV file from SiliconDust.
Exception Thrown:
Index was out of range. Must be non-negative and less than the size of the colle
ction.
Parameter name: index
at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argu
ment, ExceptionResource resource)
at hdhr2mxf.XmltvMxf.BuildProgram(String tmsId, XmltvProgramme program)
at hdhr2mxf.XmltvMxf.BuildScheduleEntries()
at hdhr2mxf.XmltvMxf.BuildMxfFromXmltvGuide(List`1 homeruns)
at hdhr2mxf.Program.DetermineUpdateMethod()
at hdhr2mxf.Program.Main(String[] args)

Generated .mxf file contains 1 lineups, 182 services, 2888 series, 15389 program
s, and 0 people with 4704 image links.
Execution time was 00:00:10.6860188

If I can't find anything obvious in the code, would you mind if I send you a debug build which will save the XMLTV file that you could send back to me?

[007]

Yes, Please send it.

[garyan2]

Just sent a PM with the new file. Thank you!