BMT 4.9.7 Released (Couple of fixes + Enhancements)

[stuckless]

BMT 4.9.7 fixed 2 bugs
* Initial about dialog displays all the time
* Recording metadata was getting overwritten even if the Preserve Recording Metadata flag was set. This was a bug introduced in 4.9.6.

It also adds a couple of other enhancements to the phoenix api
* Fanart lookup caching. This should give a slight benefit to people that have fanart residing on a server
* Ability to pass a null image transform. This can be used by stv devs that want to cache fanart lookups locally (which is already being done by most plugins)

In the web ui, I've added a couple of minor enhancements.
* Added a watch indicator to the media files. Will show a watched icon on any files that have been watched.

* Added a play button to the media files.
The play button will show a dialog of connected clients/placeshifters. You can then play the file on a selected client. That dialog will also show on option to add the item to the BMT Web UI playlist. If you select this then the item will get added to the playlist, and the playlist will be created, if it is not created already. I use this feature to find a movie that I want to watch using the bmt web ui, and then I add it to the playlist, so that I can find it easily when I go into SageTV. Over time, I'll probably do more with this dialog, but for now, it's a start.

[Qusix]

I installed the update and now I get an error when trying to browse via the web ui.

Message

Failed to get Scans in progress
Unable to get items for view


Anyone else get that message?

[stuckless]

Clear your browser caches and
Maybe restart the sage server as well.

[LehighBri]

Originally Posted by stuckless

* Added a play button to the media files.
The play button will show a dialog of connected clients/placeshifters. You can then play the file on a selected client. That dialog will also show on option to add the item to the BMT Web UI playlist. If you select this then the item will get added to the playlist, and the playlist will be created, if it is not created already. I use this feature to find a movie that I want to watch using the bmt web ui, and then I add it to the playlist, so that I can find it easily when I go into SageTV. Over time, I'll probably do more with this dialog, but for now, it's a start.

Great release as always. I tried out this feature and seems to work well, but one thing I noticed is that it is my client running on my server does not show up in the list. In my case, I use my windows server PC to also watch TV. Is there a different API call or method that is used to show a client that is running on a server PC?

[Skirge01]

Originally Posted by Qusix

I installed the update and now I get an error when trying to browse via the web ui.

Message

Failed to get Scans in progress
Unable to get items for view


Anyone else get that message?

I just did some very basic testing of the latest BMT Web UI and it seems to be working fine.

[stuckless]

Originally Posted by LehighBri

Great release as always. I tried out this feature and seems to work well, but one thing I noticed is that it is my client running on my server does not show up in the list. In my case, I use my windows server PC to also watch TV. Is there a different API call or method that is used to show a client that is running on a server PC?

i'm not sure. I'm using the GetConnectedClients() api and the GetUIContextNames() apis to figure out which clients are connected? I'm not sure what else to use to figure this out.

[LehighBri]

Originally Posted by stuckless

i'm not sure. I'm using the GetConnectedClients() api and the GetUIContextNames() apis to figure out which clients are connected? I'm not sure what else to use to figure this out.

Not sure if it's just me or if anyone else is having this issue. Maybe you could add the GetServerAddress() to the list of clients that returns? Either that or perhaps there is a request to have Sage update the APIs? This is all minor stuff I just want to make sure I understand what is truly supposed to appear in the list of clients that I can play to

[stuckless]

Originally Posted by LehighBri

Not sure if it's just me or if anyone else is having this issue. Maybe you could add the GetServerAddress() to the list of clients that returns? Either that or perhaps there is a request to have Sage update the APIs? This is all minor stuff I just want to make sure I understand what is truly supposed to appear in the list of clients that I can play to

My understanding was that GetConnectedClients() would return the full list of clients that are connected. I'm not sure why your client would not show in the list. Now, I only show a client that is actively connected. ie, if you are not currently connected, then it won't show.

[Fuzzy]

In my limited testing, it all seems strange what the various calls return. For instance, right now I'm at work, but I can use the sagex services to check the calls. At home I've got just my local UI running, and I've got a placeshifter connected from here at work. The GetConnectedClients() call returns just 127.0.0.1.49343 (the local UI instance). However, the GetUIContextNames() only returns 00237dc4e449 (the mac address of my work computer, so this is representing the placeshifter instance).

[stuckless]

Originally Posted by Fuzzy

In my limited testing, it all seems strange what the various calls return. For instance, right now I'm at work, but I can use the sagex services to check the calls. At home I've got just my local UI running, and I've got a placeshifter connected from here at work. The GetConnectedClients() call returns just 127.0.0.1.49343 (the local UI instance). However, the GetUIContextNames() only returns 00237dc4e449 (the mac address of my work computer, so this is representing the placeshifter instance).

In BMT, when I get the clients, I actually call both GetConnectedClients() and GetUIContextNames() and merge the list together to get a list of all available sagetv frontends that can accept commands.

