Re: [Bluemusic-users] repair BlueShare insruments and effects

[Steven Yi <ste...@gm...>]

Hi Menno,

I've wondered what's the best solution for this.  I think in the new
blueShare, it would be a system for implementing forks, so that users
could create a fork and mark it as a fork from another instrument.
That way a situation like this would be addressed by someone creating
a fixed-up instrument and submitting as a fork, and when browsing the
original it would show that there were forked versions.  This kind of
system is implemented with projects in Github, and seems to make sense
here.  Thoughts?  (Also, I plan to add comments to
instruments/effects, which could also be helpful)

Thanks!
steven

On Sat, Jan 19, 2013 at 2:29 PM, menno <nab...@ya...> wrote:
> Hi Steven,
>
> now that i have started Blue intensively i find that most BluesShare
> Instruments and Effects produce errors due to the fact that at one point
> parameters were not automatable anymore, but in fact are simply i
> statements.
> I can do the repairs if you agree.
> Is there a way that i can clean up this repository? I would not like to have
> my name attached to all those instruments, because i repair them, but i did
> not design them.
> What do you think?
>
> bye,
> Menno
>
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/repair-BlueShare-insruments-and-effects-tp5719474.html
> Sent from the Csound - Blue - User mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. SALE $99.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122912
> _______________________________________________
> Bluemusic-users mailing list
> Blu...@li...
> https://lists.sourceforge.net/lists/listinfo/bluemusic-users