Thoughts from the battlefield:
One nice thing about the Pi is that it supports many
sample rates. So if you can run at 22.05k or even
16k or less, then you'll get much more bang for
your buck.
Also, you might look into using WvIn (non looping)
or WavLoop (looping), rather than SndBuf,
Ok,
I just tried this on Windoze 8.1 Pro. Newest installer from
The ChucK/mini download page. Ran both command line
and miniAudicle. Audacity, QuickTime player, iTunes, and
my own sndview (DOSBox based sound/spectrum viewer,
First created in 1988, migrated forward since) all read and
play the
Could we be looking at a running status problem? It's legal in MIDI to skip
the status byte if it doesn't change. Not sure how ChucK/RTMidi handle this.
I sold my WX7, or I'd check it.
Prc
___
chuck-users mailing list
Ack! This is a common problem, and I thought I had caught all of
the clipping/distortion cases on Windows/Linux with our last
passes on checking the source code. I'll check it all again and
put it in our Errata file for future ChucK/Mini releases, and future
printings of the book.
As others
I'm using the hell out of it on Yosemite. Only problems I've
observed are:
Something odd going on with Processing sending OSC to ChucK.
It works sometimes, then not.
Something odd going on with networked pieces like CliX, Gamelan,
etc. Possibly a new machine/firewall settings issue rather than
Atte,
A handy list of Shred functions (From our new Book, Appendix A :-):
The ones you want are running() or done()
Shred.fromId(int id) Returns shred object corresponding to id.
int id(); Returns the ID number of the shred.
void yield(); Causes the shred to temporarily discontinue
:
cak4g45dtccjruewivmckrhnlcne6s3me5__oqoozfm20ner...@mail.gmail.com
Content-Type: text/plain; charset=utf-8
On 19 February 2015 at 18:59, Perry Cook p...@cs.princeton.edu wrote:
Ack! This is a common problem, and I thought I had caught all of
the clipping/distortion cases on Windows/Linux with our last
This is really odd, because I have two Yosemite machines that work
fine with your posted code. I’m trying to figure which of my Macs I
want to subject to the ElCap upgrade, and will test on that and report.
For fun, have you tried the other non-hid keyboard device example?
This one suffers from
Calling all Windows Hax@rs. I have discovered (thanks to someone
in the online Physics-Based DSP course) that the Mesh2D chugin that’s
distributed with the Windows installer is different from that shipped
for Mac. (Haven’t checked Linux yet).
Unacceptable behaviors include
myMesh.x and
ChucK definitely has all you need! ChucK is “DSP Complete”
(like Turing Complete for computational engines/languages),
because since ChucK allows for single-sample connections
and manipulations, then we don’t provide lots of flavors of
things. You can build from primitives. Like a RISC
It’s pretty old-school, but often my solution for this is to pipe text output
of ChucK
into stdin of the Cxx program in a terminal. You need to be sure to send to
chout
and not just use the <<< “PRINT THIS” >>>; form, because the latter prints to
stderr, not stdout. Here’s a simple ChucK
In miniAudicle, it’s in the Preferences window.
In terminal, the --srate switch sets sample rate:
> chuck --srate8000 MyChucK.ck
But both ADC and DAC must run at same rate. AND there has to be
supporting hardware there to run at that sample rate. So native Mac
coreaudio won’t allow for
Lars Wrote:
> Is there any search function in Mini audicle?
>
> Thanks!
Within a file in the editor, standard -F Find, replace,
replace all, next, etc. work as with any text editor. Were you hoping
for a more multi-file search functionality?
PRC
(Michael wrote)
>
> The ChucK source is here
>
> https://github.com/ccrma/chuck
>
> As far as documentation goes, there's not really much to Chubgraphs and
> Chugens, just chuck inlet to outlet with something in between or override
> fun float tick(float in), respectively.
>
> michael
Yep
I don’t have your environment, but some directory should do
the trick. On my Mac, it’s in /usr/lib/chuck
For now, you could try loading the specific ChuGin by name
at runtime:
chuck -chugin: yourchuckfiles.ck
I put the chugin I want right in the same directory just
to make sure.
Hope
Hey Sheri,
The book is available in EBook form from the publisher (Manning) here:
https://www.manning.com/books/programming-for-musicians-and-digital-artists
There is also an intro to programming in ChucK video course
on Kadenze here:
You’ll need to connect your gain explicitly to channel 32 as well. Gain is a
mono UG, but there’s special treatment when connecting any mono UG to the
system default stereo dac.
Note that if you want true “stereo” gain control or panning, you can do:
Gain g[2] => dac;
or
Pan2 p => dac;
I’ve done this a lot. Just make a nicely oversampled single-cycle sine .wav
file and use SndBuf. You’ll need a .freq function that does the right thing
based on how many samples are in your wavetable. I think you can also use GenX
to do it.
Prc
Sent from my iPhone
> On Oct 23, 2018, at
I didn’t look at the verbose log, but it looks like maybe it can’t find the
chugin. I’ve been having some trouble getting command line chuck to find the
factory chugins. One way seems to be to have the .chug in the local directory,
and specify it on the command line.
Prc
Sent from my iPhone
Very interesting question, and I don’t know. In case the answer comes back no
tho:
I’ve done this by launching with the start time in a command line argument.
Then added “now” to that to get current time.
Prc
Sent from my iPhone
> On Apr 3, 2019, at 9:00 AM,
Perhaps the Chuck Book might at least provide good examples.
I don’t know of a formal style guide. I think we authors, while differing from
each other, generally use OOP conventions we brought from C++, Java, (and
myself) Objective C and Smalltalk.
Prc
Sent from my iPhone
> On Apr 1,
Do a —probe to see how many adcs (and dacs) are there. Then try command line
forcing to that adc.
I find that if I’ve recently airplayed, or forget I have soundsource enabled,
or sound flower, or some other real/virtual adc/dac, sometimes those are sticky
in system audio and ChucK defaults to
You script got scrubbed for some reason, but I suspect that you’re shadowing
the global somehow locally (if you use the same name as an argument or a
local within a function, it masks the global version).
Here’s a simple example of using a global:
1000 => float freqGlob; // global frequency
.interp doesn’t do what you think it does. It just specifies the
type of internal interpolation for smoothing of playback (only
applicable for non 1.0 rates).
SndBuf .loop just tells it to start over at the beginning
when it reaches the end (or end after reaching the beginning):
SndBuf s =>
The trick here is you also have to tell ChucK to be 4 channels.
From the command line:
chuck -c8 YourFile.ck
depending on what your —probe shows, you might even have to
specify which dac (and adc) to use, especially if they’re different
device numbers or channel numbers. Also, might need to up
specific
> than "Re: Contents of chuck-users digest..."
>
>
> Today's Topics:
>
> 1. Re: playing SndBuf backward (Perry Cook)
> 2. Error in book "Programming for Musicians and digital artists
> by Ge Wang" ? (herman verbaeten)
> 3. playing
We also added Std.ftoi(x) to the language a while back (at 1.3.2.0). It’s much
clearer to read, and more obvious as to what’s going on and why, than the
casting notation. To round, just add 0.5 to x in the function arg.
so:
> Std.ftoi(0.4*myBuf.samples()+0.5) => myBuf.pos;
would set your
The parallel multi-delay and multi-tap single delay line are identical in
function. Delays are linear so they can be factored any way you like and as
long as the impulse response is the same, it’s a duck. I use the multi delay
version myself. Wastes memory, but who cares.
Prc
Sent from my
Also, A more obvious and Java-like way to convert float to int is the built-in
function:
Std.ftoi(myFloat) => int myInt;
Sent from my iPhone
> On Mar 10, 2020, at 8:51 AM, chuck-users-requ...@lists.cs.princeton.edu wrote:
>
> Send chuck-users mailing list submissions to
>
This is truly odd. I don’t have easy means to test it. I don’t
know why it wouldbe broken dependent on the dac, however.
For fun you might try something like this, just to verify that the
valueAt() function is what’s busted.
SndBuf s => blackhole;
“Fred.wav” => s.read;
while (s.pos() <
what does
chuck —probe
print out? Maybe you’re connecting to the wrong dac??
For reference, here’s an invocation script I used last time
I did a multichannel performance:
chuck -c8 -bufsize2048 -in2 --dac1 --adc0 INIT.ck
That would have been an older version of chuck, but it worked then.
Depending on how HUGE the SndBuf files are, I have often loaded all of the files
sequentially at the beginning, before I make any sound at all, into a single
SndBuf,
not to play them, but to get them into the cache. Then when the time comes to
truly load them, they can be zero-disk loads. If
So if I understand you correctly, this is solved fairly easily by a structure
we propose in the "ChucK Book”
1) Create a file that loads (by Machine.add()) all the classes you think
you’ll need.
2) As the last line of that, have it Machine.add() a different file, which then
either does the
Hi all,
Since Mojave, MacOS has instituted increasing security restrictions on Mic (and
Camera) use.
One of my Mojave machines at least launched the “MiniAudicle wants access to
your microphone” dialog, and Mini now shows up in the Security pane of System
Preferences.
BUT, opening adc with
34 matches
Mail list logo
