From: Bram R. <bra...@ph...> - 2006-08-25 14:42:06
|
Hi Chris, A features like "component mapping" to allow the user to select which component to use for what purpose is already proposed for quite some time. Although discussed in several occasions, the ideas as not completely settled down. This is an attempt to describe the current ideas, as they levelled from discussions with Harold, Rene, etc. Currently, we can select the "color display method" (cycles through the options by hitting the 'c' key). Depending on the method, the software automagically selects some components from the file... This needs to be decoupled. So here is the proposal. For each entry of the "color display method", some inputs are required as follows: full color R G B | Y U V | Y grayscale R G B | Y Y & vector Y Vx Vy only vector Vx Vy Y & scalar Y S only scalar S Further, one needs to specify which component from the input file serves as input to the selected the color display method. This is called "component mapping". For compatibility with current mode of operation and for conveniency, proper default component mapping can be implemented. The components read from the file are processed through a matrix (if appropriate). Currently there is only the ITU601 matrix. This will be generalized to offer selections for - ITU601 - ITU709 - custom Again, proper defaults are possible. Further, there is a choice for "normal or full range". This is an independent choice, which can be extended with properties like offset and gain to facilitate high dynamic range video. So, the selection order is: - color display method which determines what kind of components are required, then - component mapping (to determines the components to be accessed from the file) - matrix choice Independent of this, several display settings can be chosen (like currently normal/full range). The processing order is: - select components from file - execute matrix - execute color display method - handle display settings Currently, Harold is working on the underlaying calculations, which requires a major code refactoring to generalize and streamline many of the existing functions. Most of the individual steps can be implemented by a single pixel loop (by first cascading the operations on the generalized matrix definition), so performance is expected to remain very good, even though the code is significantly generalized. In a next stage, the user interface will be adapted to enable the wider and more generic functionality. Your further inputs and suggestions are welcome. Support and manhours even more... Regards, Bram. -- A.K. (Bram) Riemens Principal Scientist, DSP group, Philips Research Office: WO-p-94, Postbox WO02 High Tech Campus 36 (WO), 5656 AE Eindhoven, The Netherlands Tel: +31 40 27 43833, Fax: +31 40 27 44675 E-mail: bra...@ph... Chris Bartels Sent by: pfs...@li... 17-08-2006 13:51 To pfs...@li... cc Subject [Pfs...@sf...] multilayer extension to pfspd Classification As a feature request for new pfspd toolset versions: is it possible to add a multiple layers extension to the format / viewer, i.e. such that the user can add an arbitrary number of color (RGBA) / vector (float,float) overlays. The viewer already contains a feature for one vector overlay but this is not always sufficient. Has anybody had similar problems, or maybe solutions? Kind regards, Chris Bartels ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Pfspd-users mailing list Pfs...@li... https://lists.sourceforge.net/lists/listinfo/pfspd-users |