Resuming from Stop Causes LONG delay (1 Viewer)

[ferndave]

TV-Server Version:
MediaPortal Version: 1.0.1
MediaPortal Skin:
Windows Version: XP SP3
CPU Type: AMD 2800
HDD:
Memory: 1GB
Motherboard:
Video Card: ATI 9600
Video Card Driver:
Sound Card:
Sound Card AC3:
Sound Card Driver:
1. TV Card:
1. TV Card Type:
1. TV Card Driver:
2. TV Card:
2. TV Card Type:
2. TV Card Driver:
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec:
MPEG2 Audio Codec:
h.264 Video Codec:
Satelite/CableTV Provider:
HTPC Case:
Cooling:
Power Supply:
Remote:
TV:
TV - HTPC Connection:

I'm having a problem with resuming playback after hitting stop. In other words:
- Start playback of a video (takes only a few seconds to begin playing)
- Hit stop
- Hit play on the same video (it doesn't happen if it is a different video), and no matter if I resume where I left off or not, it will take at least 3-5 minutes before the video starts playing again.
- I can quit MP and restart MP and it will still take 3-5 minutes to start playing that video again.

It's frustrating to me, but the wife gets a little when things "just don't work."

I've upgraded to 1.0.1, but this happened with the 1.0 release as well. I run a simple install only using Videos. I've attached the log file of the above process and would appreciate any help or input.

 

[tourettes]

Really weird if restarting MP doesn't solve the delay. That would point the issue to be somewhere outside MP. I cannot personally reproduce the issue (or haven't ever seen it on any MP version).

 

[ferndave]

It IS odd, and I've tried everything that I can think of to resolve the problem, so I turned to the forum. I did a quick install on another computer and didn't incur the same problem using the same video folder and files. It must be something effecting MP, but only when resuming playback, and for the life of me I can't figure out why.

At first I thought that the file was being scanned for codec/length/whatever, but it doesn't matter the file type. Plus, the HD wasn't active enough that would evidence such a scan. I'm stumped and hope someone has an idea of what could be the problem.