Closed Bug 782091 Opened 7 years ago Closed 6 years ago

multichannel opus test files

Categories

(Core :: Audio/Video, defect)

x86
macOS
defect
Not set

Tracking

()

RESOLVED FIXED
mozilla23

People

(Reporter: rillian, Assigned: rillian)

References

Details

(Whiteboard: [mentor=rillian])

Attachments

(1 file)

Bug 748144 adds support for multichannel Opus files, but doesn't have a license-compatible test file.

This bug is about creating such a file and adding it to the mochitests. We should verify playback completion and mozChannels.
Whiteboard: [mentor=rillian]
(In reply to Ralph Giles (:rillian) from comment #0)
> Bug 748144 adds support for multichannel Opus files, but doesn't have a
> license-compatible test file.

I sat down with Monty and we made a set of files:
http://people.xiph.org/~tterribe/opus/multichannel/

I've confirmed with Monty that these can be used as public domain (quote: "They may be used to troll me indefinitely, and I expect they will.").
Thanks!

BTW, Monty said he also made a higher quality recording at home. Hopefully he will forward those when the conference is over so we can make higher quality examples.
Monty lost his recording, so maybe we should go with derf's set for now, despite the poor quality.

It would also be nice to have some kind of automated verification of the output to catch issues like bug 787788. E.g. we could port opus_compare to js and run that on the output (but this requires a lossless original in the test suite). A simpler idea is computing a few moments in each frequency band, which would at least have found the wildly-off downmix coefficient.
Depends on: 787788
I've not made anything better in the intervening six months, so here's a patch to add the basic speaker-matching tests Tim and Monty created.
Attachment #744280 - Flags: review?(tterribe)
Attachment #744280 - Flags: review?(tterribe) → review+
https://hg.mozilla.org/mozilla-central/rev/8324f2f4007b
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla23
You need to log in before you can comment on or make changes to this bug.