[goatboy160]

I just upgraded and now BMT is failing to load. Where can I look for meaningful logs to see why it's failing?

Updated:
After rebooting my Server it came up, but now I'm getting an error loading Phoenix on the status page.
Failed to get status for: Phoenix

[stuckless]

Originally Posted by goatboy160

I just upgraded and now BMT is failing to load. Where can I look for meaningful logs to see why it's failing?

Updated:
After rebooting my Server it came up, but now I'm getting an error loading Phoenix on the status page.
Failed to get status for: Phoenix

I see this from time to time. Normally, if I see this, I will restart sagetv server and then try again. And if that doesn't work, then clear caches on your browser (sometimes it's just as easy as hitting reload on the page while holding down shift, but if that doesn't work, then use the clear cache options built into your particular browser)

It appears that sometimes the web archive doesn't extract correctly, which can result in this error. Most time, just restarting sagetv is the fix.

[wayner]

Originally Posted by stuckless

* Added a play button to the media files.
The play button will show a dialog of connected clients/placeshifters. You can then play the file on a selected client. That dialog will also show on option to add the item to the BMT Web UI playlist. If you select this then the item will get added to the playlist, and the playlist will be created, if it is not created already. I use this feature to find a movie that I want to watch using the bmt web ui, and then I add it to the playlist, so that I can find it easily when I go into SageTV. Over time, I'll probably do more with this dialog, but for now, it's a start.

Great idea, although I haven't had a chance to try this yet.

I have been thinking recently that it would be nice if BMT and the Sage WebUI were merged, or at least somewhat integrated. IMHO the Web UI is great but it is getting a bit stale - I believe jreichen converted it to Jetty from Nielm's orignal webserver but I don't know that much has changed in the functionality in a long time.

The one area that the WebUI is rather weak is in your Video Library and that is where BMT shines.

I know that you may not want to be stuck supporting the whole web server but any thoughts on this?

[gplasky]

I don't know. I see them as 2 seperate apps doing 2 seperate things. I certainly don't need BMT access on the road to manipulate metadata. I use the Web UI just to check if recordings are going on or add a show to record that I forgot or find new and looks interesting. Keep in mind someone would just have to pickup the neilm webserver code and rework the code or add any new feature they want. So far no one has the initiative. And I wouldn't expect neilm to come back and pick it up either. I saw robogeek reworked the css and updated the color layout so it is more v7ish.

Gerry

[LehighBri]

Originally Posted by stuckless

In BMT, when I get the clients, I actually call both GetConnectedClients() and GetUIContextNames() and merge the list together to get a list of all available sagetv frontends that can accept commands.

Upon looking at this more, if I choose the 127.0.0.1 option to play to, it will play to my server's client that is open. I was just confused by the 127.0.0.1 as I was browsing the BMT website on a PC other than my server. Works great... just worth either cleaning up the names/IPs that appear or letting folks know that 127.0.0.1 means to play to the client on the sage server. Great stuff.

[stuckless]

Originally Posted by wayner

I have been thinking recently that it would be nice if BMT and the Sage WebUI were merged, or at least somewhat integrated. IMHO the Web UI is great but it is getting a bit stale - I believe jreichen converted it to Jetty from Nielm's orignal webserver but I don't know that much has changed in the functionality in a long time.

The one area that the WebUI is rather weak is in your Video Library and that is where BMT shines.

Originally Posted by gplasky

I don't know. I see them as 2 seperate apps doing 2 seperate things. I certainly don't need BMT access on the road to manipulate metadata. I use the Web UI just to check if recordings are going on or add a show to record that I forgot or find new and looks interesting. Keep in mind someone would just have to pickup the neilm webserver code and rework the code or add any new feature they want. So far no one has the initiative. And I wouldn't expect neilm to come back and pick it up either. I saw robogeek reworked the css and updated the color layout so it is more v7ish.

jreichen and I have spent some time discussing possibilities here. I think as bmt matures, there will be some overlapp with the standard web ui. I don't think that it will ever be a complete replacement for it, and certainly, I'm not looking for that, but I think that bmt will get some duplicate features. A core part of BMT is being able to better visualize and browse your media, and it relies heavily on the Phoenix Virtual Filesystem (VFS) to do that. I use bmt a lot myself, and sometimes, I hear myself saying, "I wish I could do that from within bmt instead of having to jump to the standard web ui". Being able to play on an extender or building up a playlist was an example of that, so I added it in. A nice part of the phoenix VFS is that is deal with all sorts of objects, not just media files. I've added views for upcomming recordings and upcomming movies. I'll probably add a quick record button to epg airing type objects so that if I look at the upcomming movies, then I can click record to quickly schedule a recording. ie, over time, bmt may become more of a media browser that has metadata features (which is how I see it today).

