Recording metadata - TPeterson

Want to write your own code to work with a HDHomeRun or work with the HDHomeRun DVR? We are happy to help with concepts, APIs, best practices.
TPeterson
Posts: 130
Joined: Thu May 31, 2007 8:29 pm
Device ID: 10123716, 10157425, 1039FE2B, 103AEA6C, 1075D4B1, 1076C3A7, 1080F19F
Location: San Carlos, CA
x 2
Contact:

Re: Recording metadata - TPeterson

Post by TPeterson »

Thanks, Nick. I looked for SeriesID in the Schedules Direct SD-JSON developer's guide and didn't see it. Did I miss it or is that your own name for it?

nickk
Silicondust
Posts: 20206
Joined: Tue Jan 13, 2004 9:39 am
x 387

Re: Recording metadata - TPeterson

Post by nickk »

The SeriesID we use is a composite of 3 different things from the GN data... the format is:

"C"
seriesID value from GN (integer)
language code (2 characters uppercase)
hash of the title (4 characters uppercase)

TPeterson
Posts: 130
Joined: Thu May 31, 2007 8:29 pm
Device ID: 10123716, 10157425, 1039FE2B, 103AEA6C, 1075D4B1, 1076C3A7, 1080F19F
Location: San Carlos, CA
x 2
Contact:

Re: Recording metadata - TPeterson

Post by TPeterson »

Got it! Thanks.

gtb
Expert
Posts: 4224
Joined: Thu Oct 06, 2011 1:00 pm
Location: Sunnyvale, CA USA
x 16

Re: Recording metadata - TPeterson

Post by gtb »

