Plex Scanner and BMT Agent for SageTV

[zoop]

Originally Posted by PiX64

if you are getting errors in the scanner then its not likely the agent is getting called at all.

Please attach your entire PlexMediaScanner log as well as the bmtagent.log if one exists.

A few things to check
1) is bmt installed
2) are you able to hit the url http://x.x.x.xort/sagex/api
3) does your bmt require a username and password
4) did you correctly specify your sage username, password, ip address, etc in the properties file of teh bmtagent.bundle
5) did you correctly change the line of code in the SageTVScanner.py file which points to your sage server
6) did you place the plex.js file in the correct place on your sage server

~Mike

sorry, i should have been more complete with my post.

BMT is installed and working fine. hitting sagex with a browser works fine, including using the proper u/p combination. i changed both properties files, and here are some logs from sagex after a rescan request inside plex:

Sun 1/29 19:01:17.038 [323870850@qtp-320844814-9 - /sagex/api?c=plex:GetMediaFileForName&1=NFLLive-14746961-0.ts&encoder=json@134de082] ::DEBUG: REQUEST /sagex/api on org.mortbay.jetty.HttpConnection@1316b8f8
Sun 1/29 19:01:17.038 [323870850@qtp-320844814-9 - /sagex/api?c=plex:GetMediaFileForName&1=NFLLive-14746961-0.ts&encoder=json@134de082] ::DEBUG: Credentials: Basic amhhcnRtMjpmaXJlMXVw
Sun 1/29 19:01:17.038 [323870850@qtp-320844814-9 - /sagex/api?c=plex:GetMediaFileForName&1=NFLLive-14746961-0.ts&encoder=json@134de082] ::DEBUG: servlet=sagex.remote.SagexServlet-324662012
Sun 1/29 19:01:17.038 [323870850@qtp-320844814-9 - /sagex/api?c=plex:GetMediaFileForName&1=NFLLive-14746961-0.ts&encoder=json@134de082] ::DEBUG: chain=null
Sun 1/29 19:01:17.038 [323870850@qtp-320844814-9 - /sagex/api?c=plex:GetMediaFileForName&1=NFLLive-14746961-0.ts&encoder=json@134de082] ::DEBUG: servlet holder=sagex.remote.SagexServlet-324662012
Sun 1/29 19:01:17.150 [323870850@qtp-320844814-9 - /sagex/api?c=plex:GetMediaFileForName&1=NFLLive-14746961-0.ts&encoder=json@134de082] ::DEBUG: RESPONSE /sagex/api  200
Sun 1/29 19:01:17.154 [323870850@qtp-320844814-9 - /sagex/api?c=plex:GetMediaFileForName&1=IronChefAmerica-S02E03-FlayvsLang-14686493-0.ts&encoder=json@134de082] ::DEBUG: REQUEST /sagex/api on org.mortbay.jetty.HttpConnection@1312f506
Sun 1/29 19:01:17.154 [323870850@qtp-320844814-9 - /sagex/api?c=plex:GetMediaFileForName&1=IronChefAmerica-S02E03-FlayvsLang-14686493-0.ts&encoder=json@134de082] ::DEBUG: Credentials: Basic amhhcnRtMjpmaXJlMXVw
Sun 1/29 19:01:17.154 [323870850@qtp-320844814-9 - /sagex/api?c=plex:GetMediaFileForName&1=IronChefAmerica-S02E03-FlayvsLang-14686493-0.ts&encoder=json@134de082] ::DEBUG: servlet=sagex.remote.SagexServlet-324662012
Sun 1/29 19:01:17.154 [323870850@qtp-320844814-9 - /sagex/api?c=plex:GetMediaFileForName&1=IronChefAmerica-S02E03-FlayvsLang-14686493-0.ts&encoder=json@134de082] ::DEBUG: chain=null
Sun 1/29 19:01:17.154 [323870850@qtp-320844814-9 - /sagex/api?c=plex:GetMediaFileForName&1=IronChefAmerica-S02E03-FlayvsLang-14686493-0.ts&encoder=json@134de082] ::DEBUG: servlet holder=sagex.remote.SagexServlet-324662012
Sun 1/29 19:01:17.260 [323870850@qtp-320844814-9 - /sagex/api?c=plex:GetMediaFileForName&1=IronChefAmerica-S02E03-FlayvsLang-14686493-0.ts&encoder=json@134de082] ::DEBUG: RESPONSE /sagex/api  200

thx

/jer

[PiX64]

Originally Posted by zoop

sorry, i should have been more complete with my post.

BMT is installed and working fine. hitting sagex with a browser works fine, including using the proper u/p combination. i changed both properties files, and here are some logs from sagex after a rescan request inside plex:

