I didn’t realise there was anything else to do other than read the contents of the particular buffer returned in the callback. I understood from the documentation that the buffer switching happened in the background. If this wasn’t the case then surely I’d be getting overruns every callback? I’m not and the code has been running mostly well for months on end. Only the recent storms seem to have intensified the issue.
I don’t see anything in the code examples to suggest what to do with an emptied buffer other than to leave it to the device to refill… or am I misunderstanding you?