Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[park]

I think that the issue comes from the Auto-import process. I have got used to it and just wait it out, but for new users this could be confusing and clicking around on the interface to try and get it to work would cause Windows to issue the "program not responding" dialog.

Is there any way you could make MC less busy when starting up? Perhaps queue some of its tasks till it senses there is CPU, memory and network bandwidth to attempt them.

[glynor]

This does not happen for me.

I suspect it is Windows spinning up drives, for which (unfortunately) there is nothing JRiver can do, because the Windows API just works that way. See if you can set your media drive not to sleep, and see if it goes away.

[Vocalpoint]

I suspect it is Windows spinning up drives, for which (unfortunately) there is nothing JRiver can do, because the Windows API just works that way. See if you can set your media drive not to sleep, and see if it goes away.

This started happening to me when I switched our media share from Windows Server to Windows 7.

I can confirm the HTPC is on the "high performance plan" with no drive spin down ever. Yet - MC still sometimes takes 5-7-10 seconds to actually access media on some days.

VP

[glynor]

Park, do you have an optical disc in the drive? Spinning up an optical disc can also cause a full system hang for any application requesting it (which MC does) while it spins up.

[glynor]

This started happening to me when I switched our media share from Windows Server to Windows 7.

I can confirm the HTPC is on the "high performance plan" with no drive spin down ever. Yet - MC still sometimes takes 5-7-10 seconds to actually access media on some days.

Well, it would be the disks on the media server that mattered, not the HTPC (at least, not as much). If any application on windows requests a disk location that is sleeping or otherwise delayed, Windows blocks the application (hangs it) until the disk system responds.

This is not MC specific. It happens even to Windows components. As an example: If I delete a file off of my Users drive (which is allowed to sleep on my systems) and then wait a while for it to sleep again, and then lastly empty the Recycle Bin, then Windows Explorer hangs for a minute or so while the user's volume spins back up (and you can hear the drive spinning back up if you're close to the PC). It is fairly dumb, but that's just the way Windows works.

I don't know that a disk delay is what is causing Park's issue, but that's what it sounds like, for sure.

[DoubtingThomas]

I see this too sometimes, usually when I upgrade to a newer build.  I have MC autostart playback and playback starts and continues to play, but the pgm is totally unresponsive for up to 10 seconds.

So in my case.. it's not a disk spin up issue since the music is playing before the freeze and during the freeze.

[DJLegba]

Are you connecting to more than one library? Fire up Windows Resource Monitor, set it to overview mode, and then start MC. If MC is doing something for 10 seconds you're bound to see it in the Resource Monitor.

[Vocalpoint]

Are you connecting to more than one library? Fire up Windows Resource Monitor, set it to overview mode, and then start MC. If MC is doing something for 10 seconds you're bound to see it in the Resource Monitor.

I connect to a single local library. And that part seems to be fine. MC starts up fine and displays the UI fine - it when I select an album and hit play - sometimes it's 5-10 seconds before the library items appear or any song can actually start up.

When I had my media on the Windows Server - everything was instant. No delays in anything. Probably a combo of network and other downstream things with Windows 7.

VP

[JimH]

I connect to a single local library. And that part seems to be fine. MC starts up fine and displays the UI fine - it when I select an album and hit play - sometimes it's 5-10 seconds before the library items appear or any song can actually start up.

When I had my media on the Windows Server - everything was instant. No delays in anything. Probably a combo of network and other downstream things with Windows 7.

That could just be a drive spinning up.  Unless it happens every time you start playback.

Play from memory would also give a slight lag.

[Vocalpoint]

That could just be a drive spinning up.  Unless it happens every time you start playback.

Play from memory would also give a slight lag.

The HTPC is set to never let the drives spin down. I may want to check play from memory tho...

VP

[JimH]

Antivirus software is another possibility.

[park]

Sorry for posting this and not following up sooner. Some more information. I have a pretty minimal system. Windows 10 with just media center, handbrake, and makemkv installed. No antivirus software. All storage directly attached.
Regarding the disk spin up, I guess that could be a factor except that if I close media center after playing something and then immediately open it again I get the same 10 second freeze. I will test toggling some settings and try to save some logs. I think it might be auto import related.

[JimH]

Double check auto import settings.

Turn off podcast support.

Turn off auto import.

Look to see if anything refers to devices that are not available.

A delay like that could be a DNS timeout.

Make a backup of your library, then create a new one with a few files to see what happens.