TPeterson wrote: Mon Mar 18, 2024 9:01 am The other tags are pretty self explanatory (or explained in gtb's code).
Please remember that the tags in my documentation/codes are guesses. I believe we are still waiting for NedS to find some time to make an authoritative doc.

TPeterson
Posts: 130
Joined: Thu May 31, 2007 8:29 pm
Device ID: 10123716, 10157425, 1039FE2B, 103AEA6C, 1075D4B1, 1076C3A7, 1080F19F
Location: San Carlos, CA
x 2
Contact:

Re: Recording metadata - TPeterson

Post by TPeterson »

Thanks to everyone's help here, the current version of the Cliff Watson EPG app (CW_EPG) in the MSFT Store will soon have proper (AFAIK) metadata in all its new HDHomerun recordings. And it can insert the metadata into user-selected prior recordings.

I've confirmed that these play in the HDHomerun app as well, but unless I explain to users how to set up their systems to do this it will be an essentially invisible change. I think that Silicondust is OK with having such an explanation in the CW_EPG user manual, but if that's not correct please let me know now.

jasonl
Silicondust
Posts: 16836
Joined: Sun Oct 28, 2007 9:23 pm
x 64

Re: Recording metadata - TPeterson

Post by jasonl »

It's fine if you want to put it in there, but maybe add a note that people should reach out to your team for any support questions related to that function.

TPeterson
Posts: 130
Joined: Thu May 31, 2007 8:29 pm
Device ID: 10123716, 10157425, 1039FE2B, 103AEA6C, 1075D4B1, 1076C3A7, 1080F19F
Location: San Carlos, CA
x 2
Contact:

Re: Recording metadata - TPeterson

Post by TPeterson »

Thanks, Jason, we'll definitely point to our own team for user support in setting up for the player.

It really would be good to have @NedS 's metadata API description though, since I think I'm missing at least one metadata tag related to informing the player about the actual file length/duration. The player's progress bar, when hosted on my LG TV, Onn Box, and Windows does not show the correct proportion of file progress.

I'd also like to have some control over the style and size of the closed captions, but I gather that's not going to happen, since it's been requested in this forum before.

emveepee
Posts: 158
Joined: Sun Nov 16, 2014 3:35 pm
x 4

Re: Recording metadata - TPeterson

Post by emveepee »

TPeterson wrote: Tue Apr 09, 2024 9:33 amIt really would be good to have @NedS 's metadata API description though, since I think I'm missing at least one metadata tag related to informing the player about the actual file length/duration. The player's progress bar, when hosted on my LG TV, Onn Box, and Windows does not show the correct proportion of file progress.
Are you sure you calculated RecordStartTime RecordEndTime correctly.

TPeterson
Posts: 130
Joined: Thu May 31, 2007 8:29 pm
Device ID: 10123716, 10157425, 1039FE2B, 103AEA6C, 1075D4B1, 1076C3A7, 1080F19F
Location: San Carlos, CA
x 2
Contact:

Re: Recording metadata - TPeterson

Post by TPeterson »

emveepee wrote: Tue Apr 09, 2024 12:50 pmAre you sure you calculated RecordStartTime RecordEndTime correctly.
No. Please tell me how they should be calculated.

nickk
Silicondust
Posts: 20206
Joined: Tue Jan 13, 2004 9:39 am
x 387

Re: Recording metadata - TPeterson

Post by nickk »

StartTime and EndTime are the start and end times listed in the guide. They are unix timestamp format (UTC).

RecordStartTime and RecordEndTime are when the recording should start and end. Basically the guide start time minus the start padding and the guide end time plus the end padding.

The actual time the recording started or ended is not stored.

TPeterson
Posts: 130
Joined: Thu May 31, 2007 8:29 pm
Device ID: 10123716, 10157425, 1039FE2B, 103AEA6C, 1075D4B1, 1076C3A7, 1080F19F
Location: San Carlos, CA
x 2
Contact:

Re: Recording metadata - TPeterson

Post by TPeterson »

nickk wrote: Tue Apr 09, 2024 2:27 pmThe actual time the recording started or ended is not stored.
Thanks, Nick. That's what I guessed they were, and is what I used. But using those values in an unedited recording still doesn't seem to give a proportionate display of the progress bar in the player. And then I have the question of what about recordings that are edited, for example to remove commercials. Should the start and end times be adjusted for the time removed?

Ken.F
Posts: 2546
Joined: Fri Apr 05, 2013 9:20 am
Device ID: 1041A706, 1043EB32, 104BAD9E, 13168DC5, 1322A7AC
Location: West Rockhill, PA
x 5

Re: Recording metadata - TPeterson

Post by Ken.F »

TPeterson wrote: Tue Apr 09, 2024 2:41 pm And then I have the question of what about recordings that are edited, for example to remove commercials. Should the start and end times be adjusted for the time removed?
When I edit recordings I change RecordStartTime to match StartTime, then I change both RecordEndTime and EndTime to StartTime plus the edited file duration in seconds.

TPeterson
Posts: 130
Joined: Thu May 31, 2007 8:29 pm
Device ID: 10123716, 10157425, 1039FE2B, 103AEA6C, 1075D4B1, 1076C3A7, 1080F19F
Location: San Carlos, CA
x 2
Contact:

Re: Recording metadata - TPeterson

Post by TPeterson »

Thanks, Ken! I assume that you then see the progress bar move proportionately during file play, right?

Ken.F
Posts: 2546
Joined: Fri Apr 05, 2013 9:20 am
Device ID: 1041A706, 1043EB32, 104BAD9E, 13168DC5, 1322A7AC
Location: West Rockhill, PA
x 5

Re: Recording metadata - TPeterson

Post by Ken.F »

TPeterson wrote: Wed Apr 10, 2024 10:54 am Thanks, Ken! I assume that you then see the progress bar move proportionately during file play, right?
Yes.

nickk
Silicondust
Posts: 20206
Joined: Tue Jan 13, 2004 9:39 am
x 387

Re: Recording metadata - TPeterson

Post by nickk »

Ken.F wrote: Wed Apr 10, 2024 10:44 am When I edit recordings I change RecordStartTime to match StartTime, then I change both RecordEndTime and EndTime to StartTime plus the edited file duration in seconds.
Suggest not changing the EndTime as EndTime is the scheduled EndTime and not related to the length of the recording. In practice we only use StartTime in the UI.

(RecordEndTime - RecordStartTime) should be edited to match the actual length of the recording if possible.

Post Reply