Version 3.0- What does everyone think?

[DJ V1ckz]

Hey I just got the email about the 3.0 mapping, and I wanted to open things up to see what everyone thinks.

This is copied and pasted from my comment on the post, and basically summarizes what I think about the new mapping:

You went in a different direction than I anticipated. In version 3.0, I was hoping you would expand on the 4 deck concept, and by pressing the C/D controls, the effects slot 1-A and slot 2-B would be controlling slot 3-C and 4-D. That way you could have true 4 deck control with 1 VCI, it would be totally glorious (and I imagine a programming nightmare). In this version, slots 1, 2, and 3 are presets and 4 is a sampler. I think this would be a big mistake if enacted, and using a whole effects deck as a sampler is a total waste. Why not just have the sampler function copy the track your playing to another deck (C/D) and drop a 8 bar loop at the same time. You could argue that it would be a waste of a whole deck, but I think it would really open things up with the 4 deck set up, and allow you to cue up easily. Also you could effect the loop however you'd like, and lengthen/shorten it easily.

I like the idea of EQ FX but I never use the preset effects, but would use it all the time if I had the know how to customize it. Maybe if you provided people with an easy way to customize the effects they used, they would use it more. I'm really hoping I'm not the only one who opposes the move back to preset FX, this would be a definite step back! I like being able to customize my effects slots, and if this were in fact enacted on the mapping I would probably just stick to version 2.0. Maybe I'm settled in my ways, maybe I don't know the power of presets. I just feel like their limiting, and version 2.0 was awesome because you had the autonomy to use your own effects, and I always use the Shift+Scroll function to jump around to different effects.

As for the new layout of the 4 buttons on the bottom, I feel like theres a more elegant solution. Why not have fader fx mode turn all 4 buttons into FX presets, juggle mode turn all 4 buttons into cue points, and the default be cue, pause/play, sync, drop. That combines the innovation of 3.0 with the ease of use/autonomy of 2.0. You can still control deck C/D with the space that sync would occupy, and EQ FX would still exist.

What do you guys think of that idea? We should use the community to make this mapping as good as it possibly can be!

[MisterMoleyMole]

I think the reason for wanting echo on the transport section is for ease of use instantly. If it becomes part of fader fx you lose control of alot of functions which are possibly wanting to be used at th esame time as an echo, like echo on one deck then drop in teh next deck, not possible easily if your in fader fx i dont think.

[midifidler]

Maybe if you provided people with an easy way to customize the effects they used, they would use it more

This is easy - learn to edit a TSi!

[janzak]

This is easy - learn to edit a TSi!

This is actually real easy, just find the right entry on the long list of commands and change what FX is chosen

[lsmith]

well thats why i favor routing things through bome. this way the mapping could be down a lot. more importantly due to the use of modifiers the same setting would need to be adjusted multiple times.

[lsmith]

here is a first proof of concept without using Bome:
http://code.google.com/p/djtt/source...lsmith/modules

i have made an assignment for the transport section for deck A/C for echo-slice-cue-play and echo-drop-cue-play. so if each of the sections would be provided as "modules" people could mix and match. that is one could in theory could have echo-slice-cue-play on the left and echo-drop-cue-play on the right. we would provide modules for the EQ section, for the FX/loop section. of course all modules would have to have more or less the full modifier mapping. to get people started on doing their own modules we could provide the modifier mapping tsi.

with Bome it would obviously mean that the mappings each would be cut in half (duplicate A/C mappings would go away and the modifers as well) and of course the same mapping could be used for A/B/C/D in traktor. we would send the same midi messages for each deck via a separate virtual midi controller.

as a result people could mix and match even more. like with the above modules they could also do echo-slice-cue-play on the top and echo-drop-cue-play on the bottom. the biggest benefit would be that in traktor no modifiers would be needed at all. all people need to do is install bome, load our script and fire up traktor. load the modules, assign the midi ports and set the device targets. customizations would be alot easier.

[shogg]

Personally i prefer the 2.5 version.I think that the 3.0 version aims more at the controllerism and stuff.Im more of a mix guy,so im fine with the 2.5 version.

[lsmith]

thats the point with my modular approach. this way people can choose what they want. how much complexity they want etc. in theory you could even change the modules during a set.

[lsmith]

sorry .. i tend to be a bit spammy when i get excited about and idea. anyways, i have summarized in more detail my vision:
http://ifnotwhynot.me/djtt-30-mapping-vision