Recording metadata - TPeterson
-
- Posts: 138
- Joined: Thu May 31, 2007 8:29 pm
- Device ID: 10123716, 10157425, 1039FE2B, 103AEA6C, 1075D4B1, 1076C3A7, 1080F19F
- Location: San Carlos, CA
- x 1
- Contact:
Re: Recording metadata - TPeterson
@nickk: I used Gary Buhrmaster's GitHub python app `HDHR-DVR-fileImport.py` from https://github.com/garybuhrmaster/HDHRUtil to put the relevant metadata into a ts file recorded from one of my HDHR units. (Thanks, @gtb!) VLC was still happy to play the result, but `HDHomeRunApp.exe` (the Windows alias for the HDHR app) continues to ignore any of the command line parameters that I've tried with it to specify the augmented file. You've said here that the app can play such files if they have the metadata...what's the syntax for doing that?
Re: Recording metadata - TPeterson
Unless this is new behaviour, I've use a utility to add the metadata from NextPVR to an NextPVR created ts file and the file with metadata shows up so check the logic and the mpg file you are using.
-
- Expert
- Posts: 11213
- Joined: Wed Jan 24, 2007 1:04 am
- Device ID: 10A05954 10802091 131B34B7 13231F92 1070A18E 1073ED6F 15300C36
- x 32
Re: Recording metadata - TPeterson
the app looks for a recording engine... the engine looks at folders it is told to look at in hdhomerun.conf file or registry.
-
- Posts: 138
- Joined: Thu May 31, 2007 8:29 pm
- Device ID: 10123716, 10157425, 1039FE2B, 103AEA6C, 1075D4B1, 1076C3A7, 1080F19F
- Location: San Carlos, CA
- x 1
- Contact:
Re: Recording metadata - TPeterson
IOW, the app works via the subscribed DVR system only, is that right?
Re: Recording metadata - TPeterson
The HDHomeRun DVR can be used for playing back existing recordings and buffering live TV without a subscription.
-
- Posts: 138
- Joined: Thu May 31, 2007 8:29 pm
- Device ID: 10123716, 10157425, 1039FE2B, 103AEA6C, 1075D4B1, 1076C3A7, 1080F19F
- Location: San Carlos, CA
- x 1
- Contact:
Re: Recording metadata - TPeterson
Thanks for the clarification, Jason. My question is how exactly do I get the app to recognize those existing recordings? I gather from the mere existence of utilities that add the necessary metadata to ts files that lack it--and from emveepee's post above--that such files are not necessarily all created by the DVR system itself.
Re: Recording metadata - TPeterson
The DVR starts up and looks in the recording path(s) for video files with metadata. Those with the right kind of metadata get indexed.
-
- Posts: 138
- Joined: Thu May 31, 2007 8:29 pm
- Device ID: 10123716, 10157425, 1039FE2B, 103AEA6C, 1075D4B1, 1076C3A7, 1080F19F
- Location: San Carlos, CA
- x 1
- Contact:
Re: Recording metadata - TPeterson
Thanks, Ned. ...and I set the "recording path(s)" how?
Re: Recording metadata - TPeterson
It shows up in Recordings in the HDHR app on all platforms. I placed the mpg file in the default recording folder which was C:\Users\Public\Recorded TV\HDHomeRun and I used an app that I wrote for NextPVR called NextTool
As noted on this thread I guess the folder is defined in the registry.
Code: Select all
[HKEY_LOCAL_MACHINE\SOFTWARE\Silicondust\HDHomeRun\DVR]
"RecordPath"="C:\\Users\\Public\\Recorded TV\\HDHomeRun"
-
- Posts: 138
- Joined: Thu May 31, 2007 8:29 pm
- Device ID: 10123716, 10157425, 1039FE2B, 103AEA6C, 1075D4B1, 1076C3A7, 1080F19F
- Location: San Carlos, CA
- x 1
- Contact:
Re: Recording metadata - TPeterson
Thanks, Martin. I'll give that a shot. And I guess if setting the Registry key is not alone sufficient I should try (finally) to install the DVR subsystem that I've (obviously) never broached before.
-
- Expert
- Posts: 11213
- Joined: Wed Jan 24, 2007 1:04 am
- Device ID: 10A05954 10802091 131B34B7 13231F92 1070A18E 1073ED6F 15300C36
- x 32
Re: Recording metadata - TPeterson
Yes you need the dvr engine running some place that has local access to that folder and set to look there as that is what serves the content to the app.
-
- Posts: 138
- Joined: Thu May 31, 2007 8:29 pm
- Device ID: 10123716, 10157425, 1039FE2B, 103AEA6C, 1075D4B1, 1076C3A7, 1080F19F
- Location: San Carlos, CA
- x 1
- Contact:
Re: Recording metadata - TPeterson
OK, thanks, all for the guidance.
-
- Posts: 138
- Joined: Thu May 31, 2007 8:29 pm
- Device ID: 10123716, 10157425, 1039FE2B, 103AEA6C, 1075D4B1, 1076C3A7, 1080F19F
- Location: San Carlos, CA
- x 1
- Contact:
Re: Recording metadata - TPeterson
One more question: What is the purpose of the tag SeriesID? The other tags are pretty self explanatory (or explained in gtb's code). This ones name suggests to me that it's for grouping things somehow, but darned if I can guess how!
Re: Recording metadata - TPeterson
Everything is grouped by series. For example top-level-recorded shows the series and going into it shows the episodes within that series. Recording rules work by series.
"Top Gear" (UK) and "Top Gear" (USA) have the same name but different SeriesIDs to tell them apart for recording and for grouping episodes. This is also true for shows that have been remade, for example "Battlestar Galactica" which could be the 2004-2009 series or the 1978 series.
The SeriesID is derived from the guide data and usually starts with "C". The two exceptions being movies where the SeriesID and the EpisodeID are the same (starting with MV), and New Zealand which uses different guide data.
"Top Gear" (UK) and "Top Gear" (USA) have the same name but different SeriesIDs to tell them apart for recording and for grouping episodes. This is also true for shows that have been remade, for example "Battlestar Galactica" which could be the 2004-2009 series or the 1978 series.
The SeriesID is derived from the guide data and usually starts with "C". The two exceptions being movies where the SeriesID and the EpisodeID are the same (starting with MV), and New Zealand which uses different guide data.