crusher11 1101 Posted August 5, 2019 Posted August 5, 2019 I'm using this PNG file as a logo for a TV series: But when I go to the page, it displays like this:
Luke 42077 Posted August 5, 2019 Posted August 5, 2019 Hi there, can you show a picture of the whole page? thanks.
crusher11 1101 Posted August 6, 2019 Author Posted August 6, 2019 Not sure what difference the rest of the page makes, but here it is. I've noticed similar happening with other logos in the past, it's just not usually this blatant.
ebr 16169 Posted August 6, 2019 Posted August 6, 2019 Not sure what difference the rest of the page makes, but here it is. It gives us the proper context so we know where to look . Looks like our whitespace removal routine not coping perfectly with non-rectangular white space.
crusher11 1101 Posted August 6, 2019 Author Posted August 6, 2019 Whitespace removal? It's a transparent PNG.
ebr 16169 Posted August 6, 2019 Posted August 6, 2019 Whitespace = transparent edges. The problem is that TV channel logos come from a wide variety of sources and some of them have huge transparent borders on them making them look tiny and/or non-uniform when displayed alongside others. So we try to remove these transparent borders so the logos will be more predictable.
crusher11 1101 Posted August 11, 2019 Author Posted August 11, 2019 I think the white might actually have something to do with it. I have a similar logo except with a black circle on the outside, and that one looks fine. 1
crusher11 1101 Posted September 26, 2019 Author Posted September 26, 2019 I'm having the same issue with the AFL logo, but the NBL logo works fine. Clearly the white outline is something to do with the problem.
mofa2016 2 Posted October 7, 2019 Posted October 7, 2019 Thanks for reporting. I suggest using method to auto-detect whether using horizontal or vertical filling, which should work better regarding versatile logos.
Luke 42077 Posted October 7, 2019 Posted October 7, 2019 I suggest using method to auto-detect whether using horizontal or vertical filling, which should work better regarding versatile logos. Can you give an example of a logo with an issue? Thanks.
crusher11 1101 Posted October 7, 2019 Author Posted October 7, 2019 Several examples have been posted in this thread. Also here: https://emby.media/community/index.php?/topic/78184-why-does-emby-crop-out-part-of-fanart-logo%EF%BC%9F/
mofa2016 2 Posted October 7, 2019 Posted October 7, 2019 Can you give an example of a logo with an issue? Thanks. Given a display box, is there any approach to auto-detect which direction of a logo itself (without transparent area) could first reach the border of the box? Then operate horizontal filling or vertical filling, rather than cropped it at the first place.
Luke 42077 Posted October 7, 2019 Posted October 7, 2019 No, at least not on all platforms. Any whitespace inside the logo will be preserved and make it look really small.
mofa2016 2 Posted October 28, 2019 Posted October 28, 2019 I found a solution in the tutorials on fanart.tv. They tell you how to create a LOGO that looks good. Because Emby will crop out the WHITE color space, I have the same problem as you did if I adjust a WHITE out-glowing to the logo. Some of the glowing will be cut off. All I Need to do is to adjust a shadow, and everything goes well. https://fanart.tv/members/mofa2016/tv-images/hdtvlogo/
crusher11 1101 Posted October 29, 2019 Author Posted October 29, 2019 Emby shouldn't be cutting off white areas to begin with though.
Luke 42077 Posted October 29, 2019 Posted October 29, 2019 We don't crop the white area, only the transparent area.
crusher11 1101 Posted October 29, 2019 Author Posted October 29, 2019 That's clearly untrue, as the many examples in this thread show.
ebr 16169 Posted October 29, 2019 Posted October 29, 2019 That's clearly untrue, as the many examples in this thread show. Just because the cropping appears to not be working perfectly right now does not make our design statement "untrue". Thanks.
crusher11 1101 Posted October 30, 2019 Author Posted October 30, 2019 The context was: Me: Emby shouldn't be cutting off the white. Luke: It doesn't. How is Luke's statement true? Whether it's supposed to or not, it does.
Happy2Play 9780 Posted October 30, 2019 Posted October 30, 2019 Note this issues appear to be specific to Logos as it works properly as a primary image.
ebr 16169 Posted October 31, 2019 Posted October 31, 2019 The context was: Me: Emby shouldn't be cutting off the white. Luke: It doesn't. How is Luke's statement true? Whether it's supposed to or not, it does. Because, notice how it does not cut off ALL the white? This is obviously just a problem with the determination of exactly what is transparent and what is not (or, probably more correctly, just how precise in terms of curves that the routines are). It isn't a simple fix of us just doing the wrong thing. I probably confused this issue by using the term "whitespace" earlier. That term means "blank areas" as opposed to actual white parts of an image (from the concept of a page being white). I apologize for that confusion. Thanks.
Spaceboy 2573 Posted October 31, 2019 Posted October 31, 2019 Apparently having aspirations is sufficient these days, you never actually have to deliver on them
crusher11 1101 Posted October 31, 2019 Author Posted October 31, 2019 Because, notice how it does not cut off ALL the white? This is obviously just a problem with the determination of exactly what is transparent and what is not (or, probably more correctly, just how precise in terms of curves that the routines are). It isn't a simple fix of us just doing the wrong thing. I probably confused this issue by using the term "whitespace" earlier. That term means "blank areas" as opposed to actual white parts of an image (from the concept of a page being white). I apologize for that confusion. Thanks. Luke's post, at least the way I read it, suggests that it's working as intended and the bug noted in this thread isn't occurring.
ebr 16169 Posted October 31, 2019 Posted October 31, 2019 Luke's post, at least the way I read it, suggests that it's working as intended and the bug noted in this thread isn't occurring. Okay, that was absolutely not the intent. There is clearly a problem of some sort.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now