MVDSTD:CalculateWorkBufSize - Revision history

2670QM at 12:35, 3 April 2025

2025-04-03T10:35:19Z

← Older revision		Revision as of 14:35, 3 April 2025
Line 91:		Line 91:
	\| FLAG_ENABLE_EXTRA_OP (see below)		\| FLAG_ENABLE_EXTRA_OP (see below)
	\|-		\|-
	\| ~~0x03~~		\| 0x04
	\| FLAG_UNK		\| FLAG_UNK
	\|}		\|}

2670QM at 11:54, 2 April 2025

2025-04-02T09:54:31Z

← Older revision		Revision as of 13:54, 2 April 2025
Line 153:		Line 153:
	\|}		\|}

	This will calculate maximum possible buffer size (==buffer size that '''''may''''' be needed to decode video) based on H.264 level and resolution, <s>so any videos that are compliant with H.264 specs should be decoded with this buffer size</s> '''''it seems there is some buffer overflow (some hundreds bytes according to test) when maximum number of reference frames are used''''', so adding some extra bytes (maybe around 4K is enough) is safer.		This will calculate maximum possible buffer size (==buffer size that '''''may''''' be needed to decode video) based on H.264 level and resolution, <s>so any videos that are compliant with H.264 specs should be decoded with this buffer size</s> '''''it seems there is some buffer overflow (some hundreds bytes according to test) when maximum number of reference frames are used''''', so adding some extra bytes (maybe around 4096Bytes is enough) is safer.

	Calculation procedures are :		Calculation procedures are :

2670QM: Fixed wrong description

2025-04-02T09:52:36Z

Fixed wrong description

← Older revision		Revision as of 13:52, 2 April 2025
Line 153:		Line 153:
	\|}		\|}

	This will calculate maximum possible buffer size (==buffer size that '''''may''''' be needed to decode video) based on H.264 level and resolution, so any videos that are compliant with H.264 specs should be decoded with this buffer size.		This will calculate maximum possible buffer size (==buffer size that '''''may''''' be needed to decode video) based on H.264 level and resolution, <s>so any videos that are compliant with H.264 specs should be decoded with this buffer size</s> '''''it seems there is some buffer overflow (some hundreds bytes according to test) when maximum number of reference frames are used''''', so adding some extra bytes (maybe around 4K is enough) is safer.

	Calculation procedures are :		Calculation procedures are :

2670QM at 13:43, 1 April 2025

2025-04-01T11:43:31Z

← Older revision		Revision as of 15:43, 1 April 2025
Line 194:		Line 194:
	If number of reference frames (offset 0x01) is less than 0x02, 0x02 is used internally, if it's greater than 0x10, 0x10 is used internally.		If number of reference frames (offset 0x01) is less than 0x02, 0x02 is used internally, if it's greater than 0x10, 0x10 is used internally.

			----

	It is possible to enable more than 1 calculation methods simultaneously, in that case the ~~biggest~~ buffer size among them is returned.		It is possible to enable more than 1 calculation methods simultaneously, in that case the largest buffer size among them is returned.

	SKATER uses		SKATER uses
	~~```~~
			<nowiki>
	cmd.CalculateWorkBufWithLevel.enable = 0x01;		cmd.CalculateWorkBufWithLevel.enable = 0x01;
	cmd.CalculateWorkBufWithLevel.flag = 0x07; //(FLAG_ENABLE_CALCULATION \| FLAG_ENABLE_EXTRA_OP \| FLAG_UNK).		cmd.CalculateWorkBufWithLevel.flag = 0x07; //(FLAG_ENABLE_CALCULATION \| FLAG_ENABLE_EXTRA_OP \| FLAG_UNK).
Line 209:		Line 211:
	cmd.width = 854; //Regardless of input video, 854 is always used.		cmd.width = 854; //Regardless of input video, 854 is always used.
	cmd.height = 480; //Regardless of input video, 480 is always used.		cmd.height = 480; //Regardless of input video, 480 is always used.
	~~```~~		</nowiki>
	and result is 9438920Bytes (0x9006C8), aka MVD_DEFAULT_WORKBUF_SIZE.
			and result is '''9438920Bytes''' (0x9006C8), aka MVD_DEFAULT_WORKBUF_SIZE.

	This doesn't write to MVD state / registers at all.		This doesn't write to MVD state / registers at all.

2670QM: Added command detail.

2025-04-01T11:34:31Z

Added command detail.

Show changes

Yellows8: moved MVDSTD:CalculateVideoOutBufSize to MVDSTD:CalculateWorkBufSize

2014-11-06T16:02:47Z

moved MVDSTD:CalculateVideoOutBufSize to MVDSTD:CalculateWorkBufSize

← Older revision		Revision as of 19:02, 6 November 2014
(No difference)

Yellows8: Created page with "=Request= {| class="wikitable" border="1" |- ! Index Word ! Description |- | 0 | Header code [0x00030300] |- | 1..12 | ? |} =Response= {| class="wikitable" border="1" |- ! In..."

2014-11-03T05:29:54Z

Created page with "=Request= {| class="wikitable" border="1" |- ! Index Word ! Description |- | 0 | Header code [0x00030300] |- | 1..12 | ? |} =Response= {| class="wikitable" border="1" |- ! In..."

New page

=Request=
{| class="wikitable" border="1"
|-
! Index Word
! Description
|-
| 0
| Header code [0x00030300]
|-
| 1..12
| ?
|}

=Response=
{| class="wikitable" border="1"
|-
! Index Word
! Description
|-
| 0
| Header code
|-
| 1
| Resultcode
|}

=Description=
This calculates the buffer size for [[MVDSTD:Initialize]] using the input parameters. This doesn't write to MVD state / registers at all.