Abstract: A method and architecture for obtaining a desired frame and identifying a selected frame in an image container. A request for a frame of an image is received. The request may include an identifier that identifies a type of frame. In response thereto, a frame is located corresponding to the identifier and a reference to the frame is provided. In another aspect, a request is received to identify a frame of an image. A determination is made as to what identifier identifies the frame. The identified frame is returned to the requesting component.

Abstract: Techniques and tools for analyzing and adjusting the exposure of digital images are described. For example, a computer processes a digital image by analyzing exposure data, assigning an image classification (e.g., StretchNeeded, UnderExposed, OverExposed, or Normal) based on the analysis, and selecting an exposure compensation technique (e.g., histogram stretch, positive gamma curve, negative gamma curve, or no adjustment) based on the image classification. The exposure data can be luminance values for pixels in the digital image represented in a histogram. The computer can produce transform data comprising a transformation of the exposure data according to the selected exposure compensation technique. The computer can store transform data in a look-up table and can store the look-up table in the digital image file. The described techniques and tools can be implemented as a feature of an operating system environment and can be activated responsive to user action via a user interface.

Abstract: An image acquisition system has a computer and one or more imaging devices coupled thereto. Each imaging device has a device memory and is capable of capturing and storing a digital image in its memory. An image device manager is implemented in software on the computer to control imaging device operation. The image device manager presents a user interface (UI) within the familiar graphical windowing environment. The UI has a context space to a particular imaging context (e.g., scanning, photography, and video). The UI also has a persistently-visible imaging menu positioned within the context space that lists options particular to the imaging context. The image acquisition system also includes a set of application program interfaces (APIs) that enable applications to manage loading and unloading of imaging devices, monitor device events, query device information properties, create device objects, capture images using the devices, and store or manipulate the captured images.

Abstract: A method and architecture for reading and updating metadata. A policy component is arranged to receive a request to read or update metadata that may include metadata from a plurality of standards. Each metadata format potentially includes a field corresponding to the request. The policy component determines which fields to read or update in satisfying the request by consulting a repository. The repository includes mappings that map information included in the request (e.g., a path) to locations in the metadata corresponding to the request. The policy component uses the locations to read or update the metadata.

Abstract: In one aspect, an application analyzes and adjusts image data (e.g., pixel data) automatically upon acquiring (e.g., from a source such as a digital camera) a digital image. Adjustments can be based on, for example, image orientation, red-eye detection, blurriness, color balance, exposure, or noise detection. Metadata corresponding to image adjustments can be stored in an adjusted image file to preserve the original image. In another aspect, a computer system includes image analysis and image adjustment software modules for analyzing and adjusting digital image data at image acquisition time. The image adjustment module can include one or more processing filters. A customizable software architecture allows customization of the image adjustment software module (e.g., by adding, removing or reordering processing filters). The described techniques and tools can be implemented as features of an operating system environment.

Abstract: An improved system and method for an extensible codec architecture for digital images is provided. Executable software code may be operably coupled to a codec manager for requesting imaging operations to be performed on a digital image. The codec manager may receive the request to perform an imaging operation on the digital image and may select an imaging component, such as a codec, from one or more imaging components registered in the computer system for performing an imaging operation on the digital image. An arbitration manager may include functionality for requesting enumeration of the operations an imaging component may perform on a particular digital image. One or more pixel format converters may then convert the pixel format in the digital image to a pixel format supported by an imaging component installed on the system.

Abstract: Techniques and tools for analyzing and adjusting the exposure of digital images are described. For example, a computer processes a digital image by analyzing exposure data, assigning an image classification (e.g., StretchNeeded, UnderExposed, OverExposed, or Normal) based on the analysis, and selecting an exposure compensation technique (e.g., histogram stretch, positive gamma curve, negative gamma curve, or no adjustment) based on the image classification. The exposure data can be luminance values for pixels in the digital image represented in a histogram. The computer can produce transform data comprising a transformation of the exposure data according to the selected exposure compensation technique. The computer can store transform data in a look-up table and can store the look-up table in the digital image file. The described techniques and tools can be implemented as a feature of an operating system environment and can be activated responsive to user action via a user interface.

