Csound Wiki FUBAR

[mark jamerson]

  The Csound Wiki has been completely bombarded with hacking, and I can't seem to find the revert option anywhere.  Is anyone still acting as administrator to it, or has it been abandoned?  Just curious.  

                                 Mark



      ____________________________________________________________________________________
Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  http://tools.search.yahoo.com/newsearch/category.php?category=shopping


Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[rasputin]

mark jamerson wrote:

  The Csound Wiki has been completely bombarded with hacking, and I can't seem to find the revert option anywhere.  Is anyone still acting as administrator to it, or has it been abandoned?  Just curious.  

                                 Mark

I had the idea: if there were a Csound WIKI, it might help address the problems of a Csound beginner (which I still consider myself to be.) So when I went to where it used to be, then found this posting, I was somewhat dejected.

I found the recent discussions with Jim Aikin very interesting since (a) he is definitely not a beginner when it comes to electronic music technology and (b) it was his goal to be able to write an article that would make Csound comprehensible to an interested musician, presumably relatively conversant with both electronic music and computer technology. Apparently he sort of abandoned the project as too intractable.

A wiki for Csound would have some definite advantages. One of the problems I continually encounter in my explorations is the detritus of the past. Csound is so venerable, and has been worked on by so many people, that the archives are littered with projects that have been superseded, discontinued or updated. Like CsoundVST to take just one example. Searching for that you find that it was included in some versions of Csound but not the latest, discussions of the Silence system, CsoundAC, and so forth. But there's no simple way to find out what (a) its latest status is and (b) how to simply use it in a particular host.

A wiki would allow for easy location of information about peoples' particular interests: Csound tutorials, various front ends that are still supported and/or used, GUIs and editors that are still relevant, the API and its hooks for various languages, real time and MIDI use, use as a VST, history, building from source on different platforms, etc. etc. Right now all that information is spread across hundreds of websites, countless articles in this forum, and elsewhere.

The biggest advantage of a wiki, the way I'm thinking now, is that hopefully only the newest information will go in at first. For instance, which version of Python you need to work with Csound, and how you need to install and configure it.

I could go on but this probably outlines my thoughts. Hopefully there is little enough controversy in Csound that there would need to be any moderation issues. Spammers and hackers are always a problem, of course, but other wikis seem to be able to operate.

Here's one for Python documentation http://www.python.org/doc/
One for Cakewalk's Project5 application http://p5.sonarama.com/index.php?title=Home
And the one for ChucK http://wiki.cs.princeton.edu/index.php/ChucK

None of these are perfect but they should roughly convey the idea...

[Michael Gogins]

There are several months between when a writer submits an article and when it shows up on newsstands. So it will take a while to see if Aikin's article shows up.

Regards,
Mike

-----Original Message-----

>From: rasputin <tims45@...>
>Sent: Jul 1, 2008 4:13 PM
>To: csound@...
>Subject: [Csnd] Re: Csound Wiki FUBAR -> leads to these thoughts
>
>
>
>mark jamerson wrote:
>>
>>
>>   The Csound Wiki has been completely bombarded with hacking, and I can't
>> seem to find the revert option anywhere.  Is anyone still acting as
>> administrator to it, or has it been abandoned?  Just curious.  
>>
>>                                  Mark
>>
>
>I had the idea: if there were a Csound WIKI, it might help address the
>problems of a Csound beginner (which I still consider myself to be.) So when
>I went to where it used to be, then found this posting, I was somewhat
>dejected.
>
>I found the recent discussions with Jim Aikin very interesting since (a) he
>is definitely not a beginner when it comes to electronic music technology
>and (b) it was his goal to be able to write an article that would make
>Csound comprehensible to an interested musician, presumably relatively
>conversant with both electronic music and computer technology. Apparently he
>sort of abandoned the project as too intractable.
>
>A wiki for Csound would have some definite advantages. One of the problems I
>continually encounter in my explorations is the detritus of the past. Csound
>is so venerable, and has been worked on by so many people, that the archives
>are littered with projects that have been superseded, discontinued or
>updated. Like CsoundVST to take just one example. Searching for that you
>find that it was included in some versions of Csound but not the latest,
>discussions of the Silence system, CsoundAC, and so forth. But there's no
>simple way to find out what (a) its latest status is and (b) how to simply
>use it in a particular host.
>
>A wiki would allow for easy location of information about peoples'
>particular interests: Csound tutorials, various front ends that are still
>supported and/or used, GUIs and editors that are still relevant, the API and
>its hooks for various languages, real time and MIDI use, use as a VST,
>history, building from source on different platforms, etc. etc. Right now
>all that information is spread across hundreds of websites, countless
>articles in this forum, and elsewhere.
>
>The biggest advantage of a wiki, the way I'm thinking now, is that hopefully
>only the newest information will go in at first. For instance, which version
>of Python you need to work with Csound, and how you need to install and
>configure it.
>
>I could go on but this probably outlines my thoughts. Hopefully there is
>little enough controversy in Csound that there would need to be any
>moderation issues. Spammers and hackers are always a problem, of course, but
>other wikis seem to be able to operate.
>
>Here's one for Python documentation http://www.python.org/doc/
>One for Cakewalk's Project5 application
>http://p5.sonarama.com/index.php?title=Home
>And the one for ChucK http://wiki.cs.princeton.edu/index.php/ChucK
>
>None of these are perfect but they should roughly convey the idea...
>--
>View this message in context: http://www.nabble.com/Csound-Wiki-FUBAR-tp14806903p18224377.html
>Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>
>Send bugs reports to this list.
>To unsubscribe, send email sympa@... with body "unsubscribe csound"

Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[rasputin]

Now that I think about it, I think I wrote wrongly; rather I believe he gave up on trying to use Csound as a VSTi, but did continue trying to explore it using blue...I'm sure if an article shows up in print it will be mentioned in this list.

Michael Gogins wrote:

There are several months between when a writer submits an article and when it shows up on newsstands. So it will take a while to see if Aikin's article shows up.

Regards,
Mike