Print

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

[iEditor]

When I run MC20, I find it launches quickly, but after 3-4 seconds of use, the spinning blue wheel appears. The blue wheel then prevents access for about 40-50 seconds. After that, everything is fine.

I've had this same problem in every version since MC11, but it is much worse in MC20. The same problem is there on my laptop and my desktop. The desktop is an i7 (2.8ghz) with 8GB ram. No other programs run slowly.

I'm using Windows 7. During those first 3-4 seconds, the program functions as normal (e.g. I can start it playing music). During the 40-50 seconds, any music that is playing will continue to play. However, I won't have access to any other controls (so I can't stop music or close MC or do anything else).

I don't use any plugins. My music library is about 27000 files.

[glynor]

Please read:
http://wiki.jriver.com/index.php/Troubleshooting_Guide

Many of the tips included in that guide are for solving problems exactly like that one.  This is commonly caused by Anti-Virus interference or using MC with a slow or network disk.  There are solutions to both issues addressed in the guide.

[iEditor]

Thanks for your message and quick reply.

So in the FAQ-speak, the problem I have is 'hanging'. But I haven't been able to solve that:
- I'm not using a network drive.
- There is no sign of any disk or OS corruption.
- My anti-virus is very lightweight, but I've uninstalled that anyway. The problem is still there.
- Sound and video quality are both fine. It's just the initial hang after startup.

Attached is the log file.

[JimH]

A hang at startup may be a Windows device that is no longer present.  Disconnect anything you can.

[iEditor]

Thanks. I disconnected my phone (Samsung N4 Mini) with MC running. And it hung then.

I restarted without the phone connected or the USB hub in the monitor connected. However, there isn't anything else to disconnect (just mouse/keyboard). The problem is still there.

[glynor]

A hang at startup may be a Windows device that is no longer present.  Disconnect anything you can.

Yes, and your logs show evidence of this.

Code: [Select]

0004228: 4228: Handheld: CHHManagerMap::Init: Start
0004228: 4228: Handheld: CHHManagerMap::LoadDevices: Start
0004228: 4228: Handheld: CHHManagerMap::LoadDevices: Number of stored devices: 20
0004228: 4228: Handheld: CHHManagerMap::LoadDevices: Creating manager for: $$?$usb#vid_04e8&pid_6860&mi_00#7&1605539e&0&0000#{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Start
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Finish (0 ms)
0004228: 4228: Handheld: CHHManagerMap::LoadDevices: Creating manager for: $$?$usb#vid_04e8&pid_6860&mi_00#7&1605539e&0&0000#{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$1
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Start
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Finish (0 ms)
0004228: 4228: Handheld: CHHManagerMap::LoadDevices: Creating manager for: $$?$wpdbusenumroot#umb#2&37c186b&0&storage#volume#_??_usbstor#disk&ven_apple&prod_ipod&rev_1.62#000a2700130ca25e&0##{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Start
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Finish (0 ms)
0004228: 4228: Handheld: CHHManagerMap::LoadDevices: Creating manager for: $$?$wpdbusenumroot#umb#2&37c186b&0&storage#volume#_??_usbstor#disk&ven_apple&prod_ipod&rev_1.62#000a27001350240b&0##{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Start
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Finish (0 ms)
0004228: 4228: Handheld: CHHManagerMap::LoadDevices: Creating manager for: $$?$wpdbusenumroot#umb#2&37c186b&0&storage#volume#_??_usbstor#disk&ven_generic&prod_flash_disk&rev_8.07#o8osdatj&0##{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Start
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Finish (0 ms)
0004228: 4228: Handheld: CHHManagerMap::LoadDevices: Creating manager for: $$?$wpdbusenumroot#umb#2&37c186b&0&storage#volume#_??_usbstor#disk&ven_google_&prod_inc.nexus_one&rev_#ht9cpp805583&0##{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Start
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Finish (0 ms)
0004228: 4228: Handheld: CHHManagerMap::LoadDevices: Creating manager for: $$?$wpdbusenumroot#umb#2&37c186b&0&storage#volume#_??_usbstor#disk&ven_intenso&prod_3in1_line&rev_#12062400000148&0##{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Start
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Finish (0 ms)
0004228: 4228: Handheld: CHHManagerMap::LoadDevices: Creating manager for: $$?$wpdbusenumroot#umb#2&37c186b&0&storage#volume#_??_usbstor#disk&ven_jetflash&prod_transcend_4gb&rev_8.07#s7hvdx59&0##{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Start
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Finish (0 ms)
0004228: 4228: Handheld: CHHManagerMap::LoadDevices: Creating manager for: $$?$wpdbusenumroot#umb#2&37c186b&0&storage#volume#_??_usbstor#disk&ven_jetflash&prod_transcend_4gb&rev_8.07#txwvo5w3&0##{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Start
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Finish (0 ms)
0004228: 4228: Handheld: CHHManagerMap::LoadDevices: Creating manager for: $$?$wpdbusenumroot#umb#2&37c186b&0&storage#volume#_??_usbstor#disk&ven_kindle&prod_internal_storage&rev_0100#b00aa0a00527089f&0##{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Start
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Finish (0 ms)
0004228: 4228: Handheld: CHHManagerMap::LoadDevices: Creating manager for: $$?$wpdbusenumroot#umb#2&37c186b&0&storage#volume#_??_usbstor#disk&ven_kindle&prod_internal_storage&rev_0100#b0241603302300xt&0##{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Start
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Finish (0 ms)
0004228: 4228: Handheld: CHHManagerMap::LoadDevices: Creating manager for: $$?$wpdbusenumroot#umb#2&37c186b&0&storage#volume#_??_usbstor#disk&ven_lg&prod_usb_drive&rev_2.00#44c44343829c001c&0##{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Start
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Finish (0 ms)
0004228: 4228: Handheld: CHHManagerMap::LoadDevices: Creating manager for: $$?$wpdbusenumroot#umb#2&37c186b&0&storage#volume#_??_usbstor#disk&ven_mainic&prod_flash_disk&rev_1.a0#2012102721493615&0##{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Start
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Finish (0 ms)
0004228: 4228: Handheld: CHHManagerMap::LoadDevices: Creating manager for: $$?$wpdbusenumroot#umb#2&37c186b&0&storage#volume#_??_usbstor#disk&ven_mainic&prod_flash_disk&rev_1.a0#2012103114550023&0##{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Start
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Finish (0 ms)
0004228: 4228: Handheld: CHHManagerMap::LoadDevices: Creating manager for: $$?$wpdbusenumroot#umb#2&37c186b&0&storage#volume#_??_usbstor#disk&ven_nokia&prod_s60&rev_1.0#354225030417500&0##{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Start
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Finish (0 ms)
0004228: 4228: Handheld: CHHManagerMap::LoadDevices: Creating manager for: $$?$wpdbusenumroot#umb#2&37c186b&0&storage#volume#_??_usbstor#disk&ven_olympus&prod_ud800_s800&rev_1.00#a44506203&0##{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Start
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Finish (0 ms)
0004228: 4228: Handheld: CHHManagerMap::LoadDevices: Creating manager for: {1EB6E6D4-9B64-43EB-87C2-514C7875C920}
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Start
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Finish (0 ms)
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Start
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Finish (0 ms)
0004228: 4228: Handheld: CHHManagerMap::LoadDevices: Creating manager for: {67C2626B-57C6-4FA3-A9D4-CCA5E27F9486}
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Start
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Finish (0 ms)
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Start
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Finish (0 ms)
0004228: 4228: Handheld: CHHManagerMap::LoadDevices: Creating manager for: {A65EADD4-A176-45F5-9BF9-F3C8AA0064E7}
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Start
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Finish (0 ms)
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Start
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Finish (0 ms)
0004228: 4228: Handheld: CHHManagerMap::LoadDevices: Creating manager for: {EDE1FB95-893E-43F2-B871-84EB716539F3}
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Start
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Finish (0 ms)
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Start
0004228: 4228: Handheld: CHHManager::UpdatePluginDeviceInfo: Finish (0 ms)
0004228: 4228: Handheld: CHHManagerMap::LoadDevices: Finish (0 ms)
0004228: 4228: Handheld: CHHManagerMap::Init: Finish (0 ms)
0004228: 4228: General: CLoaderThread::PerformAction: Waiting... (0 ms)
0004228: 4228: General: CLoaderThread::PerformAction: Finish (0 ms)
Right at the top:
0004228: 4228: Handheld: CHHManagerMap::LoadDevices: Number of stored devices: 20

Twenty handheld devices must be enumerated and detected?  Holy schnikes! Overall the entire Handheld startup process is shown in the most recent log as:

0008081: 5716: Handheld: CWMDMThread::Thread: Finish (3853 ms)

That's almost 4 full seconds, just to enumerate and load the various handhelds.

That process I quoted from the log is only the start of what it must do to enumerate and load each of those devices.  It looks like there are entries for all sorts of things.  It does also look like you have a variety of USB-connected "camera card" reading devices (probably one of those multi-format readers).  I've personally encountered many of these that were just plain badly behaved.  This could be one of the biggest "handheld" delay culprits on your system.

You may want to try:

* Disconnecting any devices MC treats as handhelds and launch MC cleanly to see if behavior improves.  If so, reconnect them one at a time and check for particularly troublesome devices.

* Telling MC to forget some of those 20 devices that may all be old "orphans".  If you can't figure out how, ask, and I can explain a few different ways to nuke them.

If that doesn't help, or only helps a bit, then there are other possibilities...

Neither log file you provided shows any file playback, so I can't check to see where your media files are stored.  You said they weren't on a network disk, so that's one potential source of slowdowns, but where are they stored?  I'm assuming it is on this disk:
* ST31000528AS ATA Device

That is a 7200rpm disk, so isn't a slouch by spinning disk standards.  However, if you are using a USB disk or something (or that particular model has poor access time performance), then basically all of the same stuff that is discussed in this guide applies.  Your Library is on C, so you're set there, but does deselecting the other option discussed in the article have any impact?

One other thing that can cause it is spinning up sleeping disks.  When Windows provides access to a disk that has been parked (a spinning disk that is sleeping) there is substantial latency as the disk gets up to speed, unparks the head, and gets it into position.  If you have multiple "media disks" the problem will be aggravated because Windows will have to spin them all up (and does so in a staggered pattern, typically).  All this time, there is very little that MC can do but be frozen if the UI elements on screen depend on the disk.

If this is the cause, you may be able to mitigate this by setting your media volumes to not sleep.  This will cost a bit of power in some circumstances, but actually may increase the longevity of your drives (because spinning up from parked is hard on the bearings, once they're running, they're usually quite safe as long as they aren't jostled).  And, it is worth noting, the power savings will really depend on the frequency with which you wake the disks.

[rec head]

Are your HDDs sleeping and spinning back up?

[Arindelle]

I also found these drives missing and podcast updates (from the missing drives??) ....

Code: [Select]

0047752: 4228: General: CFileSystemManager::AnalyzeDrive: Error using connection '\\ULTRABOOK\My Music': 53
0047752: 4228: General: CFileSystemManager::AnalyzeDrive: Drive does not exist (drive: \\ULTRABOOK\My Music, filename: \\ULTRABOOK\My Music\, type: 0, attributes: 0)
0047752: 4228: Handheld: CHHManager::InitializeProxyDevice: Finish (39016 ms)
0047752: 4228: Handheld: CHHManager::InitializeProxyDevice: Start
0059046: 4228: General: CFileSystemManager::AnalyzeDrive: Error using connection '\\OFFICECOMPUTER\Movies': 53
0059046: 4228: General: CFileSystemManager::AnalyzeDrive: Drive does not exist (drive: \\OFFICECOMPUTER\Movies, filename: \\OFFICECOMPUTER\Movies\, type: 0, attributes: 0)
0059046: 4228: Handheld: CHHManager::InitializeProxyDevice: Finish (11294 ms)
0059046: 4228: Handheld: CHHManager::InitializeProxyDevice: Start
0059046: 4228: Handheld: CHHManager::InitializeProxyDevice: Finish (0 ms)
0059046: 4228: Handheld: CHHManager::InitializeProxyDevice: Start
0070356: 4228: General: CFileSystemManager::AnalyzeDrive: Error using connection '\\N510\Music': 53
0070356: 4228: General: CFileSystemManager::AnalyzeDrive: Drive does not exist (drive: \\N510\Music, filename: \\N510\Music\, type: 0, attributes: 0)
0070356: 4228: Handheld: CHHManager::In

[glynor]

Good eye Arindelle.

It is almost certainly those.  Look at those times!

\\ULTRABOOK\My Music - 40 seconds
\\OFFICECOMPUTER\Movies - 12 seconds

And so on and so forth.  That's all the Handheld system initializing filesystem locations which don't actually exist and so can't be used.  These are probably locations you set set up manually as Handhelds at one point, and stopped using, but which MC is still loading (or trying, and failing because they don't exist).  They're shown with the GUIDs in the portion of the log I posted above.  It looks like there are four of them total.

[iEditor]

This is amazing help! Thank you so much.

There are lots of good suggestions in your mail, and I haven't figured out which is the one cause yet. However, I want to start with the orphaned devices. I can see from the logs that those 20 devices are pretty much every thing I have ever connected to the computer (perhaps even to my old computers that also used MC). I tried searching the forum, but I couldn't find out how to get rid of those. Would you mind suggesting ways to nuke them? Or perhaps you could point me to a relevant post?

It also might be one of the other things you suggested (especially the card reader). But those orphaned devices would make a lot of sense, so I'd really like to start with that suggestion.

[glynor]

Check under Drives & Devices in the Tree.  Select any offending items and right-click > Remove and Ignore Device.

If that doesn't work, we can nuke them with the registry editor if needed.

[iEditor]

Amazing! You got this totally right!

None of the devices were in the tree. But I went to the registry. There were no extra devices under MC20. However, all of the old devices that I ever installed for MC18 and MC16 were still there under those registry entries. I deleted both of those registry keys completely, and now the loadup is instant.

Thank you so much!

[Arindelle]

good stuff glad it worked out

[glynor]

There were no extra devices under MC20. However, all of the old devices that I ever installed for MC18 and MC16 were still there under those registry entries. I deleted both of those registry keys completely, and now the loadup is instant.

Interesting.

That points to a subtle bug in MC20 (and almost certainly earlier versions as well).  What I'm guessing was happening is that MC20's "settings upgrade" system was running each time it launched and trying to import those old settings.  Since the settings pointed to locations that didn't exist, the "settings import" was failing, and so the settings in question never actually got imported.  But, it just kept trying over and over with each new launch.

Again, I'm guessing, but that would certainly seem to be the case.  Assuming I'm right, they need to ensure that this process only happens once, and then stops, failed or not.

[iEditor]

I think that's right. It seems as if the correct device settings weren't brought across, so I kept adding new ones with each new release. That would explain why it got slower with each new release instead of faster. And it would also explain why I had the same problem on my laptop.

It wouldn't have been an issue if I had uninstalled the previous versions. But I always upgraded really carefully, leaving both versions on the machine (then forgetting about the old one).

[iEditor]

The problem is back.

I added a device (my laptop which connects via a home network). And now JRiver is slow every time it launches.

It's easy to see what's causing it - it's trying to reach the network every time I launch JRiver. Is there a way to make it only look for devices if I click the 'Drives and Devices' option?

[iEditor]

Did anyone have any ideas on this? Is there a way to stop media center from checking for a network device every time it loads?

[CountryBumkin]

But why is that slowing you down so much?

Is there something strange about your network setup? Is your slowdown happening even when the laptop is connected and running (on the network and available), or just when its missing and MC is spending time looking for it?

I have multiple iPhones, three client machines, and a laptop that connects to JRiver, but when they are not available or turned off, I don't see any delays in MC's start up time.

[iEditor]

Maybe I shouldn't be guessing as to what is causing this!

This was my thought process: Every computer that I've ever seen takes time to figure out what is on the network and what is not. So my assumption (and it could be wrong) is that once I added a device with a network location, Media Center is scanning to look for all network connected devices every time that it opens.

But if we just stick to facts:
1. When we removed all devices via the registry, the problem was fixed.
2. When I added a laptop with a network location, the problem came back.
3. The problem is there whether or not the laptop is connected.

As I say, my guess is that it's scanning for all network devices. But that's just a guess. Any suggestions or any other ideas based on just the facts?

[Arindelle]

Have you tried cleaning up your network shares and especially the drive mappings like Glynor and I referred to before. Maybe you have a similar problem where its is not a "device" per se but a drive that is not connecting. (see the code from your log I posted above)

 See if any network drives or UNC paths are not connected to the network before launching JRiver. By the way, under network options, Client , is "play local file if available ..." checked?

Also check on your clients to see if you have media server running on them too. If so, that can cause issues. Most of the time you do not want to be running multiple instances of media server.