FS#2848 - xvid raw image extractor

Attached to Project: Rockbox
Opened by karim (mirak63) - Sunday, 18 December 2005, 19:28 GMT
Last edited by Daniel Stenberg (bagder) - Tuesday, 31 July 2007, 13:02 GMT
Task Type Patches
Category Video
Status Closed
Assigned To No-one
Operating System All players
Severity Low
Priority Normal
Reported Version Unstable (example)
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No


I failed to do a patch so that's just tar with the xvid
plugin folder.

It's based on an exemple from xvidcore library.
It extract a xvid stream (you must extract the stream
from an avi) to single images and is a very good base
to create a codec.

This line should be added to apps/plugins/viewers.config

xvid,viewers/xvid_decraw,10 08 58 38 04 02

It's needed to increase the plugin ram since nothing is
optimised yet and plugin is big.
In firmware/exports/config-h300.h

#define PLUGIN_BUFFER_SIZE 0x200000

This task depends upon

Closed by  Daniel Stenberg (bagder)
Tuesday, 31 July 2007, 13:02 GMT
Reason for closing:  Rejected
Additional comments about closing:  There's just no good use of this, even of course it could be the base for an xvid player, it is a long way from that
Comment by karim (mirak63) - Sunday, 18 December 2005, 22:37 GMT

I forgot to say that you can exit with left arrow.
There is not many thing you can do beside that anyway :)

Most of the code would need to be cleaned.
Especially remove what is related to the encoder, there is
some left.
There is many warnings, they happen only when compiling
xvidcore into rockbox, I didn't have that many warnings on x86.
Comment by karim (mirak63) - Sunday, 18 December 2005, 22:42 GMT

mmm, I added -DARCH_IS_BIG_ENDIAN to the CFLAGS of the make
This is required at least for coldfire cpu.
I guess it should done with a #ifdef.
Comment by Daniel Stenberg (bagder) - Sunday, 18 December 2005, 22:54 GMT

Endianness should be figured out by using the autoconf.h
file that configure generates for you.
Comment by karim (mirak63) - Monday, 19 December 2005, 13:34 GMT


ok, I will use a define with that.
Comment by karim (mirak63) - Thursday, 22 December 2005, 01:48 GMT

So this one is striped and fit in the standart plugin ram.
It can read a mpeg4 stream and outputs it to screen at the
impressive rate of 2 frame per seconds :p
The image looks uglier than on the original firmware, maybe
because it's not 18 bits, or maybe because less frame per
seconds can't hide the bad quality.
Comment by karim (mirak63) - Thursday, 22 December 2005, 01:50 GMT

I forgot to say that there is absolutely no check of the
image size.
You should use 220*176.