Accesso rapido:  

Forum: VirtualDJ Technical Support

Topic: VDJ 2021 -- Need Help With MIDI Map Of "KORG NanoKontrol2" - Page: 2

Questo argomento è obsoleto e potrebbe contenere informazioni obsolete o errate.

Quick question:
Now, when I choose "Connected Controllers",
VDJ shows 'Korg NanoKontrol2'.
However, under Deck:, it shows "Automatic (1)"

Why is there a "(1)" there now?
Is there a duplicate somewhere?


PS:
Can you tell me how to get a custom (or force-custom.xml ) set up going,
for custom MIDI mapping, of the nanoKONTROL2 ?

( Yesterday, in frustration, I deleted all mapper .XML files,
including the 'custom mapping ... .xml' file and kept NOTHING there )
 
Inviato Sun 21 Jun 20 @ 7:20 pm
djdadPRO InfinityDevelopment ManagerMember since 2005
Good news.
Can you get another Log Report.txt now (without the drivers) ?

As for any custom mapping, if you had deleted (from Mappers folder), unless they have been kept in Trash, there is nothing you or anyone else can do. Always a good reason to do a fresh start !

Automatic(1), means that the device is automatically assigned to control Deck 1. It's OK. Not preventing you to use actions like .. deck 2 volume, but just volume will apply to deck 1 (or the default deck to be more precise)
 
Inviato Sun 21 Jun 20 @ 7:32 pm
I ask again, how to assign 'custom mapping' now ?,
without destroying the 'default' nanoKONTROL2 MIDI settings from VirtualDJ ?



djdad wrote :
Good news.
Can you get another Log Report.txt now (without the drivers) ?

here you go, djdad,

--- 2020/06/22 - 05:49 (5929)
[05:49] Audio device found: name="Intel(R) Display Audio" vid="0x8086" pid="0x2807" hardwareID:"{0.0.0.00000000}.{6504967c-a52e-4ac6-85a3-f3f0f5ccdd10}"
[05:49] Audio device found: name="Realtek High Definition Audio" vid="0x10EC" pid="0x0283" hardwareID:"{0.0.0.00000000}.{839996f4-2a84-45be-93f5-ffb192f81a0f}"
[05:49] Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
[05:49] MIDI Device Identifying: \\?\usb#vid_0944&pid_0117#5&2f762188&0&2#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global (in:0 out:1) (name: nanoKONTROL2)
[05:49] MIDI Device Identified by PID/VID: \\?\usb#vid_0944&pid_0117#5&2f762188&0&2#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global : Korg NanoKontrol2
[05:49] Assigned Keyboard, type:0, index:1
[05:49] Assigned Korg NanoKontrol2, type:4, index:1
[05:49] MIDI Device Identifying: Microsoft GS Wavetable Synth (in:-1 out:0) (name: Microsoft GS Wavetable Synth)
[05:49] Midi Out Closed (Microsoft GS Wavetable Synth)
[05:49] MIDI Device Not Identified: Microsoft GS Wavetable Synth
[05:49] HID Device found: VID:0x046D PID:0xC52B path:\\?\hid#vid_046d&pid_c52b&mi_02&col01#7&1287e22e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[05:49] HID Device found: VID:0x046D PID:0xC52B path:\\?\hid#vid_046d&pid_c52b&mi_02&col02#7&1287e22e&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
[05:49] HID Device found: VID:0x046D PID:0xC52B path:\\?\hid#vid_046d&pid_c52b&mi_02&col03#7&1287e22e&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
[05:49] HID Device found: VID:0x046D PID:0xC52B path:\\?\hid#vid_046d&pid_c52b&mi_01&col02#7&365f1ff0&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
[05:49] HID Device found: VID:0x046D PID:0xC52B path:\\?\hid#vid_046d&pid_c52b&mi_01&col03#7&365f1ff0&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
[05:49] HID Device found: VID:0x046D PID:0xC52B path:\\?\hid#vid_046d&pid_c52b&mi_01&col04#7&365f1ff0&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}
[05:49] Assigned Keyboard, type:0, index:1
[05:49] Assigned Korg NanoKontrol2, type:4, index:1
 
Inviato Sun 21 Jun 20 @ 7:52 pm
djdadPRO InfinityDevelopment ManagerMember since 2005
iamanotheryou wrote :
I ask again, how to assign 'custom mapping' now ?,
without destroying the 'default' nanoKONTROL2 MIDI settings from VirtualDJ ?


The factory default mapping cannot be overwritten/lost. As soon as you start changing the actions of the factory default mapping, a new "custom" mapping will be created and saved, and you will have the ability to choose one or the other from the Mappings drop list.
 
Inviato Sun 21 Jun 20 @ 8:50 pm
alright.
i'll try that out soon.
 
Inviato Sun 21 Jun 20 @ 9:02 pm
Just for 'fun', I tried the nanoKONTROL2 in a different machine (Win7 x64),
running VDJ 2020 (x32). The same problem exists there, ie. the device is not recognised,
because it is recognized as: "nanoKONTROL2 1 SLIDER/KNOB", etc... it's like the issue from the Win10 machine.
( the Win7 machine, also has the Korg USB drivers installed already )

So, now, when I use Pocket MIDI , and do this:

________________________________________________________

Send: F0 7E 7F 06 01 F7

MIDI In:
F0 7E 00 06 02 42 13 01 00 00 03 00 01 00 F7

