Stanto SCS.3?

[NemSim]

What does DJTT think of the Stanton SCS.3 system?

http://www.stantondj.com/stanton-con...s/system3.html

It looks kinda fun to me, I would love to implement it with my Traktor PRO setup. eBay has them for a good $200 to $300, which doesn't seem like a bad investment for me.

[VanGogo]

I liked mine. I really liked the touch control for Fx in particular, and I still have it forsale.

I just moved on to the KS4.

[NemSim]

Was it fairly intuitive to perform on? I'm worried about all the touch stuff being a novelty that makes it hard to do an actual performance on. I would like to have it as sort of a center piece to my setup, in addition to the X1 and whenever I find an iPad.

[nukage]

The default traktor mapping is quite good, you can customize it somewhat, but a lot of people complain that it's not customizable enough unless you learn Bome's midi translator, which is the software they use to create the 'DaRouter' application. IMO it's a good little controller, some people use it along a DVS to do loops and cue points, others use it by itself, personally I use my single unit alongside my APC-40 and it's mostly used as a jog wheel to do track cueing and the occasional scratching. You can set it up to do a kind of 'fader fx' mode like the VCI-100 mapping too if you are creative with mappings.

[pepperoncini]

there is no preset for traktor pro 2 as far as I know, I may have to ditch mine unless I find one that at least works. any help???

[djproben]

They took forever getting a preset for Traktor Pro 1 when it came out; and since Traktor had the audacity to be released right after the SCS3d, it was really annoying. When the presets did finally come out they were buried on discussion boards and there were multiple versions which made it even more difficult. I bought the SCS when it first came out and then it sat unused for months because I had been hoping to use it with Traktor Pro. So I'm not surprised if it's happening again with Traktor Pro 2. I always really liked this controller but support is difficult at best. Suppose I should sell mine at some point since I never use it anymore....

[tito]

The idea is great but the support it is very limited because all the da router implementation it is just plain stupid to put a software between software and the hardware, it is buggy. So you can map it without da router but you lost the functionallity. They did it better with the 3m because you can change firmware presets in the hardware. In the other hand they took the approach that they are not obligated to do presets sending the product to doom. I really like the idea, the concept and the lack of moving parts but for example mapping the led feedback it is nightmare or the insinuation to buy bomes and learning how to use it to really customize the product just another pr stupid move

[nem0nic]

I bought the SCS when it first came out and then it sat unused for months because I had been hoping to use it with Traktor Pro...

You're exaggerating a bit here to add drama. First of all, there was nothing stopping you from using the SCS.3d with Traktor Pro from the onset. It's a MIDI device. For that matter, there's nothing stopping anyone from using it with Traktor 2.

As far as presets being on the forums go, the presets were on the forums when in beta, and bundled into DaRouter when official. The different presets were for different software packages. If a beta preset was updated, it was placed in the existing thread replacing the old preset. ALL preset threads were stickied to make them easy to find.

The idea is great but the support it is very limited because all the da router implementation it is just plain stupid to put a software between software and the hardware, it is buggy.

No offense, but the only reason you think the software layer is stupid is because you have no idea at all what it did. If it wasn't for the DaRouter software, we wouldn't have been compatible with Serato (because of their software limitations - not ours). There would have been no LED feedback in several programs as well because they didn't support it at the time (we generated the LED feedback in the preset). It also allowed us to work around other software issues (like MIDI buffering problems). In the case of the SCS.1, it enabled us to implement a HUI preset for Ableton Live and most other DAWs out there. And of course, it allowed us to give a single layer controller multiple layouts and functions.

As for it being buggy, the same kind of software sits in the middle of a LOT of products - but they just hide the front end and install it like a driver. Wacom and Frontier Design Group are just 2 examples.

I really like the idea, the concept and the lack of moving parts but for example mapping the led feedback it is nightmare or the insinuation to buy bomes and learning how to use it to really customize the product just another pr stupid move

And this is the biggest single misconception surrounding the SCS.3 controllers. You ALWAYS had the option of remapping the controllers by changing the TSI. And that was what 99% of users needed to do to make what they wanted. Between Traktor's ability to alias controllers (so no need to worry about conflicts between different controllers), and DaRouter's ability to aggregate multiple devices into a single controller, I can think of only a handful of situations where you would need to change the actual control messaging. And even then, you had the option of going with the generic preset if you wanted a different mapping.

