Method and apparatus for providing and on-screen display with variable resolution capability

[0002] This application is a divisional of copending U.S. Ser. No. 08/962,514 (TI- 24731) filed on Oct. 31, 1997 and hereby incorporated herein by reference. The aforementioned copending application claims priority under 35 U.S.C. 119(e)(1) of U.S. provisional application Serial Nos. 60/030,107 (TI-24441P), 60/030,106 (TI-24442P), 60/030,105 (TI-24443P), 60/030,104 (TI-24630P), 60/030,108 (TI-24646P) and 60/029,923 (TI-22990P), all filed on Nov. 1, 1996 and hereby incorporated herein by reference.

[0003] The invention relates generally to digital data processing, and more particularly, to digital data processing associated with on-screen displays.

[0004] Many conventional on-screen display (OSD) techniques disadvantageously require high resolution processing for an entire screen if any part of the screen requires high resolution processing. For example, Table 1 shows the number of bytes required to store a full screen picture 720 pixels×576 lines in different display modes for an OSD system that does not allow mixing of several modes of display in real time on the same screen. When one part of the screen requires 256 colors, the full screen must be 256 colors, even if another part of the screen requires only 2 colors.

[0005] The present invention provides for on-screen display with a variable resolution capability that advantageously permits respective parts of a screen to be processed according to their respective resolution requirements, thereby reducing the processing power and memory required to produce the on-screen display. In particular, for any active window in the on-screen display, the invention can determine the data format used in memory to represent the pixels of that window, thereby permitting the window resolution to vary from window to window.

[0006] FIG. 1 depicts a high level architectural diagram of an audio/video decoding system employing an OSD coprocessor of the present invention illustrating the global flow of data from decoding to displaying an OSD picture.

[0007] FIG. 2 depicts display modes of an OSD coprocessor of the present invention and their associated memory requirements.

[0008] FIG. 3 depicts two representative OSD pictures generated by an OSD coprocessor of the present invention.

[0009] FIG. 4 depicts how a CPU builds windows in a portion of its memory and the windows are used to build a frame in a frame memory which is displayed by an OSD coprocessor of the present invention on a screen display.

[0010] FIG. 5 depicts a high level architectural block diagram of an OSD coprocessor of the present invention and selected interconnections.

[0011] FIG. 6 depicts two windows having different color schemes that illustrate how an OSD coprocessor of the present invention displays two overlapped windows.

[0012] FIG. 7 depicts how a portion of the windows of FIG. 6 are stored in a frame memory.

[0013] FIG. 8 depicts in more detail selected portions of the blocks of FIG. 5.

[0014] FIG. 9 depicts a portion of a window controller of the present invention.

[0015] FIG. 10 depicts portions of a memory cell and memory logic utilized in a window controller of the OSD coprocessor of the present invention.

[0016] FIGS. 11-13 depict the generation, assembly and display of portions of windows depicted in FIGS. 6 and 7.

[0017] FIG. 14adepicts representative window transition timings, such as those for FIGS. 6 and 7.

[0018] FIG. 14bdepicts representative pixel selection and multiplexer timings for FIG. 13.

[0019] The following describes how an OSD controller 270 may be employed to provide OSD (e.g., for use with a digital television set-top box) with variable resolution. FIG. 1 shows the global flow to decode and display an OSD picture. The PSI buffer 312acontains the coded picture, for example: a Teletext data to be displayed within an OSD picture. The CPU 220 decodes (1) the Teletext data and builds (2) the OSD picture using the Bitblt hardware 272 accelerator. The OSD controller 270 reads (3) the OSD buffer 312band generates the OSD video that is mixed with MPEG video(4).

[0020] Different modes are displayed simultaneously on the screen: A bit-map window 1000 with 2 colors, a still video picture 1010, a 256 colors graphic window 1020, a decimated motion video picture 1030 and a Logo in true color. The OSD controller 270 minimizes the memory required to display service information. The OSD uses a new hardware windowing technique to mix different mode of display such as: Bit map with variable resolution, graphic plane, still video picture and decimated motion video.

[0021] FIG. 2 shows the various modes of display available according to the invention.

[0022] In a bit map mode 1050, the frame buffer contains the code of the color of each pixel to be displayed. The number of bit per pixel defines the number of the colors that can be displayed on screen. Two colors require 1-bit per pixel and 256 colors require 8-bit per pixel. This mode is used to display graphic and text. The code of the color addresses the color look up table that contains the three color components with 8-bits each.

[0023] Graphic plane, 4:4:4 mode 1060, uses 8_bit per pixel for each color component R,G,B or Y,Cr,Cb. Each pixel requires 24-bits (16 million colors per pixel).

