We have a project consisting of a large number of video files, (some are MPEG-2, some are H.264, some are MP4, etc.). These are served from a web service running under tomcat using the HTTP streaming protocol. Prior to version 1.0, we were able to successfully stream these files to the VLC client, either the standalone application or the Mozilla plug-in running in a web page. The performance was generally pretty good. The web service correctly handles partial download requests, so seeking worked well, and when videos were simply played without fast-forwarding, there were very few connections made between the VLC player and the web service.
With the release of 1.0.0, and now 1.0.1 as well, the performance is so bad the videos are not viewable. On the player side, the symptoms we see are that the first few seconds of video/audio play, (probably just the buffered portion), and then frames start arriving late and the video either stutters or stops playing completely.
Looking at the logs generated by the HTTP streaming server, it is apparent that VLC is constantly disconnecting and reconnecting to the server to seek a short distance forward and then read a small buffer of bytes. I tried to compare the code for the 0.9.9 and 1.0.0 http access module and didn't see anything too significantly different. I did notice in the streaming input module that the minimum read size is quite a bit smaller in the 1.0.0 code than in 0.9.9, but I do not know the internals well enough to see if this is causing the problems or not.
In any case, we have had to revert back to the 0.9 player to make things work. Any idea what would have changed to make the performance under http so bad?