Sounds great, Mario!

The way I use ChucK & LiCK, which may or may not be properly documented, is to run

$ chuck --loop

in one terminal, setting --adc and --dac if necessary, and then from the lick directory in a second terminal

$ chuck + import.ck
$ chuck + examples/…

Then I often use a MIDI device and/or a guitar pedal board that appears as a keyboard so I don't have to touch the computer any more.

I have wanted to bundle all this up to deploy to a Raspberry Pi in a guitar pedal enclosure and/or eurorack synth module for some time, but I get distracted by other things.  :)

   michael


On Sep 1, 2019, at 3:13 PM, Mario Buoninfante <mario.buoninfante@gmail.com> wrote:

Hi Michael,

Thanks for giving me a bit context here.
I think before I can say anything about it, I should have a proper look at LiCK. Something more than just poking around and get inspired by it, but instead I should spend some time actually using it.
Thus, I'll take some time in the next weeks and then I should be able to provide my view about it.
At the first sight I can only say that absolutely LiCK is quite powerful, from what I've seen in the code. And if the documentation is the only issue, well we're in a good place though :)

Cheers,
Mario

-- Electronic Musician, Creative Coder, QA Engineer https://vimeo.com/creativecodingsalerno http://mbuoninfante.tumblr.com https://github.com/mariobuoninfante https://bitbucket.org/mariobuoninfante

On 1 Sep 2019 02:58, Michael Heuer <heuermh@gmail.com> wrote:
Hello Mario,

A long time ago, on this very list, some folks thought it would be a good idea to create a place to collect their ChucK code into a shared library.  I volunteered to start such a library and LiCK was born.

For one reason or another, LiCK didn't really take off as a community library.  I would guess the primary reason is that LiCK comes off as more of a programmer library rather than a musician library.  There is a lot of good stuff for musicians in there, I am just not so good at documentation!  :)

Going forward, I'm more than welcome to contributions via Github pull request or to the docs via FLOSS manuals.  Or if a new shared library should be created from scratch, for another try at broader community involvement, I'm all for that as well.

Cheers,

   michael


On Sun, Aug 25, 2019 at 2:58 PM Mario Buoninfante <mario.buoninfante@gmail.com> wrote:

Hi Michael,

Considering the nature of the thread, would you like to expand a bit on "The original intent was that it be a place for lots of people to dump their stuff, but that hasn't really happened"?
I mean that seems exactly what I was looking for :)
How do you see that happen, if it's still something you'd like to see happening?

Cheers,
Mario

-- Electronic Musician, Creative Coder, QA Engineer https://vimeo.com/creativecodingsalerno http://mbuoninfante.tumblr.com https://github.com/mariobuoninfante https://bitbucket.org/mariobuoninfante

On 23 Aug 2019 21:03, Michael Heuer <heuermh@gmail.com> wrote:
Hello Mario, Sarerac

Thank you for the reminder about the FLOSS manuals documentation — that is quite a bit out of date, and doesn't really mention much about making music.  :)

Very generally, LiCK is where I dump all the stuff I write in ChucK.  The original intent was that it be a place for lots of people to dump their stuff, but that hasn't really happened.

Nearly every class/effect/instrument has an example in the examples directory


The examples named *Pedal.ck work similar to a guitar pedal, I typically use them with an Apogee Jam interface, or my real multichannel interface, and this stomp board which acts as a keyboard (though it can also do MIDI over USB)


   michael


On Aug 21, 2019, at 4:07 PM, mario buoninfante <mario.buoninfante@gmail.com> wrote:

Hi Sarerac,


You can find more info about LiCK here: https://en.flossmanuals.net/chuck/_full/#lick-library-for-chuck


Cheers,

Mario

On 20/08/2019 17:39, sarerac wrote:
Hello;

How is it implemented LiCK in Chuck? LiCK is a little confuse for me because i didn’t know it.