Imported TV as Imported Video

[Spectrum]

How can I force Sage to show imported TV shows as imported videos instead of merging them with TV recordings? In advanced video browser options I have "Recordings in Import Directories" set to Imports, and it has been since ~ beta 10 and in the the "Import TV Media Types as Recordings" is unchecked in the Phoenix settings (BMT); however, it seems like when I add new TV episodes to my imported videos folder they get scattered between the recordings view and the imported videos view.

I know I can use BMT to move them from one to the other, but doing this on 4 seasons of a show would be royal PITA because as far as I can tell it would have to be done on each episode, not at the show or season level.

Also once Sage latches on to the video file as a recording, the only way I have found to get it out of the database is to move the files out of an import directory, rescan, then restart the SageTV service. The rescan doesn't seem to acknowledge the fact that the files are no longer in the import path, even though it can see the root of where they were.

I like the fact that there is a choice for this but it would be nice if it would do what it is told!

[stuckless]

It's odd that you are seeing some imported tv shows showing up as videos and some as recordings. If you have "Import TV as Recordings" turned off, then bmt is not doing this, but i wonder if another plugin is somehow setting the ExternalID field to something that sage considers a recording, only in some cases.

Either way, it's a little known fact, that the "b" in bmt stands for "batch", meaning to to a single operation on a "batch" or collection of files. In the bmt web ui, if you were to browse to a folder in a view, say the "TV (Series/Season)" view, then at each folder level, there is a combo box of batch operations that you can apply the current folder, and it's children. One of the batch operations is "Un-Import as Recording", which removes a file that sage thinks is a recording from the the Recordings and enables it to show up in the Imported Videos. It does not move the file, but rather it changes the properties on the file so that sage no longer thinks that it is a recording. the Un-Import as recording is probably one of the most dangerous operations that you can do since to accomplish this, bmt will "delete" the file and then re-add it, in place, but renaming the file, telling sage to delete it, and then renaming it back to the original file.

[Spectrum]

Thanks Stuckless, that works like a charm. It is odd that they get split between imports and recordings and I have no clue what is causing it which is why I didn't point the finger at anything in particular I am sure it is a plugin though; I tried disabling all plugins and all the files imported into imported videos just fine. Whether it is in the BMT stuff, Phoenix stuff, or Ortus stuff I have no idea but now that I know about the batch drop down, all is well

Another for BMT!

[stuckless]

Originally Posted by Spectrum

Thanks Stuckless, that works like a charm. It is odd that they get split between imports and recordings and I have no clue what is causing it which is why I didn't point the finger at anything in particular I am sure it is a plugin though; I tried disabling all plugins and all the files imported into imported videos just fine. Whether it is in the BMT stuff, Phoenix stuff, or Ortus stuff I have no idea but now that I know about the batch drop down, all is well

I'd like to think that bmt is not responsible I import a fair amount of content, and I don't want ripped tv shows to show up in my recordings... and they never have. The option to import tv as recordings was added for the people that do want that to happen, but I don't use it, so the option is disabled by default The next time you notice this happening, go into the web ui and bring, bring up the show, and note the "Show ID" field. If it starts with EPmt (the 3rd and forth characters are 'mt'), then BMT was the plugin that was responsible When I import tv shows, I mark the 3rd and 4th characters in the Show ID with 'mt' (for metadata tools), as a signature. It helps me determine if bmt is responsible for changing the ShowID, which is how a normal file can end up as a recording.

Another for BMT!

Thanks! There's a lot more to bmt than most people realize

[gplasky]

I'm wondering are there overlapping options for this in BMT and Phoenix. I'm not at home but I do recall looking in the Phoenix plugin options and thought I saw it. and some other options that were the same as BMT. I thought maybe it was just exposing it from BMT. But I could be misremembering the whole thing. I'll take a look tonight.

Gerry

[stuckless]

Originally Posted by gplasky

I'm wondering are there overlapping options for this in BMT and Phoenix. I'm not at home but I do recall looking in the Phoenix plugin options and thought I saw it. and some other options that were the same as BMT. I thought maybe it was just exposing it from BMT. But I could be misremembering the whole thing. I'll take a look tonight.

Gerry

Gerry, there is a very close relationship between bmt and phoenix Since I maintain the code for both, much of what used to be bmt, is actually a part of core phoenix. ie, bmt doesn't really fetch metadata and fanart, but rather the phoenix services do, and bmt uses those services. The only thing that is really "bmt" these days is the bmt web ui, which is really just a front end to the services that exist in core phoenix code (confused yet)

That is why, when you look in the plugin configuration for the "phoenix-core" plugin, you'll find the very same options that exist in the bmt web ui. But also notice that in the bmt web ui, all the configuration options are actually stored on "Phoenix" in the configuration. BMT doesn't have any configuration options (or very few).

So, you can think of BMT has simply being a web front end to the fanart/metadata services that exist in Phoenix.

[gplasky]

Originally Posted by stuckless

Gerry, there is a very close relationship between bmt and phoenix Since I maintain the code for both, much of what used to be bmt, is actually a part of core phoenix. ie, bmt doesn't really fetch metadata and fanart, but rather the phoenix services do, and bmt uses those services. The only thing that is really "bmt" these days is the bmt web ui, which is really just a front end to the services that exist in core phoenix code (confused yet)

That is why, when you look in the plugin configuration for the "phoenix-core" plugin, you'll find the very same options that exist in the bmt web ui. But also notice that in the bmt web ui, all the configuration options are actually stored on "Phoenix" in the configuration. BMT doesn't have any configuration options (or very few).

So, you can think of BMT has simply being a web front end to the fanart/metadata services that exist in Phoenix.

Thanks for that explanation. It starts to explain the "glue" between these two plugins.

Gerry

[Spectrum]

Originally Posted by stuckless

I'd like to think that bmt is not responsible I import a fair amount of content, and I don't want ripped tv shows to show up in my recordings... and they never have. The option to import tv as recordings was added for the people that do want that to happen, but I don't use it, so the option is disabled by default The next time you notice this happening, go into the web ui and bring, bring up the show, and note the "Show ID" field. If it starts with EPmt (the 3rd and forth characters are 'mt'), then BMT was the plugin that was responsible When I import tv shows, I mark the 3rd and 4th characters in the Show ID with 'mt' (for metadata tools), as a signature. It helps me determine if bmt is responsible for changing the ShowID, which is how a normal file can end up as a recording.

I'll keep an eye out and if I notice it happening again Ill post it in the BMT thread so you don't have to monitor this one.

Originally Posted by stuckless

Gerry, there is a very close relationship between bmt and phoenix Since I maintain the code for both, much of what used to be bmt, is actually a part of core phoenix. ie, bmt doesn't really fetch metadata and fanart, but rather the phoenix services do, and bmt uses those services. The only thing that is really "bmt" these days is the bmt web ui, which is really just a front end to the services that exist in core phoenix code (confused yet)

LOL made me think of this (slightly modified for context)