Jump to content

hschneider

Members
  • Content Count

    58
  • Joined

  • Last visited

Everything posted by hschneider

  1. It might be the same problem. Have you tried this? Change the Rendering Intent to Relative Colourimetric and create a new document, with a colour profile setting of CMYK/8, Euroscale v2. Then draw again a white square.
  2. Pls check this post, the solution provided by Hangman at the end of the thrread:
  3. A customer of mine used a rather old barcode generator. Meanwhile he uses SVG files. However, it was just an example. The problem also appeared with product images, too.
  4. WAAAAAAAA !!!! You nailed it! :-) Thank you so much - for the detailed explanation and the fix itself! You did a really good job, compliments!
  5. Thanks. Replacing the profile had unfortunately no effect. Rather strange ....
  6. OK. Can you attach yours, please? There was no attachment on your last post.
  7. I ticked 'Convert opened files to working space', but it makes no difference as long as my working space profile is 'Euroscale Coated V2'. As I wrote before, when my profile is Coated Forgra39, then the test doc is converted into Coated Fogra39 and the JPG appears bright white as is should. @GabrielM: The question is: Why is the doc's profile corrupt? All my documents and those of a customer of mine seem to have the same bug. The only things we both have in common and which is not true for the testers here is: We both have a multiple monitor setup with an external 3rd party screen (Non-Apple, but LG and HP). Is there a way to reset or delete AD's color profile information?
  8. When changing the doc profile to Coated Fogra39, the RGB bitmap is imported correctly. On my machine, the doc background and the bitmaps's white both sample to CMYK 0 0 2 0. Both appear bright white, as they should. I still believe it is some profile and / or multiple monitor related bug.
  9. For the developers reading this: Doing the same procedure in Affinity Publisher works perfectly, even in the AD Persona.
  10. Looks like this is only a part of the problem: When I assign the profile Coated Fogra 27, the background samples to CMYK 0 0 0 0, but the test jpg is still yellowish.
  11. It is the same I see here, when I create a new doc with EuroScale Coated V2.
  12. Looks like something AD writes to the file, when it is created: The sample created by mac_heibu works fine at my machine. My test file with the same settings shows on Hangman's machine a background with CMYK 0 1 4 0 and does not work on my machine.
  13. My monitor profile is the standard one, which comes with the iMac. The test doc IS created with the same settings as the working sample. Can we compare the color settings in AD, please ? See screenshot attached.
  14. Thanks for testing. Now things get more weird: Your sample doc works perfect. All files I drag onto your doc are rendered perfectly. Now I create a new doc, with the same settings: Profile Euroscale Coated VS, CMYK/8 and I run into the same issue again. BTW: The barcode has been created by a customer of mine. He has the same issue on his machine. So there must be something else different on your machine and ours here. Just a guess: Do you have an external monitor attached to your Mac? If so, is it an Apple or 3rd party product? Which macOS do you run ? There are color profile issues mentioned in the forum, which are related to external monitors.
  15. That's exactly the same I did. I even tested it again, the result is still yellowish.
  16. > The issue though is that the test.afdesign file doesn't have a 'white' background, as you say if you sample it, it has the values CMYK 0, 1, 4, 0 IMHO this is the result of assigning EuroScale Coated V2 as a doc profile.There all the trouble begins.
  17. @mac_heibu: The original file is attached to my 1st message. It IS a color conversion or profile issue: I have loaded the original RGB jpg into the Apple ColorSync Tool and assigned the EuroScale Coated V2 profile. After this, the output is a CMYK jpg wich shows in perfect white in AD. So the problem seems to be color profile handling or conversion in AD.
  18. Thanks for the detailed description. When I open the JPG in Affinity Photo then is shows clear white with RGB #ffffff. When I export it as a CMYK TIFF, then the problem appears again. The exported file has CMYK 0 1 4 0. Meanwhile, this becomes a huge problem, because we have to remove the white background of images, which were useable in AD 1.6 without any problems. There is definitely something wrong with the color translation between RGB and CMYK since version 1.7
  19. White RGB bitmaps appear yellowish, when they are imported into a CMYK document. Scenario: Affinity Designer 1.7.1 on macOS 10.14 Document is CMYK/8 with color profile Euroscale Coated V2 Bitmap is a RGB JPG with profile Adobe RGB How to reproduce: Drag and drop barcode.jpg into the test doc. See files attached. The JPG is pure white when opening it in the Apple Preview app or Affinity Photo. -- Harald test.afdesign
  20. Scenario: Affinity Designer 1.6.1 This bug is also present in the latest Beta. Tested under macOS Mojave and macOS Yosemite Symptoms: Text with the "Univers Ultracondensed" font renders underlined words as striked through. The same font renders perfectly under Illustrator CS6, Printworks 2 and other DTP software. A sample archive is attached. Thank you very much, Harald Univers underline problem.zip
  21. This seems to be partially solved under Affinty Designer 1.6: The skin tones are nearly normal, but the white background has a light yellow tone. This also happens when importing images not generated by the screenshot tool. -- Harald
  22. Sorry - I also have to drawback my solution. After restarting, the problem reappeared. Switching forward an back between the graphics engines, cannot reproduce the method which worked before .... So this is a cross-platform issue, wich is still present in the latest version of Affinity Designer. -- Harald
  23. I had the same issue after upgrading to Affinity Designer 1.6 and macOS High Sierra: White backgrounds of imported bitmaps had a yellow touch. The solution: Switch the graphics engine from OpenGL to Metal ! -- Harald
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.