Re: [chuck-users] Electronic ChucK
Kassen, Your point is well taken. I guess I'm not concerned about the audiophile quality of this system at all. If it's going to be so inexpensive then it will probably be inaccurate as well, and I'm OK with that. It's not intended to produce perfectly orchestrated audio, but rather to do something fun and interesting. Also, that 555 example was indeed for a variable frequency oscillator, more specifically a pulse position modulator from the data sheet. there is a CV input that stops the oscillator at ground and sets maximum frequency at Vcc. Though to get a 50% duty cycle one must add a flip-flop to the output. I'm really just going for a cool toy that will make lights blink and go woo-woo when I put together a ring of oscillators, this does not have to be super precise. That and the limited types of modulation input kind of make for a departure from ChucK, however. But that's OK too. It can simply be ChucK-inspired not ChucK duplicated. Les (Inventor)
This is a very interesting discussion. I'd be interested to see the schematic diagrams purely for the purposes of learning more about how you might perform audio synthesis in hardware. Rob On 3/10/2008, at 7:50 AM, inventor-66@comcast.net wrote:
Kassen,
Your point is well taken. I guess I'm not concerned about the audiophile quality of this system at all. If it's going to be so inexpensive then it will probably be inaccurate as well, and I'm OK with that. It's not intended to produce perfectly orchestrated audio, but rather to do something fun and interesting.
Also, that 555 example was indeed for a variable frequency oscillator, more specifically a pulse position modulator from the data sheet. there is a CV input that stops the oscillator at ground and sets maximum frequency at Vcc. Though to get a 50% duty cycle one must add a flip-flop to the output.
I'm really just going for a cool toy that will make lights blink and go woo-woo when I put together a ring of oscillators, this does not have to be super precise. That and the limited types of modulation input kind of make for a departure from ChucK, however. But that's OK too. It can simply be ChucK-inspired not ChucK duplicated.
Les (Inventor) _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
Hi All,
I suspect the charm of this would be the roughness and unpredictability...
the thing'll have a life of its own, with all sorts of emergent sonic
qualities. Non-audiophile quality isn't a bug, it's a feature.
Not sure it's got all that much to do with chuck, and I very much doubt
it'll make anyone rich... but all good fun.
Cheers,
peter
On Thu, Oct 2, 2008 at 7:50 PM,
Kassen,
Your point is well taken. I guess I'm not concerned about the audiophile quality of this system at all. If it's going to be so inexpensive then it will probably be inaccurate as well, and I'm OK with that. It's not intended to produce perfectly orchestrated audio, but rather to do something fun and interesting.
Also, that 555 example was indeed for a variable frequency oscillator, more specifically a pulse position modulator from the data sheet. there is a CV input that stops the oscillator at ground and sets maximum frequency at Vcc. Though to get a 50% duty cycle one must add a flip-flop to the output.
I'm really just going for a cool toy that will make lights blink and go woo-woo when I put together a ring of oscillators, this does not have to be super precise. That and the limited types of modulation input kind of make for a departure from ChucK, however. But that's OK too. It can simply be ChucK-inspired not ChucK duplicated.
Les (Inventor) _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
Peter Todd; Hi All,
I suspect the charm of this would be the roughness and unpredictability... the thing'll have a life of its own, with all sorts of emergent sonic qualities. Non-audiophile quality isn't a bug, it's a feature.
Not sure it's got all that much to do with chuck, and I very much doubt it'll make anyone rich... but all good fun.
Your mail came in right as I was catching up on this conversation and I'll pick yours to reply to as it's closest to my own thoughts. <some free-form assositions> For a long time modular synths were my favourite instruments, they were most conductive to strange experiments and for hardware ones there is the physical appeal, not in the last place because with a large enough modular two or even three people can play and patch it at the same time. As I mentioned earlier; one of the big issues is that the modules are typically in fixed locations and so you tend to end up with a bird's nest of cables. Seeing your own patch on a analogue modular the next morning can be worse then seeing your own year old code (I have been known to use post-it notes...). I agree with your perspective here; this does bring out some of the best aspects of hardware modulars while nicely side-stepping the traditional problems. For me, BTW, this has a lot to do with ChucK. Describing how to construct a modular synthesis patch, even to a fellow modular enthousiast can be quite hard. At times I have longed for a formal, non-ambiguous way of describing modular synthesis patches and in some way ChucK is exactly that. A few years ago I might've described a simple monophonic synth to a friend by email as; Sawosc => LPF => ADSR => springreverb. This is almost correct ChucK code, aside from the modules not having a name. Them not having a name would invariably be where those conversations would get tricky. "that ADSR that I mentioned that modulates the LFO" is quite awkward yet I've seen worse in printed manuals for commercial synthesisers. Ok, admittedly that still had only a vague relation to ChucK but to me it's a relevant relationship. I'm interested in this and I'd also be interested in a reactable-like interface for ChucK but the precise nature of ChucK's syntax in pure text form holds at least as much appeal to me as relatively cheap, relatively random, nature of these proposed modules. Yours, Kas.
Or you could be like Bebe and Louis LaBarron, and just overdrive the heck
out of to force things to make unintended sounds... but of course, once you
are done, you end up with a useless piece of hardware, as you burned it to
death...
Mike
On Thu, Oct 2, 2008 at 2:54 PM, Peter Todd
Hi All, I suspect the charm of this would be the roughness and unpredictability... the thing'll have a life of its own, with all sorts of emergent sonic qualities. Non-audiophile quality isn't a bug, it's a feature.
Not sure it's got all that much to do with chuck, and I very much doubt it'll make anyone rich... but all good fun.
Cheers, peter
On Thu, Oct 2, 2008 at 7:50 PM,
wrote: Kassen,
Your point is well taken. I guess I'm not concerned about the audiophile quality of this system at all. If it's going to be so inexpensive then it will probably be inaccurate as well, and I'm OK with that. It's not intended to produce perfectly orchestrated audio, but rather to do something fun and interesting.
Also, that 555 example was indeed for a variable frequency oscillator, more specifically a pulse position modulator from the data sheet. there is a CV input that stops the oscillator at ground and sets maximum frequency at Vcc. Though to get a 50% duty cycle one must add a flip-flop to the output.
I'm really just going for a cool toy that will make lights blink and go woo-woo when I put together a ring of oscillators, this does not have to be super precise. That and the limited types of modulation input kind of make for a departure from ChucK, however. But that's OK too. It can simply be ChucK-inspired not ChucK duplicated.
Les (Inventor) _______________________________________________ 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
-- Peace may sound simple—one beautiful word— but it requires everything we have, every quality, every strength, every dream, every high ideal. —Yehudi Menuhin (1916–1999), musician
Hmm, so you mentioned using PICs to program UGens... to me, it seems wasteful to pass analog audio between a graph of PIC + ADC/DAC's, why not pass digital audio between multiple PIC units? A digital modular synthesizer of sorts. A simplified SPDIF or I2S might do the trick for shuttling samples around. There could be designs for ADC/DAC units, and also USB Audio-class units for I/O to conventional computers. It seems interference/parasitic issues might be more problematic for a digital signal on unshielded cabling, but I can't claim to be an expert on any of this. One also loses analog cred in this way, but it would definitely keep costs down, and permit easy on the fly reprogrammability. spencer On Oct 2, 2008, at 11:50 AM, inventor-66@comcast.net wrote:
Kassen,
Your point is well taken. I guess I'm not concerned about the audiophile quality of this system at all. If it's going to be so inexpensive then it will probably be inaccurate as well, and I'm OK with that. It's not intended to produce perfectly orchestrated audio, but rather to do something fun and interesting.
Also, that 555 example was indeed for a variable frequency oscillator, more specifically a pulse position modulator from the data sheet. there is a CV input that stops the oscillator at ground and sets maximum frequency at Vcc. Though to get a 50% duty cycle one must add a flip-flop to the output.
I'm really just going for a cool toy that will make lights blink and go woo-woo when I put together a ring of oscillators, this does not have to be super precise. That and the limited types of modulation input kind of make for a departure from ChucK, however. But that's OK too. It can simply be ChucK-inspired not ChucK duplicated.
Les (Inventor) _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
participants (6)
-
inventor-66@comcast.net
-
Kassen
-
Mike McGonagle
-
Peter Todd
-
Robert Carter
-
Spencer Salazar