This should be done when the user clicks the save button. Data should sent to the API for storing recordings.
The audio data is stored in an audio element until this is done (or the page is closed/refreshed). Prompt identifier will also be included.
| Sebastian_Berlin-WMSE | |
| Jan 26 2021, 9:58 AM |
This should be done when the user clicks the save button. Data should sent to the API for storing recordings.
The audio data is stored in an audio element until this is done (or the page is closed/refreshed). Prompt identifier will also be included.
| Subject | Author | Repo | Branch | Lines +/- | |
|---|---|---|---|---|---|
| [WIP] Send recording to API | Sebastian Berlin (WMSE) | mediawiki/extensions/WikispeechSpeechDataCollector | master | +78 -4 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T266658 ☂Create frontend for recording functionality | |||
| Open | None | T272960 Send recording to storage | |||
| Resolved | Sebastian_Berlin-WMSE | T267783 Add recording functionality to the frontend | |||
| Open | None | T268325 Load prompt in record page |
It took a bit of a song and dance to get the actual data out of the audio element. There were several different callback variant that made testing a bit tricky.
Looks like we want to use mw.Api.postWithToken() since we are modifying data.
Change 663000 had a related patch set uploaded (by Sebastian Berlin (WMSE); owner: Sebastian Berlin (WMSE)):
[mediawiki/extensions/WikispeechSpeechDataCollector@master] [WIP] Send recording to API
Looks like I still have not managed to get the correct data. It is not actually audio data, it seems. I tried with a website that managed to transform a sound file into data and it gets a different result.