> I know this has been mentioned several times in the past but I don't think > anyone has made any progress in getting hardware MPEG decoding on the Via > CLE266 and related chips from DirectFB apps.
That pretty much matches my understanding. > so I get a few jerks and A-V sync isn't as good as > it should be. I've started looking into this again now... The A-V sync suffers a little because triple-buffering introduces a noticable delay into the video so the audio becomes noticably early. I'm a xine-lib user and surprisingly there seems to be no way to account for this using any config option. What's needed is a corresponding audio delay. As for your jerks, can't help there -- my video is jerk-free. > Currently, softdevice uses libavcodec to do the actual MPEG2 decoding. What I > was hoping for was a simple slot-in solution where I just pass the relevant > MPEG2 data to a different library, retrieve the decoded frames, and leave > softdevice to display them using DirectFB. I'm not sure it works like this: I think you feed data to the hardware decoder and it puts the result directly into video memory. What you need is for this to be represented by a DirectFB surface so that you can then flip it out to a display layer. I've only spent a small amount of time looking into this though, so I may be wrong. > VeXP-VIAXine: not really delved into this but I think this requires X too. No, I think there is a framebuffer output option. However, it won't coexist with DirectFB. Messages on the VeXP forum from 2004 suggest they do have a DirectFB compatible version but they're not making that open source. I wondered whether it might be possible to have VeXP just use the overlay layer leaving DirectFB to manage the primary but that would require some work to stop them fighting and to manage video memory allocation. > mtest: not fully built this yet because it requires a patch to DirectFB. It > seems to need /dev/cle266vgaio which linux-viafb from DirectFB doesn't > provide. You shouldn't need that if you're using the DirectFB viafb module: cle266vgaio just allows user-space code to access the video registers: the framebuffer driver does that too. > Now, I'm not totally sure whether the data can be read back from the decoder > or whether it goes directly to a framebuffer from there, somehow! I think it goes directly into video memory. > Has anyone made any more progress with this or am I starting from scratch? Not as far as I know. Regards, Mark _______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
