TREE234
hi i recently bought a mixtrack quad controller plugged it in and at first all lights come on for a second. after that only jog wheels stay lit . and no controlls work also in mapping mixtrack quad is showing as mixtrack pro controller not quad
geposted Mon 11 Jan 16 @ 4:52 pm
djdad
You havent installed any drivers, right ? No drivers are needed for the Quad, but just to be sure there is no conflict with any other Numark drivers.
Please provide us some data (see instructions below).
- Open VirtualDJ 8 and go to Settings->OPTIONS tab.
- Enable the Show Advanced Options from the top.
- Search for the setting createMidilog and set it to Yes.
- Close VirtualDJ and make sure your controller is connected and powered on.
- Open VirtualDJ 8 and close right after launch (no need to do anything else there).
- Post here the content of the Log report.txt file you will find in /Documents/VirtualDJ
thanks
Please provide us some data (see instructions below).
- Open VirtualDJ 8 and go to Settings->OPTIONS tab.
- Enable the Show Advanced Options from the top.
- Search for the setting createMidilog and set it to Yes.
- Close VirtualDJ and make sure your controller is connected and powered on.
- Open VirtualDJ 8 and close right after launch (no need to do anything else there).
- Post here the content of the Log report.txt file you will find in /Documents/VirtualDJ
thanks
geposted Mon 11 Jan 16 @ 4:58 pm
TREE234
--- 2016/01/11 - 17:42 (2770)
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
[17:55] Midi Out Closed (Microsoft GS Wavetable Synth)
[17:42] Midi In Closed (\\?\usb#vid_15e4&pid_004b&mi_00#7&376c174c&0&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global)
[17:55] Midi Out Closed (\\?\usb#vid_15e4&pid_004b&mi_00#7&376c174c&0&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global)
--- 2016/01/11 - 17:42 (2770)
Audio device found: name="MixTrack Pro II" vid="0x15E4" pid="0x004B" hardwareID:"{0.0.0.00000000}.{0fc852d9-65d0-4d91-8563-5129d71582f6}"
Audio device found: name="Realtek High Definition Audio" vid="0x10EC" pid="0x0282" hardwareID:"{0.0.0.00000000}.{48e8d1d8-948c-4037-8d05-3afbd9764bdd}"
Audio device found: input name="Realtek High Definition Audio" vid="0x10EC" pid="0x0282" hardwareID:"{0.0.1.00000000}.{46ab2355-3697-4caf-929b-03d113eba196}"
Audio device found: asio="ASIO4ALL v2" hardwareID:"232685C6-6548-49D8-846D4141A3EF7560"
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
MIDI Device Identifying: \\?\usb#vid_15e4&pid_004b&mi_00#7&376c174c&0&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global (in:0 out:1)
MIDI Device Identified by PID/VID: \\?\usb#vid_15e4&pid_004b&mi_00#7&376c174c&0&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global : Numark MixTrack PRO II
MIDI Device Identifying: Microsoft GS Wavetable Synth (in:-1 out:0)
[17:10] Midi Out Closed (Microsoft GS Wavetable Synth)
MIDI Device Not Identified: Microsoft GS Wavetable Synth
[17:43] Midi In Closed (\\?\usb#vid_15e4&pid_004b&mi_00#7&376c174c&0&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global)
[17:12] Midi Out Closed (\\?\usb#vid_15e4&pid_004b&mi_00#7&376c174c&0&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global)
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
[17:55] Midi Out Closed (Microsoft GS Wavetable Synth)
[17:42] Midi In Closed (\\?\usb#vid_15e4&pid_004b&mi_00#7&376c174c&0&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global)
[17:55] Midi Out Closed (\\?\usb#vid_15e4&pid_004b&mi_00#7&376c174c&0&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global)
--- 2016/01/11 - 17:42 (2770)
Audio device found: name="MixTrack Pro II" vid="0x15E4" pid="0x004B" hardwareID:"{0.0.0.00000000}.{0fc852d9-65d0-4d91-8563-5129d71582f6}"
Audio device found: name="Realtek High Definition Audio" vid="0x10EC" pid="0x0282" hardwareID:"{0.0.0.00000000}.{48e8d1d8-948c-4037-8d05-3afbd9764bdd}"
Audio device found: input name="Realtek High Definition Audio" vid="0x10EC" pid="0x0282" hardwareID:"{0.0.1.00000000}.{46ab2355-3697-4caf-929b-03d113eba196}"
Audio device found: asio="ASIO4ALL v2" hardwareID:"232685C6-6548-49D8-846D4141A3EF7560"
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
MIDI Device Identifying: \\?\usb#vid_15e4&pid_004b&mi_00#7&376c174c&0&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global (in:0 out:1)
MIDI Device Identified by PID/VID: \\?\usb#vid_15e4&pid_004b&mi_00#7&376c174c&0&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global : Numark MixTrack PRO II
MIDI Device Identifying: Microsoft GS Wavetable Synth (in:-1 out:0)
[17:10] Midi Out Closed (Microsoft GS Wavetable Synth)
MIDI Device Not Identified: Microsoft GS Wavetable Synth
[17:43] Midi In Closed (\\?\usb#vid_15e4&pid_004b&mi_00#7&376c174c&0&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global)
[17:12] Midi Out Closed (\\?\usb#vid_15e4&pid_004b&mi_00#7&376c174c&0&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global)
geposted Mon 11 Jan 16 @ 5:44 pm
TREE234
has this helped i think my computer has renamed my controller from mixtrack quad to pro 2 as i had mixtrack pro two before this
geposted Mon 11 Jan 16 @ 10:42 pm
djdad
Your Log report says..
MIDI Device Identifying: \\?\usb#vid_15e4&pid_004b
PID 004b belongs to Mixtrack Pro II, so VirtualDJ correctly thinks that a Mixtrack Pro II is connected.
You can try a USB History cleaner such as USBOblivion (Google it)
then restart you rcomputer, plug Mixtrack Quad again and try again.
It is also recommended to uninstall ASIO4ALL (not needed), as there may be some conflict there as well.
MIDI Device Identifying: \\?\usb#vid_15e4&pid_004b
PID 004b belongs to Mixtrack Pro II, so VirtualDJ correctly thinks that a Mixtrack Pro II is connected.
You can try a USB History cleaner such as USBOblivion (Google it)
then restart you rcomputer, plug Mixtrack Quad again and try again.
It is also recommended to uninstall ASIO4ALL (not needed), as there may be some conflict there as well.
geposted Tue 12 Jan 16 @ 7:36 am
TREE234
i have uninstalled iso4all . and done the usboblivion . but still the same . i called numark and they are telling me that its because i d/l virtual dj from virtual dj site and not from numark . but i dont believe that is the reason why its not working (i could be wrong) i have an acount on vdj that allows me to use unlimited controllers so it dont sound right what they have told me
geposted Tue 12 Jan 16 @ 10:55 am
djdad
maybe because they think that you are using some LE version and not the Pro.
Just for the records and to have some proof for the Numark Support Team, open Device Manager, right-click on the Numark device (probably under Sound, video and Gam controllers folder) and choose Properties.
In the Details tab, search for Hardware ID property and take a screenshot of the provided info (it should show somewhere the PID value there)
Just for the records and to have some proof for the Numark Support Team, open Device Manager, right-click on the Numark device (probably under Sound, video and Gam controllers folder) and choose Properties.
In the Details tab, search for Hardware ID property and take a screenshot of the provided info (it should show somewhere the PID value there)
geposted Tue 12 Jan 16 @ 11:52 am
TREE234
im srry dont know how to screen shot but this is only thing that shows up USB\VID_15E4&PID_004B&REV_0104&MI_00
USB\VID_15E4&PID_004B&MI_00
USB\VID_15E4&PID_004B&MI_00
geposted Tue 12 Jan 16 @ 12:38 pm
djdad
PID_004B indicates a Mixtrack Pro II, so there is nothing you or we can do about. Email Numark and ask if there is a way to "flash" your unit with the correct firmware.
If no solution is provided from Numark, post here again. I may have a workaround but still not sure if it will work.
PS. google "screenshot" ;)
If no solution is provided from Numark, post here again. I may have a workaround but still not sure if it will work.
PS. google "screenshot" ;)
geposted Tue 12 Jan 16 @ 12:57 pm
TREE234
they told me the unit does not need to be reflashed as it should still run from mixtrack pro drivers. and that there is no way the controllers harder would of been affected
geposted Tue 12 Jan 16 @ 2:41 pm
djdad
Mixtrack Pro drivers ? lol ... there is no such thing. Tell them that the VID/PID is not defined by Windows or any drivers. Its up to the firmware. lol... anyways. I emailed you a workaround.
geposted Tue 12 Jan 16 @ 3:31 pm
TREE234
also i have tried on another laptop and this laptop has not had any dj related equipment on it . and the controller still shows as mixtrack pro to .
geposted Tue 12 Jan 16 @ 4:32 pm
TREE234
djdad you are a greatest lol. ty for all your help it seems to be working all lit up really apreciate it i owe you one lol
geposted Tue 12 Jan 16 @ 4:53 pm