INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: jbholtz: MC 11.1 iRiver device issue  (Read 1462 times)

jbholtz

  • Recent member
  • *
  • Posts: 49
jbholtz: MC 11.1 iRiver device issue
« on: February 04, 2006, 11:05:27 am »

When I plug in my IRiver-795 or iRiver-395T MediaCenter just hangs!.  I've tried redetecting the device (which removes everything in Media Center) and then plug in the iRiver but no dice.
Logged

Matt

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 42373
  • Shoes gone again!
Re: jbholtz: MC 11.1 iRiver device issue
« Reply #1 on: February 04, 2006, 11:38:51 am »

Could you post a full log after the hang? (Help > Configure Debug Logging...)

Some of the iRiver device drivers don't deal well with threading.  I thought we had the issue side-stepped, but apparently not in all cases.

Thanks for helping.
Logged
Matt Ashland, JRiver Media Center

jbholtz

  • Recent member
  • *
  • Posts: 49
Re: jbholtz: MC 11.1 iRiver device issue
« Reply #2 on: February 04, 2006, 02:45:15 pm »

Here's what I got.  Started MC and reset the log and then pluged in my iRiver 795.  Hang and then I looked at the log:

0000000: General: Starting logging: Date: 2/4/2006 3:40:13 PM
0000000: General: Log Reset: Logging reset
0051625: Database: MCDB::Save: Start
0051625: Database: MCDB::Save: Saving (bCleanDB: 0, bForce: 0)
0051625: Database: MCDB::Save: Finish (0 ms)
0051875: General: CPodcastMain::Update: Start
0051875: General: CPodcastMain::Update: Finish (0 ms)
0057235: Handheld: CWMDMNotificationHandler::_HandleDeviceArrival: Start
0057235: Handheld: CWMDMNotificationHandler::_HandleDeviceArrival: \\?\USB#Vid_4102&Pid_1007#5&1bbb32c1&0&1#{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0
0057235: Handheld: CWMDMNotificationHandler::_HandleDeviceArrival: Finish (0 ms)
0057500: Handheld: CWMDMThread::EnumerateDevices: Start
0057500: Handheld: CWMDMThread::EnumerateDevices: Starting enumeration
0057500: Handheld: CWMDMThread::EnumerateDevices: Found device (pointer: 2242500)
0057500: Handheld: CWMDMThread::EnumerateDevices: Gathering device information
0057500: Handheld: CWMDMThread::EnumerateDevices: DeviceInfo: (iRiver IFP-795T, $$?$usb#vid_4102&pid_1007#5&1bbb32c1&0&1#{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0, 0, 0, ) = 0
0057500: Handheld: CWMDMHelper::CheckForJanusCapable: Start
0057500: Handheld: CWMDMHelper::CheckForJanusCapable: CoCreateInstance(CLSID_WMDRMDeviceApp returns hr=0x0
0057500: Handheld: CWMDMHelper::CheckForJanusCapable: Querying for device status
0057922: Handheld: CWMDMHelper::CheckForJanusCapable: Returning Janus: 0
0057922: Handheld: CWMDMHelper::CheckForJanusCapable: Finish (422 ms)
0057922: Handheld: CWMDMThread::EnumerateDevices: Finish (422 ms)
0057922: Handheld: CWMDMThread::ProcessMainThreadMessage: Start
0057938: Handheld: CWMDMThread::ProcessMainThreadMessage: Done enumerating
0057938: Handheld: CHHManagerMap::EnumDevices: Start
0057938: Handheld: CHHManagerMap::EnumWMDMDevices: Start
0057938: Handheld: CHHManagerMap::EnumWMDMDevices: Getting / creating handheld manager
0057938: Handheld: CHHManagerMap::EnumWMDMDevices: Updating device
0057938: Handheld: CHHManager::UpdateWMDMDevice: Start
0057938: Handheld: CHHManager::UpdateWMDMDevice: PDTName: ''; DisplayName: 'iRiver IFP-795T'
0057938: Handheld: CHHManager::UpdateWMDMDevice: Loading PDTInfo: ''
0057938: Handheld: CHHManager::UpdateWMDMDevice: Finish (0 ms)
0057938: Handheld: CHHManagerMap::EnumWMDMDevices: Finish (0 ms)
0057938: Handheld: CHHManager::Initialize: Start
0057938: Handheld: CHHManager::InitializePlugin: Start
0057938: Handheld: CHHManager::InitializePlugin: PluginName: 'Portable Drives'
0057938: Handheld: CHHManager::InitializePlugin: Creating plugin...
0057969: Handheld: CHHManager::InitializePlugin: Valid plugin created
0057969: Handheld: CHHManager::EnableEvents: Start
0057969: Handheld: CHHManager::EnableEvents: Finish (0 ms)
0057969: SDK: CMJAutomation::CMJAutomation: Global Count: 4, Main 0, 551c848
0057969: Handheld: CHHPluginThread::ProcessCommand: Start
0057969: Handheld: CHHPluginThread::Thread Message Processing: Start
0057969: Handheld: CHHPluginThread::Thread Message Processing: Type: 0, Function: 2
0057969: Handheld: CHHPluginThread::Thread Message Processing: Finish (0 ms)
0058032: Handheld: CHHPluginThread::ProcessCommand: Finish (63 ms)
The above CHHPluginThread happens alot (~15 times) then:
0058032: Handheld: CHHManager::SetPaths: Finish (0 ms)
0058032: Handheld: CHHManager::InitializePlugin: Initializing plugin...
0058032: Handheld: CHHPluginThread::Initialize: Start
0058032: Handheld: CHHPluginThread::Thread Message Processing: Start
0058032: Handheld: CHHPluginThread::Thread Message Processing: Type: 0, Function: 0
0058032: Handheld: CPortableDriveWMDM::Initialize: Start
0058032: Handheld: CPortableDriveWMDM::Initialize: Initializing device: $$?$usb#vid_4102&pid_1007#5&1bbb32c1&0&1#{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0
0058047: Handheld: CWMDMSupport::Init: Start
0058047: Handheld: CWMDMInterface::CWMDMInterface: Start
0058047: Handheld: CWMDMInterface::CWMDMInterface: Creating secure channel client
0058047: Handheld: CWMDMInterface::CWMDMInterface: Updating certificate
0058047: Handheld: CWMDMInterface::CWMDMInterface: Updating channel
0058047: Handheld: CWMDMInterface::CWMDMInterface: Authenticating
0058063: Handheld: CWMDMInterface::CWMDMInterface: Getting device manager
0058063: Handheld: CWMDMInterface::CWMDMInterface: WMDM valid: 1
0058063: Handheld: CWMDMInterface::CWMDMInterface: Finish (16 ms)
0058063: Handheld: CWMDMSupport::Init: Finish (16 ms)
0058063: Handheld: CPortableDriveWMDM::Initialize: Initialize return value: 0 (hr)
0058063: Handheld: CPortableDriveWMDM::Initialize: Setting device
0058063: Handheld: CWMDMSupport::SetDevice: Start
0058063: Handheld: CWMDMSupport::SetDevice: Setting to device: $$?$usb#vid_4102&pid_1007#5&1bbb32c1&0&1#{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae}$0
0058063: Handheld: CWMDMSupport::SetDevice: Enumeration devices...
Logged

Matt

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 42373
  • Shoes gone again!
Re: jbholtz: MC 11.1 iRiver device issue
« Reply #3 on: February 04, 2006, 03:01:29 pm »

I think you just need to add an entry to the PDT.

Try editing MC\Data\Default Resources\PDT.xml

Find this entry:
   <Device>
      <Type>0</Type>
      <Vendor>iRiver</Vendor>
      <Name>iFP-780T;iRiver iFP-395T;iFP-880T;iRiver IFP-880;iRiver IFP-890T;iFP-990T</Name>
      <PlaylistBasePath>ROOT</PlaylistBasePath>
      <RootBasePath>\</RootBasePath>
      <AlwaysPumpCOMMessages>1</AlwaysPumpCOMMessages>
   </Device>

Add "iRiver IFP-795T" (and other iRiver devices you're using) to the name list.  The key is that "AlwaysPumpCOMMessages" thing.  iRiver drivers don't handle threading like they should, but this works around it.

Let us know.  If it fixes it, we'll roll the changes into the next build for everyone.

Thanks.
Logged
Matt Ashland, JRiver Media Center

jbholtz

  • Recent member
  • *
  • Posts: 49
Re: jbholtz: MC 11.1 iRiver device issue
« Reply #4 on: February 05, 2006, 11:42:39 am »

Great!! Seems to have worked.  Although the only other thing is that there is no eject for the handheld in MC.  And I cann't "safely eject" via windows because MC has a lock on it.  Is this some other alteration to the PDT.xml file?
Logged
Pages: [1]   Go Up