![]() UPDATE:HP has released 3.0 Patch 3 which corrects the mis-configured file I describe below. If you experience this problem, here is how you can fix it. This was a new behavior, so I started comparing the new system with my recently upgraded EX487 that is running the 3.0 software update, and discovered an important difference in the Audio Transcoding configuration file. Files that were encoded at a high bitrate (320kbit, for example), were converted to 32kbit which sounds worse to me than AM radio. Most files were converted to 96kbit bitrate, which was acceptable but not great quality. Twonky was now transcoding and caching versions of my music library when I would attempt to play them via Remote Media Streaming. In the course of investigating the issue, I uncovered some interesting details. Terrible, low resolution sound quality for some songsīasically, one of the features that I use the most had just become unusable.When a song completed, playback would not continue to the next track in the album.Songs would take tens of seconds or longer to begin playing.I experienced very poor performance while using the Music streaming feature, with the system exhibiting the following symptoms. ![]() The second problem had to do with the Remote Media Streaming feature. A reader of this site named marco also experienced this same issue and was able to resolve the problem the same way I did. I do not know why this file caused a problem, it plays fine on my computer and its metadata can be read by MediaInfo. You may have to perform this multiple times if there are more than one file causing issues for Twonky. Start Twonky again and hope that it doesn’t get stuck on another file. You’ll need to stop Twonky (the Stop Sharing button the Media Server tab works for me), then move this file out of the Twonky indexed folders (I moved mine to the Public share). I’ve highlighted the offending file on my system below in red. You should see output similar to the below, including the name of the media file that has Twonky “stuck” while indexing. Type the following into the command prompt window. Start a command prompt (Start->Run and type “cmd” with no quotes then hit Enter). Copy the zip file from the Software share to your server Desktop, unblock it, and then extract it. Copy the zip file to your server Software share, and then log onto your server via Remote Desktop. Update: I’ve found an easy way to identify the exact file that is causing Twonky to freeze, keep reading for the details.įirst, download the free “handle” utility from SysInternals here. Eventually the indexing completed and I was able to determine which file was problematic. This didn’t resolve the issue, so I moved up a directory and continued. I started moving files out of that directory and into the Public share, telling Twonky to rebuild the database each time. I watched the Twonky status in the “Media Server” tab of the server console, and noticed that it had indexed a lot of my content but the Last Database Update status showed that it was “In progress” and appeared to be stuck indexing a specific directory. I don’t have a magic fix for this, unfortunately, but I can tell you how I investigated the problem. I eventually narrowed this down to a single video file in my library and have worked around the problem, however this is very frustrating since I did not experience this issue prior to installing Patch 2, and the updated 5.1.1 version of Twonky was specifically supposed to contain the resolution for this issue. The first was a problem where I experienced the high CPU utilization caused by Twonky. Since performing the initial install I’ve spent some more time with my EX495 running the update and have encountered a couple of issues. Yesterday I reported on the availability of the 3.0 Patch 2 software we discovered on the HP web site, and gave instructions on how to install it.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |