btw. for recording scsynth as it runs a jack recorder
can be simpler to manage, at least so i find. i tend
to use jack.record + jack.plumbing, but there are
many others about.
darcs get http://slavepianos.org/rd/sw/sw-77/
___
haskell-art mailing list
drat, different client same problem, sorry...
---BeginMessage---
Henning Thielemann [EMAIL PROTECTED] writes:
what gives that error? hosc or hsc3 or scsynth?
scsynth
ok, i'd guess that restriction could be trivially lifted
for nrt but it is not usually an issue. of course, in
this case the
Henning Thielemann [EMAIL PROTECTED] writes:
I boiled the problems down to a simple example. There are no errors
reported about the messages, but the result is not what we expect.
I've added encodeNRT and writeNRT to hsc3, these
ought to work out of the box. Let me know if
that helps. (They
Henning Thielemann [EMAIL PROTECTED] writes:
We need
encodeOSCZeroBase :: OSC - B.ByteString
which converts a message by converting Double to Integer
and does the message encoding (which is currently done by encodeOSC)
delayOSC :: Double - OSC - OSC
which shifts a message in time
Henning Thielemann [EMAIL PROTECTED] writes:
But I indeed mean 'zero based'. Since scsynth doesn't know about Haskell's
OSC type we can use any time base, and I think time base 0 is the most
natural one. The actual time base needed for scsynth is added when
encoding the message.
the meaning
this all works here, apart from the fixed SR in the
audio file, which does not correspond to the SR that
scsynth runs at (-S doesn't seem to help, but
whatever...)
your osc file and the generated file are equal,
at least according to cmp...
~$ cmp tone.osc ht-tone.osc
~$
not sure what the
Henning Thielemann [EMAIL PROTECTED] writes:
I hoped that in non-realtime mode scsynth would simply generate the same
sound as in the realtime mode, but there are crackles in the generated
audio files. They look and sound like artifacts of too high elongations
and probably different clipping
Dear Henning,
Recently I had a bug in my program, which was due to adding 'out'
twice to a UGen (however at different places). I thought it could be
better to give UGens which have no output (in other words: UGens that
cannot be input of other UGens), a different type. Say
out :: UGen -
Rohan Drape [EMAIL PROTECTED] writes:
(and are biased to using many single threaded
connections, hence wait design etc.)
that was a little terse, to clarify:
wait in hosc discards any non-matching messages in the queue until it
receives the waited for message.
error handling at sc3
alex,
On Tue, Apr 1, 2008 at 1:41 AM, alex [EMAIL PROTECTED] wrote:
I'm planning on using a midi device in a performance on Friday, does
anyone already have some example code for using this to control
supercollider patchecs made with Rohan's HSC3, to save me a bit of time?
If not I'll
great, thanks, mce is what i was looking for. am i correct in
there is a start of a sketch of the mce rules at:
http://slavepianos.org/rd/sw/hsc3/Help/hsc3.help.lhs
(ie. in the hsc3 sources, notes from never completed sc3 book effort)
assuming that in' 2 AR 0 compiles to a single In ugen,
11 matches
Mail list logo