Re-buffering occurs at the beginning of each song.Ĭlient phase 3. On the server side this is about all I observed, but on the client side (with streaming enabled) there are more phases, so I will list them, but I'm not sure if this information will be helpful.Ĭlient phase 2. Still, it usually needs more than 24 hours to get to this phase, but its behavior may shed some light on what the problem may be.ĭuring that phase before it fails Winamp plays files at about 4x the normal speed, therefore indicating it loses its timings, whatever those timings are. On the server side there is one important phase before it stops playing. It gradually progresses from good to unusable. However, this testing reminded me about one very important piece of information that I forgot to mention at the beginning. Winamp is not to be blamed here.Ī limited testing with single local looping file shows so far that it makes no difference. This proves that the configuration I have is sound (I've been streaming music for many years already) and the problem (whatever it is) is on the VBox side. Winamp streams mp3 music for weeks at at time without being touched at all. So networking issue can be safely excluded.Ī physical box with almost identical configuration (with more stuff installed on the physical box) has no problem. Actually on the same host there is another XP guest running P2P client, transmitting copious amount of data daily and there is no problem whatsoever with that one. It doesn't seem to be a problem with audio resources (because sound it is muted by Winamp) or a network resource limit (with or without network traffic same problem). It seems to be a problem with a resource leak of some sort or some other limit reached (shared folder reaching transmission limit ) ). The VM (guest) has to be rebooted to clear the problem. Winamp starts up, but it won't play anything at all. Restarting Winamp doesn't fix the problem. ![]() It seems to respond to shut down (window closes), but it reamins in the task list and has to be killed. The problem is that after some time (AT LEAST 24 hours of continuous playing, but usually less than 48 hours) Winamp stops playing. ![]() The audio is muted (it's meant for network streaming) and without a network traffic (streaming turned off for testing) the same problem happens. The mp3 files that Winamp plays are shared through VBox shared folder from the host. Winamp (latest version 5.621, much older version 5.24 tried with the same result) is configured for mp3 streaming (however with streaming turned off the same problem exists) using Icecast2 (v2.3.2) and Edcast (3.1.21). This seems like a resource leak problem and it's been there always (3.x.x? first version I tried).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |