At 22:49 17/02/02 +0100, you wrote: > Hi John, hi Klaus, > > First, I removed the OSD resizing code from the driver because I think size > is more important than color ;-) Then, I changed VDR so that it now creates > 1-bit OSD windows only. Initially, this caused VDR to hang because it still > tried to allocate color space that wasn't available later. So, I changed the > code to use only black and white to draw the menus etc. This works with the > status (channel info) display, but I still get no main menu (OSD window > larger than 32k???). After opening and closing the status window a couple of > times, VDR will still hang. Apart from that, audio and video are sometimes > out of sync after using the OSD 8-}
I considered changing the bitmap colours within my driver patch code. But I found that VDR already uses just a few colours (I think 4); by changing to 2 colours I could reduce the bitmap size by 50%, but by changing the bitmap size I reduced it by 75%, which was better. > > I've got some questions now: > > How does an OSD window work? Is this an area of the screen that is being > allocated once (and visibility is just being turned on and off) or does it > work like a "window" under MS Windows/X11, i.e. the memory is being freed > after the window is being closed? I think it's more like in Windows. There's some documentation for the AV7110 chip somewhere (I think on the Convergence site) that explains it. > > Does VDR use bitmap functions to display text, too? If I understand > correctly, there are some text functions available from the driver which > seem to be more reliable. VDR doesn't use the text functions; it makes all the text into bitmaps. I don't know why. I don't know whether the text function would be more reliable. > > Finally: what will the OSD look like without using bitmap drawing functions? > I suppose there will be just text on transparent background, right? No, no text at all. > hh You might like to investigate the new code to read and write the CI that has appeared in the latest driver versions (0.9.4 and later). It is undocumented, but I suppose it is doing the same as my code was trying to do. Perhaps Convergence have fixed the CI support in their firmware; if so, then I'll be the first to throw away what I've done and use their code. John ______________________________________________ The information contained in this e-mail is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you are not the intended recipient of this e-mail, the use of this information or any disclosure, copying or distribution is prohibited and may be unlawful. If you received this in error, please contact the sender and delete the material from any computer. The views expressed in this e-mail may not necessarily be the views of The PCMS Group plc and should not be taken as authority to carry out any instruction contained. -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