As for merging, I don't see that happening. As was noted, bmt relies heavily on Phoenix to provide the view engine and many other features. Really BMT is a web frontend to Phoenix. To make the default web ui rely on phoenix would probably be wrong, since there are a lot of people that use the standard web ui that are not running bmt or phoenix.

What would be nice, and this has been discussed as well, is if we could simply create a common set of css files so that all web applications could take advantage of that and have a similar look and feel. Also, if we could somehow add dynamic linking between apps, then that would be cool as well. ie, if you were browsing bmt, and hit record on an item, it would take you to the main web ui record page where you could create manual recording or add a favorite for the item. All these things have been discussed and maybe someday, they'll take shape.

Originally Posted by LehighBri

Upon looking at this more, if I choose the 127.0.0.1 option to play to, it will play to my server's client that is open. I was just confused by the 127.0.0.1 as I was browsing the BMT website on a PC other than my server. Works great... just worth either cleaning up the names/IPs that appear or letting folks know that 127.0.0.1 means to play to the client on the sage server. Great stuff.

BMT uses the extender.properties (and it will soon use the newer model developed by jreichen and shadeblue) to add a friendly name to your clients. If you know how the configure the extender.properties, then you can add your own custom name.

[goatboy160]

Although Phoenix says it is running I'm not able to get any meta data to import. When I browse through Sage Video Imports. When I go to open up the episode I see a message "Failed to get metadata for item..." and then the episode details are blank.

Also the vertical scroll bars appear to be missing in the browse screen (tried FF and IE).

Update: upgrade Jetty Web Server fixed the previous issues.. Now I just keep getting Unable to get metadata when loading meta data

Attached screenshot of unable to get metadata error.

Log Message:
2011-01-15 19:35:37,677 [12767107@qtp-8585506-4] ERROR org.jdna.bmt.web.server.BrowsingServicesImpl - Failed to get metadata: 134062; The Cape 2011 S01E01
java.lang.NoSuchMethodError: sagex.phoenix.metadata.IMetadata.getTitle()Ljava/lang/String;
at org.jdna.bmt.web.server.BrowsingServicesImpl.newMetadata(BrowsingServicesImpl.java:311)
at org.jdna.bmt.web.server.BrowsingServicesImpl.loadMetadata(BrowsingServicesImpl.java:268)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:562)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:188)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:224)
at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:389)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:879)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520)

[stuckless]

Originally Posted by goatboy160

Although Phoenix says it is running I'm not able to get any meta data to import. When I browse through Sage Video Imports. When I go to open up the episode I see a message "Failed to get metadata for item..." and then the episode details are blank.

Also the vertical scroll bars appear to be missing in the browse screen (tried FF and IE).

Update: upgrade Jetty Web Server fixed the previous issues.. Now I just keep getting Unable to get metadata when loading meta data

Attached screenshot of unable to get metadata error.

Log Message:
2011-01-15 19:35:37,677 [12767107@qtp-8585506-4] ERROR org.jdna.bmt.web.server.BrowsingServicesImpl - Failed to get metadata: 134062; The Cape 2011 S01E01
java.lang.NoSuchMethodError: sagex.phoenix.metadata.IMetadata.getTitle()Ljava/lang/String;
at org.jdna.bmt.web.server.BrowsingServicesImpl.newMetadata(BrowsingServicesImpl.java:311)
at org.jdna.bmt.web.server.BrowsingServicesImpl.loadMetadata(BrowsingServicesImpl.java:268)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:562)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:188)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:224)
at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:389)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:879)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520)

It doesn't appear that your BMT version matches the phoenix version? You may want to try restarting the sagetv server to see if it will extract the latest version, and clear your browser cache to ensure that you are loading the most up to date browser code as well. What was your previous version, it must have been fairly old, since the method that it is trying to call, hasn't been in phoenix for some time.

[goatboy160]

I had last upgraded in December. I ended up removing BMT and Phoenix completely and then reinstalling everything to get it working.

Here are the versions from the BMT Status page
Phoenix Version 2.3.13
sagex.api Version 7.0.23.3
SageTV Version 7.0.23.246
BMT Version 4.9.7

Restarted everything again (including the machine) still got the errors.

[stuckless]

Originally Posted by goatboy160

I had last upgraded in December. I ended up removing BMT and Phoenix completely and then reinstalling everything to get it working.

Here are the versions from the BMT Status page
Phoenix Version 2.3.13
sagex.api Version 7.0.23.3
SageTV Version 7.0.23.246
BMT Version 4.9.7

Restarted everything again (including the machine) still got the errors.

You are definately not running the latest bmt web. The line numbers and code segment that it is failing on, is from a much older build.

You can try uninstalling bmt, restarting sagetv, and then installing bmt again, and see if that helps. Also, perhaps you can use the Help -> Create Support Request function from the UI (if it works) and send me the logs.