Quick Sign In:  

Forum: VirtualDJ Technical Support

Topic: Latest update wiped all midimaps and xml mapping file
Overnight while I was doing some library work an update window popped up so I read the log and then gave it a yes. It closed like always and then reopened.
When it came back and I started to pick up where I left off right away my controller was not working.
Restarted the pc and started over and still nothing. I went into settings/controllers and it was at system defults. My controller was no longer in the dropdown or listed anywhere. I went into the VDJ Folder in documents and indeed my custom xml was gone as if I had just done a clean windows install and started from zero. My controller is a Korg nanoKONTROL Studio and I have been working on and creating custom functions to this map for over 2 years.
I have backups of everything and I'll see where it goes from here and post updates if I discover anything out of the ordinary but there's no reason an update should have deleted a xml device file. Be careful with this latest update.
Edit: FYI all my other settings remained the same as always. It was just the midi device xml that was lost.
Update: After replacing the missing mapper files it is still not seeing them. In the right hand "Mapping" dropdown I am seeing new entries, Ignore, Factory default (legacy), Factory default, Factory default (Rekordbox compat.) and factory default (serato compat.). I have never seen this in here before and no matter what I do it is not seeing my controller at all. I also replaced the settings xml file with my backup and still no change.
According to all the Korg software the drivers are working and all functions are working properly as I can see the activity in its own application but VDJ is no longer seeing the device at all. I'll update as I go deeper into this. Up until this update happened, all had been working fine as it always has. Never had any kind of a problem with an update until now.
 
geposted Mon 14 Feb 22 @ 11:23 am
Update: Still no change and VDJ is not seeing the controller at all. I have tried everything I can at this point short of a windows restore which I really do not want to do for any reason.
At one time there was a page of all the recent downloads. I am looking for the 1-16-22 build 6800 to uninstall the current version to go back to the last known good version. However I have lost the link or shortcut to that page or it is no longer available, but if anyone knows where the past builds downloads are available at please let me know.
Either way something is definitely not right with this latest update. Everything has run flawlessly for years here on this machine including all the updates up until now and this has never happened before and for the record this is my daily driver at home, not my club machine or any of the others I work with and use. Also when I went to contact support to send a support ticket, it is not opening for me so does this mean all support is now handled in forums?

Ill be watching
 
geposted Mon 14 Feb 22 @ 12:43 pm
 
geposted Mon 14 Feb 22 @ 1:45 pm
Thanks. Uninstalled the updated build and went back to 6800. This includes deleting all the software related folders and using the vdj registry cleaner. I am seeing the mapping again now and all looks normal but the controller is doing nothing to it. Once again thanks for the links. Ill update as I make progress here.
 
geposted Mon 14 Feb 22 @ 2:02 pm
12 hours later........
After my last update I did everything else I could think of again, and gave up. Now after a clean install of windows and all fresh everything back on build 6800 all is normal again in this world. Not sure whats up with that latest build but nothing would get it working again or let it recognize the controller I've been using for the last two + years. My thanks once again to Klaus for the download page link, I do appreciate it. Ill get brave and try again a few updates from now or the next time I'm ready to clean install an upgrade to windows or something.
Edit: I forgot to mention, the system that was running when the update came was windows 10 64 pro. I took advantage of this mess to upgrade to windows 11 and my hardware was all ready for it. No issues with 11 at all so far all is normal.
 
geposted Mon 14 Feb 22 @ 10:05 pm
djdadPRO InfinityDevelopment ManagerMember since 2005
Have you created a custom definition in /Devices folder or was your controller mapped as Simple MIDI ?
Can you share the first lines of those files ? (the <device> and/or the <mapper>)

It would also help to see how your device is detected, so ..
- Open VirtualDJ, goto Options , search for createMidiLog seting and set it to Yes.
- Close VirtualDJ, make sure your controller is connected, then open VirtualDJ
- Close again, and post here the content of the Log Report.txt file you will find in /Documents/VirtualDJ folder.
 
