Here’s the deal… I have a show June 11th… and a lot of things i have to do before then…
mapping my apc40 is an added amount of work i really can’t afford to do (well, i probably could but it will eat up a few nights with frustration) and I rather focus on writing music and promoting our party…
if anyone is down, please let me know… i can paypal you the cash… i need the mapping as soon as possible to work with…
here’s what i would like to do with my apc… also i am in the usa… i am noting this because apparently different apc’s have different midi messages… or at least there are 3 kinds of apcs out there…
please respond if you can get on this plus how much you would like for payment…
ok ok… one big deep inhale later and a coffee… f it… mapping is complete… except i just realized i am using my 4 fx units already and have none left for the device control on the right other than that… all seems to work well so far… i’ll post in a couple days after i run a set through it…
but still, what if someone just doesn’t have time you know? i bet you could put together a shop of highly detailed TSI with comments, proper documentation, training video etc and people would buy them to ramp up their traktor newlywed period as well as reduce their learning curve.
True, my mappings get so confusing/complicated it takes a while for ppl to work with them, while I know every button from the moment I’m finished mapping.
then again, I was making templates for my apc’s more then a month before I got the actual unit
well, i guess i should clarify my expectations of such service… it wouldn’t put the responsibility on the “programmer” to design the mapping. the individual requesting the mapping would have to design their mapping as they need it. Simply provide graphic representation and some additional annotations of the functionality. then the “programmer” could work on the actual mapping and ship off the tsi. otherwise - yes, there could be many confusing and convoluted mappings being sold which doesn’t really help anyone.
yeah. i can see how that can be an issue. but maybe if it was approached like application design with a ux designer, programmer and beta testers it may be a streamlined work flow with expectations easily managed. but again, it would have to be work. so…
this is exactly what I was thinking a while back. But id need to own every controller in the world. Or at least have access to midi note diagram, but then can’t bug test…
yeah. each controller is essentially a platform. and it becomes a challenge to prioritize which platforms to release on first. then possibly getting manufactures to loan devices for development periods.
For quite some time I thought that way but then I was surrounded by people who were basically ignorants who even if I did share a map, they didn’t appreciate it, as they didn’t appreciate the company’s effort enough to buy it…
The DJTT maps are different in the way they do play with firmware changes that can’t be done by the vast majority. Besides, they are a “bundle” with the controller, like the S4.
This no sharing attitude changed when I started frequenting this site but I still think it’s a “skill” worth learning.
Might be just be just me being retarded or giving priority to something most people find useless, but I’m comfortable with my position at the moment. I prefer teaching people how to fish.
other than that… all seems to work well so far… i’ll post in a couple days after i run a set through it…