A little further investigation shows that going to from 1Msps to 100ksps significantly improves the data streaming. Of course, this isn't great if we want high temporal resolution data, but at least it's a clue. Moving the scope API calls off the main thread might help, in case there is some content...

The saga continues! It might be something being done wrong on my end once more, but I get weird spikes, typically offsets by 0xFED1 (-0x12F or 303 decimal) more or less often in my streaming data through the SDK. I cannot replicate this in the Picoscope software, but I am also unsure when it is stre...

Thanks, I did figure out that there was a typo in the buffer setup, leading to the wrong size being computed.

As a follow up, I figured out that the crash likes to happen with fast data rates, but streaming does kind of work with lower sampling rates. However, one odd thing I found is that the streaming callback will indicate there being more data than the buffer is long, how is one supposed to handle that ...

I'm trying to get a Swift Mac app to talk to my 3405D MSO scope with the SDK v10.7.21.227, on Apple Silicon. The initial connection seems fine, eg. the device is detected and can be queried for properties. Unfortunately, I cannot seem to get the streaming to work, as it produces an EXC_BAD_ACCESS so...