[0024] With the 4:2:2 mode 1070 the resolution of the chroma is divided horizontally by two. Each pixel has a luminance component Y and alternately a chrominance component Cr or Cb. This mode is used for video still or motion picture. Each pixel requires 16-bits.

[0025] With the 4:2:0 mode 1080 the resolution of the chroma is divided by two horizontally and vertically. Each pixel has a luminance component Y and a chrominance component Cr and Cb for 4 pixels. This mode is used by the MPEG video decoder to the size of the memory required to store a video motion picture. Each pixel requires 12-bits. The chroma interpolator generates the 4:2:2 output format.

[0026] The OSD controller 270 can display several modes described above simultaneously on the same screen. Each part of the screen with different display modes uses a window fully programmable in size, in position and priority level. The windows can be overlapped without limitations. The characteristic of each window is defined by a set of attributes stored in SRAM. Those attributes are used to calculate the memory address in real time during display and to control the hardware display system.

[0027] FIG. 3 shows typical OSD pictures. The left screen is composed of 5 OSD windows with different characteristics displayed on a full screen background color 1110:

[0028] a bit-map window 1100 having 360 pixels by 288 lines with two colors that requires 1-bit per pixel,

[0029] a bit-map window 1102 having 360 pixels by 144 lines with 16 colors that requires 4-bits per pixel,

[0030] a graphic window 1104 having 90 pixels by 72 lines with 16 million colors that requires 24-bits per pixel,

[0031] a still video picture window 1106 having 180 pixels by 144 lines in 4:2:2 format using 24-bits per pixel,

[0032] an MPEG motion video window 1108 having 180 pixels by 144 lines in 4:2:0 format. The window size and position is generated by the OSD system. The MPEG video decoder generates the content of the window by decimation of the full screen picture.

[0033] This OSD picture requires 110 Kbytes memory. Without the OSD controller 270 the memory requirement could be up to 1.24 Mega bytes.

[0034] The right screen of FIG. 3 shows another picture composed of 2 OSD windows displayed over a full screen motion video 1120:

[0035] a bit-map window 1122 having 540 pixels by 504 lines with two colors that requires 1-bit per pixel. The background color is blended over motion video; and

[0036] a bit-map window 1124 having 360 pixels by 144 lines with 16 colors that requires 4-bits per pixel.

[0037] The memory size is 93 Kbytes using the OSD controller 270 compared to 207 Kbytes without it.

[0038] The following illustrates the memory needed for the examples in FIG. 3.

[0039] As depicted in FIG. 4, in frame mode the CPU 220 and frame use different memory areas. The CPU 220 builds the windows separately in the CPU memory 240 and each window has its own display attributes i.e. display mode, resolution . . . . The new display picture is created by the CPU, by copying sequentially each segment of the window 1 and 2 in such way that the OSD display controller 270 reads the frame memory 312 sequentially and displays line by line from the left upper corner to the right lower corner. The display area that does not contain any OSD data, such as background color or motion video, is not included in the frame memory. Each transition of window, each line, the controller synchronously change the attribute in order to display the window with the corresponding mode. The number of bits to display a pixel of window 1 and 2 can be different.

[0040] A block diagram of the OSD controller 270 is shown FIG. 5.

[0041] The pixel and line counter 270-1 receives the pixel clock, generates X, Y that represent the pixel position on the screen and uses the synchronization signals Hsync and Vsync to control screen display.

[0042] The windows controller 270-2 contains the position X and Y of each windows to be displayed on the screen. The controller 270-2 compares X, Y position and indicates to the display controller 270-4 each window transition and window number.

[0043] The address calculator 270-3 is not used in the frame mode.

[0044] For each new window transition the display controller 270-4 reads the new attribute from the attribute memory 270-5. It generates the address for the display memory 312 and loads the FIFO 270-7 with a new block of data. It then generates the attribute for the current window and sends it to the Decoder 270-6.

[0045] For each pixel, the decoder 270-6 extracts from the FIFO 270-7 the number of bits corresponding to the current pixel to be displayed. It transforms data bits into pixels.

[0046] The windows attributes are as follows:

[0047] Display modes: empty window for decimated video. Bitmap, YCrCb 4:4:4 graphics component, YCrCb 4:2:2 CCIR 601 component and background color

[0048] Supports blending of bitmap, YCrCb 4:4:4, or YCrCb 4:2:2 with motion video and with an empty window

[0049] Supports window mode and color mode blending

[0050] Provides a programmable 256 entries color look up table

