<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Arial; font-size: 12pt; color: #000000'>Hi all,<br><br>I am loving the new 0.22 and all the improvements on the UI. It looks much more<br>polished and hi-end and I especially love the screenshots and fanart, etc. in both<br>the watched recordings screen and mythvideo. A great, big Thank You to all the<br>people and developers involved in making this happen!!<br><br>However, I am having several issues with the frontend UI which I wanted to mention<br>on the list. I know that there are several threads discussing CPU usage of mythfrontend<br>but I think that some of the issues that I am seeing are unrelated to that.<br><br>1. In a lot of occasions, when switching from one menu to another (for example, from the<br>top frontend menu to the Media Library menu) the menus freeze for about 10 seconds while<br>both are being displayed. The best way I can describe this is that the menus freeze while the<br>old menu is being faded out and the new menu is being faded in. There is nothing in the frontend<br>log at the normal logging levels during this.<br><br>2. It takes a long time to switch the fanart in both the watch recordings screen and mythvideo<br>and while that is happening the UI freezes. I am using Storage Groups so I know that the<br>frontend sends a request to the backend for the image instead of reading it directly. However,<br>the frontend and the backend are running on the same machine and most of the time, the CPU<br>load is not that great.<br>I also noticed the following errors while trying to load some fanart in the Watch recordings screen:<br><br>2009-11-19 19:19:00.691 MythSocket(5aa6a80:42): readStringList: Error, timed out after 7000 ms.<br>2009-11-19 19:19:00.691 RemoteFile::openSocket(file data socket), Error: Failed to open socket, timeout<br><br>When this error happens on the frontend, the backend has these entries in its log:<br><br>2009-11-19 19:19:23.650 RingBuf(/video/groups/fanart//Burn Notice_fanart.jpg): Could not open /video/groups/fanart//Burn Notice_fanart.jpg.<br>2009-11-19 19:19:23.654 MainServer, Warning: Unknown socket closing MythSocket(0x7fe7990ba740)<br>2009-11-19 19:19:23.663 MythSocket(7fe7990ba740:-1): writeStringList: Error, socket went unconnected.<br> We wrote 0 of 35 bytes with 1 errors<br><br>The image is definitely there, as it sometime manages to show up in the frontend background and I have<br>verified that it exists on the filesystem and is readable.<br>On a separate note, these backend log entries show up a lot in my log, not only when using the Watch Recordings<br>screen but also in mythvideo.<br><br>3. This is probably another instance of the general UI slowness, but when I am exiting the frontend,<br>it could take up to a minute or two to actually have it exit as evident my the following log snippet:<br><br>2009-11-20 00:51:57.854 TV: Attempting to change from Watching Video to None<br>2009-11-20 00:51:57.855 TV: Changing from Watching Video to None<br>2009-11-20 00:51:57.882 ~OpenGLVideoSync() -- closing opengl vsync<br>2009-11-20 00:52:48.167 Deleting UPnP client...<br>2009-11-20 00:53:20.104 New DB connection, total: 1<br><br>You can see that there is almost a minute between "closing opengl vsync" and "Deleting UPnP client"<br><br>I am using a dual core Athlon64 3800+ (2GHz) and any graphics acceleration provided by the nvidia drivers,<br>so my system should have the power to display the UI graphics and menus.<br><br>As I said, I love the new UI and I am more then willing to help track this down with any logs and/or<br>experiments, so please let me know if there is anything I can do?<br><br><br></div></body></html>