Sun 1/29 19:01:17.038 [323870850@qtp-320844814-9 - /sagex/api?c=plex:GetMediaFileForName&1=NFLLive-14746961-0.ts&encoder=json@134de082] ::DEBUG: REQUEST /sagex/api on org.mortbay.jetty.HttpConnection@1316b8f8
Sun 1/29 19:01:17.038 [323870850@qtp-320844814-9 - /sagex/api?c=plex:GetMediaFileForName&1=NFLLive-14746961-0.ts&encoder=json@134de082] ::DEBUG: Credentials: Basic amhhcnRtMjpmaXJlMXVw
Sun 1/29 19:01:17.038 [323870850@qtp-320844814-9 - /sagex/api?c=plex:GetMediaFileForName&1=NFLLive-14746961-0.ts&encoder=json@134de082] ::DEBUG: servlet=sagex.remote.SagexServlet-324662012
Sun 1/29 19:01:17.038 [323870850@qtp-320844814-9 - /sagex/api?c=plex:GetMediaFileForName&1=NFLLive-14746961-0.ts&encoder=json@134de082] ::DEBUG: chain=null
Sun 1/29 19:01:17.038 [323870850@qtp-320844814-9 - /sagex/api?c=plex:GetMediaFileForName&1=NFLLive-14746961-0.ts&encoder=json@134de082] ::DEBUG: servlet holder=sagex.remote.SagexServlet-324662012
Sun 1/29 19:01:17.150 [323870850@qtp-320844814-9 - /sagex/api?c=plex:GetMediaFileForName&1=NFLLive-14746961-0.ts&encoder=json@134de082] ::DEBUG: RESPONSE /sagex/api  200
Sun 1/29 19:01:17.154 [323870850@qtp-320844814-9 - /sagex/api?c=plex:GetMediaFileForName&1=IronChefAmerica-S02E03-FlayvsLang-14686493-0.ts&encoder=json@134de082] ::DEBUG: REQUEST /sagex/api on org.mortbay.jetty.HttpConnection@1312f506
Sun 1/29 19:01:17.154 [323870850@qtp-320844814-9 - /sagex/api?c=plex:GetMediaFileForName&1=IronChefAmerica-S02E03-FlayvsLang-14686493-0.ts&encoder=json@134de082] ::DEBUG: Credentials: Basic amhhcnRtMjpmaXJlMXVw
Sun 1/29 19:01:17.154 [323870850@qtp-320844814-9 - /sagex/api?c=plex:GetMediaFileForName&1=IronChefAmerica-S02E03-FlayvsLang-14686493-0.ts&encoder=json@134de082] ::DEBUG: servlet=sagex.remote.SagexServlet-324662012
Sun 1/29 19:01:17.154 [323870850@qtp-320844814-9 - /sagex/api?c=plex:GetMediaFileForName&1=IronChefAmerica-S02E03-FlayvsLang-14686493-0.ts&encoder=json@134de082] ::DEBUG: chain=null
Sun 1/29 19:01:17.154 [323870850@qtp-320844814-9 - /sagex/api?c=plex:GetMediaFileForName&1=IronChefAmerica-S02E03-FlayvsLang-14686493-0.ts&encoder=json@134de082] ::DEBUG: servlet holder=sagex.remote.SagexServlet-324662012
Sun 1/29 19:01:17.260 [323870850@qtp-320844814-9 - /sagex/api?c=plex:GetMediaFileForName&1=IronChefAmerica-S02E03-FlayvsLang-14686493-0.ts&encoder=json@134de082] ::DEBUG: RESPONSE /sagex/api  200

thx

/jer

ill take a look for ya now.

What os are you running this on?

Also make sure you are running the most version of SageTV, BMT, and sagex. I saw a similiar issue when i first started using the custom .js file that would NOT allow me to call the file which is what looks like is happening. Make sure all that stuff is up to date, and then make sure to restart sage/service. Also please remove the import directory in plex, restart plex, then readd. Post your new logs...

[PiX64]

* Initial SageTV Movie Scanner (Recorded Movies) built
* Initial SageTV BMTMovie Agent also built

both are working nicely. working out the kinks and will release later this week.

[sagestuff]

https://docs.google.com/open?id=0ByQ...EwOTA4Zjc4NWY3

[PiX64]

For anyone running plex client on Roku2 -- check this out

http://streamfree.tv/apps/roku-priva...81-thread.html

I have been using this for a while and its pretty awesome. bascially makes the roku2 ui for plex look exactly like the netflix standard ui for roku its cool!

[PiX64]

SageTV Movie Scanner
&
BMTMoviesAgent

might be release sooner than we thought! working great so far.

[WellThen]

Originally Posted by darcilicious

Here's the thing about Plex / Plex clients.

If the Plex client can play the format natively, it will. If it can't, then I believe the Plex Media Server will try to transcode on the fly -- how well that works depends on the horsepower of the server.

Darci, when you talk about whether the client "can play the format" in the quote above, is that related to the horsepower of the client, or is it about which codecs (or some other separately installable item) are installed on the client? Or, is it tied to which formats Plex intrinsically knows how to play back?

