« Return to Thread: sc crossplatform future (was re: sc3 with emacs on windows?)

Re: sc crossplatform future (was re: sc3 with emacs on windows?)

by andrea valle-3 :: Rate this Message:

Reply to Author | View in Thread


I think it's more than that. Even with the best of documentation, SC is hard to wrap one's head around. And new users, even those willing to put a lot of effort into learning SC will be wondering "why should I use SC rather than [fill in the blank here]"? The documentation does not always provide the necessary motivation. Just as one example, you recently suggested checking out FlowView. The documentation for that class is not much more than a list of examples. That's the kind of documentation you don't read, you reverse-engineer it. Now think how someone whose favorite programs are things like Live or Reason will feel about documentation like that. Now let's get a bit more basic. Someone who is new to SC would probably read "Getting Started with SuperCollider." Is there anything in there that tells me why I would want to use SC rather than Live, Csound, MaxMSP, my IRCAM servant, or ProTools plugins? Or let's say I've gotten a bit intrepid and want to write some classes. The first thing the Class documentation informs me is:


I don't know If I succeeded but that's way (a part from linguistic issues, indeed) I wrote the Italian manual.
e.g.
http://www.cirma.unito.it/andrea/sw/sc/prd_tSCIRMA_a5.pdf

A I have to teach SC from scratch, I had to introduce all: classes, syntax, GUI, architecure etc
Section 2.2. is dedicated to very short -but helpful for newbies- list of "reasons" why one could use SC.
Many different applications are listened, obviously just with the idea of showing variety.

If I have to recollect my original SC experience, I have to say that a friend of mine showed it to him, and I get so strongly conquered that I decided to buy a Mac (there weren't other versions).
Then, I understood nothing for a big time. So I made a long detour on OOP with Python (I knew it before, but I used it in an imperative way) and got back to SC.
But really, you cannot compare SC to Reason or Live. It's just much more complex, and much more powerful. And it's much more complex to grasp than PD. But it's pretty logical: it's really a general language plus a client/server architecture plus a sequencing system plus DSP etc

But I would like to have a general e.g. Qt program, the same on all platform, and then specific flavours (Cocoa, Emacs).
Frankly, I have never understood the name "psycollider". I guess it's for some historical reason. But you have the idea that you are using something different from mac/Linux.


Best

-a-




--------------------------------------------------
Andrea Valle
--------------------------------------------------
CIRMA - DAMS
Università degli Studi di Torino
--------------------------------------------------


"
Think of it as seasoning
. noise [salt] is boring
. F(blah) [food without salt] can be boring
. F(noise, blah) can be really tasty
"
(Ken Perlin on noise)






_______________________________________________
sc-users mailing list
sc-users@...
http://lists.create.ucsb.edu/mailman/listinfo/sc-users

 « Return to Thread: sc crossplatform future (was re: sc3 with emacs on windows?)

LightInTheBox - Buy quality products at wholesale price!