thetracker510
Duh ...GOT IT!!!!!! system shut down...even without holding a button! HALELUYAH!....he,he
edit: was using wasapi drivers (what's up "P"?)....yeeez...
edit: was using wasapi drivers (what's up "P"?)....yeeez...
Mensajes Wed 03 Sep 14 @ 11:52 pm
thetracker510
dang..when I restarted the definitions apparently changed the config away from left,right again.now to Automatic 1,2 with a second map as Automatic 3,4...nonetheless I think were on to something...
edit:device dat its made again and system locks up...sorry...
edit:device dat its made again and system locks up...sorry...
Mensajes Thu 04 Sep 14 @ 12:31 am
thetracker510
new Log report...
Audio device found: name="Speakers / Headphones (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: name="Line 1/2 (M-Audio Xponent)" vid="0x0763" pid="0x2016"
Audio device found: name="Digital Audio (S/PDIF) (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: name="Line 3/4 (M-Audio Xponent)" vid="0x0763" pid="0x2016"
Audio device found: name="Communications Headphones (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: input name="Microphone Array (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: input name="Microphone (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: input name="HDMI In (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: input name="M-Audio Xponent" vid="0x0763" pid="0x2016"
Audio device found: asio="Hercules DJ Console RMX ASIO"
Audio device found: asio="M-Audio USB ASIO"
Audio device found: name="Speakers / Headphones (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: name="Line 1/2 (M-Audio Xponent)" vid="0x0763" pid="0x2016"
Audio device found: name="Digital Audio (S/PDIF) (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: name="Line 3/4 (M-Audio Xponent)" vid="0x0763" pid="0x2016"
Audio device found: name="Communications Headphones (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: input name="Microphone Array (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: input name="Microphone (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: input name="HDMI In (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: input name="M-Audio Xponent" vid="0x0763" pid="0x2016"
Audio device found: asio="Hercules DJ Console RMX ASIO"
Audio device found: asio="M-Audio USB ASIO"
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
MIDI Device Identifying: \\?\usb#vid_0763&pid_2016&mi_00#7&36cc7125&0&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\xponentmidiincontrol (in:0 out:1)
MIDI Device Identified by PID/VID: \\?\usb#vid_0763&pid_2016&mi_00#7&36cc7125&0&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\xponentmidiincontrol
MIDI Device Identifying: \\?\usb#vid_0763&pid_2016&mi_00#7&36cc7125&0&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\xponentaudioin2 (in:1 out:2)
MIDI Device Identified by PID/VID: \\?\usb#vid_0763&pid_2016&mi_00#7&36cc7125&0&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\xponentaudioin2
MIDI Device Identifying: Microsoft GS Wavetable Synth (in:-1 out:0)
MIDI Device Not Identified: Microsoft GS Wavetable Synth
Audio device found: name="Speakers / Headphones (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: name="Line 1/2 (M-Audio Xponent)" vid="0x0763" pid="0x2016"
Audio device found: name="Digital Audio (S/PDIF) (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: name="Line 3/4 (M-Audio Xponent)" vid="0x0763" pid="0x2016"
Audio device found: name="Communications Headphones (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: input name="Microphone Array (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: input name="Microphone (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: input name="HDMI In (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: input name="M-Audio Xponent" vid="0x0763" pid="0x2016"
Audio device found: asio="Hercules DJ Console RMX ASIO"
Audio device found: asio="M-Audio USB ASIO"
Audio device found: name="Speakers / Headphones (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: name="Line 1/2 (M-Audio Xponent)" vid="0x0763" pid="0x2016"
Audio device found: name="Digital Audio (S/PDIF) (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: name="Line 3/4 (M-Audio Xponent)" vid="0x0763" pid="0x2016"
Audio device found: name="Communications Headphones (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: input name="Microphone Array (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: input name="Microphone (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: input name="HDMI In (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: input name="M-Audio Xponent" vid="0x0763" pid="0x2016"
Audio device found: asio="Hercules DJ Console RMX ASIO"
Audio device found: asio="M-Audio USB ASIO"
Audio device found: name="Speakers / Headphones (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: name="Line 1/2 (M-Audio Xponent)" vid="0x0763" pid="0x2016"
Audio device found: name="Digital Audio (S/PDIF) (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: name="Line 3/4 (M-Audio Xponent)" vid="0x0763" pid="0x2016"
Audio device found: name="Communications Headphones (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: input name="Microphone Array (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: input name="Microphone (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: input name="HDMI In (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: input name="M-Audio Xponent" vid="0x0763" pid="0x2016"
Audio device found: asio="Hercules DJ Console RMX ASIO"
Audio device found: asio="M-Audio USB ASIO"
Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
MIDI Device Identifying: \\?\usb#vid_0763&pid_2016&mi_00#7&36cc7125&0&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\xponentmidiincontrol (in:0 out:1)
MIDI Device Identified by PID/VID: \\?\usb#vid_0763&pid_2016&mi_00#7&36cc7125&0&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\xponentmidiincontrol
MIDI Device Identifying: \\?\usb#vid_0763&pid_2016&mi_00#7&36cc7125&0&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\xponentaudioin2 (in:1 out:2)
MIDI Device Identified by PID/VID: \\?\usb#vid_0763&pid_2016&mi_00#7&36cc7125&0&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\xponentaudioin2
MIDI Device Identifying: Microsoft GS Wavetable Synth (in:-1 out:0)
MIDI Device Not Identified: Microsoft GS Wavetable Synth
Audio device found: name="Speakers / Headphones (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: name="Line 1/2 (M-Audio Xponent)" vid="0x0763" pid="0x2016"
Audio device found: name="Digital Audio (S/PDIF) (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: name="Line 3/4 (M-Audio Xponent)" vid="0x0763" pid="0x2016"
Audio device found: name="Communications Headphones (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: input name="Microphone Array (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: input name="Microphone (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: input name="HDMI In (IDT High Definition Audio CODEC)" vid="0x111D" pid="0x7675"
Audio device found: input name="M-Audio Xponent" vid="0x0763" pid="0x2016"
Audio device found: asio="Hercules DJ Console RMX ASIO"
Audio device found: asio="M-Audio USB ASIO"
Mensajes Thu 04 Sep 14 @ 12:55 am
thetracker510
deleted the device dat and restarted vdj,its back to left,right.now what does that tell you....that the definitions downloade are not correct.jeeez!
edit: when I delete the device dat file I get the left,right back.otherwise automatic deck 1,2 because Dj dad's mod.but what about that device dat?
edit: when I delete the device dat file I get the left,right back.otherwise automatic deck 1,2 because Dj dad's mod.but what about that device dat?
Mensajes Thu 04 Sep 14 @ 1:08 am
djdad
Ok, i found an easy way to save my time and help you at the same time ... quote my self lol..
djdad wrote :
The build number e,g, 1942.780 shows 2 different things. The 1st number (1942) indicates the software build number, with all its features, updates, fixes etc.
the 2nd number (780) indicates the controllers version and all the included mapping and definition files updates.
When a build is compiled from the Development Team it usually includes the latest controllers version (at that time) but it may also not. When you launch VirtuaLDJ 8, it does 2 things.
1. Looks for updated software builds and pops up a message asking you if you want to use it.
2. Looks for updated controllers version and automatically downloads and updates the controllers.dat file you have in Devices Folder. The new updates of this file will be applied next time you relaunch.
So in your case...
1. You dont have to get the latest software build. You can still run which ever you wish, so you dont have to agree to use the latest one if the message pops up.
2. You MUST have the latest controllers version, so DONT delete the controllers.dat from Devices folder and make sure yoru build ends at 786 or higher (actually the current one is .791)
3. Make sure you dont have any definition files in Devices folder (even though this shouldnt matter)
4. Select the factory default mapping file from CONTROLLERs tab for the Xponent.
5. Make sure the DisableBuiltInDefintion setting is set to No
the 2nd number (780) indicates the controllers version and all the included mapping and definition files updates.
When a build is compiled from the Development Team it usually includes the latest controllers version (at that time) but it may also not. When you launch VirtuaLDJ 8, it does 2 things.
1. Looks for updated software builds and pops up a message asking you if you want to use it.
2. Looks for updated controllers version and automatically downloads and updates the controllers.dat file you have in Devices Folder. The new updates of this file will be applied next time you relaunch.
So in your case...
1. You dont have to get the latest software build. You can still run which ever you wish, so you dont have to agree to use the latest one if the message pops up.
2. You MUST have the latest controllers version, so DONT delete the controllers.dat from Devices folder and make sure yoru build ends at 786 or higher (actually the current one is .791)
3. Make sure you dont have any definition files in Devices folder (even though this shouldnt matter)
4. Select the factory default mapping file from CONTROLLERs tab for the Xponent.
5. Make sure the DisableBuiltInDefintion setting is set to No
djdad wrote :
make sure you have the latest CONTROLLERS BUILD NUMBER which is currently builds ending at .791 !!!! All of the above pics shows a much earlier controllers version which of course will not solve any of your issues.
Again dont worry for the software build (the 4 first digits)..let the software running idle for a few minutes and then relaunch in order the last 3 digits to get updated.as above.
Again dont worry for the software build (the 4 first digits)..let the software running idle for a few minutes and then relaunch in order the last 3 digits to get updated.as above.
Mensajes Thu 04 Sep 14 @ 2:58 am
djdad
Btw i ve noticed that the device is detected twice as MIDI, meaning that in your screenshots, i see 2 Xponent devices. Is this because you have 2 units connected ?
If only one is connected, then we may have an issue here.
If only one is connected, then we may have an issue here.
Mensajes Thu 04 Sep 14 @ 3:06 am
thetracker510
only one dad.but when left,right is working the second xml its in fact a audio map,reads audio.hmm but thats when I used the wasapi drivers and was routing master to line 1&2 and headphones to line 3&4? I just tried various reinstalls of versions past 1872 and no go? I am in the middle of reinstalling again...
Mensajes Thu 04 Sep 14 @ 3:35 am
thetracker510
have tried it all.its not that hard to understand...ended up with build 1932.768.it wont work...this thing wont work unless it is in a left,right config let me put it that way.then I can go Asio drivers and roll...deck mode its not hapenning....and that's the way it was untill the changes in the builds after1872.so what where they?
Mensajes Thu 04 Sep 14 @ 4:13 am
djdad
thetracker510 wrote :
ended up with build 1932.768.it wont work.
Mensajes Thu 04 Sep 14 @ 4:21 pm
thetracker510
I know,but the latest build is gonna work? all you did was kill the second layer.now it shows as Automatic deck 1,2. it is still in deck mode? is that it? well whatever it is it only works when Automatic Left,Right comes up in config...is it so hard to control that?
Mensajes Thu 04 Sep 14 @ 11:45 pm
the SOUND INSURGENT
Sell them antiques bro, lmmfao!!
Just do what Bob said.
Just do what Bob said.
Mensajes Fri 05 Sep 14 @ 9:50 am
thetracker510
I dont like selling stuff.I only buy...
Mensajes Fri 05 Sep 14 @ 2:01 pm
fiverfiver
How can I use 1 Stanton scs.3d controller with VDJ8? I need MIDI help setting up the unit to go from deck A and B when hitting the Deck button. When I hit the button now it goes from deck A and C.
Mensajes Wed 17 Sep 14 @ 2:43 pm