<d1b2>
<azonenberg> Yes that is true with a lot of scopes
<d1b2>
<azonenberg> we have to do some finagling to control sample rate and memory depth, often one of them requires changing another variable etc
<d1b2>
<azonenberg> as far as interleaving the problem with the HMCAD15xx based scopes like the ds1000z is that there are three possible configurations, not two
<d1b2>
<azonenberg> since its one shared adc for all the channels
<d1b2>
<azonenberg> While the API is designed around the assumption that you have one adc per channel and you can optinoally combine two adjacent channels
<d1b2>
<azonenberg> What you probably want is something similar to what we do on Pico
<d1b2>
<azonenberg> Where we never advertise interleaving, and GetSampleRatesNonInterleaved() changes its return value dynamically based on the currently enabled set of channels
<d1b2>
<azonenberg> As far as API docs, yes this is something we are working on. The focus for the v0.1 release is primarily getting the end user facing docs to be "good" since that's the one more people are going to read
<d1b2>
<azonenberg> Dev facing docs will probably be more of a v0.2 priority
josuah has quit [Quit: zzz]
<d1b2>
<johnsel> I'm surprised you do prefer this option, unless there is some way to indicate that some samplerates arent available due to the amount of channels enabled?
<d1b2>
<johnsel> @azonenberg did you end up rescheduling the call?