OggOpus/testvectors - Revision history

Derf: Comment data shorter than the packet is allowed (RFC 7845 Section 5.2)

2016-04-25T23:47:27Z

Comment data shorter than the packet is allowed (RFC 7845 Section 5.2)

← Older revision		Revision as of 23:47, 25 April 2016
Line 36:		Line 36:
	* Channels mapped to nonexistent stream indices (255 > index >= M+N)		* Channels mapped to nonexistent stream indices (255 > index >= M+N)
	* Illegal OpusTags comments		* Illegal OpusTags comments
	** Total length larger ~~or shorter~~ than the packet		** Total length larger than the packet
	** Illegal field names		** Illegal field names
	** Illegal field contents		** Illegal field contents

MrZeus at 09:05, 19 August 2015

2015-08-19T09:05:33Z

← Older revision		Revision as of 09:05, 19 August 2015
Line 47:		Line 47:
	* preskip > final granulepos		* preskip > final granulepos

			[[Category:Ogg]]
	[[Category:Opus]]		[[Category:Opus]]

MrZeus at 15:34, 18 August 2015

2015-08-18T15:34:22Z

← Older revision		Revision as of 15:34, 18 August 2015
Line 46:		Line 46:
	* first data granulepos too small		* first data granulepos too small
	* preskip > final granulepos		* preskip > final granulepos

			[[Category:Opus]]

Rillian: link to greg's file collection

2012-06-26T00:24:56Z

link to greg's file collection

← Older revision		Revision as of 00:24, 26 June 2012
Line 1:		Line 1:
	This page lists test vectors needed for OggOpus which are specific to the Ogg mapping (separate from the opus bitstream test vectors, though they do some bitstream testing as a side efffect)		This page lists test vectors needed for OggOpus which are specific to the Ogg mapping (separate from the opus bitstream test vectors, though they do some bitstream testing as a side efffect)

			Greg is collecting a draft file set at https://people.xiph.org/~greg/opus_testvectors/


	* All test vectors should be chained files with at least two parts		* All test vectors should be chained files with at least two parts

Rillian: /* Illegal test vectors that MUST fail */ two new cases from derf's updates

2012-05-10T17:14:49Z

Illegal test vectors that MUST fail: two new cases from derf's updates

← Older revision		Revision as of 17:14, 10 May 2012
Line 40:		Line 40:
	** R128_TRACK_GAIN comments containing illegal values (should this be required to fail?)		** R128_TRACK_GAIN comments containing illegal values (should this be required to fail?)
	*** Non-ASCII encodings of correct-looking values		*** Non-ASCII encodings of correct-looking values
	*All GP==0		* All GP==0
			* first data granulepos too small
			* preskip > final granulepos

Rillian: Note we should test duration calculation features

2011-12-09T23:02:08Z

Note we should test duration calculation features

← Older revision		Revision as of 23:02, 9 December 2011
Line 24:		Line 24:
	* Stereo files using many mono frames at the beginning/end		* Stereo files using many mono frames at the beginning/end
	* OpusTags comment values containing very large nonsense comments, duplicate comment values etc.		* OpusTags comment values containing very large nonsense comments, duplicate comment values etc.
			* Files with non-zero initial granulepos, pre-skip, trimmed last page to check duration calculation

	=== Illegal test vectors that MUST fail ===		=== Illegal test vectors that MUST fail ===

Bemasc at 20:53, 17 August 2011

2011-08-17T20:53:43Z

← Older revision		Revision as of 20:53, 17 August 2011
Line 8:		Line 8:
	** Multichannel w/pre-skip and random channel maps		** Multichannel w/pre-skip and random channel maps
	** Multichannel with silent channels		** Multichannel with silent channels
			*** Totally silent multichannel (Should this one be invalid?)
	** Multichannel with repeated channels (i.e. one stream used for multiple channels)		** Multichannel with repeated channels (i.e. one stream used for multiple channels)
	*** Totally silent multichannel (Should this one be invalid?)
	** Multichannel with 256 channels		** Multichannel with 256 channels
	** Mapping tests for the Vorbis mappings (e.g. name of the speaker spoken by each speaker)		** Mapping tests for the Vorbis mappings (e.g. name of the speaker spoken by each speaker)

Bemasc: Update proposed tests to match latest header ideas

2011-08-17T20:51:49Z

Update proposed tests to match latest header ideas