[0051] Outputs motion video or mixture with OSD in a programmable 422 or 444 digital component format

[0052] Provides motion video or mixture with OSD to the on-chip NTSC/PAL encoder

[0053] Each hardware window has the following attributes:

[0054] window position: any even pixel horizontal position on screen; windows with decimated video have to start from an even numbered video line also

[0055] window size: from 2 to 720 pixel wide (even values only) and 1 to 576 lines

[0056] window base address

[0057] data format: bitmap, YCrCb 4:4:4, YCrCb 4:2:2, and empty

[0058] bitmap resolution: 1, 2, 4, and 8 bits per pixel

[0059] full or half resolution for bitmap and YCrCb 4:4:4 windows

[0060] bitmap color palette base address

[0061] blend enable flag

[0062] 4 or 16 levels of blending

[0063] transparency enable flag for YCrCb 4:4:4 and YCrCb 4:2:2

[0064] output channel control

[0065] FIG. 6 shows an example of display of two overlapped windows. Window 2 in back is a bit map with 16 colors per pixel. Each pixel requires 4-bits in the frame memory to define the code of the color. The window 1 on top is a bit map with 2 colors per pixel. Each pixel requires 1-bit in the frame memory 312 to define the code of the color. The position and dimension of the window 1 is given by the attributes X_10, X_11, Y-10, Y_11. Horizontally the number of pixel is: X_11-X_10. Vertically the number of lines is: Y_11-Y_10. Same for window 2 with X_20, X_21, Y_20 and Y_21.

[0066] The display controller 270-4 accesses sequentially the display memory 312 from the first word containing the pixel X_20, Y_20 to the last word containing the pixel X_11, Y_11. Details of the line 20 are shown in FIG. 7. The line begins with the pixels of the window 2, and window 1 starts at X_10, Y_10. Pa is the last pixel of window 2 with 4-bits per pixel and Pb is the first pixel of window 1 that uses 1-bit per pixel. Window 1 ends on Pc and window 2 restarts at Pd and continues until pixel position X_21 (see also FIG. 6).

[0067] The same word contains pixels of window 1 and 2. During display the windows controller 270-2 detects the transition between Pa and Pb and controls the data processing after FIFO 270-7 access.

[0068] Although not explicitly shown in FIG. 5, a pixel selector 270-12 and multiplexer 270-18 shown in FIG. 8 provide the input of the decoder block 270-6 of FIG. 5. The pixel selector 270-12 receives the outputs of the FIFO 270-7, and the multiplexer 270-18 receives the window attributes and control signals from the display controller 270-4. The basic function is to transform data stored in the frame memory 312 into pixels. In case of bit map display, the output, Pixel_Mux[7:0] 270-10 is the address of the CLUT (color look up table). For graphic or still video picture the output is one color component. Pixel_Mux[7:0] 270-10 output is produced by bits coming from the FIFO 270-7 and bits from attribute memory 270-5.

[0069] The pixel selector 270-12 receives 32-bit data from the FIFO outputs F[31 :0]. The first stage 270-13 selects one of the five bytes F[31:24], F[23:16], F[15:8], F[7:0] and F-1 [6:0] (F-l means delayed by one clock sample). The second stage 270-14 is a half barrel shifter that allows shifting right a 15-bit input data by 0 to 7 bit positions. The output of the barrel shifter 270-14 positions the LSB of the code of the pixel to be displayed in Bs[0]. The pixel counter 270-20 provides the control signals for the multiplexer 270-13 and barrel shifter 270-14. Table 2 shows the effect of the control Mux_S[1:0] on the byte selection and Table 3 shows the output of the barrel shifter in function of Bs_S[2:0]. Table 4 combines Tables 2 and 3 and shows the bits of the FIFO selected at the output of the barrel shifter as a function of the 5-bit pixel counter.

[0070] The multiplexer 270-18 receives data Bs[7:0] from the barrel shifter and Base[7:0] from the attribute register. It is controlled by 4 control bits coming from the attribute register 270-4A, and cursor and default signals from display controller 270-4 as shown in Table 5.

[0071] When active Pm[7:0] is equal to the 8-bit default color DEF[7:0] provided by the general control register of the display controller, no data is read from the FIFO.

[0072] When active Pm[7:0] is equal to the 8-bit cursor color CUR[7:0] provided by the general control register of the display controller, no data is read from the FIFO.

[0073] Bp[3:0]=0000 indicates that the current window is empty and contains 0_bit per pixel or color component. Pm[7:0] is equal to Base[7:0] stored into the attribute register 270-4. In bit-map mode, the Base[7:0] selects one of the 256 colors of the CLUT as a background color.

