HID mode instability on one deck

[superdj4life]

First off FREAKING AWESOME! being able to plug in two cables and get to mixing without any hassle, great job guys.

I am having some issues with one of my decks though. Deck B always loses communication with the laptop, the light up circle on the CDJ jog wheel will flash repeatedly like it would at the end of a track but no data will be displayed on the display. I've noticed you can still select and load tracks even activate loops, but it will not show any updated information on the deck B only the Cross GUI shows whats going on. after a few tracks the software crashed on me and needed to be restarted.

I think it's the CDJ-2000 since the deck A has been 100% everytime I've used it. does anyone know if resetting the CDJ to factory defaults of updating the firmware on the player will help?

I'm using a pair of limited edition white CDJ-2000 but thought other than paint and price they we're the same as the black CDJ-2000 the drivers we're direct from the Pioneer site though i do have ASIO4all installed for my soundcard, and the Numark ASIO driver for a controller I use I didn't think they would cause any conflict.

[superdj4life]

anybody??? sorry to bump

[Jim B]

I would start at the Pioneer site, and see if you have the latest firmware installed.

If not download and install the latest version, then go from there

[Support@MixVibes]

The issue is on the hardware for me. If you change usb port I'm sure the issue will move too...

[superdj4life]

thanks I'm looking into the firmware now, changing what port I plugged into didn't change the behavior, the right player or player B still acted up. I'm also going to make sure they have the same version of FW installed as the Pioneer websites says that can cause issues as well. Eitherway,I doubt it's Cross, but wanted to check with the gurus first. Thanks again for all your hardwork, been a satisfied user since '07 and don't plan on changing that anytime soon

[superdj4life]

Another weekend and another crash in HID mode, I switched to timecode and no issues the rest of the night.

before connecting anything I verified they are both running the same firmware version 4.10 and I reset both units to factory defaults. here's the error report from windows if it helps

Code: Select all

