Stanto SCS.3?

Quote:

---

Originally Posted by djproben

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...

Code:

---

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.

Quote:

---

Originally Posted by ZiiK

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?

---

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 ;)

---

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"?

Quote:

---

Originally Posted by ZiiK

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?

---

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.

Quote:

---

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.

---

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.

Quote:

---

And how do you set that up? I have a theory... not sure it's right though.

---

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:

Code:

---

-- 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"?

---

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 ;)