Difference between revisions of "ChucK/Bugs/Release"

From CSWiki
Jump to: navigation, search
m
(Hopefully these will be fixed for the next release of ChucK)
Line 15: Line 15:
 
As posted to the list, July4(Kas.)
 
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)'''
 
*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;
 +
me.id() => int my_id;
 +
fun void second_shred()
 +
    {
 +
    second => now;
 +
    Machine.remove(my_id);
 +
    }
 +
spork ~ second_shred();
 +
hour => now;
 +
 
* go for it!
 
* go for it!

Revision as of 14:52, 13 August 2007

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.

  • 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;

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

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

spork ~ second_shred(); hour => now;

  • go for it!