Plex Scanner and BMT Agent for SageTV

[PiX64]

The initial scan will take some time to setup oringinally but it is not a SageTV Scanner or BMTAgent issue, it is a plex shortcoming. once populated fully, your update scans will be quick, short, and to the point :-)

[Taddeusz]

Originally Posted by PiX64

The initial scan will take some time to setup oringinally but it is not a SageTV Scanner or BMTAgent issue, it is a plex shortcoming. once populated fully, your update scans will be quick, short, and to the point :-)

Ok, the machine that I had Plex on is kind of slower compared to brand new tech. A 2.33Ghz C2D. I moved Plex over to my other machine that is a 2.66Ghz C2Q and it runs much better and can actually transcode to 1080p to my iPad.

Since Plex is no longer running on my SageTV machine I guess I can just let it run and see what it does as the scans no longer impact playback performance for my extenders.

[Taddeusz]

Originally Posted by PiX64

Is Toy Story of Terror marked as a Movie in your BMT ui ?

It's marked as TV. I recorded it when it originally aired.

[Taddeusz]

I still don't understand why it's not immediately picking up the artwork. Is BMT not responding fast enough for the script so it's timing out?

[mdnttoker]

Originally Posted by Taddeusz

I still don't understand why it's not immediately picking up the artwork. Is BMT not responding fast enough for the script so it's timing out?

Mine takes quite a while initially as well (on a pretty quick processor). Is it trans-coding the artwork?

In fact, some of the series I have to manually hit the "refresh" button a few times to get the artwork to finally pull from Sage.

But once the artwork is loaded properly once into Plex, I can watch and delete all episodes, and any new episodes show up immediately with the correct artwork....

[PiX64]

Originally Posted by Taddeusz

I still don't understand why it's not immediately picking up the artwork. Is BMT not responding fast enough for the script so it's timing out?

I believe it has to do with the order by which plex media server stacks up stuff in the queue for processing. Initial scan takes longer from my experience because it is downloading all of the metadata and plex purposely leaves the artwork which could take a really long time based on response from source until the end. this can be seen by you to if you pop open console on mac and watch the bmtagent logs as it pulls down metadata.

[Taddeusz]

Originally Posted by PiX64

I believe it has to do with the order by which plex media server stacks up stuff in the queue for processing. Initial scan takes longer from my experience because it is downloading all of the metadata and plex purposely leaves the artwork which could take a really long time based on response from source until the end. this can be seen by you to if you pop open console on mac and watch the bmtagent logs as it pulls down metadata.

How long should the initial scan take? It started yesterday at about 10:40AM and is still going. We have 222 recordings. 6 of which are considered movies. I have never before had a scan take this long. Something is not right.

[PiX64]

Originally Posted by Taddeusz

How long should the initial scan take? It started yesterday at about 10:40AM and is still going. We have 222 recordings. 6 of which are considered movies. I have never before had a scan take this long. Something is not right.

that does seem to be a bit long for 222 recordings.

please check the "movies" and let me know if those are classified as movies in BMT. If they aren't, and plex scanner/agent are trying to pull in metadata fields related to a tv show and its not, that can cause issues. I have seen it before in several users setups, as well as my own.

[Taddeusz]

Originally Posted by PiX64

that does seem to be a bit long for 222 recordings.

please check the "movies" and let me know if those are classified as movies in BMT. If they aren't, and plex scanner/agent are trying to pull in metadata fields related to a tv show and its not, that can cause issues. I have seen it before in several users setups, as well as my own.

The movies are being seen as movies. I have a separate Plex section for recorded movies.

I'm going to try downgrading to the previous version of Plex and see if that clears up this scan issue.

[PiX64]

Originally Posted by Taddeusz

The movies are being seen as movies. I have a separate Plex section for recorded movies.

I'm going to try downgrading to the previous version of Plex and see if that clears up this scan issue.

R u certain they are being seen as movies?

The reason i ask is that the screenshot you sent the other day in this thread was a SAGETV recordings sections (TVshows) and it has a movie in it... if that is the case then they are actually not seen as movies by BMT and utlimatly not seen as movies by plex

I think the movie was Toy Story Something or other

[Taddeusz]

Originally Posted by PiX64

R u certain they are being seen as movies?

The reason i ask is that the screenshot you sent the other day in this thread was a SAGETV recordings sections (TVshows) and it has a movie in it... if that is the case then they are actually not seen as movies by BMT and utlimatly not seen as movies by plex

I think the movie was Toy Story Something or other