LED mapping was easy because it was all on a macro. You only ever needed one massage to control single LEDs OR clusters (like peak meters). And this is also exactly how Traktor works. To remap an LED to a different function, look in the TSI for the existing function and write down the message used to write to those LEDs. then delete the old message and add in the new one, copying the settings you wrote down. Or you could just look at the MIDI spec and use that as your guide instead. This is no different than any other controller. Feedback messages are defined on ANY controller. If you don't send what the hardware is looking for, it's not going to work right.

[tito]

I did a lot of mappings with and without da router. The midi specs are useless if you want to map with darouter in the other hand without da router you can map exactly the way you wanted, feedback included, but you can not have vinyl mode and trigger mode in the center area like using da router. For me it is the major flaw and all the people I know who bought is no longer using it. It takes a long time to map the feedback with a lot of trial and error because the feedback messages are different that the input ones.at the end a lot o hassle with so so results. At the end most of the scs3 became paperweights because the lack of simplicity to make your own mappings, you can see it in the forums and a lot of customers disappointed . For example I have a vci100 and xone 4d and I have done my own mappings to do the controllers exactly what I want without hassle. And let's face it darouter is buggy and took a lot of versions to be semi-stable. Still I have it and I think someone will solve those issues with a software or firmware solution like tech tools did with the vci100, the da scratch it is a clear example of a product that could been so great but the approach to make it compatible was not a good one. Take the scm3 and the options to change the behavior of the controller without the software was a great step forward but I see more possibilities on the dascratch. I know you were working at Stanton and did a great support job but the point of view that "you can do a lot but you need bomes and get a lot of time consuming effort put a lot of people off the product. 5 of 5 people that I know who got it, abandoned it because there are plenty of more user friendly solutions.
Cheers.

[nem0nic]

For me it is the major flaw and all the people I know who bought is no longer using it.

You're asking for the ability to change the FUNCTIONALITY of the controller - not the ability to map towards it. And NO CONTROLLER on the market lets you do this. Some controllers let you change small things, like what particular CC message an encoder sends, but they don't give you multiple layouts with wildly changing functionality like the SCS.3 does. So in that aspect, the SCS.3 controllers operate just like any other controller. The fact that Stanton used DaRouter to give them so much more functionality built up the expectation that you'd be able to change those behaviors. And it IS possible through BMT programming (on other controllers this would NOT be possible, because that behavior would be handled via firmware and not available to the user at all).

It takes a long time to map the feedback with a lot of trial and error because the feedback messages are different that the input ones.

No, it doesn't take any trial and error. The LEDs are being written to in the TSI. As I said before, all you need to do is look at the message in the TSI and COPY IT. If you're having a problem with the last byte message on an LED array (like a peak meter), and you want it to do a sweep pattern instead of a boost/cut, then you can either look at the MIDI spec (the last bytes don't change), or just keep moving up in value until you hit the next macro.

At the end most of the scs3 became paperweights because the lack of simplicity to make your own mappings, you can see it in the forums and a lot of customers disappointed .

There's a handful of users on the Stanton forums, and THOUSANDS of users who bought the SCS.3 controllers (it's very safe to say there are tens of thousands of SCS.3 controllers in the market). You have no idea what happened to "most of the scs3".

For example I have a vci100 and xone 4d and I have done my own mappings to do the controllers exactly what I want without hassle.

And both of those controllers combined don't have HALF the messaging or feedback the SCS.3d does even without a preset.

And let's face it darouter is buggy and took a lot of versions to be semi-stable.

No, DaRouter hasn't been buggy since the initial release (where there as a problem with the virtual ports in newer operating systems). If you were having performance issues with DaRouter, they were almost always down to one of 3 things (sketchy USB power, AV software or user rights not allowing the virtual driver to be installed, or a corrupt installation in the first place). All 3 of these issues were well documented on both the forums and by service personnel.

I know you were working at Stanton and did a great support job but the point of view that "you can do a lot but you need bomes and get a lot of time consuming effort put a lot of people off the product. 5 of 5 people that I know who got it, abandoned it because there are plenty of more user friendly solutions.

Just because you keep saying it doesn't make it true. Again, you do not need BMT to do 99% of what a typical user would need to do to remap an SCS.3 controller. Between the option of doing a direct mapping and using one of the many different presets available, there is a wide variety of mappings possible. Now, if you wanted to do something like change an absolute encoder to relative, that would require a preset change - but at least it's possible. How do I change the output of an encoder on the Xone 4D (let's say I wanted to change CC37 or CC45 to an absolute message)? Or how would I change a button's output from a note to a CC? How is the Xone 4D MIDI implementation any more flexible than the SCS.3?