Quantcast

GitHub Migration: Status

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

GitHub Migration: Status

Steven Yi
Hi All,

I'm currently working on migrating tickets for Blue from Sourceforge
to GitHub.  I'm using a script from:

https://github.com/ttencate/sf2github

But I've had to modify it to work.  I'm still editing things to get
them to work.  One thing is that there is an option to assign from SF
Username to Github username.  Currently if the SF Username is not
found, it just auto assigns to me as the creator of the ticket or
comment. I think it would be nice if I could get Github usernames from
people who have filed tickets so that I can auto-create those with
your user as the creator.  If you have filed a ticket on SF, could you
send me your Github username offlist to me?

BTW: To get a picture of what the final will look like, you can look
at this project:

https://github.com/kunstmusik/test-project

I have been importing and closing tickets over and over as I fine tune
the script.  To note, the tickets all show up on your user activity
feed, but I think once I delete the test-project, those tickets will
disappear from the feed.  I'm planning to refine the script then use
it one last time with the actual Blue project as a final migration.

Thanks!
steven

------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.  Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
Bluemusic-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/bluemusic-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: GitHub Migration: Status

Steven Yi
Also to note, the link to the issues is:

https://github.com/kunstmusik/test-project/issues

I'll also be going through and trying to close out any tickets that
are out-of-date, wont-fix, or already-done.

Thanks!
steven

On Tue, Feb 11, 2014 at 3:55 PM, Steven Yi <[hidden email]> wrote:

> Hi All,
>
> I'm currently working on migrating tickets for Blue from Sourceforge
> to GitHub.  I'm using a script from:
>
> https://github.com/ttencate/sf2github
>
> But I've had to modify it to work.  I'm still editing things to get
> them to work.  One thing is that there is an option to assign from SF
> Username to Github username.  Currently if the SF Username is not
> found, it just auto assigns to me as the creator of the ticket or
> comment. I think it would be nice if I could get Github usernames from
> people who have filed tickets so that I can auto-create those with
> your user as the creator.  If you have filed a ticket on SF, could you
> send me your Github username offlist to me?
>
> BTW: To get a picture of what the final will look like, you can look
> at this project:
>
> https://github.com/kunstmusik/test-project
>
> I have been importing and closing tickets over and over as I fine tune
> the script.  To note, the tickets all show up on your user activity
> feed, but I think once I delete the test-project, those tickets will
> disappear from the feed.  I'm planning to refine the script then use
> it one last time with the actual Blue project as a final migration.
>
> Thanks!
> steven

------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.  Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
Bluemusic-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/bluemusic-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: GitHub Migration: Status

Steven Yi
Hi All,

So I misunderstood something.  It looks like ownership of tickets is
limited to only the person importing the tickets, which has to be the
project owner (which is me).  The script's README mentions:

Limitations:

All issues and comments will be owned by the project's owner on
GitHub, but mention the SF username of the original submitter.

Creation times will be the date of the import, not the creation time
from SourceForge. (However, most recently updated tracker items will
be the most recently added ones after the import: I.e., the ordering
is preserved)


This makes sense, as you shouldn't be allowed to create tickets for
other users. :)  So that will be a limitation. The part where you can
modify the user names has to do with asignee, or whom the ticket is
assigned to.  You can modify that as the asignee has to be a member of
the project for it to work, which preserves aspects of permissions.
In this case, all the tickets have been assigned to me anyways on
Sourceforge, so we're good there.

I took a look at some of the other feature requests and a lot of them
seem like it'd be better to address more fully rather than just close
out at this time.  I think it might be easier to then just migrate and
address within the new system as time permits.

My plan at the moment is:

1. Await comments on state of migrated tickets by users (will wait
until Thursday)

2. Migrate Tickets

3. Close out old trackers on Sourceforge, as well as finally close out
git repo on Sourceforge.

4. Modify "Report a Bug" and "Request Enhancment" options within Blue
to direct to GitHub.


For users, all new tickets would go into Github.  For developers,
commits should have "Issue #xxx" instead of "Bug #xxx" or "RFE #xxx"
and the issue # should refer to the Github #.

Thanks!
steven


On Tue, Feb 11, 2014 at 4:04 PM, Steven Yi <[hidden email]> wrote:

