Marc Edwards

Marc Edwards

Community Staff Founder at Bjango Joined over 4 years ago via an invitation from Christophe T. Marc has invited Matt Kelsh, Rene Ritchie, Dan V Peterson, Troy Mcilvena, Graham Clarke and 12 others

  • 476 stories
  • Posted to Is it better for designers to be generalists or specialists?, in reply to Robin Raszka , Aug 20, 2017

    I agree with “yes”. :D

    You really need to aspire to be both. It seems like a good goal to try to have enough generalised skills to be able to attempt anything in a related domain, but I’d also hope people care enough about the finer details to hone their skills in very specific tasks.

    1 point
  • Posted to JK Rowling shuts down Erik Spiekermann on Twitter, Aug 20, 2017

    Writing a book is such a huge endeavour. Well done, Laura. :)

    I’m all for criticism where appropriate, but I don’t see much benefit in Erik’s nitpick. Who says “I wrote a text”, anyway?

    11 points
  • Posted to Google Chrome rendering colors inaccurately, in reply to Roland Illés , Aug 11, 2017

    So does the recommendation that you shouldn't color manage your designs still hold up?

    My article on that is 8 years old, and a lot has changed since then. Browsers were such a mess, and a lot of the macOS colour management policies were different. I really need to update the article, and probably write a couple more on the topic. It’s complicated, and still in flux.

    Stuff was so broken back then, that I was far happier working without colour management, on a known sRGB display with sRGB targets (iOS, Android, web).

    I think if you’re using an sRGB-like display, it can still be a good way to work, but it’s becoming an increasingly bad strategy.

    If you work on a Display P3 or Adobe RGB display, or you use a mixture of displays that aren’t sRGB, you don’t have much choice — you should assign the sRGB profile to your documents. For most of your design documents, anyway.

    Should I discard the color profile when I paste a screenshot in Photoshop?

    Sometimes. :P

    It’ll largely depend on what you’re checking, and where the screenshot has come from. As Vlad mentioned, if your screenshot is 8bit per channel, and opening it in Photoshop means it’s been passed through one or more conversions, there can be severe quality loss.

    If I’m checking the quality of a gradients and low frequency changes, then I typically open screenshots and remove the profile (with no conversion). We don’t yet have high bit depth screenshots in macOS, even though the window manager does run at higher bit depth on some Macs.

    If I’m just checking measurements, then it really doesn’t matter if the colours are incorrect. I try to be very pragmatic about how to handle this stuff.

    I typically assign an sRGB profile to my design documents now, but even then, there’s issues. It really sucks how complex this is. Saying “you need to understand colour management” isn’t a good solution. :(

    I wish our tools weren’t completely ignorant of the issues, or entirely based on print design. Neither strategy is a good one.

    tl;dr Yeah, you should probably just assign sRGB to all your screen design documents. And, you should probably never sample colours from the screen. If you need to work out the value of a colour, you’re best going to the original artwork file or code (and in that case, hopefully you’ll know which colour space it belongs to).

    2 points
  • Posted to Google Chrome rendering colors inaccurately, in reply to Vlad Danilov , Aug 11, 2017

    Yep, I agree with all that. The lack of detail in my reply was for brevity. You know I’m a big fan of higher bit depths. :D

    The OP was asking about CSS colours, which is why I skipped over ICC profile support in images in Chrome.

    3 points
  • Posted to Google Chrome rendering colors inaccurately, in reply to Ted McDonald , Aug 10, 2017

    Some are good now (if set up correctly). Illustrator, Photoshop, Affinity Designer, Affinity Photo, Pixelmator, and Acorn all handle things well, if you have the correct profile attached to the document.

    It does become a bit of a challenge when you need to not only understand the colour values, but also which profile they’re using. It can get pretty tricky.

    It’s definitely also worth noting that at one point Safari wasn’t colour managed (or to be more accurate, had all kinds of wild behaviour). This stuff has changed a lot over the past decade, but it’s all heading in the same direction, thankfully!

    3 points
  • Posted to Google Chrome rendering colors inaccurately, in reply to Ted McDonald , Aug 10, 2017

    Given the changes in Android O, the colour management in iOS and macOS, and the way the entire industry is going, you should expect this to be on for all users in the future.

    3 points
  • Posted to Google Chrome rendering colors inaccurately, Aug 10, 2017

    This is because prior versions of Chrome were not colour managed. The behaviour you’re seeing (things being darker) is correct, from a colour management point of view.

    And it definitely is inaccurate, since the colors specified in the code are not the colors rendered by the browser.

    If your display is sRGB, they will be the same. CSS and SVG colours are considered to be sRGB (unless specified otherwise, using some proposed CSS features).

    If your display is not sRGB (like the new MacBook Pros and new iMacs), then the colours rendered will be converted from sRGB to the display’s profile. That means the appearance is preserved, but the colour values stored in memory are not.

    This is a good thing! It means you can expect colours to look closer across different computers and different browsers. I’m not entirely up to date with what all the browsers are doing, but I believe Firefox can also be colour managed, but it’s off by default.

    There is one big caveat though: If you rely on sampling colours from the screen, then you may need to work out some other way to work. Sampling from the screen means you’re reading from the display buffer, that’s in the display’s colour profile, and usually 8bit int per channel for Macs (or 16bit int on wide gamut devices). This means there is a very good chance the sampled value will be clipped or rounded, even with the correct conversion. Basically, don’t sample from the screen. It’s just not a reliable way to get colours.

    You should expect all browsers to have this behaviour soon. All design tools need to do this as well.

    52 points
  • Posted to Apple's new Mac Pro 2018 is getting a complete redesign, in reply to Dominik Dom , Jul 31, 2017

    I think Dean just means that a Mac Pro that’s a fast big beige box is more important to most pro users than a far slower Mac Pro in a nice looking case.

    I’m with Dean on this one — I almost don’t care what the thing looks like, I just want a ton of cores in a reliable package. I don’t need an extruded aluminium case, but I do need a latest gen GPU.

    3 points
  • Posted to Apple's new Mac Pro 2018 is getting a complete redesign, Jul 31, 2017

    It doesn’t look like there’s any new info in this article at all?

    New Mac Pro 2018 latest news: Release date, UK price, features & specs

    Release date mentioned in the article: “Not until 2018, according to Apple.”


    8 points
Load more comments