Abstract:
A system and methods provide handling of variable rate playback in a multimedia computer architecture. The systems and methods provide data structures and interfaces that enable a computer architecture and components therein with the ability to playback data at speeds faster and slower than real-time, to playback data in reverse, and to change the rate of playback at any point during playback. One embodiment is a method for providing low-latency, glitch-free changes in a multimedia architecture. Other embodiments are directed to defining multimedia component responsibilities for making rate changes, allowing rate changes to work with standard playback types, coder-decoders, and renderers. The methods include determining a minimum of the maximum reported playback rates and determining minimum and maximum playback rates in a set of modes including: reverse skip mode, reverse key frame mode, reverse full mode, forward full mode, forward key frame mode, and forward skip mode.
Abstract:
Assessment of de-interlaced video quality is determined automatically by de-interlacing interlaced video content using a reference de-interlacer and a test de-interlacer. The reference de-interlacer produces a result of known quality and the test de-interlacer is one which is being assessed. The result from each de-interlacer is compared to reference video content to derive a signal-to-noise ratio for each relative to the reference video content. The difference in the signal-to-noise ratios is compared against a predefined threshold. If the difference is within the range defined by the threshold, the test de-interlacer is determined to produce an acceptable product.
Abstract:
Described herein is an implementation that facilitates the reverse presentation of an encoded digital media stream. This abstract itself is not intended to limit the scope of this patent. The scope of the present invention is pointed out in the appending claims.
Abstract:
Native operating system application programming interfaces (API's) are described using metadata and such descriptions are stored in a standard file format in a known location. By storing API definitions using such metadata, other applications can readily identify and use the APIs. To create such API representations, during development, a developer describes the shape of the API, including (but not limited to) the classes, interfaces, methods, properties, events, parameters, structures and enumerated types defined by the API. This API description is processed by a tool which generates a machine-readable metadata file. The machine-readable metadata file contains the same information as the API description, however in a format designed to be machine read rather than human authored.
Abstract:
A system and method for calculating audio processing attribute in digital signal processing system are provided. A testing system generates a multi-channel test signal in which one channel is returned to the testing system and the other channel is sent to a tested system. The test signals are processed, mixed and correlated. The resulting differences in the correlated signals are used to calculate various processing attributes of the tested system.
Abstract:
The invention provides methods and articles for the administration of a biologically active substance (BAS). These methods and articles provide for the controlled and sustained delivery of relatively large quantities of these substances with a low burst effect. The articles made using the method of the invention have increased percentages (w/w) of macromer, increased crosslinking density, and reduced pore size in comparison to articles made using solution methods.
Abstract:
The invention features articles for delivery of a biologically active substance, methods for making such articles, and methods for treating an animal using the articles.
Abstract:
Information about the operating system application programming interfaces is stored in a known format in a known location. This information fully describes the APIs exposed by the operating system and is stored in API metadata files. A language compiler or interpreter uses this API information to build a natural and familiar representation of the native system API in the target language. The language compiler or interpreter can read the API information at compile time and/or runtime. The metadata is used to allow an application to refer to named elements in the API. Projections are built that use the metadata to map named elements in the API to named elements in the target language, and to define wrappers that marshal data of those elements between the target representation and the native operating system representation.
Abstract:
Information about the operating system application programming interfaces is stored in a known format in a known location. This information fully describes the APIs exposed by the operating system and is stored in API metadata files. A language compiler or interpreter uses this API information to build a natural and familiar representation of the native system API in the target language. The language compiler or interpreter can read the API information at compile time and/or runtime. The metadata is used to allow an application to refer to named elements in the API. Projections are built that use the metadata to map named elements in the API to named elements in the target language, and to define wrappers that marshal data of those elements between the target representation and the native operating system representation.
Abstract:
A system for collecting, storing and displaying dermatological images for the purpose of monitoring and diagnosis of skin conditions and skin cancers, including melanoma. A hand-held unit illuminates a section of the patient's skin, and an imaging device generates imaging signals from light derived from a skin section. Pairs of light output ports in the hand-held unit are arranged such that their intensity distributions overlap at their half-intensity levels so that the resulting summation of their intensities has a flat central region. Three image stores are maintained, one for lesion images, one for “nearby skin” images, and one for reference-white images. The “nearby skin” images are used by the system software to automatically determine the skin/lesion border. The reference white images are used to set the dynamic range of the instrument and to compensate for lighting irregularities. Two images of the same lesion taken at different times may be displayed simultaneously so that changes in the lesion may be determined. The calibration system is designed so that image data taken on any of multiple machines built to the same specification will be corrected back to a common reference standard to ensure absolute accuracy in colour rendition.