[0074] Bp[3:0]=0001 indicates that the current window contains 1_bit per pixel or color component. Pm[7:0] is equal to Base[7:l] concatenated with Bs[0] from the barrel shifter. In bit-map mode, the Base[7: 1] is the base address of a set of 2_colors of the 256 colors CLUT.

[0075] Bp[3:0]=0011 indicates that the current window contains 2 bits per pixel or color component. Pm[7:0] is equal to Base[7:2] concatenated with Bs[1:0] from the barrel shifter. In bit-map mode the Base[7:2] is the base address of a set of 4_colors of the 256 colors CLUT.

[0076] Bp[3:0]=0111 indicates that the current window contains 4_bits per pixel or color component. Pm[7:0] is equal to Base[7:4] concatenated with Bs[3:0] from the barrel shifter. In bit-map mode the Base[7:4] is the base address of a set of 16_colors of the 256 colors CLUT.

[0077] Bp[3:0]=1111 indicates that the current window contains 8_bits per pixel or color component. Pm[7:0] is equal to Bs[7:0] from the barrel shifter. In bit-map mode the 256 colors in the CLUT are used.

[0078] The pixel counter 270-20 provides the control for the pixel selector 270-12, namely Mux_S[1:0] concatenated with Bs_S[2:0]. At the beginning of each frame the pixel counter is reset. It is decremented by 0, 1, 2, 4 or 8 depending on the current window attribute. An address clock signal is generated when the counter hits zero.

[0079] The memory address generator 270-30 generates the read address for the FIFO 270-7. For each address clock signal generated by the pixel counter 270-20, a new 32-bit word F[31:0] is sent to the pixel selector 270-12.

[0080] The attribute memory 270-5 contains the attributes of the windows to be displayed during the current frame. The attributes that control the pixel selector 270-12 and multiplexer 270-18 are:

[0081] Display mode: bit-map, graphic, still video or empty

[0082] Number of bits per pixel or color component: 0, 1, 2, 4 or 8 bits

[0083] The bit-map CLUT base address

[0084] The attribute register 270-4A contains the attribute of the current window. The attribute clock transfers the content of attribute memory 270-5 to the register 270-4A when the window changes.

[0085] As depicted in FIG. 9, the windows controller 270-2 is composed of a content addressable memory CAM 270-40, flip flops 270-41, 270-42 and priority encoder 270-45. The CAM contains the attributes of position and size of the windows to be displayed in the current frame. FIG. 9 shows a 32-word CAM 270-40. Each window requires 4 words that indicate horizontally the coordinates of the first and last pixel and vertically the coordinates of the first and last line. A 32_word CAM supports 8 windows. Other sizes of CAM may be employed.

[0086] The CAM 270-40 compares the value of the pixel and line counters respectively X and Y. When Y counter matches a value Yn0, a new window starts vertically, and the corresponding RS flip-flop is set Wn_Y=1. When the Y counter matches a value Yn1, the corresponding window ends vertically and RS flip-flop Wn_Y is reset. The process is the same horizontally. Wn_Y and Wn_X are combined to indicate that the X, Y counter is in an active window. The indices “n” indicate the window number. Since several windows can be overlapped, the priority encoder 270-45 indicates the display order on the screen. The indices “n=0” correspond to the cursor that must be always on top. Outputs of priority encoder are HIT and OSD_W; HIT generates the attribute clock and OSD_W generates the attribute memory address corresponding to the active window.

[0087] The detail of a CAM cell is shown FIG. 10. The cell contains 2 parts, a 6 transistor RAM cell 270-47 and a 4 transistor comparator circuit 270-48. The CPU 220 loads the CAM with the attributes of position of the windows, memory mode is selected. During the display the associative mode is selected. The line counter Y and pixel counter X are compared to the contents of all Yn and Xn of the CAM. When X or Y is equal to one or several values the corresponding Match lines are active to set or reset a flip-flop as noted in FIG. 9.

[0088] FIGS. 11, 12 and 13 correspond to the generation of the display and frame memory represented in FIGS. 6 and 7.

[0089] In FIG. 11, the pixel Px of the window 1 is selected in the 32_bit word “m”. The pixel counter is decrement by one each access. The pixel selector places Px at the output Bs[0]. The current window attribute selects 1_bit per pixel. The pixel multiplexer selects Base[7:I] and concatenates with Px to form the output Pixel_Mux[7:0]. In bit-map mode Pixel_Mux[7:0] selects 2 colors of the CLUT. Base[7: 1] is the base address of the CLUT. FIG. 12 shows the generation of a pixel Px for the window 2 that use 4_bits per pixel in bit-map mode. The pixel selector places Px at the output Bs[3:0]. The pixel multiplexer selects Base[7:4] and concatenates with Bs[3:0] to form the output Pixel_Mux[7:0] that selects one of the 16 colors of the CLUT. Base[7:4] is the base address of the CLUT. 16 CLUT of 16 colors can be selected with the window attributes.

