Felt (PT)
I just opened up VDJ after some time of not using it and I noticed the mapping has gone bonkers. I have a Numark Mixtrack Pro II and I'm using the NMPII skin.
Loop in and Loop Out will make the loop, but pressing loop out again won't eliminate the loop anymore, now I have to press Reloop. Also, the "tap" button, which was being used as a filter (which I didn't even do but was glad it was that way), now simply makes the track skip like half a second back and forth instead of being a filter.
The Tap button is, according to the mapping parameters and if I'm seeing correctly, set to "shift ? loop 16 : beat_tap" and "led tap" is set to "shift ? loop 16 : on". Loop out is set to "loop ? wheel_mode 'loop_out,jog' +1 : loop_out".
Loop in and Loop Out will make the loop, but pressing loop out again won't eliminate the loop anymore, now I have to press Reloop. Also, the "tap" button, which was being used as a filter (which I didn't even do but was glad it was that way), now simply makes the track skip like half a second back and forth instead of being a filter.
The Tap button is, according to the mapping parameters and if I'm seeing correctly, set to "shift ? loop 16 : beat_tap" and "led tap" is set to "shift ? loop 16 : on". Loop out is set to "loop ? wheel_mode 'loop_out,jog' +1 : loop_out".
geposted Fri 26 Aug 16 @ 1:33 am
PachN
What version of VDJ are you using?
And please make sure you are using the factory default mapping for your controller.
And please make sure you are using the factory default mapping for your controller.
geposted Fri 26 Aug 16 @ 10:15 am
Felt (PT)
I'm using the latest version and build. Everything was fine and then suddenly this happened.
geposted Sun 28 Aug 16 @ 4:36 pm
A Man and His Music
You have done nothing different; auto OS updates? Is this a Widows machine, what version? What happens if you use the default skin?
geposted Sun 28 Aug 16 @ 7:56 pm
Felt (PT)
There were some OS updates the other day, I think. I'm using Windows 7, original everything.
geposted Mon 29 Aug 16 @ 8:37 pm
djdad
You are correct. Some changes have been made to the default mapping in the latest builds.
Main reasons of those changes are :
- match mapping with the other "official" software.
- unify mapping with other Numark controllers
- match mapping with the silkscreen (e.g. no one will ever think that the BEATS encoder will control the Filter)
Please read the Operation manual of the controller for further mapping details.
http://www.virtualdj.com/manuals/hardware/numark/mixtrackpro2.html
You can still change/customize mapping.
- For the LOOP OUT, simply assign that as .. loop_out
- For the BEATS encoder, assign that as .. filter
and the TAP button as ... shift ? loop 16 : filter 50%
Main reasons of those changes are :
- match mapping with the other "official" software.
- unify mapping with other Numark controllers
- match mapping with the silkscreen (e.g. no one will ever think that the BEATS encoder will control the Filter)
Please read the Operation manual of the controller for further mapping details.
http://www.virtualdj.com/manuals/hardware/numark/mixtrackpro2.html
You can still change/customize mapping.
- For the LOOP OUT, simply assign that as .. loop_out
- For the BEATS encoder, assign that as .. filter
and the TAP button as ... shift ? loop 16 : filter 50%
geposted Tue 30 Aug 16 @ 12:23 am
Felt (PT)
Thanks a bunch!
geposted Tue 30 Aug 16 @ 1:40 pm