Version=1
EventType=APPCRASH
EventTime=130133454423292669
ReportType=2
Consent=1
UploadTime=130134065972852826
ReportIdentifier=31da2744-bfa3-11e2-be7b-f07bcba79fbb
IntegratorReportIdentifier=31da2743-bfa3-11e2-be7b-f07bcba79fbb
WOW64=1
NsAppName=Cross.exe
Response.BucketId=6def49473ff0550fba9959e5f8d1983f
Response.BucketTable=1
Response.LegacyBucketId=-750042391
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=Cross.exe
Sig[1].Name=Application Version
Sig[1].Value=2.4.0.0
Sig[2].Name=Application Timestamp
Sig[2].Value=516ea56d
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_6b03
Sig[4].Name=Fault Module Version
Sig[4].Value=6.2.9200.16420
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=505aaa82
Sig[6].Name=Exception Code
Sig[6].Value=c0000374
Sig[7].Name=Exception Offset
Sig[7].Value=PCH_8A_FROM_ntdll+0x00040DA8
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.2.9200.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=6b03
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=6b0329b6c32f3f054b41509c1781f389
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=f4d5
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=f4d5f9c3458b028ead2df4f7473f405e
UI[2]=C:\Program Files (x86)\MixVibes\Cross 2.4.0\Cross.exe
UI[3]=Cross.exe has stopped working
UI[4]=Windows can check online for a solution to the problem the next time you go online.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files (x86)\MixVibes\Cross 2.4.0\Cross.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\SYSTEM32\KERNEL32.DLL
LoadedModule[3]=C:\Windows\SYSTEM32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\SYSTEM32\WINMM.dll
LoadedModule[5]=C:\Program Files (x86)\MixVibes\Cross 2.4.0\MVU46MK2.dll
LoadedModule[6]=C:\Windows\SYSTEM32\HID.DLL
LoadedModule[7]=C:\Windows\SYSTEM32\WS2_32.dll
LoadedModule[8]=C:\Windows\SYSTEM32\WININET.dll
LoadedModule[9]=C:\Windows\SYSTEM32\SETUPAPI.dll
LoadedModule[10]=C:\Windows\SYSTEM32\SHLWAPI.dll
LoadedModule[11]=C:\Windows\SYSTEM32\IMM32.dll
LoadedModule[12]=C:\Windows\SYSTEM32\USER32.dll
LoadedModule[13]=C:\Windows\SYSTEM32\GDI32.dll
LoadedModule[14]=C:\Windows\SYSTEM32\SHELL32.dll
LoadedModule[15]=C:\Windows\SYSTEM32\ole32.dll
LoadedModule[16]=C:\Windows\SYSTEM32\OLEAUT32.dll
LoadedModule[17]=C:\Windows\SYSTEM32\COMDLG32.dll
LoadedModule[18]=C:\Windows\SYSTEM32\ADVAPI32.dll
LoadedModule[19]=C:\Windows\SYSTEM32\WINMMBASE.dll
LoadedModule[20]=C:\Windows\SYSTEM32\msvcrt.dll
LoadedModule[21]=C:\Windows\SYSTEM32\RPCRT4.dll
LoadedModule[22]=C:\Windows\SYSTEM32\NSI.dll
LoadedModule[23]=C:\Windows\SYSTEM32\iertutil.dll
LoadedModule[24]=C:\Windows\SYSTEM32\CFGMGR32.dll
LoadedModule[25]=C:\Windows\SYSTEM32\DEVOBJ.dll
LoadedModule[26]=C:\Windows\SYSTEM32\MSCTF.dll
LoadedModule[27]=C:\Windows\SYSTEM32\combase.dll
LoadedModule[28]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[29]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.9200.16384_none_bf100cd445f4d954\COMCTL32.dll
LoadedModule[30]=C:\Windows\SYSTEM32\SspiCli.dll
LoadedModule[31]=C:\Windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[32]=C:\Windows\SYSTEM32\SHCORE.DLL
LoadedModule[33]=C:\Windows\SYSTEM32\bcryptPrimitives.dll
LoadedModule[34]=C:\Windows\SYSTEM32\profapi.dll
LoadedModule[35]=C:\Windows\system32\uxtheme.dll
LoadedModule[36]=C:\Windows\SYSTEM32\dwmapi.dll
LoadedModule[37]=C:\Windows\SYSTEM32\clbcatq.dll
LoadedModule[38]=C:\Windows\system32\propsys.dll
LoadedModule[39]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9200.16384_none_893961408605e985\comctl32.dll
LoadedModule[40]=C:\Windows\SYSTEM32\WindowsCodecs.dll
LoadedModule[41]=C:\Windows\SYSTEM32\thumbcache.dll
LoadedModule[42]=C:\Windows\SYSTEM32\mscms.dll
LoadedModule[43]=C:\Windows\SYSTEM32\USERENV.dll
LoadedModule[44]=C:\Windows\SYSTEM32\WINTRUST.dll
LoadedModule[45]=C:\Windows\SYSTEM32\CRYPT32.dll
LoadedModule[46]=C:\Windows\SYSTEM32\MSASN1.dll
LoadedModule[47]=C:\Windows\System32\MMDevApi.dll
LoadedModule[48]=C:\Windows\SYSTEM32\dsound.dll
LoadedModule[49]=C:\Windows\SYSTEM32\POWRPROF.dll
LoadedModule[50]=C:\Windows\SYSTEM32\wdmaud.drv
LoadedModule[51]=C:\Windows\SYSTEM32\ksuser.dll
LoadedModule[52]=C:\Windows\SYSTEM32\AVRT.dll
LoadedModule[53]=C:\Windows\SYSTEM32\AUDIOSES.DLL
LoadedModule[54]=C:\Windows\SYSTEM32\msacm32.drv
LoadedModule[55]=C:\Windows\SYSTEM32\MSACM32.dll
LoadedModule[56]=C:\Windows\SYSTEM32\midimap.dll
LoadedModule[57]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[58]=C:\Windows\SYSTEM32\wbemcomn.dll
LoadedModule[59]=C:\Windows\SYSTEM32\CRYPTSP.dll
LoadedModule[60]=C:\Windows\system32\rsaenh.dll
LoadedModule[61]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[62]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[63]=c:\windows\usb-audio.denumarknc06\nc06asio_x86.dll
LoadedModule[64]=C:\Windows\SYSTEM32\VERSION.dll
LoadedModule[65]=C:\Windows\SYSTEM32\Secur32.dll
LoadedModule[66]=C:\Windows\SYSTEM32\winhttp.dll
LoadedModule[67]=C:\Windows\system32\mswsock.dll
LoadedModule[68]=C:\Windows\SYSTEM32\IPHLPAPI.DLL
LoadedModule[69]=C:\Windows\SYSTEM32\WINNSI.DLL
LoadedModule[70]=C:\Windows\SYSTEM32\dhcpcsvc6.DLL
LoadedModule[71]=C:\Windows\SYSTEM32\dhcpcsvc.DLL
LoadedModule[72]=C:\Windows\SYSTEM32\DNSAPI.dll
LoadedModule[73]=C:\Program Files (x86)\Bonjour\mdnsNSP.dll
LoadedModule[74]=C:\Windows\SYSTEM32\wlidNSP.dll
LoadedModule[75]=C:\Windows\System32\rasadhlp.dll
LoadedModule[76]=C:\Windows\SYSTEM32\urlmon.dll
LoadedModule[77]=c:\windows\usb-audio.denumark_idj3\nkidj3asio_x86.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Cross.exe
AppPath=C:\Program Files (x86)\MixVibes\Cross 2.4.0\Cross.exe
NsPartner=windows
NsGroup=windows8

[Support@MixVibes]

I'm still concerned about the usb issue.

Let me explain my view :
- the Pioneer asio driver is agregating both devices into a virtual one
- if one of them is missing, the whole is broken
- modifying the same soundcard while using it, will always be an issue

I'm still sticking to the fact that you have a usb stream that get broken at a point. So may be change your usb cable or check for plugs on the deck side (I know they are prone to break due to the missing central plastic pin on the usb type B side).

[cas41532]

I use cdj 2000 so hid with the Cross, and I have no problem.
my firmware version 4.10.

The only thing that is not working as it should is the function secutity mode

[sylMV]

The only thing that is not working as it should is the function secutity mode

You mean the fact there's no security when loading via the CDJ-2000?
If I remember well, that was on purpose to follow the native CDJ-2000 behavior.

[superdj4life]

thanks sly,

Let me explain my view :
- the Pioneer asio driver is agregating both devices into a virtual one
- if one of them is missing, the whole is broken
- modifying the same soundcard while using it, will always be an issue

I've tried different cables before I reported the issues, I was hoping it was something simple like that.

the Pioneer driver on my computer had already been re installed and always shows up correctly in the Cross config screens

I'm not sure I follow what you meant by modifying the same soundcard. once everything is plugged I don't touch it until it crashes. After that I reset both decks before restarting Cross, so again they should be in sync communication wise.