this thread just convinced me to pick one up for 50quid from ebay anyway. i’m going to have a hell of a lot of fun mapping with this device 
If you need info, let me know.
cheers - i may well do 
i’ve had a quick gander at the docs i downloaded from the stanton site and they seem to explain it all - but i won’t know until i actually try i guess.
very interesting device this anyway. don’t think i’d like to have a solely touch sensitive set of controllers but having this one in the mix (literally 
) for effects or deck control (or who knows what) should be very cool.
edit: i seem to be going for the record for the largest set of cheap controllers here… not that the scs.3d was cheap when new but is a bargain 2nd hand.
Can someone tell me how to achieve this? I’m referring to the ability to only hold an effect while your finger is down on the SCS. Is it possible with the default traktor settings or do you need to use the generic settings, or change something in bome’s? I’ve always wanted this feature, to be able to use mine like a Kaoss pad.
I agree that you can really mess around with it just by changing the .tsi, I changed all the functions on my single unit to be ‘focus deck’ then I use all the deck B controls for alternative functions. For example you can have the deck B scratch mode control fx similar to Ean’s Fader FX mode. Now I’m thinking of making one of the deck B modes control the loop recorder since I’m running out of buttons on my APC40. I still mainly use my SCS for finding the first beat of a song since all my other controllers are button-based, and it’s just great to have it just in case I need to throw in a track that I haven’t gridded.
I have to chime in on this.
I don’t personally own the SCS3 system, but a close friend of mine does. He used Torq with Numark TT100’s for years (and recently has been messing about with Torq 2.0 with the tables again) and decided he wanted/needed something more portable. And so he bought (under my recommendation and his want for complete touch control) the SCS3 system and Traktor.
It’s neat. It takes some time to get familiar with. It’s not like hopping on tables or CDJ’s and being used to the layout completely. Messing around with the mixer is different, but not in a bad way.
Honestly, it’s fun. It’s VERY portable which is also great.
If you have interest in the touch capabilities, it’s great. The only issue being is mapping to a certain extent, but people come out with mappings fairly often for all controllers, or you can buckle down and do it yourself.
If you are wanting an extremely neat portable setup (and hot damn does it look cool to boot) then I’d say go for it. If you want something more professional? Then go for that. The different parts can also work great down the line for cue and FX controls, so you aren’t losing anything if you decide to go full out DVS later as well.
Sure. Map to the controller directly (no DaRouter). Use the MIDI spec to do the mapping manually in Traktor is going to be easier than trying to learn it, but it’s possible either way.
The SCS.3d’s “natural” MIDI output is what we called “super slider mode”, where every slider area (anything that looks like it would generate a CC) sends a note on/off, a relative CC, and an absolute CC. So if you wanted to use the gain strip for effect on/off and dry/wet, you would map the following…
Effect on/off - 90 07 ** (and it would be a toggle)
Effect dry/wet - B0 07 ** (B0 08 ** is the relative message, but it’s not necessary since this isn’t a physical control and gets app feedback).
To drive your LED feedback, your dry/wet output message should be set to B0 07 ** (where ** is 28 to 2F for a peak meter pattern). Be sure to use blend.
i read what u said before about it sending relative as well as absolute values but it didn’t stick in my thick skull for some reason… that is pretty awesome! (plus the note on/off is an added bonus ofc)
i do like the idea of the circular touch strip area as a virtual jog wheel but mostly i think it’s going to make a fantastic effects control surface…
finally had time to write some code for this controller and i have to say that it really is one amazing controller…
fantastic midi spec too. i’m not using the darouter so not sure what that pushes out - but the native midi implementation is ideal. using my own app i’ve mostly replicated how darouter sets it up for now, tho using the two top outer buttons as toggle modifiers and the bottom two as hold/shift ones - which gives me stacks of layers to play with when you include in the fx/eq/loop/trig/vinyl/deck buttons at the top.
i think i’ve setup the various modes of the central area to be the same as darouter atm, but is simple to change, i love being able to change how the central area operates (circle, buttons, faders) whenever i need to.
shame tho that by default in button mode you get 4 buttons on the left, 4 on the right and a fader in the middle, i’m changing that to work as a 3x4 bank of buttons which seems more useful. shame its not possible to squeeze a 4x4 out of it i guess tho.
had a look on ebay and people seem to be wanting silly money for these atm, but i only paid about 50 quid for mine which i think is a steal 
i loooove the fact that any control acting like a fader sends out a relative message (ala an encoder) as well as absolute, not to mention a note on and note off too…
how come these things arent more popular?
i wouldnt mind an scs.3m, not to replace an actual mixer, but for fx or something but i havent seen one of those go for a reasonable price.
i suspect whatever controller(s) i end up using in a few years i’ll still keep this scs.3d
edit: as well as the 3 modes they document you can also make the central area have 2 faders/sliders and one column of buttons:
– buttons + faders 5+6
– F0 00 01 60 01 01 f7
– faders 4,5 + buttons
– F0 00 01 60 01 02 f7
just in case anyone is interested this is my lua code that does the darouter type stuff http://djism.com/lua/scs3d.lua
need to work on the led feedback for the sliders next and the scs.3d has some neat tricks for that…
What program are you mapping this controller for? Are you using bomes or something to get around darouter?
i’ll probably use the scs.3d mostly for traktor but might map a page of controls to use for ableton too - not sure.
i’m using my own midimasher software to run everything. it’s sort of a “bomes meets midikatapult” type app i guess. it allows me to write my actual config in lua, like that example lua file i listed. i use virtual midi ports to communicate with traktor and ableton which allows any element of any controller to use traktor or ableton or any other app i might want to use.
hooking into traktor is via this lua file in conjunction with a tsi file and i have other configs like this one that lets me create buttons/faders ala midikatapult and even create a virtual midifighter (which then uses the vanilla midifighter tsi’s in traktor) in either normal or 4banks mode from any controller that has a grid of 4x4 pads.
i just want to be able to use all my controllers together as basically a single control surface and not be limitted by traktors (or other app) mappings, modifiers etc.
certainly impressed with the scs.3d anyway. for now going to make it control either deck a or b unless i select the top/right button around the circular area that then adds a whole new set of layers that i’ll use to control the sample decks.
customizing actual mappings from my app to something like traktor is actually pretty simple, for example this line would link the play button from the scs.3d when it’s on its virtual page 0 (deck a) to play_a in traktor and the same button to play_b when it’s on its page 1 (deck b) with feedback from traktor etc (first 2 lines are to connect to the appropriate midi port):
open_midi_device(“traktor”, “traktor”, “Traktor to MM”, “MM to Traktor”, 2);
open_midi_device(“scs3d”, “scs3d”, “SCS.3d”, “SCS.3d”, 2);
create_button(“scs3d”, “play”, 0, “traktor”, “play_a”)
create_button(“scs3d”, “play”, 1, “traktor”, “play_b”)
and since lua is just a coding language you can use as many variables as modifiers to put whatever logic in there u want. the create_button() function is just some lua code that creates a pipe between the two devices.
i saw a guy using bomes to make the circular led’s ‘spin’ like on a cdj, turns out this is all the code i needed to do the same thing and looks pretty cool…
capture_event("traktor", "beat_phase_monitor_a", 0, function(d, e, v, p)
if v ~= scs3d_cache["scs3d"]["beat_phase_a"] then
scs3d_cache["scs3d"]["beat_phase_a"] = v
send_event("scs3d", "fader3", scs3d_cache["scs3d"]["beat_phase_a"])
end
end)
tho for some reason in my tsi i had to set the range for the beat phase monitor midi to 0..17
I can see that you have worked a little on the scs3ds code since last time we spoke! Looking good!
By finding this thread I found the reply for that PM I sent aswell, so no need to reply that zestoi.
This has made me almost certain I will pick one of these up to and learn to write some code for your program. Looks like great fun!
I’m one of those guys who find tinkering to be almost as fun as playing. So much fun to explore! Just a never ending desire to find out what can be done and how to make the programs and controllers to work the way I want them to.
Good times,
I probably will bother you both with questions zestoi and nem0nic if I follow through with this…
Hope thats cool
Cheers
//Joel
zestoi, I’m thinking about making a four deck layout with your software. Linking one layer of deckspecific stuff onto each of the four hardware buttons at the bottom and then make sublayers for different functions. Would that be doable or am I spinning out of control here?
I recall reading about three colour feedback on the LEDs so I suppose it would be possible to make three cycling layers for each of the six mode buttons or perhaps just stick with two to keep it simple
Would be great if you guys could let me know if I’m on track or losing it.
Cheers
edit: btw, I intend to have transportcontrol on another unit so wont need them anyways.
that should work ok, that’s a lot of layers all in all - no reason why not tho.
[quote]I recall reading about three colour feedback on the LEDs so I suppose it would be possible to make three cycling layers for each of the six mode buttons or perhaps just stick with two to keep it simple
[/quote]
yep - there’s 2 colors for most buttons from the two colors of led, red + blue, making the third color a kind of purple.
i would use the 4 bottom buttons to select the deck and then the 6 mode buttons to select the mode for that deck - making 24 total layers - which is still quite a lot… i’m not sure why you’d need/want to use the mode buttons in cycling mode? could be useful if a modifier that is independant of the overall layer or something - but probably too confusing to use.
you’re probably right about that beeing a bit much!
Will probably make a 4layers with 6 functions to start with and then use extra layers to work in experiment mappings.
//Joel
a couple of more q’s come to mind…
are the layer layouts and notes fixed as in the generic presetguide found at stantons homepage or is it possible to chose to put three faders on all six modes?
You say that you remade the triggerpattern to 3x4, is that space the same way as seen in video from the mixxx software crew? one point every second led along the sliders.
And how do you set that up? I have a theory… not sure it’s right though.
Looks like so much fun mapping and using this unit. Still a little scared to go touch though.
Cheers
edit: one more thing, when using the circular bit does that also have an absolute cc? And where is the startingpoint? Where on the “clock”?
yes u can do that. the scs3d just changes it’s mode when a sysex message is received - so just need to ensure the one u need is sent out from the layer-change call. if u just wanted the fader mode all the time then no need to send out anything after startup ofc.
i haven’t seen the video. i just divided up the central vertical slider into the same 4 areas u get from the left and right hand ones. it’s a great idea in theory but not sure now so much in practice as i have found myself pressing the wrong ones at time - hence why i guess stanton decided to just use it as a single fader even in button mode.
the faders send out a note on inititally followed by the cc’s for absolute and relative movement so my code uses the noteon to indicate when it has been pressed but works out what “button” has been pressed (and then process it) once it gets the absolute cc value.
so something like:
-
if we get a non zero noteon message remember that the user has pressed a “button” somewhere on the fader
-
if we get a cc work out what “button” has been pressed and send noteon message for that button if we haven’t done already
-
if we get a noteoff message send/process the noteoff for the “button” that was used
this is the midi coming out of that fader area:
-- central bottom fader
add_control("fader5_press", 1, "note", 1);
add_control("fader5", 1, "cc", 1);
add_control("fader5_relative", 1, "cc", 2);
[quote]
edit: one more thing, when using the circular bit does that also have an absolute cc? And where is the startingpoint? Where on the “clock”?[/quote]
all faders have relative and absolute messages. in mm events like faderX are the absolute while faderX_relative is the relative. faderX_press is the noteon/off. don’t remember where the circular control starts off hand - 12 oclock i think/presume
The same way I thought it could be done, probably done that way in that mixxx video aswell. Can’t find it now though.
Great beeing able to swap the layout to…
Think I would end up using the platter layout the most at the moment, and probably not use trigger at all. I like the launchpad
Now it just comes down to make the choice, scs3d or not. Been looking at the Reloop contour aswell, has great layers from scratch laid out pretty much as I would want them. And all encoders and minifaders give added functionality otherwise needed to add by another small unit. However only heard bad things about reloop customer service. and would not give me the same flexibility and portability due to its weight.
Since I don’t intend to use it in a traditional fashion the tradional layout might be confusing. Still think physical controllers are a plus…
these choices