I think the problem with that is when a DJ/controllerist holds down the button from passion , or holding it down to keep the cue playing, they might accidentally delete and destroy that cue.
It’s nice idea to have some additional commands on hold of the button. This can be done also by routing midi back to traktor to create some automation for this purpose. Question is, can it be done strait in traktor, without some inmiddle software.
Line up all eight modifiers so it scrolls modifier values from M1=1 to M8=7 when button is held. That should give you 5-6 sec in play duration till modifier line reaches end (known as modifier wall). Trick is to map delete hotcue (invert, hold) with modifier condition that’s last in a row. Also you need to map M=0 command for all modifiers so every time button is released all modifiers jump back to zero and ready for next use. Probably would be the best to add one generic device only for this smart hotcue
yea i dont think that is going to work, remember we are trying to set a hot cue AND delete the hot cue all in the same button.
putting all 8 modifiers on the same button will not do anything. i personally think it can’t be done. UNLESS, native instruments adds a modifier states that shows “is in active hot cue” or something of that nature. so that way when u press/hold the same button it knows “OH this button correlates to a hot cue, now i must delete this”
you can do it in VDJ Pro, but I don’t think it’s a very good way to do it as when you press the button down the timer starts, if the hold has exceeded the timer set it would delete, but if the the button is held for less time than the timer set it would hot cue…
holding 1000ms ? action if held for less than 1000ms then released : action if held for longer than 1000ms then released
The problem is that the button doesn’t work when pressing only on release. Using a shift modifier is a much better way of doing it in any software IMO
I don’t think you have understand how to line up modifiers part…
This mapping have 18 commands in total and it’s all mapped to one button as your original idea says. I mapped my hotcue #8 to be smart one and let the rest of it to act same as before (shift+).
stewe- wow thats awesome, and you’re right i did not understand how to line up the modifiers till last night as i was researching and started to see that this is possible
thanks for the visual of how it actually looks like. keep it up man! in the future, would you mind me coming to you for help if i run into problems with mapping? my VCI 400 is on its way. and i plan to map everything to my taste
You can add another midi device giving you additional 7 modifiers. Like I said before it would be best to start mapping from there. I agree modifiers are limitation but that s something we can expect to happen hopefully till 3.5 version.
My custom mapping has 10 generic devices and still adding That is problem with traktor - it’s taking a neap while importing tsi since it’s huge map. It’s all good while performing, just this annoying minute of waiting to import… It would be great to have two of more controllers with ultimate mappings but traktor isn’t designed for such that. This can be overcome with adding more modifiers like at least double it to 16 so more stuff can be mapped in frame of one generic device leaving less pages in controller editor.
I did short video how it works. Isn’t actually deleting hotcue while holding button - it happen on release of button. You can imagine modifiers like sort of buffer so when modifiers scroll to last position then delete hotcue become ready. I also mapped LED outputs that indicate buffer size while hotcue is holding. That’s for video purpose and maybe you can map just one flashing LED on same hotcue button.
ok nvm i got it scroll up, however. because it scrolls starting from M1=0 therefore it will jump back to the hot cue…before it can scrolls through then delete the hotcue.
yup i got it to work exactly like your video on my laptop. so your video shows the concern that i have.
im thinking of a way to see if it can start scrolling from M1=1, so it doesnt jump to the cue spot
Start new mapping and add Modifier 1 / button / inc / auto repeat check. This will make values to scroll from 0 to 7 and every next time you press button it will stay at 7… That’s why you need to duplicate modifier 1, set as button, check invert, set as hold. After this when you scroll modifier and release button - modifier value should jump back to 0.
so pretty much, track is playing, press/release droping a cue track still playing > press/hold it jumps back to the cue spot, and the track still plays, 5-6 secs later i release then the cue is deleted.
your setup doesn’t do that? it seems like it is in the video.