Details about metadata properties files

[Fonceur]

Duration and EndTime in SageTV can be a mess... Based on the StartTime you can often reconstruct one of the missing values, but not always...

[Opus4]

The default STV displays the airing duration or show duration for a DVD, if that info is known.

The first post of this topic links to a list of properties (which may not be all of them now), but it does list Duration and RunningTime. If Duration doesn't do it, use RunningTime.

- Andy

[will]

Originally Posted by Opus4

The default STV displays the airing duration or show duration for a DVD, if that info is known.

The first post of this topic links to a list of properties (which may not be all of them now), but it does list Duration and RunningTime. If Duration doesn't do it, use RunningTime.

- Andy

I have tried both and they don't seem to work. I am wondering if I am entering them correctly.

How should the duration or runningtime entry look in the properties file?

Example:

Duration=96 or

Duration=96 minutes or

Duration=2 hours

[Fonceur]

Duration would be in seconds without units...

[Opus4]

Almost all, if not all, time values are in milliseconds.

- Andy

[will]

Originally Posted by Opus4

Almost all, if not all, time values are in milliseconds.

- Andy

For a 96 minute movie, the properties file should have line that reads:

Duration=5760000

Correct?

[will]

Originally Posted by will

For a 96 minute movie, the properties file should have line that reads:

Duration=5760000

Correct?

RunningTime=5760000 works for a 96 minute movie.

Thanks for the help everyone!

[Fonceur]

Originally Posted by Opus4

If Duration doesn't do it, use RunningTime.

I don't remember seeing any getRunningTime() method and actually I just searched the API and didn't find any, must be why I wasn't aware of this property...

Originally Posted by Opus4

Almost all, if not all, time values are in milliseconds.

Right, I'm probably rescaling them in SageTCPServer before I send them out.

[stuckless]

Originally Posted by Fonceur

I don't remember seeing any getRunningTime() method and actually I just searched the API and didn't find any, must be why I wasn't aware of this property...


Right, I'm probably rescaling them in SageTCPServer before I send them out.

RunningTime is a property name... so you'd get it by

long value = MediaFileAPI.GetMediaFileMetadata(MediaFile, "RunningTime")

[Opus4]

RunningTime also applies to the Show's duration, so you can get it via GetShowDuration(Airing). The default STV checks that if GetAiringDuration(Airing) isn't valid.

- Andy

[will]

Can we use .properties files on TV recordings?

For example, I have a TV show that is missing the episode number, can I create a .properties file with EpisodeNumber=12 and will Sage use that to fill in missing information?

[will]

Originally Posted by will

Can we use .properties files on TV recordings?

For example, I have a TV show that is missing the episode number, can I create a .properties file with EpisodeNumber=12 and will Sage use that to fill in missing information?

Anyone?

I've tried EpisodeNumber and SeasonNumer (the name of the fields that SageTV embeds in video file's meta info) but they don't work.

Would Episode=12 and Season=01 work?

[HelenWeathers]

Originally Posted by will

Anyone?

I've tried EpisodeNumber and SeasonNumer (the name of the fields that SageTV embeds in video file's meta info) but they don't work.

Would Episode=12 and Season=01 work?

The properties file created by the Phoenix scraper has the following format:

EpisodeNumber=15
SeasonNumber=7

Not positive they're read by the stock interface.

EDIT: And remember - some properties files are not picked up without a SageTV restart IIRC.

[Fuzzy]

The preferred method of altering metadata is via the SageTV API, not by alerting properties files.

[Fuzzy]

Originally Posted by HelenWeathers

The properties file created by the Phoenix scraper has the following format:

EpisodeNumber=15
SeasonNumber=7

Not positive they're read by the stock interface.

EDIT: And remember - some properties files are not picked up without a SageTV restart IIRC.

The properties files are not read by any interface. They are read by the SageTV core when a file is imported. After an imoort, the file will only be read in again if the time stamp of the media file itself is changed. This is why it is not the preferred method of altering files already in the database. When you DO alter metadata via the sage api, sage DOES alter/create a properties file, so that if the file had to be reported at some point, it will have the right data with it.

[will]

Originally Posted by Fuzzy

The properties files are not read by any interface. They are read by the SageTV core when a file is imported. After an imoort, the file will only be read in again if the time stamp of the media file itself is changed. This is why it is not the preferred method of altering files already in the database. When you DO alter metadata via the sage api, sage DOES alter/create a properties file, so that if the file had to be reported at some point, it will have the right data with it.

Thanks for the info, based on what you said I was able to get the .properties file to work.

I know I should probably just use BMT but I'm not crazy for adding another plug-in to an already very stable system.

[will]

Originally Posted by HelenWeathers

The properties file created by the Phoenix scraper has the following format:

EpisodeNumber=15
SeasonNumber=7

Not positive they're read by the stock interface.

EDIT: And remember - some properties files are not picked up without a SageTV restart IIRC.

I confirmed they do work, thanks for the info. The trick is just getting sage to read the property file.

[Fuzzy]

Well, you can also install the Sagex library, and access the api via HTTP calls also. You don't HAVE to use phoenix/bmt (though running the phoenix api will likely automatically fill in those missing season and episode numbers for you, and any fixes can be done easily from the UI with CMT.