Abstract: An image acquisition system has a computer and one or more imaging devices coupled thereto. Each imaging device has a device memory and is capable of capturing and storing a digital image in its memory. An image device manager is implemented in software on the computer to control imaging device operation. The image device manager presents a user interface (UI) within the familiar graphical windowing environment. The UI has a context space to a particular imaging context (e.g., scanning, photography, and video). The UI also has a persistently-visible imaging menu positioned within the context space that lists options particular to the imaging context. The image acquisition system also includes a set of application program interfaces (APIs) that enable applications to manage loading and unloading of imaging devices, monitor device events, query device information properties, create device objects, capture images using the devices, and store or manipulate the captured images.

Abstract: An image acquisition system has a computer and one or more imaging devices coupled thereto. Each imaging device has a device memory and is capable of capturing and storing a digital image in its memory. An image device manager is implemented in software on the computer to control imaging device operation. The image device manager presents a user interface (GI) within the familiar graphical windowing environment. The GI has a context space to a particular imaging context (e.g., scanning, photography, and video). The GI also has a persistently-visible imaging menu positioned within the context space that lists options particular to the imaging context. The image acquisition system also includes a set of application program interfaces (APIs) that enable applications to manage loading and unloading of imaging devices, monitor device events, query device information properties, create device objects, capture images using the devices, and store or manipulate the captured images.

Abstract: An image acquisition system has a computer and one or more imaging devices coupled thereto. Each imaging device has a device memory and is capable of capturing and storing a digital image in its memory. An image device manager is implemented in software on the computer to control imaging device operation. The image device manager presents a user interface (UI) within the familiar graphical windowing environment. The UI has a context space pertaining to a particular imaging context (e.g., scanning, photography, and video). The UI also has a persistently-visible imaging menu positioned within the context space that lists options particular to the imaging context. The image acquisition system also includes a set of application program interfaces (APIs) that enable applications to manage loading and unloading of imaging devices, monitor device events, query device information properties, create device objects, capture images using the devices, and store or manipulate the captured images.

Abstract: An image acquisition system has a computer and one or more imaging devices coupled thereto. Each imaging device has a device memory and is capable of capturing and storing a digital image in its memory. An image device manager is implemented in software on the computer to control imaging device operation. The image device manager presents a user interface (UI) within the familiar graphical windowing environment. The UI has a context space to a particular imaging context (e.g., scanning, photography, and video). The UI also has a persistently-visible imaging menu positioned within the context space that lists options particular to the imaging context. The image acquisition system also includes a set of application program interfaces (APIs) that enable applications to manage loading and unloading of imaging devices, monitor device events, query device information properties, create device objects, capture images using the devices, and store or manipulate the captured images.

Abstract: Conventional computer systems include numerous application programs which by default store files, or documents, in folders containing the application program that creates them. For example, wordprocessing documents are stored by default in the folder with the wordprocessing application program, and so forth. Thus, users who choose not to organize their documents according to subject matter or other criteria end up having their documents dispersed across numerous application-program folders, sometimes making them difficult to find. Accordingly, the inventors devised a computer operating system that defines a common default document folder for application programs. Moreover, to promote use of the default document folder, one embodiment of the operating system includes a graphical user interface which provides links, that is, one-button access to the common default folder, at file access points, such as in file-open and file-save dialog boxes accessed by the application programs.

Abstract: An image acquisition system has a computer and one or more imaging devices coupled to the computer. Each imaging device has a device memory and is capable of capturing a digital image and storing the image in its memory. An image device manager is implemented in software on the computer to control operation of the imaging devices. The image device manager presents a user interface (UI) within the familiar graphical windowing environment. The UI has a context space that pertains to a particular imaging context (e.g., scanning, photography, and video). The UI also has a persistently-visible imaging menu positioned within the context space that lists options particular to the imaging context. For example, if the context space pertains to the digital camera context, the menu lists options to take a picture, store the image on the computer, send the image in an email, and so on.

Abstract: A standard user interface enables a user to filter an arbitrary unfamiliar data set intuitively and effectively. The illustrated interface includes a header control presenting labels, filters, and pulldown menus for each attribute of a data set, presented by an associated display control. The control communicates with a data provider through a set of APIs included in the computer's operating system. Through these APIs the data provider indicates the labels and menus to be displayed, while the header control passes new filter criteria to the data provider as it is specified by the user. The data provider filters the data set according to the user-specified filter criteria, and returns the filtered data set for display by the display control. Desirably, new filter criteria are passed to the data provider as they are being typed by the user, allowing the data provider to return successively smaller sets of result data, thus giving the visual impression of a shrinking data set.