ChucK/Bugs/Release

From CSWiki
Revision as of 04:57, 24 April 2008 by Kassen (talk | contribs)

Jump to: navigation, search

Hopefully these will be fixed for the next release of ChucK

Please enter the bug as descriptively as possible, with the shortly code that shows the symptom. Examples can be found here.

  • Probable typos in the source discovered by Moudi while attempting to build a ASIO MiniAudicle as well as various other issues and potentially questionable bits;

[[1]] (Ah, I just noticed this is already in the works)

  • Full out crashage when defining a class within a class, maybe that should simply be illegal like defining a function within a function is? Info with example by Pablo;

[[2]]

  • Sitar.pluck() doesn't work and giving Sitar very low notes results in errors, so many errors that it breaks up audio. I looked into it but had a hard time deciding what the desired functionality should be --Kassen 07:33, 7 December 2007 (EST).
  • .getchar() for the old keyboard interface doesn't adhere to the new (coherent) naming scheme yet, I think it should be .getChar() with the old one getting depreciated --Kassen 07:33, 7 December 2007 (EST).
  • a class that extends Event needs to be defined before it's called or there will be a complaint that the class doesn't have a member named "broadcast" or "signal". Example that will yield a complaint yet should be correct;
Trigger trig;
trig.broadcast();
class Trigger extends Event { int target; }

(as reported on the list March3) --Kassen 14:06, 3 March 2008 (EST)

  • Seg-fault at overloaded functions returning non-identical-type arrays.
  • more seg-faulting at something (probably) involving assignment to arrays in functions that were parameters (as per email, here for tracking) --Kassen 00:33, 27 March 2008 (EDT)
  • PulseOsc.width() is write only (should be read-write according to the manual)
  • SqrOsc.width() exists but doesn't do a thing. Manual claims it works, Adam (on the list) suggested it should return .5 but not be writable. this makes sense as PluseOsc has this covered.--Kassen 05:56, 24 April 2008 (EDT)
  • (add your own)

Fixed in 1.2.1.1

  • Odd Envelope behaviour. Documentation and a suggested fix to be found here; [[3]]


Fixed in 1.2.1.0

  • Make sure members of classes get properly instantiated when the instances of the classes are implicidly defined in a array (as discussed on the list June10 to July7, found by Eduard) (ge: fixed and will be in 1.2.0.9)
  • Arrays of Ugens over 10 locations long inside of classes will crash, like this; (ge: this should now work - part of the above fix)
// I picked this 10 at random, for length 5 it'll crash too
Foo x[10];
class Foo
    {
    // at length 10 it'll run but this will crash(!!??)
    SndBuf array[11];
    }

As posted to the list, July4(Kas.)

  • 1 => rhodey.noteOff (and the same for wurley) cause stuck-notes.(kas.) (ge: bug in ADSR from an earlier fix, oops. now fixed, hopefully and will be in 1.2.0.9)
  • crash because of killing the parent-shred; (ge: bug in VM messaging not quite expected the remove to come from calling shred or his/her parent! fixed, and will be in 1.2.0.9)

me.id() => int my_id; fun void second_shred()

   {
   second => now;
   Machine.remove(my_id);
   }

spork ~ second_shred(); hour => now;