Not surprising. the only thing in this patch that would tell the sfplay~ object to loop what it's playing back is connected to the toggle that turns sfplay~ on/off rather than to the sfplay~ object, and whoever patched this didn't notice that the $1 means that the message box is waiting to substitute an input value [say, from a toggle] in order to send a message like "toggle 0" or "toggle 1." The toggle object sure won't know what to do with that [although an sfplay~ object would].