Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Report Errors/Spikes to Rdio Scanner #660

Merged
merged 1 commit into from
Apr 3, 2022

Conversation

taclane
Copy link
Contributor

@taclane taclane commented Mar 31, 2022

API-compliant fix for Rdio Scanner to see transmission errors and spikes.

The Rdio plugin API takes the following input:

- frequencies - [optional] JSON array of objects for frequency changes throughout the conversation.
{
errorCount: number;
freq: number; // in hertz
len: number; // in seconds
pos: number; // in seconds
spikeCount: number;
}[];

Uploading errors/spikes to Rdio Scanner via the upload-script method should already work as of this branch. When parsing a t-r metadata file, r-s is expecting error_count and spike_count json keys which recent commits now provide.

API-compliant fix for Rdio Scanner to see transmission errors and spikes.
@taclane
Copy link
Contributor Author

taclane commented Mar 31, 2022

This should address #602 as well as some of the comments in #635.

@robotastic robotastic merged commit a2ce88a into robotastic:no-overlap Apr 3, 2022
@taclane taclane deleted the rdio-scanner-error-spike branch May 16, 2023 21:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants