[Rohan Drape] Re: [Fwd: Re: [haskell-art] Re: Creating .wav or .aiff with SuperCollider/HSC3]
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 case the size was probably off by 2^31 or so... >> try unreversed encode_i32 (osc tends to use sized integers, >> this is the case also for bundle sizes) > > Is the difference between u32 and i32, unsigned vs. signed? yes, a typo in my message, replace sized with signed. > Good to know. perhaps... actually nrt in scsynth is very nice, what are ordinarily asynchronous operations become synchronous (eg. b_alloc and friends). rt designs generally 'degrade' well to nrt use, the other direction tends to be a disaster area. --- End Message --- ___ haskell-art mailing list haskell-art@lists.lurk.org http://lists.lurk.org/mailman/listinfo/haskell-art
Re: [Fwd: Re: [haskell-art] Re: Creating .wav or .aiff with SuperCollider/HSC3]
On Tue, 24 Jul 2007, Rohan Drape wrote: > 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, 2007 9:52 am > To: "Henning Thielemann" <[EMAIL PROTECTED]> > -- > > On Tue, July 24, 2007 5:35 am, Henning Thielemann wrote: > > I have used the TCP transport data type and derived a File data type from > > it. However I got the error that the OSC message is longer than 8192 > > what gives that error? hosc or hsc3 or scsynth? scsynth > > let b = encodeOSC msg > > n = fromIntegral (B.length b) > > in B.hPut fd (B.append (B.reverse (encode_u32 n)) b) > > > > Now it seems that the times are not interpreted properly: > > try unreversed encode_i32 (osc tends to use sized integers, > this is the case also for bundle sizes) Is the difference between u32 and i32, unsigned vs. signed? > > Maybe this is still an issue of byte ordering. Server-Architecture.rtf > > states that values must be in network byte order. What is 'network byte > > order' in the case of files? > > network order = big endian. there are a few simple score functions at: > > http://slavepianos.org/rd/sw/sw-76/Rhs/Score.hs > > i've not used these recently though! Good to know. ___ haskell-art mailing list haskell-art@lists.lurk.org http://lists.lurk.org/mailman/listinfo/haskell-art
