The Traktor and the iPad - Control Redefined

Pretty Damn Creative I say !

 

Thanks!

Yours too, really!
It´s really nice, how much things you can do with TouchOSC.
I´m really looking forward to the new version of the editor.
And maybe MIDIpad will give us an editor too in the future …

 

I've been wanting to learn iPhone/Pad development for a while so might actually start working on my own TouchOSC/MidiPad style app - TouchOSC is awesome but there doesn't seem to be much communication re: updates, and I have a lot of specific ideas for stuff I'd like (e.g. "tabbed" panes within a template, "jog wheel" style controls, etc.); and MidiPad is looking more and more like vapourware to me, and seems to lack the customization of TouchOSC. I'm not saying I'll have anything soon (or maybe ever!) but if anyone has any ideas for how their ideal control software would work, feel free to shout out.

Edit: according to MidiPad's Twitter (ugh), they have a version coming out next week with Ableton Live view and Studio view... sounds like no Traktor functionality yet...

 

I have a couple of thoughts for you based on hundreds of hours of TouchOSC template programming and wants for that app.

1/ K.I.S.S Don't try to be too fancy! Do the real basics and do them supremely well!
2/ when you implement your knobs and sliders do them as relative controls. Absolute is probably much easier to do but implement as relative because the gestures you use on a knob or slider are match that type of control. Absolute controls only work well when you have tactile response, on a touch surface those controls jump around if you are not accurate when touching down on the control.
3/ make sure your controls can support both local out and remote out. By local out I mean the control state shown to the user matches up with the control state input by the user and does not rely on or use MIDI OUT from an application. Remote out solely relies on the MIDI OUT of the application. The local value value change does not feedback into the control. The intent here is to prevent feedback jabber when there are two values feeding into the system to set a controller value.
4/ Support graphics as labels also support extended character sets and fonts.


Phil

 

Hey PhilL, can you explain this a bit more. I like the sound of reducing the feedback jabber, but not sure how to do the 'local/remote out' thing
---
…and has anyone succeeded in building a good scratch wheel with TouchOSC?

I saw this guy's work... [ame="http://www.youtube.com/watch?v=UOlVtd2B_14"]YouTube- Giant TouchOSC Rotary as deck for Traktor PRo Scratching[/ame]

…but can't get it to work when I match his settings (detailed in another vid on his channel). Maybe it's because he's using PD and I'm on OSCulator?

 

TouchOSC just got updated

 

Am I fashionably late to the party?

TouchOSC added relative mode for faders and knobs in the last update. Also, GRIID was just released today. Very cool!

 

urrrrrgggg? You what? Which version do you know? How does it do that? Current indications don't show that tho. That maybe right mate, but until we get OSCULator able to generate Relative or get direct OSC into Traktor then we are still stuck. I cannot for the life of me get a stable Bome translator to produce relative values from a slider in TouchOSC.

 

Never mind Just found the update waiting to be downloaded in the App Store looks like an interesting night in store tonight and a template I thought I nearly had ready to ship to its owner will need to be reworked :-|

 

Seems like relative mode in version 1.6 is not yet working properly. It is producing odd values and does not react properly to gestures. I can get sort close but its jumpy and the controller keeps reverting to quasi-analog modes. Absolute mode seems to work OK. If you do manage to get it working properly then please let me know how you set it up.

 

I'm buried in SCS.1 land this week, but have planned to give these new apps a run-through next week for another round of reviews. On a separate note, Phil, I need to chat with you for a bit when you get time. You have expertise on a subject I need a little visibility on.

 

Started on my own template.

Current Setup is

Xone 92 and 1D
2 x Kontrol X1s
Maschine

1st page is going to be what i need from the mixer section of Traktor other than what i get from the physical hardware (xone 92)

 

Page 01 of my layout

 

hey guys im using osculator and when i open the file and go to change the OSC routing to my ipad on the network it isnt there. Is there some sort of guide to link it all together? im not having any success with Osculator so far : /

 

Not bad mate, A constructive observation if you'll permit me.....
Try an keep about 20pixels clearance between the bottom of your rotaries and the top of any active control object below it, even if it is related to the rotary. I have found the error rate (wrong control selected) to be very high when trying to adjust the rotaries near the top and bottom of the range, and stacked close vertically. What you may find in your current design is that you accidently trigger the buttons (if they are buttons) just below Filter and key when you were trying adjust the rotary or the opposite.

Phil

 

Cheers phil will keep in mind

 

I find is that in any of the templates that ive downloded i can't get the crossfader to work. All other functions work fine. Am I doing something wrong? And which template can I use to simulate a real basic 2 deck layout with working crossfader.

 

Hi there

You may have some conflicting midi signals stopping the crossfader working.

In Traktor Preferences, do you have your in/out ports set to OSCulator/PD? You'll find them top right of the Controller Manager page.

 

Whose Templates are you using?
Check in OSCULATOR to see if the TouchOSC control is producing messages...
Does Traktor show its receiving messages (MIDI indicator blinking in the top of the UI)?

Phil

 

Phil please pv me I have stuff to show you and share and work from there. I to learn Puredata ....

Peace out