ForestCat

This may be common sense, but it bit me, so I pass it along for fellow noobs..

If you are, for example, observing the isRecording property of a clip, and that clip is deleted while it is recording, any downstream logic in your patch will continue to believe that clip is still recording, since the observed isRecording property doesn't change once the clip is deleted. This will bite you if you are relying on that logic to turn off LEDs (in my case...), etc. Since I'm doing everything w/ footswitches via m4l, the solution for me was simply to disarm the track(pops it out of record) before I call delete_clip. If you're using the ui/delete key, etc., it may be a little trickier...

If you are, for example, observing the isRecording property of a clip, and that clip is deleted while it is recording, any downstream logic in your patch will continue to believe that clip is still recording, since the observed isRecording property doesn't change once the clip is deleted.  This will bite you if you are relying on that logic to turn off LEDs  (in my case...), etc. Since I'm doing everything w/ footswitches via m4l, the solution for me was simply to disarm the track(pops it out of record) before I call delete_clip.  If you're using the ui/delete key, etc., it may be a little trickier...


Careful when deleting observed objects...