When a .wav file is uploaded with the correct 16-bit/44.1kHz/mono or stereo, detect and catch the case that the audio contains metadata that would lead to invalid Chunk Size error, and instead automatically strip the metadata.
Why is this feature important to you? How would it benefit the community?
It is not unusual for .wav audio to come with audio tags such as Title, Artist, Producer etc.
These audio tags are not handled by the uploader and cause the 'Wrong chunk size' error.
I am a software engineer who just happens to know a bit about wav files which is why I could diagnose this issue myself, but I doubt the average user would understand why their viewer is telling them 'invalid chunk size' despite exporting with the settings presented on the wikipedia page
I think that it should not be too difficult a task to strip this data out on the viewer side and just removes one more thing that a user is likely to get stuck on when dabbling in creating.
How would you like the feature to work?
When a .wav file is uploaded with the correct 16-bit/44.1kHz/mono or stereo, detect and catch the case that the audio contains metadata that would lead to invalid Chunk Size error, and instead automatically strip the metadata.
Why is this feature important to you? How would it benefit the community?
It is not unusual for .wav audio to come with audio tags such as Title, Artist, Producer etc.
Free and Paid Audio editing software often also insert self advertisement into these audio tags. For example on Windows, the audio editing software WavePad inserts "WavePad xyz Edition © NCH Software" into the 'producer' tag.
These audio tags are not handled by the uploader and cause the 'Wrong chunk size' error.
I am a software engineer who just happens to know a bit about wav files which is why I could diagnose this issue myself, but I doubt the average user would understand why their viewer is telling them 'invalid chunk size' despite exporting with the settings presented on the wikipedia page
I think that it should not be too difficult a task to strip this data out on the viewer side and just removes one more thing that a user is likely to get stuck on when dabbling in creating.
Original Jira Fields
| Field | Value | | ------------- | ------------- | | Issue | BUG-229169 | | Summary | Sound Upload - Catch audio tags causing wrong chunk size error, automatically strip tags | | Type | Bug | | Priority | Unset | | Status | Accepted | | Resolution | Triaged | | Reporter | Extrude Ragu (extrude.ragu) | | Created at | 2020-07-30T18:21:10Z | | Updated at | 2020-07-31T17:45:39Z | ``` { 'Build Id': 'unset', 'Business Unit': ['Platform'], 'Date of First Response': '2020-07-30T15:34:22.909-0500', 'How would you like the feature to work?': 'When a .wav file is uploaded with the correct 16-bit/44.1kHz/mono or stereo, detect and catch the case that the audio contains metadata that would lead to invalid Chunk Size error, and instead automatically strip the metadata.', 'ReOpened Count': 0.0, 'Severity': 'Unset', 'System': 'SL Viewer', 'Target Viewer Version': 'viewer-development', 'What just happened?': '.', 'What were you doing when it happened?': '.', 'What were you expecting to happen instead?': '.', 'Why is this feature important to you? How would it benefit the community?': 'It is not unusual for .wav audio to come with audio tags such as Title, Artist, Producer etc. \r\n\r\nFree and Paid Audio editing software often also insert self advertisement into these audio tags. For example on Windows, the audio editing software WavePad inserts "WavePad xyz Edition © NCH Software" into the \'producer\' tag.\r\n\r\nThese audio tags are not handled by the uploader and cause the \'Wrong chunk size\' error.\r\n\r\nI am a software engineer who just happens to know a bit about wav files which is why I could diagnose this issue myself, but I doubt the average user would understand why their viewer is telling them \'invalid chunk size\' despite exporting with the settings presented on the wikipedia page\r\n\r\nI think that it should not be too difficult a task to strip this data out on the viewer side and just removes one more thing that a user is likely to get stuck on when dabbling in creating.', } ```