Re: [chuck-users] cannot load chugins

Thanks Ge! I'll be looking to try 1.5.0.1. In the meantime, i noticed a lot of midi sequence functionality in the the source. (midiio_rtmidi.cpp) But I cannot see how to access it. Things like getBPM and various other midi events. Is this something for future? I have some free cycles now, so I can test if that helps. thanks -d On Tue, 23 May 2023 01:43:14 -0700 Ge Wang wrote:

Hi!

Glad that worked!

Alas, however, miniAudicle on Linux is a different story and currently experiencing some build woes. Apologies. We are currently looking into this and a fix will hopefully be coming in in 1.5.0.1.

Ge!

On 5/22/23 4:31 PM, d wrote:

...

success! thanks!

All the chugins work including FluidSynth.

Looks like I can't build the audicle though, it requires libqt4 and all I see are qt5 and qt6.

I running devuan linux (debian testing without systemd)

Linux uptown 6.1.0-7-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.20-1 (2023-03-19) x86_64 GNU/Linux

-d

On Mon, 22 May 2023 15:28:13 -0700 Ge Wang wrote:

...

Happy Monday!

If you cloned/pulled from the chugins repo since Friday, we are already working on 1.5.0.1 and the chugins headers have been already updated from version 8.0 to 8.1 due to additions to the chugin modules API. (Chugins built with 8.1 headers need the latest dev build of chuck to load.)

Solution #1: build chugins from the chuck-1.5.0.0 tag:

(from your local chugins repo) git fetch --all --tags

git checkout tags/chuck-1.5.0.0 (or) git checkout tags/chuck-1.5.0.0 -b [your branch name]

(for good measure) git submodule update --init --recursive

FYI if you want to double check, verify this following line in chugins/chuck/include/chuck.h reads as follows: #define CHUCK_VERSION_STRING "1.5.0.0 (chai)"

If you do a clean build of chugins from this tag, they should properly load in chuck-1.5.0.0.

(Solution #2: an alternate approach is to build and use the latest chugins and the latest chuck: 1.5.0.1-dev.)

Tip: if you'd like, you can run chuck with with the -v3 (verbose level 3 or higher) flag to see chugins loading status / any error messages, e.g.:

chuck -v3 WPKorg35-test.ck

Sorry for the confusion! Please let us know if you run into any other issues.

keep on chuckin, Ge!

~~~ Ge Wang Associate Professor Center for Computer Research in Music and Acoustics (CCRMA) Department of Music (also Computer Science, by Courtesy) Stanford University https://ccrma.stanford.edu/~ge/ ~ Artful Design: Technology in Search of the Sublime! -- what we make, makes us -- https://artful.design/ ~~~

On 5/22/23 1:33 PM, d wrote:

...

I downloaded and rebuilt chuck and chugins this morning. The chuck examples work but none of the chugins. Looks like they are not being found.

happy monday :-) -d ================= uptown:uname -a Linux uptown 6.1.0-7-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.20-1 (2023-03-19) x86_64 GNU/Linux uptown: === uptown:chuck --help usage: chuck --[options|commands] [+-=^] file1 file2 file3 ... [options] = halt|loop|audio|silent|dump|nodump|about|probe| channels:<N>|out:<N>|in:<N>|dac:<N>|adc:<N>|driver:<name>| srate:<N>|bufsize:<N>|bufnum:<N>|shell|empty| remote:<hostname>|port:<N>|verbose:<N>|level:<N>| callback|deprecate:{stop|warn|ignore}| chugin-load:{on|off}|chugin-path:<path>|chugin:<name> [commands] = add|remove|replace|remove.all|status|time|kill [+-=^] = shortcuts for add, remove, replace, status

chuck version: 1.5.0.0 (chai) linux (alsa) : 64-bit http://chuck.cs.princeton.edu/ http://chuck.stanford.edu/ ==== uptown:ls -l /usr/local/lib/chuck/WPKorg35.chug -rwxr-xr-x 1 root root 21856 May 22 12:34 /usr/local/lib/chuck/WPKorg35.chug ==== uptown:chuck WPKorg35-test.ck [chuck]: RtAudio: no compiled support for specified API argument! [WPKorg35-test.ck]:line(1): undefined type 'WPKorg35'... [WPKorg35-test.ck]:line(1): ... in declaration ... [chuck]: [chuck]: uptown: === uptown:chuck --chugin-path:./WPKorg35.chug WPKorg35-test.ck [chuck]: RtAudio: no compiled support for specified API argument! [WPKorg35-test.ck]:line(1): undefined type 'WPKorg35'... [WPKorg35-test.ck]:line(1): ... in declaration ... [chuck]: [chuck]: uptown:

_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

---

chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users