[0090] FIG. 13 shows a specific case of the window 2 where Pn+1 has its 2 msb's in the word m+1 and 2 lsb's in word m+2. Word m+2 is currently selected at the output of the FIFO and the 7 lsb bits of word m+1 are maintained in the 7_bit register F-1 [6:0]. Pixel selector takes F-1[1:0] concatenated with F[31:30] to generate Bs[3:0]. The corresponding timing is shown in FIG. 14b. At Pn+1, the pixel counter equals 30. The barrel shifter output generates F-i [5:0] concatenated with F[31:30]. The current FIFO address is word m+2 and the Pixel_Mux output is Base[7:4] & F−1[1:0] & F[31:30]. At pixel Pn+2 the pixel counter is decrement by 4, and the pixel selector selects the next 4_bits of word m+2.

[0091] In FIG. 6, the window 1 is on top of window 2. The CAM of the window controller is loaded with window 1 attributes position on top of window 2. The window displayed on top has the lower indices. Pixel Pa is last pixel for this portion of window 2 in the frame memory, the next bits contain the code of color of window 1, the first bit is Pb. During the same line window 1 ends at Pc and window 2 restarts at Pd. Each of these window transitions are detected by the window controller that generates the attribute clock (see FIG. 8) to change the current display attribute stored in register 270-4A, as shown in timing FIG. 14a. For Pa−1 and Pa the Pixel counter is decrement by 4 each pixel. After the attribute clock, Bp[3:0]=1 (see also FIG. 8) decrements the counter by 1 each pixel.

[0092] In bit-map mode the frame memory contains the code of the color, 1,2,4 or 8 bits per color depending on the attributes. The code of the color concatenated with the CLUT color base attribute selects a color from the CLUT. The CLUT contains 3 color components, one component for Luma and two components for Chroma.

[0093] When the current window is graphic, the CLUT is not used. For each pixel there are 3 identical accesses to the bit-map mode to extract the 3 color components from the frame memory. There are 3 accesses during a pixel.

[0094] In a still video picture the CLUT is not used. Still video reduces Chroma bandwidth. For each pixel there are 2 accesses identical to the bit-map mode to extract one Luma component and chroma component Cr or Cb (alternately each pixel) from the frame memory.

[0095] When the picture is empty, the mode is bit-map with 0-bit per pixel. This mode is used to generate a window with a background color or a decimated motion video picture coming from the MPEG video decoder.

[0096] The pixel selector allows the hardware to mix different modes of display. The pixel selector and multiplexer hardware, its control, the window controller, the window attribute generation and the flow of data from the frame memory to the Pixel_Mux output allows the different display modes for different resolution.

[0097] The frame memory contains a description of the current displayed picture. The Or description is done sequentially starting from the first upper left corner of a window “n” to the last lower right corner of a window “m”. Only the active windows need to be described, not the full screen, background color or motion video.

[0098] The description is done pixel per pixel, the number of bits to describe one pixel can vary for each window. Each transition of a window is indicated by the attributes of position stored into the CAM. The window controller selects the attribute of the corresponding window in real time during display.

[0099] The pixel selector selects the number of bits corresponding to the current pixel to be displayed. The complementary bits to form the 8_bit pixel output are obtained by concatenation of selected data bits from the frame and a window attribute from the attribute memory.

[0100] When the current window is a bit-map, the Pixel_Mux output selects a color from the CLUT. The CLUT contains the 3 color components.

[0101] When the current window is graphic, the CLUT is not used. For each pixel there are 3 accesses identical to the bit-map mode to extract the 3 colors components from the frame memory.

[0102] In still video picture the CLUT is not used. For each pixel there are 2 accesses identical to the bit-map mode to extract the 2 color components from the frame memory. Luma is extracted each pixel and the chroma component Cr or Cb is alternately extracted for each pixel.

[0103] When the picture is empty the mode is bit-map with 0_bit per pixel. This mode is used to generate a window with a background color or a decimated motion video picture coming from the MPEG video decoder.

[0104] Although exemplary embodiments of the invention are described above in detail, this does not limit the scope of the invention, which can be practiced in a variety of embodiments.