Currently, the sampling rate needs to be set in the config file by the user although the sampling rate is fetched directly from the WaveRunner scope.
To overcome this issue, we could have two alternative scope constructors on the 'API', one based on samples, one based on cycles and internally they can nicely share the code.
Currently, the sampling rate needs to be set in the config file by the user although the sampling rate is fetched directly from the WaveRunner scope.
To overcome this issue, we could have two alternative scope constructors on the 'API', one based on samples, one based on cycles and internally they can nicely share the code.