Impressed, eh? If you knew my obsession with trying to spot the pattern between requested versus achieved capture counts, you'd probably be sending in the Nice Young Men In Their Clean White Coats...
Luckily you don't know how many hours I've spent, repeating trial runs, trying to become competent, confident and "fluent" with this new tool. Not just with this question of capture size, but with most other aspects too. But the breakthrough evades me. I don't want to stay a simple-minded user, relying only on basic features.
Even trying to use only the basics, I go back to the broken car, patiently reconnect the test wires, and fail, fail, fail to execute the intended plan; fail, fail, fail to capture the set of traces that I need: flummoxed by the sophisticated tool that does something that I didn't expect, in response to a "trivial" change.
Back on topic: the Sample Rate Calculator is really neat and will help me to overcome this example of deficiency in the documentation.
My second thought: why isn't the Sample Rate Calculator built into the software?
My third thought: is something back-to-front here? Since capture size and sampling rate are (IMO) so important, why bury then in the background? -- Question for Michael
Best regards to all,