← Older revision		Revision as of 20:51, 17 August 2011
Line 3:		Line 3:
	* All test vectors should be chained files with at least two parts		* All test vectors should be chained files with at least two parts
	** Chained file where the second link has no pregap and starts with inter frames (to ensure that decoder state is reset)		** Chained file where the second link has no pregap and starts with inter frames (to ensure that decoder state is reset)
	* ~~Pregap~~ (set large pre-~~gap~~ with a chime "if you just heard a chime, your player is broken")		* Pre-skip (set large pre-skip with a chime "if you just heard a chime, your player is broken")
	* Multichannel		* Multichannel
	** Multichannel stereo (e.g. mono+mono)		** Multichannel stereo (e.g. mono+mono)
	** Multichannel w/~~pregap~~ and random channel maps		** Multichannel w/pre-skip and random channel maps
	** Multichannel with silent channels		** Multichannel with silent channels
			** Multichannel with repeated channels (i.e. one stream used for multiple channels)
	*** Totally silent multichannel (Should this one be invalid?)		*** Totally silent multichannel (Should this one be invalid?)
	** Multichannel with 256 channels		** Multichannel with 256 channels
	** Mapping tests for the Vorbis mappings (e.g. name of the speaker spoken by each speaker)		** Mapping tests for the Vorbis mappings (e.g. name of the speaker spoken by each speaker)
	* Files with replaygain metadata (esp files which are obviously too quiet/loud without applying replaygain)
	** Multiple identical ReplayGain comments in OpusTags
	** matching unnormalized WAV output.
	* Files with crazy input rate.		* Files with crazy input rate.
	* Header-gain set very high with a very quiet input (silent if you don't implement header gain).		* Header-gain set very high with a very quiet input (silent if you don't implement header gain).
	* Header-gain set very low with an input that will clip a decoder if the header gain is not done internally.		* Header-gain set very low with an input that will clip a decoder if the header gain is not done internally.
			* Header-gain set very low, and R128_TRACK_GAIN to normalize it
			** matching WAV outputs ... but matching to what?
	* Single packet per page		* Single packet per page
	* Utterly stuffed pages with constant continued pages		* Utterly stuffed pages with constant continued pages
Line 25:		Line 25:
	* OpusTags comment values containing very large nonsense comments, duplicate comment values etc.		* OpusTags comment values containing very large nonsense comments, duplicate comment values etc.

	* Illegal test vectors that ~~must~~ fail		=== Illegal test vectors that MUST fail ===
	** Zero streams (N=0)		* Zero streams (N=0)
	** Too many two-output streams		* Too many two-output streams
	*** M>N		** M>N
	*** M<=N but M+N>255		** M<=N but M+N>255
	** Channels mapped to nonexistent stream indices (255 > index >= M+N)		* Channels mapped to nonexistent stream indices (255 > index >= M+N)
	** Illegal OpusTags comments		* Illegal OpusTags comments
	*** Total length larger or shorter than the packet		** Total length larger or shorter than the packet
	*** Illegal field names		** Illegal field names
	*** Illegal field contents		** Illegal field contents
	*** Illegal field (no "=")		** Illegal field (no "=")
	*** Multiple ~~conflicting ReplayGain~~ comments		** Multiple R128_TRACK_GAIN comments (should this be required to fail?)
	*** ReplayGain comments containing illegal values		** R128_TRACK_GAIN comments containing illegal values (should this be required to fail?)
	**** Weird encodings of correct-looking values?		*** Non-ASCII encodings of correct-looking values
	*All GP==0		*All GP==0

Gmaxwell at 19:51, 17 August 2011

2011-08-17T19:51:01Z

← Older revision		Revision as of 19:51, 17 August 2011
Line 8:		Line 8:
	** Multichannel w/pregap and random channel maps		** Multichannel w/pregap and random channel maps
	** Multichannel with silent channels		** Multichannel with silent channels
	*** Totally silent multichannel		*** Totally silent multichannel (Should this one be invalid?)
	** Multichannel with 256 channels		** Multichannel with 256 channels
	** Mapping tests for the Vorbis mappings (e.g. name of the speaker spoken by each speaker)		** Mapping tests for the Vorbis mappings (e.g. name of the speaker spoken by each speaker)

Gmaxwell at 16:12, 17 August 2011

2011-08-17T16:12:49Z

← Older revision		Revision as of 16:12, 17 August 2011
Line 39:		Line 39:
	*** ReplayGain comments containing illegal values		*** ReplayGain comments containing illegal values
	**** Weird encodings of correct-looking values?		**** Weird encodings of correct-looking values?
			*All GP==0