Why do online & offline chirps differ when using Python 2.0.0 SDK's save_wav?

Solved!
Posted in API by Jason Denney Mon Jan 30 2017 01:25:49 GMT+0000 (UTC)·3·Viewed 163 times

On OSX with Python 2.0.0 SDK, using sdk.save_wav(chirp, offline=True) produces a different (and unusable) chirp wav file as opposed to when offline is set to False. Also, it errors if the chirp is ultrasonic, thus am unable to save ultrasonic chirps. Anyone else with this issue? Maybe I'm doing something wrong?
Quentin Roquefort
Jan 30, 2017

Hello Jason,

This is a known bug we've been working on and it will be fixed in an upcoming version later this week.
This is especially problematic for ultrasonic chirps that can't be generated online.

I'll post an update here as soon as the new version is deployed.

Many thanks for your feedback,

Quentin Roquefort
Feb 2, 2017

Hello Jason,

Version 2.0.1 of our Python SDK has been released with the fix to offline wav file generation.
You can update it either from pypi or our Admin Centre.

Thanks,


Quentin Roquefort marked this as solved
Jason Denney
Feb 2, 2017

Thanks!

Markdown is allowed