Henning Thielemann <[EMAIL PROTECTED]> writes:
| Slightly off-topic: Do you know of an USB MIDI interface that can be used
| without hassle on Linux (Suse or Kubuntu)?
i've a rather old m-audio midisport2x2, quite solid green metal case &
good alsa support, not at all sure if they still make them
Henning Thielemann <[EMAIL PROTECTED]> writes:
> > > -- Either variant allowing for both.
> > > data Which a b = One a | Other b | Both (a,b) deriving (Eq, Show)
>
> Probably not. Is (Maybe a, Maybe b) also appropriate?
Not really, precisely because:
> This also contains the case (Nothing, Noth
Henning Thielemann <[EMAIL PROTECTED]> writes:
> Is it possible to merge more than two sequences? In this case a non-empty
> list type may be a solution. You need different types? Do you have
> different types of events?
Yes, and for the case where all sequences are of the same type there
is a fun
On Thu, July 12, 2007 7:36 pm, Henning Thielemann wrote:
>
> On Wed, 11 Jul 2007, Henning Thielemann wrote:
>
>> I want to write the SuperCollider output into a file.
>> Server-Architecture.rtf tells me that I must use the -N option. However
>> I
>> need a file of OSC messages. Shall I replace all
followed wrong reply link, forwarding to list...
Original Message
Subject: Re: [haskell-art] Re: Creating .wav or .aiff with
SuperCollider/HSC3
From:"Rohan Drape" <[EMAIL PROTECTED]>
Date:Tue, July 24,
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...
--- Begin Message ---
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
apologies yet again, another two mis-directed replies...
--- Begin Message ---
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.
This is an NTP/UTC issue.
OSC t
--- Begin Message ---
Henning Thielemann <[EMAIL PROTECTED]> writes:
> On Tue, 24 Jul 2007, Rohan Drape wrote:
>> btw. for recording scsynth as it runs a jack recorder
>> can be simpler to manage, at least so i find. i tend
[snip]
> But this means waiting for a song to
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. (The
Henning Thielemann <[EMAIL PROTECTED]> writes:
> However I consider it a slight hack to first add magic number 2208988800
> in utc_ntp, then subtract it in ntpZeroed again. Would you mind making the
> Bundle time zero based and add the appropriate offset at encoding the
> message?
2208988800 = (70
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 i
> 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 m
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 mean
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 m
Henning Thielemann <[EMAIL PROTECTED]> writes:
> I noticed it sporadicly but now I see that it is reproducable: If I send
> the synth description and the invokation of the synth in the same
> bundle then I get
> FAILURE /s_new SynthDef not found
d_recv, as the manual notes, is asynchronous, you n
On Tue, August 14, 2007 11:32 pm, Henning Thielemann wrote:
> I used this implementation so far, but I hoped that sending bundles makes
> this synchronous automatically.
this doesn't make sense? the async commands are
precisely those that cannot be run from the
synthesis thread, they are staged a
Henning Thielemann <[EMAIL PROTECTED]> writes:
> What about sharing of a signal for multiple function calls in HSC3?
hsc3 shares ugens that have equal 'id' fields and equal
inputs (it can't tell these apart).
writing (sinOsc AR 440 0 + sinOsc AR 440 0) makes only
one sinOsc ugen.
hence noise an
wrong reply address again, drat, forwarding...
--- Begin Message ---
Henning Thielemann <[EMAIL PROTECTED]> writes:
> My problem is: What time shall I expect for installing the synth graph at
> the server? Any delay I choose is either too long or too short. I want to
> say "install the sound, such
Henning Thielemann <[EMAIL PROTECTED]> writes:
> Then I'll go ahead with separated initialization and run phase. However I
> feel that at some time in the future I will want to install new sounds
> while playing others, then the problem will turn up again.
there is no problem doing other things wh
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 clipp
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
> I guess that the MIDIIn UGen of SuperCollider is for reading MIDI
> controllers, but I cannot find wrappers in Rohan Drape's SuperCollider
> wrapper. Are they supported under Linux at all?
MIDIIn and family are not UGens, they are sclang classes.
Writing directly to /dev/midi under linux is a s
hello john & stefan,
Stefan Kersten <[EMAIL PROTECTED]> writes:
> incidentally, i've been working on libsndfile bindings the last few
> days; here's the darcs repository:
>
> http://darcs.k-hornz.de/cgi-bin/darcsweb.cgi?r=hsndfile;a=summary
excellent news! i have, _much_ more incidentally,
a si
everything stefan says is true. the hosc
bindings are really just enough to use sc3.
(and are biased to using many single threaded
connections, hence wait design etc.)
> command and consequently you might get /synced too early. that's not
> a problem with TCP, of course.
the problem with tcp is
"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.
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'l
hello dave (& list),
looks like a cabal/ghc/hosc version mismatch.
unfortunately i'm no cabal expert, the setup
i have here is:
$ grep Version hosc.cabal
Version: 0.3
$ ghc --version
The Glorious Glasgow Haskell Compilation System, version 6.8.2
$ ls ~/lib/ghc-6.8.2/lib | grep Ca
hello stefan,
> is there a particular reason soundIn hides the number of channels
> being read? maybe a variation (soundInN?) could be added?
i'm not sure i understand the question, can you perhaps elaborate?
the number of channels being read is the degree (number of output
ports) of the input
> 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,
> great, thanks, mce is what i was looking for. am i correct in
> assuming that in' 2 AR 0 compiles to a single In ugen, while soundIn
> [0, 1] references two? what i meant was making the first argument to
actually, i don't think this is written down anywhere, but for unit
generators that
in sc
hello stefan,
> i've attached a patch; there's a slight runtime overhead of course for
> detecting consecutive bus indices ... the test for an empty input MCE is
> also slightly ugly, probably there's a better way.
excellent, many thanks! i am away for a few days but will apply and push
next we
hello stefan,
> i've attached a patch; there's a slight runtime overhead of course
> for detecting consecutive bus indices ... the test for an empty input
> MCE is also slightly ugly, probably there's a better way.
finally applied and pushed, away longer than expected.
i deleted the empty mce te
hello stefan (& re-directed list),
sk on haskell@ list:
> Haskell bindings for libsndfile.
> http://darcs.k-hornz.de/cgi-bin/darcsweb.cgi?r=hsndfile;a=summary
excellent work! thanks very much, this will be _very_ useful.
to celebrate i've added a simple waveset synthesis example to haskell
supe
hello stefan,
On Mon, Jun 9, 2008 at 10:03 PM, stefan kersten <[EMAIL PROTECTED]> wrote:
> when working with ugens with lots of arguments, i think it could be
> helpful to have infrastructure or conventions for named arguments,
i tend to agree
> maybe it's possible to help writing the boilerplat
hello stefan,
out of order:
> i've attached a new version of Sound.SC3.UGen.Record.Pitch, with the
> arguments reordered as to henning's suggestion ...
applied & pushed, thanks.
> what are the namespace issues? shouldn't qualified modules imports
> avoid name clashes?
yes, qualified names help
hello stefan & list
cc-ing reply to list as this may well break code (henning & alex?)
>>> in general i think it would be better anyway to
>>> type the timetag field in the Bundle constructor more strongly, but
>>> maybe it would break too much existing code?
>>
>> as in
>>
>> data OSCTime = UTCr
Henning Thielemann <[EMAIL PROTECTED]> writes:
> Different from what is stated in lfSaw.help.lhs, the iphase parameter
> is not given in radians (0..2*pi), but ranges from 0 to 2.
correct, i've fixed the help file (it's already fixed
in the sc3 help file, usually worth checking if something
seems
38 matches
Mail list logo