MIDI Out:
F0 7E 7F 06 01 F7
________________________________________________________

Just 1 x line, for IN or OUT.
 
Inviato Sun 21 Jun 20 @ 9:06 pm
djdadPRO InfinityDevelopment ManagerMember since 2005
In next update, the device will be detected properly, with or without the drivers installed.
 
Inviato Sun 21 Jun 20 @ 9:08 pm
djdad wrote :
In next update, the device will be detected properly, with or without the drivers installed.

That's great. Thank You.

PS:
In Win7, if you remove all Korg USB drivers, not much happens with VDJ.
Win7 itself, detects there's a 'Sound, Game... Controller' called KORG nanoKONTROL2 (in Device Manager).
However, no other software, MIDI detection sees the nanoKONTROL 2 (without the Korg drivers).

In summary, it looks like:
In Win7, the Korg drivers are necessary, for the OS / VDJ to detect the nanoKONTROL but VDJ does not work, to unlock the licence.
In Win10, the Korg drivers are unnecessary, as the OS sees the MIDI controller and VDJ sees the MIDI name as defined in VDJ (nanoKONTROL 2), so licence is unlocked .
 
Inviato Sun 21 Jun 20 @ 9:32 pm
Quick question:
Would 2 x nanoKONTROL2
MIDI controllers work with VDJ 2021 (Win10 x64 PC) on the 'Home Licence' ??
 
Inviato Sun 21 Jun 20 @ 9:40 pm
djdadPRO InfinityDevelopment ManagerMember since 2005
yes
 
Inviato Sun 21 Jun 20 @ 9:46 pm
djdad wrote :
In next update, the device will be detected properly, with or without the drivers installed.

djdad,
does VDJ build 5949 , contain that "fix" ?

( i'm asking because i needed to install the USB driver,
so that the KORG editor can 'talk' to the nanoKONTROL2 ,
and i can change the MIDI-behaviour of some buttons )
 
Inviato Tue 23 Jun 20 @ 11:40 pm
djdadPRO InfinityDevelopment ManagerMember since 2005
Yes, fix should be included in 5949 (current Early Access)
 
Inviato Wed 24 Jun 20 @ 12:36 am
djdad wrote :
Yes, fix should be included in 5949 (current Early Access)

djdad,
Yes!
I can confirm, that VDJ 2020 build 5949 does allow me now,
to use the nanoKONTROL2 controller, with the Win10 USB drivers, supplied by KORG.

So, the issue has been resolved now :-)

I wish I reached out last year, but whatever year, the VDJ community support is great :-D
 
Inviato Wed 24 Jun 20 @ 5:54 am
for your record-keeping, djdad :-)

--- 2020/06/24 - 15:44 (5949)
[15:44] Audio device found: name="Intel(R) Display Audio" vid="0x8086" pid="0x2807" hardwareID:"{0.0.0.00000000}.{36b03b51-9dae-4453-8725-d4d3d667cd20}"
[15:44] Audio device found: name="Realtek High Definition Audio" vid="0x10EC" pid="0x0283" hardwareID:"{0.0.0.00000000}.{839996f4-2a84-45be-93f5-ffb192f81a0f}"
[15:44] Midi in device detected, name:nanoKONTROL2 1 SLIDER/KNOB mid:55 pid:5
[15:44] Midi out device detected, name:Microsoft GS Wavetable Synth mid:1 pid:27
[15:44] Midi out device detected, name:nanoKONTROL2 1 CTRL mid:55 pid:6
[15:44] MIDI Device Identifying: nanoKONTROL2 1 SLIDER/KNOB (in:0 out:-1) (name: nanoKONTROL2 1 SLIDER/KNOB)
[15:44] MIDI Device Identified by name: nanoKONTROL2 1 SLIDER/KNOB : Korg NanoKontrol2
[15:44] Assigned Keyboard, type:0, index:1
[15:44] MIDI Device Identifying: Microsoft GS Wavetable Synth (in:-1 out:0) (name: Microsoft GS Wavetable Synth)
[15:44] Midi Out Closed (Microsoft GS Wavetable Synth)
[15:44] MIDI Device Not Identified: Microsoft GS Wavetable Synth
[15:44] HID Device found: VID:0x046D PID:0xC52B path:\\?\hid#vid_046d&pid_c52b&mi_02&col01#7&1287e22e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[15:44] HID Device found: VID:0x046D PID:0xC52B path:\\?\hid#vid_046d&pid_c52b&mi_02&col02#7&1287e22e&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
[15:44] HID Device found: VID:0x046D PID:0xC52B path:\\?\hid#vid_046d&pid_c52b&mi_02&col03#7&1287e22e&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
[15:44] HID Device found: VID:0x046D PID:0xC52B path:\\?\hid#vid_046d&pid_c52b&mi_01&col02#7&365f1ff0&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
[15:44] HID Device found: VID:0x046D PID:0xC52B path:\\?\hid#vid_046d&pid_c52b&mi_01&col03#7&365f1ff0&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
[15:44] HID Device found: VID:0x046D PID:0xC52B path:\\?\hid#vid_046d&pid_c52b&mi_01&col04#7&365f1ff0&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}
[15:44] Assigned Keyboard, type:0, index:1
 
Inviato Wed 24 Jun 20 @ 5:56 am


(Vecchi argomenti e forum sono automaticamente chiusi)