New pages
Appearance
4 May 2026
- 04:5004:50, 4 May 2026 MCI SET (hist | edit) [3,660 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_SET}} This message sets various device attributes, such as audio levels, time formats, and video states. ==Syntax== <PRE> param1 ULONG ulParam1; →Message flags.: param2 PMCI_SET_PARMS pParam2; →Pointer to the MCI_SET_PARMS structure.: </PRE> ==Parameters== ;''ulParam1'' (ULONG) - input :The following standard flags can be used: :* '''MCI_NOTIFY''' Posts a notification message when the action completes. :* '''MCI_WAIT''' Does not return...")
- 04:4804:48, 4 May 2026 MCI SEEK (hist | edit) [2,845 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_SEEK}} This message is sent to change the current media position of the device. ==Syntax== <PRE> param1 ULONG ulParam1; →Message flags.: param2 PMCI_SEEK_PARMS pParam2; →Pointer to the MCI_SEEK_PARMS structure.: </PRE> ==Parameters== ;''ulParam1'' (ULONG) - input :The following flags can be used: :* '''MCI_NOTIFY''' Posts a notification message when the action completes. :* '''MCI_WAIT''' Does not return control until the action is comp...")
- 04:4704:47, 4 May 2026 MCI SAVE (hist | edit) [3,044 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_SAVE}} This message saves the current file or device element to storage. ==Syntax== <PRE> param1 ULONG ulParam1; →Message flags.: param2 PMCI_SAVE_PARMS pParam2; →Pointer to the MCI_SAVE_PARMS structure.: </PRE> ==Parameters== ;''ulParam1'' (ULONG) - input :The following flags can be used: :* '''MCI_NOTIFY''' Posts a notification message when the action completes. :* '''MCI_WAIT''' Does not return control until the action is completed....")
- 04:4304:43, 4 May 2026 MCI REWIND (hist | edit) [2,101 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_REWIND}} This message seeks the media to the starting position. This position is defined as the first 'playable' area, beyond any header or table-of-contents data. ==Syntax== <PRE> param1 ULONG ulParam1; →Message flags.: param2 PMCI_GENERIC_PARMS pParam2; →Pointer to the MCI_GENERIC_PARMS structure.: </PRE> ==Parameters== ;''ulParam1'' (ULONG) - input :This parameter can contain any of the following standard flags: :* '''MCI_NOTIFY''' P...")
- 04:3504:35, 4 May 2026 MCI RESUME (hist | edit) [2,383 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_RESUME}} This message is sent to resume playing or recording from a paused state. ==Syntax== <PRE> param1 ULONG ulParam1; →Message flags.: param2 PMCI_GENERIC_PARMS pParam2; →Pointer to the MCI_GENERIC_PARMS structure.: </PRE> ==Parameters== ;''ulParam1'' (ULONG) - input :The following flags can be used: :* '''MCI_NOTIFY''' Posts a notification message when the action completes. :* '''MCI_WAIT''' Does not return control until the actio...")
- 04:3304:33, 4 May 2026 MCI RESTORE (hist | edit) [3,452 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_RESTORE}} This message causes a video device to transfer an image from the element buffer to the display surface. To ensure that the image is displayed, the device automatically performs a freeze operation where necessary. ==Syntax== <PRE> param1 ULONG ulParam1; →Message flags.: param2 PMCI_RESTORE_PARMS pParam2; →Pointer to the MCI_RESTORE_PARMS structure.: </PRE> ==Parameters== ;''ulParam1'' (ULONG) - input :The following flags can be...")
- 04:2704:27, 4 May 2026 MCI RELEASEDEVICE (hist | edit) [2,465 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_RELEASEDEVICE}} This message is sent to release the exclusive use of physical device resources by a group or device instance. Releasing a device does not always cause the device to be passed to another application; ownership is only changed when the MCI_ACQUIREDEVICE message is used, or if another application opens or closes the device. ==Syntax== <PRE> param1 ULONG ulParam1; →Message flags.: param2 PMCI_GENERIC_PARMS pParam2; /* Pointer to...")
- 04:2504:25, 4 May 2026 MCI REDO (hist | edit) [2,413 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_REDO}} This message redoes the cut, paste, or delete operation most recently undone by MCI_UNDO. MCI_REDO should immediately follow MCI_UNDO; otherwise, editing actions performed after MCI_UNDO (and before a corresponding MCI_REDO) will be lost when MCI_REDO is issued. The media position is at the beginning of the file after a redo operation. ==Syntax== <PRE> param1 ULONG ulParam1; →Message flags.: param2 PMCI_GENERIC_PARMS pParam2; /* Point...")
- 04:2304:23, 4 May 2026 MCI RECORD (hist | edit) [3,499 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_RECORD}} This message causes the device to start recording. Before you send this message, it is recommended that you issue MCI_ACQUIREDEVICE with the MCI_EXCLUSIVE_INSTANCE flag set. This will lock the device context and prevent it from being made inactive. Digital Video Specific This message initiates real-time recording of motion video with simultaneous audio capture. Any options, such as frame rate, quality, and so on, in effect at the time recor...")
- 04:1604:16, 4 May 2026 MCI PUT (hist | edit) [2,168 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_PUT}} ==Syntax== <PRE> param1 ULONG ulParam1; →Message flags.: param2 PMCI_VID_RECT_PARMS pParam2; →Pointer to a rectangle parameter structure.: </PRE> ==Parameters== ;''ulParam1'' (ULONG) - input :Common flags: :* '''MCI_NOTIFY''' Posts a notification message when the action completes. :* '''MCI_WAIT''' Does not return control until the operation completes. ;'''Digital Video Extensions''' :* '''MCI_DGV_PUT_RECT''' Indicates the `rc` fi...")
- 04:1304:13, 4 May 2026 MCI PLAY (hist | edit) [3,292 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_PLAY}} The `MCI_PLAY` message initiates playback for a media device. It allows for specifying start and end positions, as well as device-specific playback modes like fast-forward, reverse, or scan. ==Syntax== <PRE> param1 ULONG ulParam1; →Playback flags.: param2 PMCI_PLAY_PARMS pParam2; →Pointer to a play parameter structure.: </PRE> ==Parameters== ;''ulParam1'' (ULONG) - input :The following general flags apply to all devices: :* '''MC...")
- 04:1104:11, 4 May 2026 MCI PAUSE (hist | edit) [2,392 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_PAUSE}} The `MCI_PAUSE` message is used to suspend the current playback or recording operation on a media device. ==Syntax== <PRE> param1 ULONG ulParam1; →Pause flags.: param2 PMCI_GENERIC_PARMS pParam2; →Pointer to the MCI_GENERIC_PARMS structure.: </PRE> ==Parameters== ;''ulParam1'' (ULONG) - input :The following flags can be used: :* '''MCI_NOTIFY''' Posts a notification message to the window specified in ''hwndCallback'' when the p...")
- 04:1004:10, 4 May 2026 MCI PASTE (hist | edit) [3,416 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_PASTE}} The `MCI_PASTE` message inserts data from the clipboard or an application-supplied buffer into the current media element. This operation allows for data replacement or simple insertion depending on the flags provided. ==Syntax== <PRE> param1 ULONG ulParam1; →Paste flags.: param2 PMCI_EDIT_PARMS pParam2; →Pointer to the MCI_EDIT_PARMS structure.: </PRE> ==Parameters== ;''ulParam1'' (ULONG) - input :The following flags can be used...")
- 04:0804:08, 4 May 2026 MCI MIXNOTIFY (hist | edit) [2,741 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_MIXNOTIFY}} This message allows an application to register for notifications regarding changes to mixer attributes (such as volume, bass, or treble) or connector status changes. When a change occurs, the system sends an MM_MCIEVENT message to the registered window. ==Syntax== <PRE> param1 ULONG ulParam1; →Notification flags.: param2 PMCI_GENERIC_PARMS pParam2; →Pointer to the MCI_GENERIC_PARMS structure.: </PRE> ==Parameters== ;''ulPara...")
- 04:0704:07, 4 May 2026 MCI MASTERAUDIO (hist | edit) [2,996 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_MASTERAUDIO}} This message provides support for setting and retrieving system-wide audio control settings. Unlike MCI_SET, which affects only a specific device instance, `MCI_MASTERAUDIO` affects all logical audio devices in the system. ==Syntax== <PRE> param1 ULONG ulParam1; →Audio control flags.: param2 PMCI_MASTERAUDIO_PARMS pParam2; →Pointer to the MCI_MASTERAUDIO_PARMS structure.: </PRE> ==Parameters== ;''ulParam1'' (ULONG) - i...")
- 04:0404:04, 4 May 2026 MCI LOAD (hist | edit) [2,847 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_LOAD}} This message is used to load a new file or RIFF chunk into an already opened media device instance. ==Syntax== <PRE> param1 ULONG ulParam1; →Load flags.: param2 PMCI_LOAD_PARMS pParam2; →Pointer to the MCI_LOAD_PARMS data structure.: </PRE> ==Parameters== ;''ulParam1'' (ULONG) - input :The following flags can be used. Note that '''MCI_OPEN_ELEMENT''' and '''MCI_OPEN_MMIO''' are mutually exclusive. :* '''MCI_NOTIFY''' Posts a noti...")
- 04:0304:03, 4 May 2026 MCI INFO (hist | edit) [3,216 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_INFO}} This message returns string information from a media device instance. This information describes static attributes of the device or the loaded media, rather than its capabilities. ==Syntax== <PRE> param1 ULONG ulParam1; →Information flags.: param2 PMCI_INFO_PARMS pParam2; →Pointer to the MCI_INFO_PARMS data structure.: </PRE> ==Parameters== ;''ulParam1'' (ULONG) - input :This parameter can contain any of the following flags: :* '...")
- 04:0204:02, 4 May 2026 MCI GROUP (hist | edit) [3,427 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_GROUP}} This message allows applications to create and delete groups of device instances. Grouping allows a single command to be sent to the group ID, which the system then broadcasts to every device instance within that group. ==Syntax== <PRE> param1 ULONG ulParam1; →Grouping flags.: param2 PMCI_GROUP_PARMS pParam2; →Pointer to the MCI_GROUP_PARMS structure.: </PRE> ==Parameters== ;''ulParam1'' (ULONG) - input :This parameter can conta...")
- 04:0104:01, 4 May 2026 MCI GETTOC (hist | edit) [2,763 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_GETTOC}} This message returns a table of contents (TOC) structure for the currently loaded compact disc. ==Syntax== <PRE> param1 ULONG ulParam1; →Flags for the TOC query.: param2 PMCI_TOC_PARMS pParam2; →Pointer to the MCI_TOC_PARMS data structure.: </PRE> ==Parameters== ;''ulParam1'' (ULONG) - input :This parameter can contain any of the following flags: :* '''MCI_NOTIFY''' A notification message will be posted to the window specified...")
- 03:5903:59, 4 May 2026 MCI GETIMAGEPALETTE (hist | edit) [2,158 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_GETIMAGEPALETTE}} This message returns the current palette or color map for the currently captured image, if one is available. ==Syntax== <PRE> param1 ULONG ulParam1; →Flags for palette retrieval.: param2 PMCI_PALETTE_PARMS pParam2; →Pointer to the MCI_PALETTE_PARMS data structure.: </PRE> ==Parameters== ;''ulParam1'' (ULONG) - input :This parameter can contain any of the following flags: :* '''MCI_NOTIFY''' A notification message will...")
- 03:5803:58, 4 May 2026 MCI GETIMAGEBUFFER (hist | edit) [5,987 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_GETIMAGEBUFFER}} This message is used by digital video or video overlay devices to retrieve the contents of the capture video buffer or the current movie frame into an application-provided buffer. ==Syntax== <PRE> param1 ULONG ulParam1; →Flags for retrieval operation.: param2 PMCI_IMAGE_PARMS pParam2; →Pointer to the MCI_IMAGE_PARMS data structure.: </PRE> ==Parameters== ;''ulParam1'' (ULONG) - input :This parameter can contain any of t...")
- 03:5103:51, 4 May 2026 MCI GETDEVCAPS (hist | edit) [5,939 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_GETDEVCAPS}} This message is used to return static information about the capabilities of a particular device instance. ==Syntax== <PRE> param1 ULONG ulParam1; →Flags for capability query.: param2 PMCI_GETDEVCAPS_PARMS pParam2; →Pointer to the data structure.: </PRE> ==Parameters== ;''ulParam1'' (ULONG) - input :This parameter can contain any of the following flags. **Note:** Either MCI_GETDEVCAPS_MESSAGE or MCI_GETDEVCAPS_ITEM must be s...")
- 03:4803:48, 4 May 2026 MCI FREEZE (hist | edit) [3,718 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_FREEZE}} This message freezes the motion video on an area of the display. ==Syntax== <PRE> param1 ULONG ulParam1; →Flags for freeze operation.: param2 PMCI_OVLY_RECT_PARMS pParam2; →Pointer to the MCI_OVLY_RECT_PARMS data structure.: </PRE> ==Parameters== ;''ulParam1'' (ULONG) - input :This parameter can contain the following flags: :* '''MCI_NOTIFY''' A notification message will be posted to the window specified in the ''hwndCallback''...")
- 03:4703:47, 4 May 2026 MCI ESCAPE (hist | edit) [2,156 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_ESCAPE}} This message sends messages directly to the vendor-specific driver (VSD) or the device driver. This message is not interpreted by the media control interface driver (MCD). ==Syntax== <PRE> param1 ULONG ulParam1; →Flags for escape operation.: param2 PMCI_ESCAPE_PARMS pParam2; →Pointer to the MCI_ESCAPE_PARMS data structure.: </PRE> ==Parameters== ;''ulParam1'' (ULONG) - input :This parameter can contain any of the following flags...")
- 03:4503:45, 4 May 2026 MCI DEVICESETTINGS (hist | edit) [1,878 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_DEVICESETTINGS}} This message is sent to a media control interface driver (MCD) when the Multimedia Setup application is inserting pages into a Settings notebook. This message provides the MCD the opportunity to insert custom settings pages. ==Syntax== <PRE> param1 ULONG ulParam1; →Flags for device settings.: param2 PMCI_DEVICESETTINGS_PARMS pParam2; →Pointer to the MCI_DEVICESETTINGS_PARMS data structure.: </PRE> ==Parameters== ;''ulParam1'...")
- 03:4403:44, 4 May 2026 MCI DELETE (hist | edit) [4,102 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_DELETE}} This message removes the specified range of data from the device file. The media position after a delete operation is the MCI_FROM position if used, or the previous position if MCI_FROM is not used. ==Syntax== <PRE> param1 ULONG ulParam1; →Flags for delete operation.: param2 PMCI_EDIT_PARMS pParam2; →Pointer to the MCI_EDIT_PARMS data structure.: </PRE> ==Parameters== ;''ulParam1'' (ULONG) - input :This parameter can contain any...")
- 03:4303:43, 4 May 2026 MCI DEFAULT CONNECTION (hist | edit) [5,341 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_DEFAULT_CONNECTION}} This message is used to make, break, and query default connections between devices. ==Syntax== <PRE> param1 ULONG ulParam1; →Flags for default connection operation.: param2 PMCI_DEFAULT_CONNECTION_PARMS pParam2; →Pointer to the MCI_DEFAULT_CONNECTION_PARMS data structure.: </PRE> ==Parameters== ;''ulParam1'' (ULONG) - input :This parameter can contain any of the following flags: :* '''MCI_NOTIFY''' A notification mes...")
- 03:4103:41, 4 May 2026 MCI CUT (hist | edit) [4,590 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_CUT}} This message removes the specified range of data from the device element and places it in the system clipboard or application-supplied buffer. The position of the media after a cut command is the FROM position, if MCI_FROM is specified. If MCI_FROM is not specified, the current position is used. ==Syntax== <PRE> param1 ULONG ulParam1; →Flags for cut operation.: param2 PMCI_EDIT_PARMS pParam2; /* Pointer to the MCI_EDIT_PARMS data structure....")
- 03:4003:40, 4 May 2026 MCI COPY (hist | edit) [4,726 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_COPY}} This message copies the specified range of data from the device file to the clipboard or application buffer. The position of the media remains the same as prior to the copy operation. ==Syntax== <PRE> param1 ULONG ulParam1; →Flags for copy operation.: param2 PMCI_EDIT_PARMS pParam2; →Pointer to the MCI_EDIT_PARMS data structure.: </PRE> ==Parameters== ;''ulParam1'' (ULONG) - input :This parameter can contain any of the following f...")
- 03:3803:38, 4 May 2026 MCI CONNECTORINFO (hist | edit) [6,212 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:MCI_CONNECTORINFO}} This message is used to determine the total number of connectors on a device, the number of connectors of a specific type, the type of each connector, and whether or not a particular type of connection is valid for a connector. ==Syntax== <PRE> param1 ULONG ulParam1; →Flags for connector information.: param2 PMCI_CONNECTORINFO_PARMS pParam2; →Pointer to the MCI_CONNECTORINFO_PARMS data structure.: </PRE> ==Parameters== ;''ulP...")
3 May 2026
- 22:2922:29, 3 May 2026 DosSetKBDSigFocus (hist | edit) [519 bytes] Martini (talk | contribs) (Created page with "The DosSetKBDSigFocus() function is used to allow 32-bit programs to inform the operating system that they are "primed for signals", although the signals are dispatched as exceptions. Note the following: * 16-bit DosSetVec() exceptions are supported under OS/2 Version 2.0. * The 32-bit OS/2 Version 2.0 exception manager allows per-thread exception handling. * OS/2 Version 2.0 does not allow an exception handler to be registered for the numeric processor exception (NPX)....")
- 19:0219:02, 3 May 2026 STATUS (hist | edit) [1,231 bytes] Martini (talk | contribs) (Created page with "The STATUS command obtains status information for the device. ==Syntax== <pre> STATUS ─── object ───┬─ MODE ─┬───┬──────────┬───┤ └─ READY ─┘ ├─ WAIT ─┤ └─ NOTIFY ─┘ </pre> ==Keywords== ;object :Object associated with this media control interface command. The object can be one of the following: :*Device type :*Device name :*...")
- 19:0119:01, 3 May 2026 OPEN (hist | edit) [2,718 bytes] Martini (talk | contribs) (Created page with "The OPEN command is used to open or create a new device instance. OPEN returns a device ID that is used for subsequent calls for the procedure interface, if desired. ==Syntax== <pre> ┌──────────────────────────┐ │ │ OPEN ──── object ─┴──┬────────────────────┬──┴──┬─────...")
- 19:0019:00, 3 May 2026 INFO (hist | edit) [1,078 bytes] Martini (talk | contribs) (Created page with "The INFO command fills a user-supplied buffer with information. ==Syntax== <pre> INFO ──── object ───── PRODUCT ────┬──────────┬────┤ ├─ WAIT ─┤ └─ NOTIFY ─┘ </pre> ==Keywords== ;object :Object associated with this media control interface command. The object can be one of the following: :*Device type :*Device name :*Filen...")
- 19:0019:00, 3 May 2026 CLOSE (hist | edit) [890 bytes] Martini (talk | contribs) (Created page with "The CLOSE command closes the device context and frees resources. ==Syntax== <pre> CLOSE ──── object ────┬──────────┬────┤ ├─ WAIT ─┤ └─ NOTIFY ─┘ </pre> ==Keywords== ;object :Object associated with this media control interface command. The object can be one of the following: :*Device type :*Device name :*Filename :*Alias ;WAIT :The command is executed syn...")
- 18:5918:59, 3 May 2026 CAPABILITY (hist | edit) [3,599 bytes] Martini (talk | contribs) (Created page with "== CAPABILITY == The CAPABILITY command requests information about a particular capability of a device. ==Syntax== <pre> CAPABILITY ─── object ───┬─ CAN EJECT ────────┬───┬──────────┬───┤ ├─ CAN PLAY ─────────┤ ├─ WAIT ─┤ ├─ CAN RECORD ───────┤ └─ NOTIFY ─┘...")
- 18:2318:23, 3 May 2026 MMProgRef - Return Codes (hist | edit) [25,575 bytes] Martini (talk | contribs) (Created page with "This section lists the following categories of OS/2 multimedia return codes including number, message, and a brief description: * Media Device Manager Return Codes * Sync Stream Manager Return Codes * MMIO Manager Return Codes * DIVE Return Codes == Media Device Manager Return Codes == 5000 - MCIERR_SUCCESS MMPM/2 command completed success...")
- 18:1918:19, 3 May 2026 MMProgRef - RIFF Compound Files and Elements - Sharing and Access (hist | edit) [5,151 bytes] Martini (talk | contribs) (Created page with "{{MMProgRef}} The following tables show the relationship between sharing and accessing RIFF compound files (CF) and elements within those files, both within the current process and between processes. === Access and Sharing Modes === An '''A''' indicates that the function is allowed. Both the access and sharing values must be '''A''' for the open to work. For example, in the CF Open - CF Open of the same process, if the first CF Open is RO - DW, then the next CF Open m...")
- 06:2306:23, 3 May 2026 MMAPG - Installing a Program Using MINSTALL (hist | edit) [27,831 bytes] Martini (talk | contribs) (Created page with "This section describes the procedures for preparing control files for installing a multimedia application using the multimedia installation program (MINSTALL). The MINSTALL program utilizes features provided by the OS/2 multimedia installation engine, such as creating workplace shell objects and changing the CONFIG.SYS file, providing a consistent installation process. '''Note:''' For installation requirements when writing a subsystem, refer to the ''OS/2 Multimedia...")
- 05:5605:56, 3 May 2026 MMAPG - Sample Application Programs (hist | edit) [64,910 bytes] Martini (talk | contribs) (Created page with "{{MMAPG}} {{IBM-Reprint}} This section gives a brief overview of the sample application programs provided with the Toolkit, including programming concepts and program flow diagrams for each of the sample programs. The purpose of the OS/2 multimedia sample programs is to illustrate multimedia programming concepts and establish a basis for creating your own multimedia applications. The programs provide you with practical examples that span a range of multimedia concepts...")
- 05:4805:48, 3 May 2026 MMAPG - Resource Interchange File Format (RIFF) Services (hist | edit) [26,094 bytes] Martini (talk | contribs) (Created page with "{{MMAPG}} {{IBM-Reprint}} The Resource Interchange File Format (RIFF) is the standard file format used for storing multimedia files. RIFF enables audio, image, animation, and other multimedia elements to be stored in a common format. RIFF is also used as the basis for defining new file formats for OS/2 multimedia software. RIFF file I/O provides simple functions to locate, create, enter, exit, and access the ''chunk''—the basic building block of a RIFF file. You can...")
- 05:2705:27, 3 May 2026 MMAPG - Multimedia I/O File Services (hist | edit) [50,997 bytes] Martini (talk | contribs) (Created page with "{{MMAPG}} {{IBM-Reprint}} The multimedia input/output (MMIO) file services are an extension of the base OS/2 file services. Designed to be simple, fast, and flexible, MMIO functions enable an application to access and manipulate multimedia data files in a transparent manner. Multimedia files contain a variety of media elements such as images, graphics, digital audio and video. These elements can be in different file formats: for example, RIFF, M-Motion, and AVI. Multim...")
- 05:1505:15, 3 May 2026 MMAPG - OS/2 Multimedia Controls (hist | edit) [29,258 bytes] Martini (talk | contribs) (Created page with "{{MMAPG}} {{IBM-Reprint}} This chapter describes how to create and manage your own customized windows, graphic buttons and secondary windows. OS/2 multimedia applications, such as Volume Control shown in the following figure provide you with examples of multimedia control implementations. File:img1.png The SW.DLL dynamic link library, located in the \MMOS2\DLL subdirectory contains the functions that support creating and manipulating these controls. (The SW.H fil...")
- 05:1305:13, 3 May 2026 MMAPG - Captioning (hist | edit) [12,666 bytes] Martini (talk | contribs) (Created page with "{{MMAPG}} {{IBM-Reprint}} The Toolkit provides a sample captioning system to assist application programmers in adding captioning to multimedia applications. The sample captioning system consists of three parts: the Caption Creation Utility program, Caption DLL, and Caption Sample Application. The Caption Creation Utility program (located in \TOOLKIT\SAMPLES\MM\CAPTION subdirectory) creates a 'caption' file. This is a text file containing timing information relating to i...")
- 05:0105:01, 3 May 2026 MMAPG - Direct Interface Video Extensions (DIVE) (hist | edit) [18,010 bytes] Martini (talk | contribs) (Created page with "{{MMAPG}} {{IBM-Reprint}} Software motion video implementation under OS/2 has attained sizable performance advantages by enabling video decompressors to directly write to video memory. While this technique provides good performance, it has the disadvantage that each decompressor must deal with the pel format of the display in various modes, clipping the output to visible regions, and any scaling that is to be performed. Additionally, on bank-switched video displays, the...")
- 04:5404:54, 3 May 2026 MMAPG - Digital Video Device (hist | edit) [27,502 bytes] Martini (talk | contribs) (Created page with "{{MMAPG}} {{IBM-Reprint}} OS/2 Version 2.1 or later supports playback of software motion videos. The ability to create and record movies is provided by the Video IN product (part of the OS/2 BonusPak). The OS/2 digital video device ('''digitalvideo''') provides file-format support through the multimedia input/output (MMIO) architecture. Several movie file formats including AVI, MPEG, FLC/FLI animation are supported. Several decompression types, like Ultimotion, Indeo 2....")
- 04:4704:47, 3 May 2026 MMAPG - Videodisc Device (hist | edit) [14,005 bytes] Martini (talk | contribs) (Created page with "{{MMAPG}} {{IBM-Reprint}} The physical videodisc device is an external hardware device that plays videodiscs, producing an analog video and audio signal. The analog video output can be connected to an analog video digitizer component that produces output on the display, or it can simply be connected to a an external video monitor. The audio output can be connected to amplified speakers, headphones, or other audio media drivers. == Device Specifics == The videodisc medi...")
- 04:4304:43, 3 May 2026 MMAPG - CD-XA Device (hist | edit) [8,844 bytes] Martini (talk | contribs) (Created page with "{{MMAPG}} {{IBM-Reprint}} == CD-XA Disc Formats == The CD-XA media driver provides access to devices that support CD-ROM/XA discs. CD-XA (Compact Disc-Extended Architecture) refers to a storage format that accommodates interleaved storage of audio, video and standard file system data. CD-XA data is stored in a file system format on the discs, and playback control is managed by the CD-XA media device in cooperation with the amplifier-mixer device. CD-XA takes advantag...")
- 04:3104:31, 3 May 2026 MMAPG - CD Audio Device (hist | edit) [14,323 bytes] Martini (talk | contribs) (Created page with ":p.The CD audio media device provides access to devices that read compact discs for the purpose of playing CD audio. A typical use for CD audio is to provide high quality audio for use in a presentation. Another use of CD audio would be to provide detailed audio help for an application user. Instead of the usual hyperlinked text and graphics, an entire step by step audio tutorial might be stored on a compact disc in several different languages. :h2 id=94.Compact D...")
- 04:2304:23, 3 May 2026 MMAPG - Sequencer Device (hist | edit) [18,976 bytes] Martini (talk | contribs) (Created page with "{{MMAPG}} {{IBM-Reprint}} == Sequencer Device == The OS/2 sequencer device plays a MIDI song by sending commands from a MIDI file to a synthesizer, where the commands are converted to the sounds of a specific instrument. Typically, a digital signal processor (DSP) is used to generate the sounds of the instrument, which results in an authentic reproduction of the original performance. General MIDI (Musical Instrument Digital Interface) is a standard specification for pl...")