TSI File for Stanton SCS.3D DAScratch Traktor Pro 2

[zestoi]

a challenge question and a captcha to sign up just so i could see the attachment and still i need my acct approved by a moderator or something - they don't make it easy

just checking my old files and i have 4 spreadsheets for the scs.3d in various formats, 2 images and the pdf. i can upload those to djism.com somewhere if needed. only really bought that domain to use for midimasher and can certainly put other pages/subdomains on it. i don't have any info on the scs.3m tho

[doombadger]

No they do love you to jump through hoops before allowing you to appreciate the empty desolation. It feels like turning up at a barn after driving for hours, following some directions recorded on a rig line only to discover that the party was last weekend and all that's left is a ton of silver noz canisters and the brightly coloured corpses of shrivelled ballons.

Sorry, had a mild flashback there somewhat. lol.

Those files you described are exactly what that zip contains. I do think a resource for files and documentation of interest and use to the community is a sensible idea. I can't be the only one whose felt frustrated by a basic lack of fundamental information. It's not that it isn't out there as I'm certain it all is, it just seems to be so scattered, fragmented and in some cases, regarded as privileged information. Sites like this are great for the sharing of ideas and the rapid development of the results but as a result they are very hard to search and unless you know exactly what you're looking for it can be almost impossible to find specific information.

I just think people would rather be making music. I know I would.

[zestoi]

No they do love you to jump through hoops before allowing you to appreciate the empty desolation. It feels like turning up at a barn after driving for hours, following some directions recorded on a rig line only to discover that the party was last weekend and all that's left is a ton of silver noz canisters and the brightly coloured corpses of shrivelled ballons.

Sorry, had a mild flashback there somewhat. lol.

you paint a very tempting picture there

Those files you described are exactly what that zip contains. I do think a resource for files and documentation of interest and use to the community is a sensible idea. I can't be the only one whose felt frustrated by a basic lack of fundamental information. It's not that it isn't out there as I'm certain it all is, it just seems to be so scattered, fragmented and in some cases, regarded as privileged information. Sites like this are great for the sharing of ideas and the rapid development of the results but as a result they are very hard to search and unless you know exactly what you're looking for it can be almost impossible to find specific information.

probably would be good for quite a few controllers really but i doubt manufacturers would appreciate the info being on someone else's website, else i'd try and do something about it. getting hold of that scs.3d info before tho certainly seemed a lot easier than now... once i have a midimasher device config file for a controller than i don't need the docs - but i know most people would rather read a doc than some LUA code

I just think people would rather be making music. I know I would.

indeed

[doombadger]

Yeah, but what they like and whats legal are two completely different things. If Stanton don't like me giving away the info regarding how to use the equipment they've generously sold to their customers for a profit then I'll be quite happy for them to get in touch and cry about it. They can even put their concerns regarding the matter onto a piece paper, put it in a envelope, seal it, fold it up, selotape it to a frisbee and then fling it over rainbow all the way to Candy Mountain. They can all come round my gaff and tell me in person if they like or alternatively they can tell someone that cares.

At the end of the day, if they did this no one else would need to....

...and they know it

[zestoi]

would be quite some frisbee to get all the way over the rainbow and off to candy mountain tho i have quite a collection of docs, specs and notes for a whole heap of controllers. mostly as i've been interested in their midi specs, not because i actually own the controllers. getting this kind of info together someplace would be a pretty cool idea.

[doombadger]

Definitely. I know there are a LOT of controllers out there in the wild, tried and tested favourites, obscure niche oddities and bleeding edge, four figure, widowmakers but just a quick look at a well known Android development forum proves the concept. By keeping an updated index of links to the essentials like guides, tutorials, manufacturer presets and the latest community developments all together in a device specific thread everyone using that bit of kit can find what they need and share what they have. Beginners get support, information and guidance whilst the experienced wizards get to focus on homebrew development.

I must add this is not a criticism of this forum or any other (with the odd possible exception, lol) Everything I've learnt in the past 6 months I've only learnt by reading and learning from experiences and collected wisdom of the community. I believe a site dedicated to an index of information would compliment the other forums rather than compete with them.

Or, maybe it's something that could feasibly be worked into an existing website and slowly expand from there.

[zestoi]

i have plenty of server space if u wanted to try out any ideas. i have two dedicated servers of my own at the moment. even if that was only to collect the info together and see what kind of formats worked. as far as actual forum software goes tho there really is only one winner, vb, and that's not free. i wonder if a wiki type format would work for something like this... or something more structured that just had a central page per device and/or downloads. not really sure...

[doombadger]

Well, I'm thinking the easiest thing is to sort by manufacturer, then by model and finally split into sub catogories containing the file links. First things to put IMO would be [GUIDE], [TUT], [HOW_TO] or similar giving manufacturer and community readme.txt, user guides, first step beginners walkthroughs and other tutorials.

Also having something like [SETUP] or [CONFIG] will clearly show docs that cover first time setup and also examples of more intricate, advanced configurations. The APC40 was epic. Unboxed, plugged in, worked. Booyah. The Saffire Pro24 was slightly different. Only some FW chipsets were 100% compatible and under Win7 64bit the driver only plays nice with the TI legacy FW drivers. Add to that MixControl being less than intuitive and you can see where I'm coming from. Luckily, Focusrite have a decent support page. The SCS.3 was a ballache from the moment it came out the box. Slightly OT but it works well as an example of how very little things often make a very big difference.

Basically, as long as files are labelled using a naming convention agreed by concensus to be informative to veterans and clear to beginners it should be more than fit for purpose. Hell, I've been to ftp pages that just contain a list of cryptically named directories and found more useful data by poking around than I did asking n00bie style 'heeeeelp' questions in the support forum. Maybe I'm thick but it took me 2 days of searching just to find the telephone number for Stanton UK support.

I reckon the best bet is to throw it out to the community and see what people think. A) Do they want it? B) Would they use it? And, most importantly of all C) Would they contribute to it?

Call me a pessimist but quite frankly I don't fancy our chances of sourcing all that material on our own. If I MUST learn Python I'm using it for scripting not web harvesters

[zestoi]

sounds good and agreed that basically a "file browsing" type interface would probably work fine. other problem apart from whether people would contribute is policing it i guess and keeping it in a sane state. and agreed it would only work if other people *would* contribute.

[CONFIG] could get interesting - would need subsections for each app. i'm keeping notes/files in diff dirs for mixxx/traktor/vdj so far.

nice lol re: python and web harvesting - but that's an idea kidding... my python skills are less than minimal, i tend to use perl or php for any web scripting, but i'm open to trying new stuff.

[EquaLies]

any of you guys still around?