Repository navigation
Changes since the last Release
Added
-
Added a reply outlet: an additional non-signal outlet, rightmost, which reports data to the patch rather than only to the Max console
-
val <name> <value...>in response toget -
event <name>while alistenis active -
shred add <id>/shred remove <id>from a ChucK VM shred watcher -
global <name> <type>in response toglobals -
Selectors always come from the object's own vocabulary and any ChucK name travels as an argument, so no global variable name can collide with a control message. Route with
route val event shred global -
The name precedes the type in
global <name> <type>deliberately. Once a patch strips the selector withroute global, the next atom becomes the new selector, and ChucK'sintandfloattype names collide with Max's typed methods there, producingbad arguments for message "int". ChucK variable names cannot be reserved words, so leading with the name avoids the collision -
Replies are queued from the audio thread and flushed on the main thread; the queue drops rather than blocks when full
-
-
Added host classes bound into every VM with
ChucK::bind():Host.msg(name, ...)to the reply outlet asmsg <name> <args...>(bang, float, string andfloat[]overloads),HostIn/HostMsgformsg <name> <args...>,HostBuffer/HostBufPlayforbuffer~, andHostClockfor the Max transport (source/docs/dev/bind.md)-
The names are host-neutral and shared with numchuck and pd-chuck, so one
.ckfile can run in each host that binds them -
Host.sendBang,Host.sendFloat,Host.sendSymbolandHost.sendListsend to every[receive <name>], as in pd-chuck, without a patch cord or[route msg]; queued on the audio thread and delivered on the main thread, 256 calls per drain and 32 list elements (examples/max/max_send_receive.ck); receive names are shared by the whole Max process, unlike the reply outlet, and lists hold floats only (patchers/tests/test_max_send_receive.maxpat)
-
-
Copied the
examples/max/max_*.ckbind examples intosource/projects/examples/max/, the copysource/scripts/update.shrestores examples from; without it the next update deleted them -
Added
source/scripts/patches/, applied bysource/scripts/update.shafter every update; it fixes upstream ConvRev's inverted#include <thread>guard, which breaks the build with the current Apple libc++ -
Added
abortmessage, which aborts a shred currently executing inside the VM-
Unlike
remove, this can break out of a shred looping without advancing time -
Only has a target while the VM is inside a compute cycle, which is the situation it exists for; on an otherwise healthy patch it reports that there is nothing to abort
-
-
Added multichannel tapping:
tap <outlet> <ugen> <nchannels>assigns a multichannel global UGen across consecutive tap outlets, reading viagetGlobalUGenSamplesMulti()- Each sub-channel needs its own
bufferedflag in ChucK, for example1 => stereo.chan(0).buffered, as the parent flag does not propagate
- Each sub-channel needs its own
-
Added
CHUCK_PARAM_OTF_PRINT_WARNINGSto theparammessage tables, the only integer VM parameter that was missing -
Added
source/docs/logging.md, documenting the console and outlet reporting channels, theloglevelconflation, and the selector namespacing rules -
Added an
advancedtab tohelp/chuck~.maxhelpcovering the current message set, alongside the previous help content which is now themaintab-
Six sections: load and run, read globals, set globals, events, tap global UGens, and VM introspection
-
Demonstrates the data outlet with
route val event shred globalinto four labelled prints, and the tap outlets with three scopes -
chuck~ 2 @ntap 3leaves no outlet unconnected: the demo uses exactly one mono tap and one stereo pair -
Message boxes feed a single
[s #0-to-chuck]rather than each carrying its own patch cord to the object -
Does not demonstrate
eval, since ChucK code needs semicolons and a bare;in a Max message box means "send to a named receive"; themaintab covers this with theui_code.maxpatbpatcher
-
-
Note for maintainers: each help tab holds its own
chuck~, so their send/receive names must not collide. An unscoped name such asto-chuckis global across all of Max, so everychuck~fed by a matching[r to-chuck]runs every message intended for any other, and their audio is heard together. Themaintab still uses the unscoped name, as dotest_add,test_editor,test_global_vars,test_songandtest_sync. Note also that#0alone is not sufficient to separate two tabs: it expands per top-level patcher instance and subpatchers inherit the parent's value, so two tabs both using#0-to-chuckwould collide again. Distinct names such as#0-main-to-chuckand#0-adv-to-chuckare needed -
Added
patchers/tests/test_chuck_tilde.maxpatandexamples/test/help_features.ckdemonstrating the above-
The demo file wires its globals to audible parameters rather than leaving them as inert values:
freqdrives the oscillator pitch andlevels[0]its gain, soset float freq 660., thefreq 550.shorthand andset float[i] levels 0 0.75all produce an obvious change -
Uses a saw oscillator for the mono voice and a panning triangle for the stereo pair, so the two are distinguishable by ear and the tap scopes show a readable waveform
-
-
Added compile-time
printfformat checking to the logging helpers on GCC and Clang
Changed
-
Updated
chuckto1.5.5.9-dev (chai) -
make brewandmake brew-liteno longer enableFluidSynth.chug. They linkedlibfluidsynth.afrom the Homebrew prefix, which Homebrew'sfluid-synthdoes not ship, so both targets failed at link time.make full2builds the chugin from source -
Set
CHUCK_PARAM_IS_REALTIME_AUDIO_HINTto 1 at startup; it had been left at its default of 0 even thoughchuck~is always driven from the MSP audio callback -
Registered per-instance
chout/cherrcallbacks in addition to the process-widestdout/stderrones, so ChucK's<<< >>>output and the VM's own printing are both captured -
abortandremoveallnow report unconditionally viaobject_post, rather than through the gated helpers, which at the time could not reach the user at all -
removeallnow reports the shred count and notes that global UGens survive shred removal -
Logging helpers take
const char* fmt, removing the need for a(char*)cast at every call site -
Separated this object's reporting verbosity from the ChucK VM's log level, via a new
@verboseattribute (0quiet,1normal,2debug; also settable as a message).loglevelnow means only whatChucK::setLogLevel()means-
Previously
x->logleveldid both jobs, andck_newset it toCK_LOG_SYSTEM(2) against helper thresholds of 4, 5 and 6, so 47 of the 118 reporting calls could never appear. Raising the level to reach them also made the engine verbose -
@verbosedefaults to 0, which is what the old gating amounted to in practice, so this changes no observable behaviour; it makes the output reachable without side effects on the engine -
ck_warnis no longer gated at all: a warning nobody sees is not a warning -
Query answers in
status,vm,chuginsandloglevelnow report unconditionally, since a question that returns nothing is indistinguishable from a broken object -
See
source/docs/logging.md
-
-
Made
loglevelhonestly process-global. It maps toChucK::setLogLevel(), which is static, so one level is shared by everychuck~in the process; the code had kept a stale per-instance copy alongside it. Setting the level on one object left the others' copies stale, and querying it with no argument mutated the queried object's copy as a side effect. The copy is removed:ck_loglevelreads and writes the shared VM state directly, and the package default is now applied once by the first instance rather than re-asserted (and thus clobbered) by every new object. Per-object reporting is what the new@verboseis for -
Replaced the eleven GitHub workflows with two.
build.ymlis manual and builds any variant on any current runner, all variants at once if asked.release.ymlruns when a version tag is pushed. It builds the arm64, Intel and Windows packages in parallel, assembles the multi package from the first and last, creates the GitHub release with notes from the tag's CHANGELOG section, and attaches the four packages as zips. Signed dmgs are still produced locally. The old set targeted the retiredmacos-12andmacos-13runners, ran two different workflows on every release, and did not install every dependency thebrewtarget needs
Fixed
-
Fixed sample rate changes being ignored.
ck_dsp64()received the host rate and discarded it, leaving the VM at the rate captured when the object was created, so changing Max's sample rate afterwards caused pitch and timing to drift. The rate is now forwarded to the VM viasetParam() -
Fixed
set float[i]andset float[k]silently discarding the fractional part of every value.atom_getfloat()was assigned to along, truncating before the value reached the VM, soset float[i] a 0 0.5stored0.0 -
Fixed 13 format string mismatches, mostly
%dapplied to 64-bit types, which printed incorrect values and were formally undefined behaviour -
Fixed
ChucK::globalCleanup()being called whenever anychuck~was freed, rather than once when the last one goes away as its contract requires. It shuts down the HID manager, serial IO and the keyboard-hit manager process-wide, so closing onechuck~pulled those subsystems out from under every other instance still running. Audio, the VM and the type system are untouched by it, so instances not using HID, serial or keyboard input were unaffected, which is why this went unnoticed -
Fixed
getreplies and event notifications not being attributable to a specificchuck~object. The callback-id overloads are now used, with the id encoding both the instance and the request, so replies reach the object that asked -
Fixed
@tapbeing documented in the README where the implemented attribute is@ntap. The documented form was silently ignored by Max, producing no tap outlets -
Fixed a
size_ttointtruncation inreplace_character() -
Fixed the Windows build of
maxin.cppandmaxclock.cpp, wherestd::minandstd::maxcollided with theminandmaxmacros fromwindows.h -
Fixed
HostClock.bar(),beatInBar()andunit()answering for the previous beat when asked exactly on a boundary. At 44.1 kHz,toNextBeat() => nowlands a few 1e-14 ticks short of the beat andfloorrounded down. A position within half a sample of a boundary now counts as on it, the ruletoNext()and the jump detector already use. Found by the same test in pd-chuck's port ofHostClock