Kodi

[PLUCKYHD]

Originally Posted by Monedeath

I was discussing options that "stock" Sage will exercise. Also, you retained both the airing ID and Season## + Episode## in the file name as well as the Series Name, Sage could make an association through the wiz.bin so long as that iteration of the wiz.bin file had retained record of it. (And as per Jeff, that should be "forever" for all intents if it was recorded by that server)

Exactly so if you are renaming correctly I wouldn't worry about it honestly even if you are converting after or before the rename. I don't every convert my video files so I can't speak but it picks up files fine in sage that weren't recorded in sage with the correct naming and using bmt

[Fuzzy]

Originally Posted by Monedeath

So when it reorganizes things into Directory path/SeriesName(year)/Season##/SeriesNameS##E##miscelaneous.ext
format, does it create new directory paths or do you still need to go back into Sage and add them as import paths? I know from past experience that I wasn't able to get Sage to climb directory trees in the past when it comes to video imports so I imagine it doesn't(oddly, it does with pictures though).

All you need is the 'Directory path/' folder as a sagetv import, and anything under that will be picked up by sagetv's scanning. Sagetv most certainly does scan through subdirectories, and even has in it's base UI, a way to view imports by folder.

[PLUCKYHD]

Originally Posted by Monedeath

Yeah, files created to retain the metadata outside of the recordings themselves is the other way to pull it off and re-import them that way.

You are more than willing to test the current builds if you want PM me now is the time to provide feedback for anything you want.

[Skirge01]

Originally Posted by Monedeath

Yeah, files created to retain the metadata outside of the recordings themselves is the other way to pull it off and re-import them that way.

I was discussing options that "stock" Sage will exercise. Also, you retained both the airing ID and Season## + Episode## in the file name as well as the Series Name, Sage could make an association through the wiz.bin so long as that iteration of the wiz.bin file had retained record of it. (And as per Jeff, that should be "forever" for all intents if it was recorded by that server)

I'm not saying this is a bad idea, but I am curious to know what scenario you can think of which would make this useful.

[Monedeath]

Originally Posted by Skirge01

I'm not saying this is a bad idea, but I am curious to know what scenario you can think of which would make this useful.

Recordings where the EPG does not provide sufficient data for the SxxExx information to be appended to the filename(soap operas, and daily "talk show" format type programs are prone to this), airing ID's getting stripped for whatever reason(If I'm intending to keep it in Sage, I keep them, but otherwise I chop them; I can't speak to what other people may try to do while acting on advice for file naming conventions from Plex, Kodi, or where-ever else).

News programs fall into weird handling scenarios as well, particularly local news programs, as guide data for them is typically bad at best. Special report type programs can bring pain in other ways.


As to the suggestion of a way to "auto-add" import directory paths itself, like I posted earlier, I've had previous experiences with Sage not climbing (child) directory trees on video imports for whatever reason. So if that experience continues to hold true, firing off a program that starts tossing recordings into a few dozen new (child) directories that didn't exist previously is likely going to create quite the import directory creation party for me(and anyone else with comparable experiences) if I have to chase them down manually.

Edit to add mea-culpa: Ok, think I figured out what was going on. The Recording directory doesn't crawl sub-directories(as sage doesn't use them that way when making recordings), I just needed to remember/realize that the Import directories play by different rules than the recording directory.

[stanger89]

Out of curiosity, would it not be easier to just build a new metadata scraper for Kodi that looks up files from SageTV instead of the web?

http://kodi.wiki/view/Scrapers

[PLUCKYHD]

Originally Posted by Monedeath

News programs fall into weird handling scenarios as well, particularly local news programs, as guide data for them is typically bad at best. Special report type programs can bring pain in other ways.

I have a separate way to handle news programs/stuff without season/episode numbers. Its by title and overrides the others. You can name any title differently and even create .nfos if you need to go that far

As far as sage not climbing the directory tree never once had an issue with that all my movies have always been in their old folders and way down the tree.

Originally Posted by stanger89

Out of curiosity, would it not be easier to just build a new metadata scraper for Kodi that looks up files from SageTV instead of the web?

http://kodi.wiki/view/Scrapers

It would work but naming the files is better organization to me and it is more universal if you are using multiple programs.

[stuckless]

Sort of a side note... but still related to all of this. Java 7 added some new filesystem apis, and one of interest is the ability to monitor the filesystem for changes. I've used this a number of times in other projects to be notified when a new file/directory is added/modified/deleted, and it works extremely well, and relies on the OS specific fs events (ie, this is not a polling solution that hammers the filesytem, but rather an event driven system)

On my TODO list (which is quite long at the moment) is a plugin that can add new items to sagetv database automatically when a file is added to the directory structure, without doing a full refresh, or waiting for the next refresh interval.

[PLUCKYHD]

Stuckless good to know for future and about time Java had something like this.

[jm9843]

