Sorry for the delayed reply. Have you got this sorted or do you still need help?
Comment actions
Post
Follow
wego3 virtual dj and djay2 ipad problem
hello people !
i have problem, and maybe this is a feature :) i don't know !
when i use fx on my wego3, i press for instance fx1 button on wego3 and use jog to manual setup fx1 slot on virtual dj, when i move with jog, fx 2 and fx 3 on virtualdj are affected too. And i don't want that. I want to manually control fx1 and not all 3 at the same time like now is the case. When i go to midi map learn option in options of virtual dj, i see that even if i press fx1 and use jog, wego send signal on all 3 fx to sliders.
Is this at the end problem of controller, problem of dj software or maybe feature. Because in manual of device i don't see that somewhere is stated that jog wheel control all 3 fx even when is pressed only one
same thing is with djay2 app on ipad, when you press fx 1 on controller and use jog to manual setup fx1 even if fx2 and fx3 are not pressed they are affected like fx1
is this possible to resolve in firmware update because one of main reason to buy this device was for me reason that device is enough solid, old and bug free
i have latest firmware on wego3, latest drivers on my win7 ultimate, latest ios on my ipad and latest djay2 app on my ios device i use vritualdj infinity latest update
Post is closed for comments.
Date
Votes
2 comments
does you update firmware ? :D afc not, because in meantime i see same thing on sb1 and sb2 controler. Well i sort this out with my friend programer on virtual dj because i use most expensive version of virtual dj with midi map learn option (he try to sort this out with midi mapping commands and after 2 days was successful), but with virtual dj le version in wego box and djay2 app on ipad things are same,and as above is stadet if your sb1 and sb2 devices are doing same thing like wego on 2 different platforms (win and ios )and apps (djay and virtualdj) it is clear that something is wrong on your side (your devices firmware). you must update firmware or manual (call it feature not bug :) ).
Comment actions