Difference between revisions of "MVDSTD:Initialize"
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 12: | Line 12: | ||
|- | |- | ||
| 2 | | 2 | ||
| − | | Buffer size, normally from [[MVDSTD: | + | | Buffer size, for H.264 this is normally from [[MVDSTD:CalculateWorkBufSize]]. For "MJPEG", this is value 1. |
|- | |- | ||
| 3 | | 3 | ||
| Line 35: | Line 35: | ||
=Description= | =Description= | ||
| − | This does MVDSTD initialization. The specified buffer is for | + | This does MVDSTD initialization. The specified buffer is the H.264 work-buffer, for "MJPEG" the size is 0x1 since it's not used for that. The user process doesn't use the data stored in this work-buffer at all. The address(+size) must be within the 0x30000000 LINEAR-memory area. |
Latest revision as of 19:08, 6 November 2014
Request[edit]
| Index Word | Description |
|---|---|
| 0 | Header code [0x00010082] |
| 1 | Buffer address |
| 2 | Buffer size, for H.264 this is normally from MVDSTD:CalculateWorkBufSize. For "MJPEG", this is value 1. |
| 3 | Value 0x0 |
| 4 | KProcess handle |
Response[edit]
| Index Word | Description |
|---|---|
| 0 | Header code |
| 1 | Resultcode |
Description[edit]
This does MVDSTD initialization. The specified buffer is the H.264 work-buffer, for "MJPEG" the size is 0x1 since it's not used for that. The user process doesn't use the data stored in this work-buffer at all. The address(+size) must be within the 0x30000000 LINEAR-memory area.