VMS4 mapping thread
VMS4 mapping thread Posted on: 25.10.2011 by Madeline Seneff Ok so considering I'm fairly new to mapping and this controller (American Audio VMS4) is brand new as well, I figured I'd make sort of a log about my mapping process. I was not content with a single mapping that I found so I'm starting from the ground up.What I plan to do: I'm going to make the VMS4 work with all 4 decks in Traktor Pro 2. I'm going to map a filter function somewhere, I way to switch between decks (A/C or D/B) and I'd like to keep a majority of the primary mixer functions in tact. As for scratching and what not, this board was designed to do it so I'm going to map that as well, however that will be towards the end because I'm brand new to classic scratching as well. If I have any questions I'll try and post them to this thread, and hopefully people will help out. Chances are I'll have a lot of questions. Apart from that though, this will be a fantastic log of what I do and how I do it, just for my personal reference and hopefully anyone else with a VMS4 or simply mapping problems. ---------------- So far mapped: Deck A: Cue - Cue, Deck A, Button, Hold, Ch01.Note.C0, Condition 1 M1=1, Condition 2 None Play - Play/Pause, Deck A, Button, Direct (Value of 1), Ch01.Note.C#0, Condition 1 M1=1, Condition 2 None Pause - Play/Pause, Deck A, Button, Toggle, Ch01.Note.D0, Condition 1 Play/Pause, Condition 2 M1=1 Deck B: none Deck C: none Deck D: none Mixer: none Front Face: Mic 1 - Modifier 1, Global, Button, Hold, Value of 1, Ch01.Note.E5, Condition 1 None, Condition 2 None | |
| Madeline Seneff 25.10.2011 | Ok so considering I'm fairly new to mapping and this controller (American Audio VMS4) is brand new as well, I figured I'd make sort of a log about my mapping process. I was not content with a single mapping that I found so I'm starting from the ground up. What I plan to do: I'm going to make the VMS4 work with all 4 decks in Traktor Pro 2. I'm going to map a filter function somewhere, I way to switch between decks (A/C or D/B) and I'd like to keep a majority of the primary mixer functions in tact. As for scratching and what not, this board was designed to do it so I'm going to map that as well, however that will be towards the end because I'm brand new to classic scratching as well. If I have any questions I'll try and post them to this thread, and hopefully people will help out. Chances are I'll have a lot of questions. Apart from that though, this will be a fantastic log of what I do and how I do it, just for my personal reference and hopefully anyone else with a VMS4 or simply mapping problems. ---------------- So far mapped: Deck A: Cue - Cue, Deck A, Button, Hold, Ch01.Note.C0, Condition 1 M1=1, Condition 2 None Play - Play/Pause, Deck A, Button, Direct (Value of 1), Ch01.Note.C#0, Condition 1 M1=1, Condition 2 None Pause - Play/Pause, Deck A, Button, Toggle, Ch01.Note.D0, Condition 1 Play/Pause, Condition 2 M1=1 Deck B: none Deck C: none Deck D: none Mixer: none Front Face: Mic 1 - Modifier 1, Global, Button, Hold, Value of 1, Ch01.Note.E5, Condition 1 None, Condition 2 None |
| Simona Schar 07.01.2012 | Thanks for the file, I also own it, but it's not realy usefull (espcially concerning leds...) I also actually work on my own mapping for the vms4 : What is done : - 4 deck Mixer-with cueing, filters and crossfader assignation- (not the hardest thing to do in a mapping, so here it's done) : I plan to use the vms4 as only a controler. Its soundcard is soooo creepy that I wanna use it just as a midicontroller, not as a all-in-one solution, - decks control modifiers (I use your solution with the mic switch that I found soooooo relevant the first time I use it...), -layering modifiyer : adding to the deck control modifier, I plan to use a lot of different inboard solution (instant fx, slicer, etc...) It means having a lot of button, so I mapped switch button on the pitchbend buttons, so three layers are ready, and you can switch just one of the two parts of the vms4 from one layer to another. -browser mode : I found the load "buttons" not responsive at all when I used my vms4 day by day, so I use the 4 fx/sampler encoders as browser exploration tools/deck loader. that's all for the moment. My roadmap : What will be done very soon : - echo freeze effect as a pause button for each deck, - hotcues, - loops, What will be done later : - instant grat FX (using djtt instant grat selection+shift per hold them ) - leds mapping linked to the different layers (how do you set the bicolor leds to different colors BTW? I tried a bit, the start working on something else...) What will be harder, but is planed in the very end : - beatslicer (maybe mapped on the ribbon :$, but most certainly on buttons), - jogfx (seems veryyyy tricky, so, I'm not sure...) Final release : One month or two... If you have something about leds on the VMS4 (a real midi table with real midi note as an exemple), it'll be realy helpfull. Regards, Pierre |
| King Mascarinas 07.01.2012 | I found out that the vms 4.1 needs to be selected as the soundcard. I was using my s4 for the soundcard before, so I didn't see them work. I attached the vms4 midi table for anyone that is stuck like I was (this is how I found out that there wasn't a midi assignment for the volume leds). Enjoy! |
| King Mascarinas 07.01.2012 | Does anyone know how to program the led volume meters in traktor? I started at cc 000 and I have tried going up from there, and havn't found it yet. I am guessing you use master volume out left and right, but I don't know what channel they are. I guessed those low ccs because that is the range of the volume faders (right by the leds). Please let me know guys, I would really like to get the leds working. (It was much easier to make a custom map for the s4). I wish native instruments would improve support for leds (included segmented displays s4 cough cough). |
| Madeline Seneff 26.10.2011 | Ok so I didn't want to just keep putting this mapping off, so that's why I posted that random header of a first post. I'll be coming back to that post though and editing it. Log entry 1, October 26th 2010: mapping a on/off button to a shift function: The first problem I've run into (and I've only mapped three buttons so far lol) is being able to switch between decks A and C. I decided I'd use the mic buttons on the front side of the controller. I thought these would be ideal buttons because they are on/off buttons. when I press them they lock in, and when I press them again they pop out. My idea was on would be deck A and off would be deck C, and two buttons means I can do the same for deck B and D as well. I figured I'd use a modifier shift function, so I mapped the button to "m1=0 when m1=1 and also m1=1 when m1=0" both on direct, like a normal shift. However what I've come across from testing this is Traktor doesn't recognize the difference between on and off for this button. In other words if the button is "off" and I press it "on," it does switch to deck A, but when I press it to "off" again it does not switch back to C. In order to switch back to C I have to press the button "on" again. Now I have pressed it three times total, and if I press it a fourth to "off" again it still remains on C. A way to describe it is a regular button being pushed is a whole cycle, it is pushed in and pops back out. This on/off button has a half cycle to it, where if it is pushed on it is half pushed, and when it is pushed off again it is then fully pushed. Therefore in order to push the button as if it were a regular button, it must be pushed 4 times in order to complete a cycle, twice the amount of a regular cycle. So my solution originally was to set the modifiers to hold, considering technically this locking mechanism defining the on/off button technically holds the button for me. The idea would be when pushed to "on," or being held down by the lock, it would be on deck A, and when "off" it will be on deck C. Turned out to work perfectly, and I have to do only half the work when it comes to assigning functions to modifiers. ---------------- So far mapped: Deck A: Cue - Cue, Deck A, Button, Hold, Ch01.Note.C0, Condition 1 M1=1, Condition 2 None Play - Play/Pause, Deck A, Button, Direct (Value of 1), Ch01.Note.C#0, Condition 1 M1=1, Condition 2 None Pause - Play/Pause, Deck A, Button, Toggle, Ch01.Note.D0, Condition 1 Play/Pause, Condition 2 M1=1 Deck B: none Deck C: none Deck D: none Mixer: none Front Face: Mic 1 - Modifier 1, Global, Button, Hold, Value of 1, Ch01.Note.E5, Condition 1 None, Condition 2 None |
<< Back to Post and find Controller MappingsReply