> Also to note, the link to the issues is:
>
> https://github.com/kunstmusik/test-project/issues
>
> I'll also be going through and trying to close out any tickets that
> are out-of-date, wont-fix, or already-done.
>
> Thanks!
> steven
>
> On Tue, Feb 11, 2014 at 3:55 PM, Steven Yi <[hidden email]> wrote:
>> Hi All,
>>
>> I'm currently working on migrating tickets for Blue from Sourceforge
>> to GitHub.  I'm using a script from:
>>
>> https://github.com/ttencate/sf2github
>>
>> But I've had to modify it to work.  I'm still editing things to get
>> them to work.  One thing is that there is an option to assign from SF
>> Username to Github username.  Currently if the SF Username is not
>> found, it just auto assigns to me as the creator of the ticket or
>> comment. I think it would be nice if I could get Github usernames from
>> people who have filed tickets so that I can auto-create those with
>> your user as the creator.  If you have filed a ticket on SF, could you
>> send me your Github username offlist to me?
>>
>> BTW: To get a picture of what the final will look like, you can look
>> at this project:
>>
>> https://github.com/kunstmusik/test-project
>>
>> I have been importing and closing tickets over and over as I fine tune
>> the script.  To note, the tickets all show up on your user activity
>> feed, but I think once I delete the test-project, those tickets will
>> disappear from the feed.  I'm planning to refine the script then use
>> it one last time with the actual Blue project as a final migration.
>>
>> Thanks!
>> steven

------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.  Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
Bluemusic-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/bluemusic-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: GitHub Migration: Status

menno
Hi Steven,

i have no idea and experience with Github, so i cannot say much about it.
But i was looking through the list of Enhancements and Bugs and noticed some entries that, to my opinion, are obsolete or mentioned more than once and can be closed as far as i can see. (I cannot see who wrote them, but sometimes i recognize my English Style :) )
Here is the list:
151/104
68
42
2*69
76=35=13
78 = nonsense ( i can say it because it is mine!)

Q: at one point i would like to write a blog about the use of nGen, AthenaCL and Common Music in Blue, about the strength and differences of these Algorithm Generators. Is there a good place in the Blue pages to maintain such a blog?
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: GitHub Migration: Status

Steven Yi
Hi Menno,

Thanks for that list.  This is what I did with them:

151 - this hasn't been implemented, but I'm not sure I will implement
it or have comments for soundObjects, needs more thought
104 - grid has been implemented, but not the part of the ticket asking
for coordinates
69 - 68 - closed it
42 - closed it
69 - closed it
76 - left open
35 - closed it
13 - closed it
78 - closed it

For a blog kind of entry, there isn't anything on the blue site for
this at the moment. If you wanted to contribute something to the
manual as a tutorial, that might work.  Otherwise, I could maybe add
some kind of feature for blogging to the blue site.  I've been
re-imagining the Blue website off and on for a while, making the user
account have more features and the site and program more social.  This
means a re-imagining of BlueShare for versions/comments/ratings, RSS
feeds for things in the site, etc.  At the moment though, I've had to
put that aside (seems like it's been on the side for a very long time
though!).

Thanks!
steven

On Thu, Feb 13, 2014 at 3:31 AM, menno <[hidden email]> wrote:

> Hi Steven,
>
> i have no idea and experience with Github, so i cannot say much about it.
> But i was looking through the list of Enhancements and Bugs and noticed some
> entries that, to my opinion, are obsolete or mentioned more than once and
> can be closed as far as i can see. (I cannot see who wrote them, but
> sometimes i recognize my English Style :) )
> Here is the list:
> 151/104
> 68
> 42
> 2*69
> 76=35=13
> 78 = nonsense ( i can say it because it is mine!)
>
> Q: at one point i would like to write a blog about the use of nGen, AthenaCL
> and Common Music in Blue, about the strength and differences of these
> Algorithm Generators. Is there a good place in the Blue pages to maintain
> such a blog?
>
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/GitHub-Migration-Status-tp5732528p5732575.html
> Sent from the Csound - Blue - User mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Android apps run on BlackBerry 10
> Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
> Now with support for Jelly Bean, Bluetooth, Mapview and more.
> Get your Android app in front of a whole new audience.  Start now.
> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
> _______________________________________________
> Bluemusic-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/bluemusic-users

------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.  Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
Bluemusic-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/bluemusic-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: GitHub Migration: Status

