After quite a bit of additional experimenting I've been able to duplicate your issue and I agree this likely is a bug. It's related to how BIAB handles the erasure of the wav file. It's not picking that up and therefore for lack of a better word, thinks the wav is still there.

I will report this to the developers.

Charlie


BIAB 2025:RB 2025, Latest builds: Dell Optiplex 7040 Desktop; Windows-10-64 bit, Intel Core i7-6700 3.4GHz CPU and 16 GB Ram Memory.