Originally Posted by stuckless

On my TODO list (which is quite long at the moment) is a plugin that can add new items to sagetv database automatically when a file is added to the directory structure, without doing a full refresh, or waiting for the next refresh interval.

That would be a nice improvement. You don't think that'd be a good candidate for a "core" SageTV change?

[stuckless]

Originally Posted by jm9843

That would be a nice improvement. You don't think that'd be a good candidate for a "core" SageTV change?

Sure, I think it would be something that would be good in core... but there's a always a fine line between what I want in core, and what Jeff allows me to put in core He's a lot more concerned about preserving Java 1.5 compatibility in the core, whereas, I'm ok if we set the min requirements to be java 8.

Unfortunately, I can't even look at this for some time... but it's something that I wish was there everytime to copy over some media and go to play it, and discover that sagetv hasn't refreshed yet

[Taddeusz]

Originally Posted by stuckless

Sure, I think it would be something that would be good in core... but there's a always a fine line between what I want in core, and what Jeff allows me to put in core He's a lot more concerned about preserving Java 1.5 compatibility in the core, whereas, I'm ok if we set the min requirements to be java 8.

What is his rationale?

[Monedeath]

Originally Posted by stuckless

Sure, I think it would be something that would be good in core... but there's a always a fine line between what I want in core, and what Jeff allows me to put in core He's a lot more concerned about preserving Java 1.5 compatibility in the core, whereas, I'm ok if we set the min requirements to be java 8.

I know this is an option in some scripting languages, but not sure how it would be approached in Sage or Java in general. Perhaps implement it in such a way that it "fails gracefully" (or never even executes) if certain conditions are not met. Such as before it tries to do something have it do a check for a java version greater than x.y.z before trying to carry it out. Maintain the backwards compatibility, but allow the newer ones to take advantage of those abilities.

Of course doing that would make maintainability of the code base more difficult.

[Taddeusz]

Originally Posted by Monedeath

I know this is an option in some scripting languages, but not sure how it would be approached in Sage or Java in general. Perhaps implement it in such a way that it "fails gracefully" (or never even executes) if certain conditions are not met. Such as before it tries to do something have it do a check for a java version greater than x.y.z before trying to carry it out. Maintain the backwards compatibility, but allow the newer ones to take advantage of those abilities.

Of course doing that would make maintainability of the code base more difficult.

Not sure about Java but I know you can do that sort of thing with iOS. That was necessary with backwards compatibility when iOS 8 changed needing to prompt the user for permissions to access the camera, gps, etc. Older iOS versions crash if passed methods they don't understand. So you have to test if an object responds to a particular method before calling it. Pretty straightforward.

[stuckless]

Originally Posted by Monedeath

I know this is an option in some scripting languages, but not sure how it would be approached in Sage or Java in general. Perhaps implement it in such a way that it "fails gracefully" (or never even executes) if certain conditions are not met. Such as before it tries to do something have it do a check for a java version greater than x.y.z before trying to carry it out. Maintain the backwards compatibility, but allow the newer ones to take advantage of those abilities.

Of course doing that would make maintainability of the code base more difficult.

Originally Posted by Taddeusz

Not sure about Java but I know you can do that sort of thing with iOS. That was necessary with backwards compatibility when iOS 8 changed needing to prompt the user for permissions to access the camera, gps, etc. Older iOS versions crash if passed methods they don't understand. So you have to test if an object responds to a particular method before calling it. Pretty straightforward.

Absolutely, you can do that type of coding... Android in general is a mess of that You can test code to see if meets a java version, and only run code under certain conditions... You have to be careful to organize that code so that you are references stuff that isn't there. Just makes it more complicated when using reflection. Personally, I'd just say, Java 1.7 is the new minimum, can keep it clean. Which is why I initially suggested to use a plugin, since for a plugin I control the java version

[stuckless]

Originally Posted by Taddeusz

What is his rationale?

I think his rationale is that the current set of hardware extends can only run java 1.5. But either way, I'd have to build it first, and see what happens. (or if someone else want to forge ahead, you'd be looking at the java 7 file watcher apis, and possible the Seeker.java, which I think is responsible for refreshing the library when things change.)

[Fuzzy]

Since the code for the extenders isn't being built anymore anyway, I don't see a reason to not raise the java version to 1.7.

[Skirge01]

Originally Posted by Fuzzy

Since the code for the extenders isn't being built anymore anyway, I don't see a reason to not raise the java version to 1.7.

Because they still have extenders for sale?

[Taddeusz]

Originally Posted by Skirge01

Because they still have extenders for sale?

I wouldn't think that the Java version would affect compatibility between devices as long as the Java objects themselves still conform to 1.5 standards. Are the objects just POCO's or do they have a lot of code included in them?

[Taddeusz]

Sorry, I guess I just answered my own question. No, SageTV's objects are not simple POJO's (POCO's).