what's the best way to create a lst file for rklogoedit

[NBS]

Hi,
what tools you are using to create the lst files?
It doesn't seem hard but i can't find a fast way.
In rklogoedit there isn't a way to edit the lst on the fly?
ReadAsBmp seem pretty good to find the images,but can't display 320x240 images.
What method are you guys using?

Thanks for sharing

[knob]

I've found the best way is to use a .lst from another player that is closest to the one you have in looks and screen and then edit it.

It isn't easy in fact it's hard work!, I've been trying the look in the Rockchip firmware itself to try to find the picture information, the information must be in the firmware somewhere because the player is able to display the images correctly.
It should be possible to create a utility to produce a script automatically, but no one has been able to do this yet....

[Dancemammal]

Hi,
I have started writing a tool like RKLogoEdit, but with the features that are missing from RKLogoEdit.

It is in the early stages, there are problems with the bitmap colour, there is a shift in the green ??.

Current features include :

Realtime stretching of images, width and height (pixel accuracy) this makes it easy to find that illusive image,

Pixel image size, helps with finding an image of a particular size,

Image data chunk jump, jumps past all the bytes of the located image so the start of the next image is at 0 - 0,

Double sized image, everything on screen is double size, makes it easy to check the image,

Byte shifing, 1, 10, 100, 1000, 10000 at a time using spin boxes,

Image screen size is 320 x 320 for vertical or horizontal images,

loading and saving of bitmaps,

Assembly code conversion of 16bit to 24 bit and back for fast results,



Still to do :

Fix problem with reading bitmaps from stream (green shift),

Image replacement in firmware stream,

Lst read and write, with editing and insert and delete etc,




When this is finished I will release the code as open source, this will help create a tool that is easy to use with plenty of features.

Anyone wishing to help, please contact me through this forum topic,

need help with the bitmap bug,



Cheers
Dancemammal

[NBS]

@Knob
don't overstimate the firmware developer.
It could be just referenced with a fixed address in the code without any list of the resource.
I tried many times to ask my supplier to provide me the tools to edit the interface of rockchip,but since the solution company earn most of the money on that they aren't willing to release it,and none of the company i cooperate do the firmware in house.

@Dancemammal
Why the need of Assembly?
With modern compiler the boost is really low,and on today pc you can't even notice it.
16 bit is not multiple of 3,so it may be that you are using wrong format.It could be RRRRRGGGGGGBBBBB or something else.You may just try some shifting on the green to see if it's ok.
Btw,what's the use of the shifting in the software?
To find the start and end of the image like readasbmp?

One function you should add is image search.
For example you pass it an image you previously found on the old firmware and it aumatically search for it on the firmware,it's a simple byte code match.
It's useful because you could automatically update the lst when new firmware come out.

[Dancemammal]

Hi All,

I agree, about the fixed address in the firmware, when the developer updates and compiles the firmware, the addresses will have moved.

The bitmap format is 16bit 5-6-5 format, ie RRRRRGGGGGGBBBBB, the data has been read in correctly, but the resulting image seems to have the next pixel with added green ??, I will find it, it will just take some time,
until then it is not worth a release,

The byte shifting, is useful if you cant understand the image you are looking at you can shift the image stream by chunks until you find an image you can see, then you can work back,

The image search would be easy to impliment, and useful, thanks,


Cheers
Dancemammal