menno
i see in the blue manual file:///home/menno/bin/blue/manual/html/ar02s04.html that you yourself wrote a tutorial about Scripting in Blue ( in 2002!! ) which, of course, is still valid. I must admit, it's been a while since i've read this. I'll better do some reading before i produce a text that has too much overlap.
I'll get back to you on this one.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: GitHub Migration: Status

Jan Jacob Hofmann
In reply to this post by Steven Yi
Dear Menno,

are you thinking strictly about a blog or could it be also a bit like a manual? I think it sounds most interesting what you do offer and I wonder if it could become a chapter in the floss manuals. I wrote one chapter there about blue last year, more or less a general overview about the features of the program. There could be then your chapter  nGen, AthenaCL and Common Music and I guess I'd like to add some words about jmask and cmask. Maybe these texts could find also their way into the blue-manual or onto the blue-pages sometime, if there is an opportunity for it later.

All the best,

Jan Jacob



Am 13.02.2014 um 15:26 schrieb Steven Yi:

> Hi Menno,
>
> Thanks for that list.  This is what I did with them:
>
> 151 - this hasn't been implemented, but I'm not sure I will implement
> it or have comments for soundObjects, needs more thought
> 104 - grid has been implemented, but not the part of the ticket asking
> for coordinates
> 69 - 68 - closed it
> 42 - closed it
> 69 - closed it
> 76 - left open
> 35 - closed it
> 13 - closed it
> 78 - closed it
>
> For a blog kind of entry, there isn't anything on the blue site for
> this at the moment. If you wanted to contribute something to the
> manual as a tutorial, that might work.  Otherwise, I could maybe add
> some kind of feature for blogging to the blue site.  I've been
> re-imagining the Blue website off and on for a while, making the user
> account have more features and the site and program more social.  This
> means a re-imagining of BlueShare for versions/comments/ratings, RSS
> feeds for things in the site, etc.  At the moment though, I've had to
> put that aside (seems like it's been on the side for a very long time
> though!).
>
> Thanks!
> steven
>
> On Thu, Feb 13, 2014 at 3:31 AM, menno <[hidden email]> wrote:
>> Hi Steven,
>>
>> i have no idea and experience with Github, so i cannot say much about it.
>> But i was looking through the list of Enhancements and Bugs and noticed some
>> entries that, to my opinion, are obsolete or mentioned more than once and
>> can be closed as far as i can see. (I cannot see who wrote them, but
>> sometimes i recognize my English Style :) )
>> Here is the list:
>> 151/104
>> 68
>> 42
>> 2*69
>> 76=35=13
>> 78 = nonsense ( i can say it because it is mine!)
>>
>> Q: at one point i would like to write a blog about the use of nGen, AthenaCL
>> and Common Music in Blue, about the strength and differences of these
>> Algorithm Generators. Is there a good place in the Blue pages to maintain
>> such a blog?
>>
>>
>>
>>
>> --
>> View this message in context: http://csound.1045644.n5.nabble.com/GitHub-Migration-Status-tp5732528p5732575.html
>> Sent from the Csound - Blue - User mailing list archive at Nabble.com.
>>
>> ------------------------------------------------------------------------------
>> Android apps run on BlackBerry 10
>> Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
>> Now with support for Jelly Bean, Bluetooth, Mapview and more.
>> Get your Android app in front of a whole new audience.  Start now.
>> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Bluemusic-users mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/bluemusic-users
>
> ------------------------------------------------------------------------------
> Android apps run on BlackBerry 10
> Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
> Now with support for Jelly Bean, Bluetooth, Mapview and more.
> Get your Android app in front of a whole new audience.  Start now.
> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
> _______________________________________________
> Bluemusic-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/bluemusic-users
>


------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.  Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
Bluemusic-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/bluemusic-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: GitHub Migration: Status

Steven Yi
Ah, I just realized maybe Menno was talking about the Wiki?  Perhaps I
should start using the Wiki more once the migration is complete to
Github. Maybe things like Tutorials would be better to have in the
Wiki, instead of the manual?

On Thu, Feb 13, 2014 at 10:28 AM, Jan Jacob Hofmann
<[hidden email]> wrote:

