Beiträge von mmark

    I just asked for an example of a skin modded the way you proposed, with a full screen main png for testing, if my assumption on OoZooNs secret ingredient is correct.


    But if everything is now OK, then there is no need for that magic anymore :grinning_squinting_face:

    Hi gute
    I creating a new skin a few months ago, and i had the problem that described. was not a problem of my skin, because i found that it appeared with a unique pic included
    in the menu of default skin dmm, (we are many to have him found)


    I tried different images than the cvs, like Gemini and dream elite . These two had the same problem, while the OzOon worked regularly.


    I repeat, I have encountered this problem a few months ago, while in oozoon has always worked.


    For this reason I have asked in the forum oozoon if they had done some operation kung-fu-panda type :smiling_face:


    I also asked in this thread the same question.


    Today after yet another flash of 520 and a software update finally the problem is also solved in the cvs.


    bye

    Ok guys, to complete this thread:
    I flashed the last CSV and I did a software update, and updated many packages.
    Finally, now the skin 1920 works correctly.


    PS***
    I'm sorry it could not respond to friends who speak German I dn't understand :frowning_face:

    So the question is that the new dmm520 really can not support skin fullhd that are support by decoder with 128/256k of memory ??
    I really hope that this is not the correct answer.


    An image with only one color would essentially only require 1/32 of the space the 32 bit image uses (that's not entirely true but it's the rough dimension).
    And as dhwz said, the number of colors actually used doesn't make a difference.
    A 32 bit pixel always uses 32bits for color information (ususally it's "RGBA 8888").


    Especially on the dm520 that makes a huge difference.

    certainly, do not discuss the allocation memory of an image that has one color or 16/256 or 4/8 bits, mine was just an example to say that the image is scaled to the minimum resolutions only 1 and involves this problem, but the thing that i understand less is because other images based on the same version of cvs do not have this problem. it would be enough just to prove that i reported to detect what i write.

    no animation, 1 image with one color should not block the decoder, otherwise it would be correct to say that the image does not support skins fullhd. But even this is false because the oozoon image based on the same version of cvs, it works correctly.

    not speak of 32-bit images but of 8-bit images or based on a 16-color palette, a single image from 1k that blocks the use of the entire system
    also this problem only exists with the new 520 image, not 820 even with E2.2


    Hi sir
    I invite you to do this test :


    change dmm default skin to 1920x1080 res.


    Create an image from one single color 1920x1080



    insert it as background in the menu panel


    restart enigma and browse the menu


    Single image, 1 color, and the system collapses


    also because the OzOon works with any skin fhd and cvs not ? :confused_face:


    bye