Just about to try setting up Plex, and wondered. Thanks!

[PiX64]

Originally Posted by WellThen

Darci, when you talk about whether the client "can play the format" in the quote above, is that related to the horsepower of the client, or is it about which codecs (or some other separately installable item) are installed on the client? Or, is it tied to which formats Plex intrinsically knows how to play back?

Just about to try setting up Plex, and wondered. Thanks!

When we refer to horsepower we are mostly referring to the server. Whenever a client accesses a piece of media on Plex that it cannot play natively the server needs to transcode into an acceptable format for the client on the fly. Thr being said there are specific situations where u may have an under powered client pc running Plex front end, an Plex server thinks u can play the untranscoded format on your Plex pc client when u can't...in that situation us run into horsepower issues on the client...

[darcilicious]

Good question. And since I deal with a limited number of encoding/container types, I'll answer the best I can.

For example, iOS devices don't play .mkv files natively so the Plex server will transcode. (This is somewhat a bad example because there's a cool/special setting in Plex called direct stream to override the container since in most cases, mkv files contain h.264 files which iOS does play ) But hopefully you get the idea.

So I would say (and you may want to double-check this over at http://forums.plexapp.com) is that if the client doesn't natively support the codec/container, then the server transcodes.

What each client natively supports is dependent on that platform. For some platforms (like Windows), I don't believe it will ever transcode local content and playback quality will depend totally on the horsepower of the client. While other clients (Roku, SamsungTV, etc) I would expect that they support fewer codecs/containers and the unsupported ones get transcoded.

Does that help at all??

[WellThen]

Thanks Pix64 and Darci, I think that clarifies it. Since my clients are Windows PCs, it sounds like it's totally up to the client - and I don't have to worry about my server (which is only a Dual Core) getting bogged down by transcoding for Plex.

[PiX64]

Originally Posted by WellThen

Thanks Pix64 and Darci, I think that clarifies it. Since my clients are Windows PCs, it sounds like it's totally up to the client - and I don't have to worry about my server (which is only a Dual Core) getting bogged down by transcoding for Plex.

Yup u should be good. One cool thig about Plex IMO is that there is almost ultimate flexibilty for clients. So roku2 running Plex or plexgrid channel, atv2 running Plex, are super cheap ways to extend the system to more TVs. I can't say I would use any of the current available extenders for my main movie watchig tv only because they struggle with bluray, but for all other content they are solid in my experience. If I was going to deploy Plex at my
Main "movie" watching tv it'd most likely be a pc client...

[Halstead]

Originally Posted by SWKerr

The plugin appears to work great. I had not problems getting this to work.

I did notice in playing around with this today that I have a bad Audio sync issue with HD-PVR recordings right now. This also occurs with the Eden release of XBMC. OTA HD MPEG2 and my h264 Movie rips work fine, it is just the HD-PVR files with problems. I would be interested if anyone else is experiencing this issue.

I'm having the same sync issue- a good second or two off during playback on my Windows Plex client.

My streaming clients do not seem to have the same problem.

Does Plex use it's own codecs?

[Halstead]

Guys,
Just want to say that I was able to get the plugins installed and configured with no problem at all. Great job on the instructions!

[wbarber69]

Now if we could only get the HDX00 extenders to work with plex

[Jason]

Are there plans to implement any sort of 'watched' status synchronization across the systems (plex <-> Sage)?

-Jason

[wayner]

Originally Posted by wbarber69

Now if we could only get the HDX00 extenders to work with plex

Why? If you want Plex you have options like Roku, ATV, etc. The real problem that everyone is trying to deal with is to get Sage on other extenders.

[Halstead]

Originally Posted by Halstead

I'm having the same sync issue- a good second or two off during playback on my Windows Plex client.

My streaming clients do not seem to have the same problem.

Aaaaand, apparently I was sniffing glue when i said this. Looks like there are a few recordings that do not have the sync issue, and I got lucky. Looks like a good 90% of mine do, and on every platform.

Is anyone *not* having the sync issues? It would be interesting to see the differences in platforms.

[darcilicious]

Are you talking about HD-PVR recordings or something else?

Have you enabled HW acceleration in Plex (for Windows clients)?

Which clients are you using (other than Windows)?

[Halstead]

Originally Posted by darcilicious

Are you talking about HD-PVR recordings or something else?

HD-PVR only.

Have you enabled HW acceleration in Plex (for Windows clients)?

Yep. Tried it both ways.

Which clients are you using (other than Windows)?

OSX, iOS, Android. I've also tried both local and remote (streaming) connections. Behavior seems to be consistent across all clients.

I'm happy to troubleshoot, but given my novice Plex-sperience, I'm not are where to start.

[darcilicious]

Okay what are the CPU/GPU/OS specs/info for the Plex server and Windows clients?

I've got HDPVR/1080i recordings and I haven't had any audio sync issues, primarily on a Windows client, W7/QuadCore AMD/nVidia 8400GT.