> Dear Menno,
>
> are you thinking strictly about a blog or could it be also a bit like a manual? I think it sounds most interesting what you do offer and I wonder if it could become a chapter in the floss manuals. I wrote one chapter there about blue last year, more or less a general overview about the features of the program. There could be then your chapter  nGen, AthenaCL and Common Music and I guess I'd like to add some words about jmask and cmask. Maybe these texts could find also their way into the blue-manual or onto the blue-pages sometime, if there is an opportunity for it later.
>
> All the best,
>
> Jan Jacob
>
>
>
> Am 13.02.2014 um 15:26 schrieb Steven Yi:
>
>> Hi Menno,
>>
>> Thanks for that list.  This is what I did with them:
>>
>> 151 - this hasn't been implemented, but I'm not sure I will implement
>> it or have comments for soundObjects, needs more thought
>> 104 - grid has been implemented, but not the part of the ticket asking
>> for coordinates
>> 69 - 68 - closed it
>> 42 - closed it
>> 69 - closed it
>> 76 - left open
>> 35 - closed it
>> 13 - closed it
>> 78 - closed it
>>
>> For a blog kind of entry, there isn't anything on the blue site for
>> this at the moment. If you wanted to contribute something to the
>> manual as a tutorial, that might work.  Otherwise, I could maybe add
>> some kind of feature for blogging to the blue site.  I've been
>> re-imagining the Blue website off and on for a while, making the user
>> account have more features and the site and program more social.  This
>> means a re-imagining of BlueShare for versions/comments/ratings, RSS
>> feeds for things in the site, etc.  At the moment though, I've had to
>> put that aside (seems like it's been on the side for a very long time
>> though!).
>>
>> Thanks!
>> steven
>>
>> On Thu, Feb 13, 2014 at 3:31 AM, menno <[hidden email]> wrote:
>>> Hi Steven,
>>>
>>> i have no idea and experience with Github, so i cannot say much about it.
>>> But i was looking through the list of Enhancements and Bugs and noticed some
>>> entries that, to my opinion, are obsolete or mentioned more than once and
>>> can be closed as far as i can see. (I cannot see who wrote them, but
>>> sometimes i recognize my English Style :) )
>>> Here is the list:
>>> 151/104
>>> 68
>>> 42
>>> 2*69
>>> 76=35=13
>>> 78 = nonsense ( i can say it because it is mine!)
>>>
>>> Q: at one point i would like to write a blog about the use of nGen, AthenaCL
>>> and Common Music in Blue, about the strength and differences of these
>>> Algorithm Generators. Is there a good place in the Blue pages to maintain
>>> such a blog?
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context: http://csound.1045644.n5.nabble.com/GitHub-Migration-Status-tp5732528p5732575.html
>>> Sent from the Csound - Blue - User mailing list archive at Nabble.com.
>>>
>>> ------------------------------------------------------------------------------
>>> Android apps run on BlackBerry 10
>>> Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
>>> Now with support for Jelly Bean, Bluetooth, Mapview and more.
>>> Get your Android app in front of a whole new audience.  Start now.
>>> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Bluemusic-users mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/bluemusic-users
>>
>> ------------------------------------------------------------------------------
>> Android apps run on BlackBerry 10
>> Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
>> Now with support for Jelly Bean, Bluetooth, Mapview and more.
>> Get your Android app in front of a whole new audience.  Start now.
>> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Bluemusic-users mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/bluemusic-users
>>
>
>
> ------------------------------------------------------------------------------
> Android apps run on BlackBerry 10
> Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
> Now with support for Jelly Bean, Bluetooth, Mapview and more.
> Get your Android app in front of a whole new audience.  Start now.
> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
> _______________________________________________
> Bluemusic-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/bluemusic-users

------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.  Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
Bluemusic-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/bluemusic-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: GitHub Migration: Status

menno
i was thinking more in the line of a Wiki entry at first, then i re-found your tutorial in the Blue manual which covers some of the things that i wanted to talk about. But even more on how I work with Algorithmic Generator programs and what i think of the decision when to use which AG. For sure, how to use AthenaCL in Blue could be investigated. Also, i like to look at nGen a bit more and demystify that one too. I am still in the fight of getting people from the Common Music list to answer at least one of my questions.

Deeper reason is: i tried to learn Python in order to understand more of its possibility to use it for score generation. I stopped after a while, because i found out it was too mathematical for me. I would never reach the level so that i could use the language for score generation. I must be content with just being able to read existing Python code and sort of understand :)