geposted Mon 14 Feb 22 @ 10:42 pm
If unsure if you will be happy with an update, of any kind, you can always create an image backup of your C drive (which records the exact placement of every bit) before any update.. so its just a matter of few minutes to restore your computer exactly to its previous state.

So no need to every worry about doing an update.
 
geposted Mon 14 Feb 22 @ 10:48 pm
SchiumPRO InfinityMember since 2005
Having the same issue with my midi device not showing up after the latest update

<mapper device="SIMPLE_MIDI_2536_4169" version="850" date="2022-02-11">

Its an Akai MPK mini mk3

I had 2 other "midi" devices listed that weren't actually controllers that also aren't showing up

Here's the result of the log file


--- 2021/02/20 - 15:52 (6076)
[15:52] Thread mathEngineInit freezed.
--- 2021/03/04 - 00:38 (6076)
[00:38] Thread mathEngineInit freezed.
--- 2021/03/11 - 01:52 (6076)
[01:52] Thread mathEngineInit freezed.
--- 2021/05/01 - 19:06 (6076)
[19:06] Thread mathEngineInit freezed.
--- 2021/05/01 - 19:07 (6334)
[19:07] Thread gpudriversdownload freezed.
[19:07] Thread mathEngineInit freezed.
--- 2022/02/15 - 08:45 (6839)
[08:45:45] WASAPI device without vid/pid: Speakers (2- Sonic Studio Virtual Mixer) : {2}.\\?\swd#driverenum#{1b98ef90-ca0e-11e7-8f1a-0800200c9a66}#avolutess3vad&6&4db1a44&1#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\wavespeaker
[08:45:45] WASAPI device without vid/pid: Microphone (2- Sonic Studio Virtual Mixer) : {2}.\\?\swd#driverenum#{1b98ef90-ca0e-11e7-8f1a-0800200c9a66}#avolutess3vad&6&4db1a44&1#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\wavespeaker
[08:45:45] Audio device found: name="2- Sonic Studio Virtual Mixer" hardwareID:"{0.0.0.00000000}.{023ea4d6-e52f-4ce4-90a9-33f14c9c8a62}" 
[08:45:45] Audio device found: name="NVIDIA High Definition Audio" vid="0x10DE" pid="0x009A" hardwareID:"{0.0.0.00000000}.{66ed077d-cfd8-46ee-a3f5-a75b3f35561c}" 
[08:45:45] Audio device found: name="Speakers (MOTU Pro Audio)" vid="0x07FD" pid="0x0005" hardwareID:"{0.0.0.00000000}.{91e5950c-9d98-4fff-bd7f-68762b6ccac5}" 
[08:45:45] Audio device found: name="Out 1-24 (MOTU Pro Audio)" vid="0x07FD" pid="0x0005" hardwareID:"{0.0.0.00000000}.{ace09d48-feaa-4bcf-b69f-ab2fd749e8c2}" 
[08:45:45] Audio device found: input name="2- Sonic Studio Virtual Mixer" hardwareID:"{0.0.1.00000000}.{688dfd73-f72e-4aea-b955-3624ca4ec6b3}" 
[08:45:45] Audio device found: input name="In 1-24 (MOTU Pro Audio)" vid="0x07FD" pid="0x0005" hardwareID:"{0.0.1.00000000}.{b989538b-3449-4e86-89e6-5c9f3cafe98c}" 
[08:45:45] Audio device found: input name="In 1-2 (MOTU Pro Audio)" vid="0x07FD" pid="0x0005" hardwareID:"{0.0.1.00000000}.{ec295d15-9be4-4187-8ced-c60bad4ddeaa}" 
[08:45:45] Audio device found: asio="ASIO4ALL v2" hardwareID:"232685C6-6548-49D8-846D4141A3EF7560" 
[08:45:45] Audio device found: asio="MOTU Pro Audio" hardwareID:"3E08EBE9-46E3-45B9-8216312892B30F94" 
[08:45:45] Audio device found: asio="Realtek ASIO" hardwareID:"A80362FF-CE76-4DD9-874A704C57BF0D6A" 
[08:45:45] WASAPI device without vid/pid: Speakers (2- Sonic Studio Virtual Mixer) : {2}.\\?\swd#driverenum#{1b98ef90-ca0e-11e7-8f1a-0800200c9a66}#avolutess3vad&6&4db1a44&1#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\wavespeaker
[08:45:45] WASAPI device without vid/pid: Microphone (2- Sonic Studio Virtual Mixer) : {2}.\\?\swd#driverenum#{1b98ef90-ca0e-11e7-8f1a-0800200c9a66}#avolutess3vad&6&4db1a44&1#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\wavespeaker
[08:45:45] Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
[08:45:45] MIDI Device Identifying: \\?\usb#vid_07fd&pid_0005#0001f2fffe00a215#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\motuproaudiosyncmidiin (in:0 out:1) (name: MOTU Pro Audio LTC Sync In)
[08:45:46] MIDI Device Identified by catch-all: \\?\usb#vid_07fd&pid_0005#0001f2fffe00a215#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\motuproaudiosyncmidiin
[08:45:46] Midi Out Closed (\\?\usb#vid_07fd&pid_0005#0001f2fffe00a215#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\motuproaudiosyncmidiin)
[08:45:46] MIDI Device Identifying: \\?\usb#vid_07fd&pid_0005#0001f2fffe00a215#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\motuproaudiomidiin (in:1 out:-1) (name: MOTU Pro Audio Midi In)
[08:45:46] MIDI Device Identified by catch-all: \\?\usb#vid_07fd&pid_0005#0001f2fffe00a215#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\motuproaudiomidiin
[08:45:46] MIDI Device Identifying: \\?\usb#vid_09e8&pid_1049&mi_01#7&1228ec17&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global (in:2 out:-1) (name: MPK mini 3)
[08:45:46] MIDI Device Identified by catch-all: \\?\usb#vid_09e8&pid_1049&mi_01#7&1228ec17&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global
[08:45:46] HID Device found: VID:0x0764 PID:0x0501 path:\\?\hid#vid_0764&pid_0501#9&1ba3a06e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[08:45:46] HID Device found: VID:0x0FD9 PID:0x0080 path:\\?\hid#vid_0fd9&pid_0080#a&13be7428&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[08:45:46] HID Device found: VID:0x046D PID:0xC53A path:\\?\hid#vid_046d&pid_c53a&mi_01&col02#9&2aa9b985&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
[08:45:46] HID Device found: VID:0x046D PID:0xC53A path:\\?\hid#vid_046d&pid_c53a&mi_01&col03#9&2aa9b985&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
[08:45:46] HID Device found: VID:0x09E8 PID:0x1049 path:\\?\hid#vid_09e8&pid_1049&mi_00#8&83dac11&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[08:45:46] HID Device found: VID:0x0B05 PID:0x18F3 path:\\?\hid#vid_0b05&pid_18f3&mi_02#a&36997fda&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[08:45:46] HID Device found: VID:0x046D PID:0xC53A path:\\?\hid#vid_046d&pid_c53a&mi_02&col01#9&3a4974ab&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[08:45:46] HID Device found: VID:0x046D PID:0xC53A path:\\?\hid#vid_046d&pid_c53a&mi_02&col02#9&3a4974ab&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
[08:45:46] HID Device found: VID:0x046D PID:0xC32B path:\\?\hid#vid_046d&pid_c32b&mi_01&col02#9&1b5b7dc0&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
[08:45:46] HID Device found: VID:0x046D PID:0xC32B path:\\?\hid#vid_046d&pid_c32b&mi_01&col03#9&1b5b7dc0&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
[08:45:46] HID Device found: VID:0x046D PID:0xC32B path:\\?\hid#vid_046d&pid_c32b&mi_01&col04#9&1b5b7dc0&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}
 
geposted Tue 15 Feb 22 @ 1:54 pm
maticleePRO SubscriberMember since 2020
same happened to me i went to a previous install and sill no luck..virtual dj might loose a customer if this result of an update and they don't fix it asap
 
geposted Tue 15 Feb 22 @ 6:40 pm
AdionPRO InfinityCTOMember since 2006
Which controller do you have?
Is it listed in the left-top in the mappings section of the config page?

@Schium: It looks like there is a catch-all definition, which perhaps is not intended in your Documents\VirtualDJ\Devices folder?
 
geposted Tue 15 Feb 22 @ 7:04 pm
AdionPRO InfinityCTOMember since 2006
Update: It looks like there was an issue with the Traktor Kontrol S8 definition causing it to catch all the generic midi devices.
This has been fixed now, if you open virtualdj, wait a bit to let it update and restart it should work again.
 
geposted Wed 16 Feb 22 @ 5:08 am
SchiumPRO InfinityMember since 2005
When I reverted to 6800 my devices showed back up
No update showing as of yet from build 6839
 
geposted Wed 16 Feb 22 @ 9:25 pm
IIDEEJAYII wrote :
If unsure if you will be happy with an update, of any kind, you can always create an image backup of your C drive (which records the exact placement of every bit) before any update.. so its just a matter of few minutes to restore your computer exactly to its previous state.

So no need to every worry about doing an update.


What me worry? Kidding. I became an MS technet member in 2004 and I've been down the imaging and backup rabbit hole many times. I beta test software for a few places. In this machine I can go from secure erased to fully back to normal with all my usual software installed and activated in less than 30 minutes with an all fresh system and I've been known to change operating systems like people change clothes. I just normally do all of that on a different machine. So I gave it a good couple hours and the old college try and moved on. As for the question about "simple mapping xml" yes but its been fine for years this way and I have been working with different layouts and other things. This setup works well overall but sometimes I'll use VDJ for production type situations and switch to the 8 player skin which works perfect with the nanokontrol studio controller, so I have a few maps saved up as works in progress. It would be typical of an upgrade to ignore or not see a map, but I have never had one DELETE the map before and that was what raised my eyebrow about it. I can change folder layouts in a few seconds so that wasn't a bother either but everything else was fine. gave me an excuse to see any of the changes in win 11 since i last ran the beta anyway so I'll just wait til we see the end results of all this and as I mentioned I have never had any kind of issue with an update before other than living with the latest changes, like when stems first arrived for example. Either way it shouldn't have deleted that xml. Ill be watching.

Edit to add, DJ Dad, try as I might i have never been able to successfully create a definition file. so I did what I needed to do to make it work and live with it that way. I have saves for settings and mapping xml's for the 3 main skins I use the most and set things up accordingly for what I need to do for whatever I have on my plate for the day. My live rig is a completely separate system. Sometimes Ill be doing a cast or stream and sometimes I am doing some production work for one of the stations I work with or for an upcoming live event and if I need to go beyond the 8 channel skin and more multi-tracking then I break out my QU-16 and Ableton. Nice thing about VDJ is that its easy to make fast configuration changes for how you plan to use it and its a lot more than just a club dj program. Its one of my most used sound tools and a lot easier to setup and run than a DAW depending on what you need to do. Anyway Ill be watching.
 
geposted Thu 17 Feb 22 @ 2:53 am
I can confirm that the latest Mac version also has midi issues. The latest version does not address the issue as a previous poster has said. Build 6800 is the last version that sees all my midi devices.
 
geposted Mon 21 Feb 22 @ 3:08 pm
djdadPRO InfinityDevelopment ManagerMember since 2005
Please try the following..
Update to latest Public Release (Build 6839).
Open VirtualDJ (make sure your computer is connected to the Internet as it's a "silent" update), then close and restart.
At the very bottom of the Licenses tab of VirtualDJ Settings, you should see Build 6839.1857
If so, "Simple" MIDI devices should work.
 
geposted Mon 21 Feb 22 @ 3:44 pm
djdad wrote :
Please try the following..
Update to latest Public Release (Build 6839).
Open VirtualDJ (make sure your computer is connected to the Internet as it's a "silent" update), then close and restart.
At the very bottom of the Licenses tab of VirtualDJ Settings, you should see Build 6839.1857
If so, "Simple" MIDI devices should work.


Thank you for the instructions, but I have already done this and its still broken, at least on the MacOS.

 
geposted Mon 21 Feb 22 @ 4:03 pm