Change PostUpdate EPG Process.

[mvallevand]

I feel the PostUpdateEPG process should run right after the Update EPG logic before the recurring recordings process is run. This would allow "tweaked" guide data to be added into the scheduled recording table. An example is a recent thread that talked about manually adding the OAD to the description. Users need to preporcess files but it is trivial in a sqlite script

Code:

update epg_event
set subtitle = substr(original_air_date,1,4)
where unique_id like 'MV%'

because it impossible to do with the post update process. It should probably run in this area.

Code:

2017-06-28 06:48:44.403    [DEBUG][10]    UpdateEPG@4
2017-06-28 06:48:44.403    [DEBUG][10]    Updating recording schedule
2017-06-28 06:48:44.403    [INFO][10]    deleting old conflicts
2017-06-28 06:48:44.411    [INFO][10]    UpdateAllRecurringRecordings()

Martin

[sub]

For the sake of not breaking it for anyone currently hooking in with PostUpdateEPG.bat, how about a new PostImportEPG.bat or similar? I'm happy to take other name suggestions if you've got them...

[mvallevand]

It isn't really an import for SD JSON users, how about PostLoadEPG.bat? It needs to be something not triggered by -recurring too.

Martin

[ACTCMS]

PostAcquireEPG.bat ?

Alex

[sub]

It isn't really an import for SD JSON users, how about PostLoadEPG.bat? It needs to be something not triggered by -recurring too.

Martin

Ok, I've added this for the next release.

[BrettB]

It isn't really an import for SD JSON users, how about PostLoadEPG.bat? It needs to be something not triggered by -recurring too.

+1

[mvallevand]

Thanks sub. Will the md5 processing impact anything that is done to the database in this step? Be this I mean will the data after the refresh be like the raw SD JSON or do you skip downloading it?

Martin

[sub]

It'll skip redownloading next time, since the MD5 data will still be the original SD supplied.