This has led to the decision to cover the existing Algorithmic Generator programs. And, in conjunction with Blue.
What is appealing the most is that they are musical programs already, and they can produce interesting ideas for making sound.

The fact that Blue is migrating to Github made me wonder if there is still such a place where a user such as me could lay down such experiences, in my case with some Algorithmic Generator programs. SourceForge had this Wiki option.


complaint: i had 3 texts in the Csound Wiki, including a list of all the examples that do not have an example in the manual yet - and these seem to be gone?!
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: GitHub Migration: Status

menno
In reply to this post by Jan Jacob Hofmann
Jan Jacob, i appreciate your contribution on Blue in the Floss Manual very much. (I have the paper copy of the Floss Manual  at home)
I can see that some words on the capability of the integration of CMask, AthenaCL, nGen and CM would be good somewhere in this text. And perhaps a link to a text that explains it all in more detail.

If and when i have my text ready, i will contact you!
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: GitHub Migration: Status

Steven Yi
In reply to this post by menno
I'm not sure what happened to the wiki pages.  Csound has the old
mediawiki and the newer SF wiki:

http://sourceforge.net/apps/mediawiki/csound/index.php?title=Special:AllPages
http://sourceforge.net/p/csound/wiki/browse_pages/

I didn't see anything on either set of pages.  I'm happy to include
anything tutorials into Blue's manual, or have the wiki really be a
user community set of pages edited and organized by everyone.
Whatever works for everyone! :)

As for algorithmic generation, I've been contemplating a few paths
myself.  I've thought:

* Do things in Clojure (I'll probably do this for my personal use)
* Extend JMask, adding new features: This has some limitations though
* Revive the CeciliaModule: This is related to some other things that
will go into Blue 3.0.  I think I will eventually work on this just to
have some flavor of Cecilia within Blue.  Also, this ties into
updating ObjectBuilder and the realtime score features in 3.0.  (I
realized that ObjectBuilder + some features would be very near
equivalent to Kyma objects...)
* Create GUI object for score generation.  The objects would be backed
by user-code, so user's can create their own objects (probably via
Python and Clojure to start).  This seems to have the most flexibility
between ease of usability vs. expressability. I could imagine this
also being an alternate backend to ObjectBuilder, so that one could
create a GUI with ObjectBuilder that would in turn have this GUI
AlgoGenerator as the backend (instead of code).

Anyways, those were some thoughts I had considered recently.  I'm
starting to get some progress on 2.6, so hopefully can get to
exploring the 3.0 realtime stuff soon.

steven

On Thu, Feb 13, 2014 at 11:18 AM, menno <[hidden email]> wrote:

> i was thinking more in the line of a Wiki entry at first, then i re-found
> your tutorial in the Blue manual which covers some of the things that i
> wanted to talk about. But even more on how *I* work with Algorithmic
> Generator programs and what *i* think of the decision when to use which AG.
> For sure, how to use AthenaCL in Blue could be investigated. Also, i like to
> look at nGen a bit more and demystify that one too. I am still in the fight
> of getting people from the Common Music list to answer at least one of my
> questions.
>
> Deeper reason is: i tried to learn Python in order to understand more of its
> possibility to use it for score generation. I stopped after a while, because
> i found out it was too mathematical for me. I would never reach the level so
> that i could use the language for score generation. I must be content with
> just being able to read existing Python code and sort of understand :)
>
> This has led to the decision to cover the existing Algorithmic Generator
> programs. And, in conjunction with Blue.
> What is appealing the most is that they are musical programs already, and
> they can produce interesting ideas for making sound.
>
> The fact that Blue is migrating to Github made me wonder if there is still
> such a place where a user such as me could lay down such experiences, in my
> case with some Algorithmic Generator programs. SourceForge had this Wiki
> option.
>
>
> complaint: i had 3 texts in the Csound Wiki, including a list of all the
> examples that do not have an example in the manual yet - and these seem to
> be gone?!
>
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/GitHub-Migration-Status-tp5732528p5732582.html
> Sent from the Csound - Blue - User mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Android apps run on BlackBerry 10
> Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
> Now with support for Jelly Bean, Bluetooth, Mapview and more.
> Get your Android app in front of a whole new audience.  Start now.
> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
> _______________________________________________
> Bluemusic-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/bluemusic-users

------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.  Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
Bluemusic-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/bluemusic-users
Loading...