I don't know why that would matter. I realize it probably is a movie but it has been working fine up until this past Friday when all of a sudden it decided to take 3 days to do a scan. The EPG in SageTV shows it as a TV show and not as a movie. I've never changed it. It was recorded way back in October and has not ever been an issue.

Downgrading Plex didn't do anything. The only change to the system that I am aware of is me upgrading Plex to the latest version. I have since put Plex on a different computer and having the same issue.

[PiX64]

Originally Posted by Taddeusz

I don't know why that would matter. I realize it probably is a movie but it has been working fine up until this past Friday when all of a sudden it decided to take 3 days to do a scan. The EPG in SageTV shows it as a TV show and not as a movie. I've never changed it. It was recorded way back in October and has not ever been an issue.

Downgrading Plex didn't do anything. The only change to the system that I am aware of is me upgrading Plex to the latest version. I have since put Plex on a different computer and having the same issue.

It matters because if inside of plex the metadata agent is trying to stuff Movie related metadata into NON movie metadata fields it can blow up.

If you look at the plex element containers (show -> episode) vs (movie) they are vastly different. This is why i had to create 2 separate scanners. 1 scanner to get movie data and then call the built int OOTB Plex movie metadata agent,
and another for SageTV recordings which ultimately calls the custom BMTAgent.

Different sets of metadata elements and for different types of media.

[Taddeusz]

Originally Posted by PiX64

It matters because if inside of plex the metadata agent is trying to stuff Movie related metadata into NON movie metadata fields it can blow up.

If you look at the plex element containers (show -> episode) vs (movie) they are vastly different. This is why i had to create 2 separate scanners. 1 scanner to get movie data and then call the built int OOTB Plex movie metadata agent,
and another for SageTV recordings which ultimately calls the custom BMTAgent.

Different sets of metadata elements and for different types of media.

Ok, but it has never been an issue. And has actually always been able to get a poster for it.

[Taddeusz]

There are other recordings that could technically be considered movies such as Frosty the Snowman, The Elf on the Shelf, and Prep & Landing. But as I said these have never been a problem and doesn't appear to be a problem from what I see in the logs.

From what I see in the logs FFMPEG is all of a sudden getting hung up on some of the videos doing "Media part analysis". I swear I have media scanning turned off. I even went in and enabled and then disabled the option just to make sure.

[PiX64]

Originally Posted by Taddeusz

Ok, but it has never been an issue. And has actually always been able to get a poster for it.

I understand.

At this point we have to try and isolate the seemingly problematic file(s) in order for me to go back to the code and figure out what needs to be tweaked.

If you would be so kind:

remove the plex section.
clean bundles
empty trash
copy a subset of your sage recordings to another directory (one that is not recorded to by sage)
create a new section in plex for TVShows
add ONLY this new folder to the section
let er scan
if it fails provide me with the new server logs (MEdia Scanner, MEdia Server, BMTAgent Log)
Else: continue to add more shows to the new folder, and perform update scans.
Also please make sure plex isn't set to monitor the folder and auto scan it for now... if it is monitoring your recording folder to auto scan, and sage is constantly changing the file for one reason another (even just touching it) It could cause plex to "infinitly scan" --- This was an OLD issue with plex that has since been fixed (to my knowledge) but, it could have crept back in.

[Taddeusz]

I've been analyzing recordings from around the time when problems started. How would a partial recording affect the scanner? We began watching "The Taste" on regular TV then we went to eat dinner so I started it recording in Sage after it had been going for about 10min. That is the only recording that I can think could be considered problematic.

[PiX64]

Originally Posted by Taddeusz

I've been analyzing recordings from around the time when problems started. How would a partial recording affect the scanner? We began watching "The Taste" on regular TV then we went to eat dinner so I started it recording in Sage after it had been going for about 10min. That is the only recording that I can think could be considered problematic.

That depends -

Is your Plex Media Server set to monitory directories and auto scan on change?

[Taddeusz]

Originally Posted by PiX64

That depends -

Is your Plex Media Server set to monitory directories and auto scan on change?

No

[PiX64]

Originally Posted by Taddeusz

No

Then it could only be problematic if you had a currently running scan on the directory. (which i think we determined previously today that you did...)

[Taddeusz]

Originally Posted by PiX64

Then it could only be problematic if you had a currently running scan on the directory. (which i think we determined previously today that you did...)

I don't think I did anything.

I just downgraded back to 0.9.8.10. I noticed in the change logs that they updated ffmpeg in 0.9.8.14. Now I'm not seeing any FFMPEG errors in the logs.