[chuck-dev] Fwd: Oh no, I fixed it: log level bug.

[Andrew C. Smith]

>> What is the problem with using the STK .h and .cpp files "as is" in Chuck?

Just to be clear: RtAudio.cpp/.h are the same in both the ChucK and
standard versions--we're talking about the ModalBar, Envelope, FM etc.
UGens, right?

>> around to it by December but I see no rush, as those functions are still
>> supported until at least the next major OS release.

Well, I asked in part because I was trying to work on the ChucK
functions to iron the errors out of building toward the 10.6 SDK.
Also, I ended up writing some stuff that wouldn't work with 10.5 SDK
because of new Cocoa methods, and wouldn't work on 10.6 because of the
RtAudio methods. I feel like I managed to hack it to just omit the
problem functions, but I can't seem to find that modified RtAudio.cpp
file...

In case you don't have Snow Leopard, or you're not working on it yet,
the functions that are deprecated are AudioHardwareGetProperty,
AudioDeviceSetProperty, AudioHardwareGetPropertyInfo,
AudioDeviceGetProperty, AudioDeviceGetPropertyInfo,
AudioStreamGetProperty, AudioStreamSetProperty, and
AudioDeviceAddPropertyListener. It seems like a pretty small set of
functions, and nothing very complicated at all--just setter and getter
methods that I would assume are replaced by @property and @synthesize,
but who knows. My ugly hack involved using your playsaw program to
probe for devices, then just using those property values as constants
to drive my code. Um, I can't say it ever worked, though.

Thanks, Gary, I didn't expect you to necessarily be listening in.
Should be careful what I say on this list.

Andrew

On Thu, Oct 22, 2009 at 3:45 PM, Kassen <signal.automatique at gmail.com> wrote:
> Hi Garry.
>
>>
>> The deprecated functions in RtAudio are a relatively easy fix.  I will get
>> around to it by December but I see no rush, as those functions are still
>> supported until at least the next major OS release.  RtAudio from 2005 ...
>> wow, that's many releases old!
>>
> That would be good, as using the newer version or RtAudio would also solve
> the lack of ASIO on Windows, right? I have been campaigning for that for a
> long time now. Plain Windows audio drivers for realtime instrumentalist
> applications are a exercise in masochism, at least on XP.
>
>>
>> What is the problem with using the STK .h and .cpp files "as is" in Chuck?
>>
>
> Data-types.
>
> The STK lacks a concept of duration and so classes like Envelope in the
> plain STK set duration-based member functions in float. In ChucK we should
> clearly set duration in "dur". ChucK also changed the range of some
> parameters away from MIDI-based ranges to a 0-1 range. Also; we made some
> fixes to STK bugs that I'm not sure were send upstream.
>
> I'm not sure what you mean by ChucK having added soundfile support recently.
> I suppose it depends on what you call "recent", but I'm sure it has been
> there since I have been around which is about since the Dracula version. I
> don't think I can remember any significant changes in that area over this
> period.
>
> Syncing might still be good, but IMHO not without taking care that the way
> that ChucK uses the STK stays within this more ChucKist perspective on UGen
> control.
>
> Yours,
> Kas.
>
> _______________________________________________
> chuck-dev mailing list
> chuck-dev at lists.cs.princeton.edu
> https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev
>
>