The TVersity Media Server has been updated to version 0.9.10.3, adding full support for Sony's PS3's firmware 1.8 and Microsoft's Spring Update for the Xbox 360. This should make the task of streaming media content to and from your consoles occur with fewer conflicts this time round.

• Internet radio now works on the PS3. First playback attempt is likely to fail with an "Access to the media server has been denied" message (or "unsupported data" message), this is because the PS3 does not wait long enough for the data to be fetched over the Internet. After this failure, wait a few seconds and try playing this same station again. Assuming a connection to that station was possible, there won't be an error message, however the actual playback may take up to two minutes and more to start since the PS3 requires about 1 MB of data before it initiates playback.
• Internet video and transcoded content starts playing faster on the PS3 than it used to (saving about 5 seconds).
• Library refresh is now reflected on the PS3 and on any other device that checks the media server for updates (leaving a folder that has updates and then going back to it is required in order to see the changes).
• Issues with green bars or distorted colors when playing via PS3 were resolved.
• TVersity can now produce for the 360, WMV7 or WMV8 or WMV9 or MSMPEG4V3 once can switch between them by setting the wmProfile variable in config.xml to one of wmv7, wmv8, wmv9, mp43.
• TVersity can now encode to WMV in two methods, the first is via directshow (which always existed and still is the default) and the second is via ffmpeg. While for now only wmv8 can be produced via ffmpeg, it is slightly faster than directshow and hence it may prove beneficial in certain cases.
• Fix image browsing for the DirectTV HR20.
• Do not block every URL with two consecutive dot characters, but rather check if the canonical path is shared or not and based on this determine if to allow ot deny access to it. This solves some playlist related playback issues.
• The TVersity service is now starting more reliably during a reboot, waiting, if necessary, for the networking to finish initializing, instead of quitting if it is not already initialized when Tversity is started.