Trouble with SMB playback on 0.5 and cache= does not seem to be used

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Using MplayerCE version 0.5, change the cache=8192 to cache=32768 and
then startup an xvid over SMB. 

What is the expected output? What do you see instead?
I would expect to see the video take about 23-25 seconds to start and then
have flawless playback throughout the video.  Instead, it takes only 7
seconds to start and then I get about 1 minute 20 seconds of flawless
playback and then the video and audio slows to about 1 frame per second.

What version of the product are you using? On what operating system?
MplayerCE 0.5 on Wii 3.1U with no cios`s or custom IOS`s installed.

Please provide any additional information below.
A little background first.  I have been using MplayerCE since version 0.1.
 In version 0.2d, I discovered that changing the cache=8192 to cache=32768
in mplayer.conf allowed me to play back some really "difficult" xvid`s with
some high bitrates (2 hour long 3gig xvid played perfectly over SMB).  I
have been using 0.21d since I discovered this.  The startup time for the
xvid`s would be about triple but the playback would be flawless.

I had trouble with crashing (issue # 78) in version 0.21e to 0.3a.  Version
0.4 I kept having trouble with video`s getting out of sync, but didn`t do
much testing on that version.

I tried out version 0.5 and left all the defaults alone and tried to play
back an xvid.  Startup time was 7 seconds.  After about 1 minute 20 seconds
of flawless playback the audio and video would slow to 1 frame per second
for about 20 seconds and then would speed up and go back to normal, but the
audio would be out of sync.  I set the cache=32768 and then started an xvid
again.  I expected the startup time to be more like 25 seconds, but instead
it still took 7 seconds and had the same problem at the same point in the
video.

I`m thinking (just a guess) that it`s no longer taking the cache= variable
from the mplayer.conf file anymore because no matter what I change it to,
the startup time does not change from 7 seconds.

Version 0.21d gets used nearly every day and my family absolutely loves it,
even if I can`t get future versions working properly, I will continue to
use 0.21d and still love it.  

All my testing and experiences are with SMB over a wireless connection. 
The wireless connection shows "green" in the wii config and if I place a
wireless laptop beside the wii I`m able to stream the same files flawlessly
with a wifi strength of 95% so i don`t think it`s a wireless strength issue.

Thanks for taking the time to read this.  MplayerCE is a truely awesome app
that gets more use than any of my wii games.

Original issue reported on code.google.com by teefe...@hotmail.com on 29 Apr 2009 at 3:09

[GoogleCodeExporter]

"I`m thinking (just a guess) that it`s no longer taking the cache= variable
from the mplayer.conf file anymore because no matter what I change it to,
the startup time does not change from 7 seconds."
Correct: we discovered that the freezing issues (perhaps issue 78?) seemed to 
be with
the cache so we fixed it to 1mb.  This is set to be increased to 4mb in v0.51.  
It
seems like this is the best way to stop freezing occurring until we get to the 
bottom
of the bug - it is a difficult one to find.  I would suggest using 0.21d for the
times when you need such a large cache until we manage to fix the bug once and 
for all.

Original comment by agent...@gmail.com on 29 Apr 2009 at 6:06

[GoogleCodeExporter]

As a fix perhaps try changing

  cache-min=30

to

  cache-min=100

in mplayer.conf and let me know if that helps

Original comment by agent...@gmail.com on 29 Apr 2009 at 6:09

[GoogleCodeExporter]

Thanks for the reply and the info on the cache.  

FYI, I tried setting cache-min=100 and when loading mplayerce, the wii would 
reboot
itself shortly after displaying the version number.  I set it to 99 and it 
didn`t
crash, but the problem remained.

Original comment by teefe...@hotmail.com on 29 Apr 2009 at 9:08

[GoogleCodeExporter]

Variable cache is back in 0.6.

Original comment by agent...@gmail.com on 23 May 2009 at 4:02

• Changed state: Fixed