[chuck-users] future of ChucK
Joel Matthys
jwmatthys at gmail.com
Tue Jan 16 11:48:14 EST 2018
Check out https://github.com/spencersalazar/libchuck. I've been meaning
to try it out, but haven't yet. It's exactly the kind of lib that should
be embeddable in an app. I think it needs someone to create a few simple
(cross-platform) examples.
Joel
On 01/14/2018 12:12 PM, Stuart Roland wrote:
> I can't speak to the future of ChucK itself, but recently I have been
> giving a lot of thought to MY future with Chuck. First off, I love
> ChucK and all the cool stuff it let's me create. I find it much more
> intuitive than any other audio programming language/environment I have
> used and I can usually create something along the lines of what I set
> out to create with it. My problem with it is that I really want to be
> able to create stand alone apps and plugins with it, which I have not
> found any way of doing. I would like for my software to be usable by
> the average musician, not just by programmer-musicians who can read
> ChucK code (though we are a cool bunch). I know ChucK Racks were just
> released (for Macs,which I don't use) but as I understand, this just
> let's you run ChucK scripts as a plugin, and does not provide a way to
> wrap up the code in any UI to distribute to musicians who are used to
> sliders, knobs, presets etc.
>
> So I guess I have a few questions for everyone/anyone here: is there a
> way to use ChucK in a mobile or desktop app? Is there a way to connect
> ChucK to a GUI that is simple enough that non-programmers could use
> it? If not, is there another language / libraries for another language
> like python, for example, that has some of the great, intuitive design
> as ChucK? Is ChucK more of an educational tool at this point and less
> of a tool for developers?
>
> Thanks for taking the time to read. Happy audio/music making!
>
> Stuart
>
> On Jan 14, 2018 11:00 AM, <chuck-users-request at lists.cs.princeton.edu
> <mailto:chuck-users-request at lists.cs.princeton.edu>> wrote:
>
> Send chuck-users mailing list submissions to
> chuck-users at lists.cs.princeton.edu
> <mailto:chuck-users at lists.cs.princeton.edu>
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
> <https://lists.cs.princeton.edu/mailman/listinfo/chuck-users>
> or, via email, send a message with subject or body 'help' to
> chuck-users-request at lists.cs.princeton.edu
> <mailto:chuck-users-request at lists.cs.princeton.edu>
>
> You can reach the person managing the list at
> chuck-users-owner at lists.cs.princeton.edu
> <mailto:chuck-users-owner at lists.cs.princeton.edu>
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of chuck-users digest..."
>
> Today's Topics:
>
> 1. Re: static strings and the future (JP Yepez)
>
>
> ---------- Forwarded message ----------
> From: JP Yepez <jpyepezimc at gmail.com <mailto:jpyepezimc at gmail.com>>
> To: ChucK Users Mailing List <chuck-users at lists.cs.princeton.edu
> <mailto:chuck-users at lists.cs.princeton.edu>>
> Cc:
> Bcc:
> Date: Sun, 14 Jan 2018 15:53:30 +1300
> Subject: Re: [chuck-users] static strings and the future
> Hello all,
>
> I can't say much about the development part itself, but in my
> experience I've noticed that ChucK is still being used widely at
> an academic level. I understand it's being used in a few
> universities that include creative technology programs and
> computer orchestra courses in their curriculums, including
> CalArts, Stanford, and VUW (New Zealand). Like Mario mentioned, it
> is a core part of a few Kadenze courses; I've been involved as a
> producer/teaching assistant in a couple of them and it seems like
> it's a popular language among students who are just learning how
> to code, and musicians who would like to develop more advanced
> projects. Also, ChucK Racks popped up a couple of months ago,
> which was pretty exciting. So yeah, I think there's quite a bit
> going on, but it certainly would be nice to have a more active
> community (I'm hoping to contribute, and hopefully I'll get to it
> before too long).
>
> About the *static strings* issue, I think they're kind of in a
> shady spot. Like Gonzalo mentioned, you can't have static
> non-primitives in your code, but there is a workaround to this by
> declaring objects as a reference and then initializing them
> outside of the class. However, if you try to do this with strings,
> it will tell you that they're a primitive type and it throws an
> error. The best hack I've found for this is through arrays (even
> if the size of the array is 1 in many cases). Here's an example:
>
>
> publicclassContainer{
>
>
> staticstringstaticString[];
>
> publicstaticvoidinit(){
>
> newstring[1]@=>staticString;
>
> "Hello World"@=>staticString[0];
>
> }
>
> publicstaticvoidprint(){
>
> <<<staticString[0]>>>;
>
> }
>
> }
>
>
> Container.init();
>
> Container.print();
>
>
>
> You don't really need an init() function, and you can initialize
> the array on the actual script, but I usually end up with much
> larger classes, which is why I like to keep things clean.
> Hope this helps!
>
> Best,
>
> JP
>
>
> *JP Yepez*
> New Media Artist - Musician - Researcher
> Website:http://www.jpyepez.com/
> Email: jpyepezimc at gmail.com <mailto:jpyepezimc at gmail.com>
> --------------------------------------------------------
> <https://www.instagram.com/jpyepez/><https://twitter.com/jpyepezmusic><https://www.linkedin.com/in/jp-yepez-063928123/>
>
>
> On Sun, Jan 14, 2018 at 12:19 AM, mario buoninfante
> <mario.buoninfante at gmail.com <mailto:mario.buoninfante at gmail.com>>
> wrote:
>
> Hi,
>
> I'd like to ask the same question about the development status.
>
> the only thing I can say is that also if the development seems
> to be a bit stuck, on the other side I noticed that they're
> pushing on the educational side (see Kadenze courses), and if
> you look at the github repository, there's been some update in
> the last 2 years.
>
> but as you guys said, it's important to know what's the plan ;)
>
> it's a couple of years I'm really diving into ChucK and I
> strongly believe that is a good programming language which
> opens up a lot of possibilities that other languages don't.
>
> but at the same time I feel like it's been a bit abandoned
> (maybe that's a huge word, let's say put aside ;) ) and of
> course using a "tool" which has an "uncertain future" it's
> not the best thing.
>
> I wish I was able to offer my contribution to the development,
> but unfortunately I'm not really into C/C++, I'm more a
> "scripting language guy" :)
>
> btw, it would be nice to hear what developers and/or other
> users have to say about it.
>
>
> cheers,
>
> Mario
>
>
>
> On 12/01/18 22:14, Gonzalo wrote:
>
> Yes, I'm wondering the same thing. There's a Facebook
> group (https://www.facebook.com/groups/1593843507578422/
> <https://www.facebook.com/groups/1593843507578422/>) but
> it doesn't look super active either.
>
> As far as static strings: I'm pretty sure you just can't
> have static non-primitives. What are you trying to achieve?
>
> Cheers,
> Gonzalo
>
>
> On 13.01.18 00:20, Atte wrote:
>
> Hi
>
> I've been away for a long time and surprised that
> activity seems to have slowed down a lot, both on the
> development of new releases chuck and the life of this
> list. Am I looking at the wrong places? What's the
> status of chuck development now and in the future?
>
> I really like chuck (mostly the timing and sporking
> including Machine.add()), should I look other places
> for a language that will privide a more secure future?
> I'm on linux and looked at Csound, Super Collider and
> PD, each has it's challenges in how I work (realtime
> generative and algorithmic MIDI), python seems to have
> realtime problems (garbage collection at random
> points). Any idea what former chuck users have
> switched to now?
>
> Back to chuck! A problem that I never been able to
> solve, static strings:
>
> public class A {
> "b" @=> static string B;
>
> public static void C(){
> <<<B>>>;
> }
> }
>
> That throws an error, how would I go about what I'm
> trying to do?
>
> Cheers
>
>
>
> _______________________________________________
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
> <mailto:chuck-users at lists.cs.princeton.edu>
> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
> <https://lists.cs.princeton.edu/mailman/listinfo/chuck-users>
>
>
>
> _______________________________________________
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
> <mailto:chuck-users at lists.cs.princeton.edu>
> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
> <https://lists.cs.princeton.edu/mailman/listinfo/chuck-users>
>
>
>
> _______________________________________________
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cs.princeton.edu/pipermail/chuck-users/attachments/20180116/f2a67c9a/attachment-0001.html>
More information about the chuck-users
mailing list