This might be a problem with either RSound or Portaudio. The contract on RSound's signal/block-play/unsafe promises that it will treat its first argument, block-filler, as a (-> cpointer? natural? void?) function, but it passes it to Portaudio's stream-play/unsafe, which treats it as a (-> cpointer? int? void?) function.
This might be a problem with either RSound or Portaudio. The contract on RSound's
signal/block-play/unsafe
promises that it will treat its first argument,block-filler
, as a(-> cpointer? natural? void?)
function, but it passes it to Portaudio'sstream-play/unsafe
, which treats it as a(-> cpointer? int? void?)
function.So,
stream-play/unsafe
calls it with the int-630867962
wheresignal/block-play/unsafe
promised a natural number.Is
stream-play/unsafe
in the wrong here? Is this some kind of overflow, or is it supposed to be able to use negative integers?