Dear list, SqrOsc (and SawOsc as well) seem to having a issue with their .width function, in particular; it doesn't work. PulseOsc and TriOsc are fine. It's not so clear to me how PulseOsc is different from SqrIOsc aside from this (I don't hear a difference, really). Depending on how "width" is seen TriOsc and SawOsc may be the same as well but with different dutycycles so perhaps there is no functional issue but it should probably still work as advertised. Demo for convenience pasted below. Yours, Kas. SqrOsc s => dac; while(second => now) { //this bit doesn't work Std.rand2f(.1, .9) => s.width; }
Hi Kassen, I think SqrOsc is supposed to have a fixed width of 0.5. regarding SawOsc the documentation states that it only affects wether width <0.5 (decreasing ramp, thus peak at 0) or width >0.5 (increasing ramp, thus peak at 1). As a side note the documentation states that Phasor has, as well, a width member, but chuck complains with class 'Phasor' has no member 'width'. eduard On 21 Apr 2008, at 09:24, Kassen wrote:
Dear list,
SqrOsc (and SawOsc as well) seem to having a issue with their .width function, in particular; it doesn't work.
PulseOsc and TriOsc are fine. It's not so clear to me how PulseOsc is different from SqrIOsc aside from this (I don't hear a difference, really). Depending on how "width" is seen TriOsc and SawOsc may be the same as well but with different dutycycles so perhaps there is no functional issue but it should probably still work as advertised.
Demo for convenience pasted below.
Yours, Kas.
SqrOsc s => dac;
while(second => now) { //this bit doesn't work Std.rand2f(.1, .9) => s.width; } _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
On 21/04/2008, eduard aylon
Hi Kassen,
Hi, Eduard! I think SqrOsc is supposed to have a fixed width of 0.5. The manual does claim it the .width for SqrOsc refers to "duty cycle" and unlike SinOsc the compiler doesn't complain when we send numbers to it. As I said; functionally speaking we are fine because PulseOsc does the job but it's confusing. regarding
SawOsc the documentation states that it only affects wether width <0.5 (decreasing ramp, thus peak at 0) or width >0.5 (increasing ramp,
thus peak at 1). Ah, that I missed. That's unusual but not a problem. As a side note the documentation states that Phasor has, as well, a
width member, but chuck complains with class 'Phasor' has no member 'width'.
Well, there I think it's fairly clear that the manual is wrong, or perhaps it would be useful to have Phasor react like SawOsc does? Thanks, Kas.
Another issue; The manual claims PulseOsc.width() to be read/write but I think it's write only. Not sure which one is right but wherever possible I prefer "readable" functions for debugging purposes. Yours, Kas.
Currently SqrOsc and PulseOsc are broken. Reading from .width does not work. I think that SqrOsc.width should just return 0.5 PulseOsc.wdith isn't readable but should be. SqrOsc.width is writeable when it shouldn't be. I'll change the manual in CVS to reflect the current state of these. Maybe these could be fixed in the next release? Thanks everyone for finding this stuff and problems with the manual. Keep em coming and it will all get better over time. --art
Hey, Adam!
You're back "on the case"? In that case I'll get back to adding issues and
suggestions to the relevant WiKi page as well. Good to hear.
Does ScrOsc have any advantages over PulseOsc at all, BTW? As I mentioned I
don't hear a difference between them at the default settings but maybe
SqrOsc is cheaper as it doesn't need to calculate width?
I added both issues to the WiKi's page on bugs to be fixed in the next
release for convenient tracking.
Cheers,
Kas.
On 24/04/2008, Adam Tindale
Currently SqrOsc and PulseOsc are broken. Reading from .width does not work. I think that SqrOsc.width should just return 0.5 PulseOsc.wdith isn't readable but should be. SqrOsc.width is writeable when it shouldn't be.
I'll change the manual in CVS to reflect the current state of these. Maybe these could be fixed in the next release?
Thanks everyone for finding this stuff and problems with the manual. Keep em coming and it will all get better over time.
--art
_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
participants (3)
-
Adam Tindale -
eduard aylon -
Kassen