Affinity Designer 2.2.0 Update - Bug

[Guenter123]

Affinity Designer 2.2.0 Update - Bug

ICC Farbprofile lassen sich im Dokument nicht abspeichern / umwandeln,

sie springen immer auf  - Japan Color 2002 Coated - zurück.

 

[MikeTO]

Hi @Guenter123 and welcome to the forums. There may be a bug in the order of the colour profile list. Try choosing the item above or below the one you want, click OK, and then open Document Setup again to see if it picked the right now.

Also, please join this other thread where two other users have reported a similar issue.

 

[v_kyr]

Dann melde dies in der "Bug Reporting" Rubrik ...

• https://forum.affinity.serif.com/index.php?/forum/71-bug-reporting/

[Dan C]

Hallo @Guenter123,

Willkommen in den Affinity-Foren und es tut uns leid, dass Sie Probleme haben!

Ich kann dieses Verhalten derzeit nicht reproduzieren. Können Sie bitte eine Bildschirmaufzeichnung bereitstellen, die die genauen Schritte zeigt, die Sie für mich unternehmen?

Wenn Sie sich nicht sicher sind, wie Sie eine Bildschirmaufnahme erstellen, lesen Sie bitte unsere unten verlinkten FAQ -

Vielen Dank im Voraus!

[R C-R]

FWIW I can't duplicate that either in the Mac 2.2.0 version of AD.

[Guenter123]

On 9/20/2023 at 12:30 AM, Guenter123 said:

Dear Sir or Madam,

 

In the meantime, I was able to clarify the problem.

 

The new update creates it when opening previous designer and publisher files.

 

The CYMK color space is always opened with "Japan Color 2002" (2a) or "U.S. Web Uncoated v2" (2b), although both files were saved with "ISO Coated v2 300% (ECI)".

 

Striking is the strange - arbitrary order of the list when opening. The old design files cannot be converted and therefore no longer export as a pdf.

 

With Photo, there are no problems, neither opening nor saving and exporting.

 

With this upgrade, I can no longer access my old designer files.

 

Can you solve this problem?

 

I have been working professionally with Affinity (MacBook and Mac M1) for years without any problems.

 

Best regards

 

Günter Ludwig

 

 

 

[Dan C]

Thanks for the further information provided, please see my update regarding this issue here - 

We've replicated the issue with the app not retaining the change in Settings > Colour when restarting, though we're having trouble replicating the Document Setup > Colour issue.

I can see your profiles are being displayed in the incorrect list order, as shown by other users in the above thread.

Are you able to replicate this issue when creating a new document in Designer please?

[Guenter123]

Dear Sir or Madam,
here are the attempts including screenshots.

New documents open as desired and can also be converted accordingly in the RGB/CYMK color space or in the desired color profile. (1 - 6)

However, the general settings in the CYMK color space cannot be stored as "ISO Coated v2 300% (ECI)“ but jump back after the reopening on "U.S. Web Coated ...". (7A)The document profiles are preserved (7b), the order of the settings are alphabetically correct.

However, until yesterday, the same errors occurred again when opening or importing old files (V2.1). (8 - 9).
These files could not be saved as desired, the color profile "Japan Color ..." displayed when opened could not be changed. (10)

Since today, the document profiles seem to work fine (they can be saved and remain set), for whatever reason?
However, the general settings in the CYMK color space can still not be saved as "ISO Coated v2 300% (ECI),“ but show after the reopening "U.S. Web Coated ...".

Can you correct the whole thing so that the system reacts reliably.
Professional work is not possible in this way.

Best regards
Günter Ludwig

 

 

 

[Dan C]

Thanks for your screenshots provided @Guenter123,

I can confirm that our team have identified 2 separate issues here, which are covered by the below FAQs:

We're working to resolve these issues ASAP, in the meantime we recommend rolling back to update 2.1.1 to workaround these issues.

If you need assistance in rolling back to a previous version, please let me know

[Guenter123]

22 hours ago, Dan C said:

Thanks for your screenshots provided @Guenter123,

I can confirm that our team have identified 2 separate issues here, which are covered by the below FAQs:

We're working to resolve these issues ASAP, in the meantime we recommend rolling back to update 2.1.1 to workaround these issues.

If you need assistance in rolling back to a previous version, please let me know

How can i roll back to update 2.1.1 and can i open files / docoments from 2.2? Thanks

[walt.farrell]

On 9/28/2023 at 11:13 AM, Guenter123 said:

How can i roll back to update 2.1.1

Uninstall your current release, download the 2.1.1 release from https://affinity.store/update/macos/photo/2 (substitute designer or publisher if appropriate), and install it.

On 9/28/2023 at 11:13 AM, Guenter123 said:

and can i open files / docoments from 2.2?

No.

Edited October 7, 2023 by walt.farrell
Fix the url.

[ajarborn]

Get a 404 error - page no longer exists ....

 

[walt.farrell]

3 minutes ago, ajarborn said:

Get a 404 error - page no longer exists ....

 

Sorry, I had a typo in the URL. Please try again with the updated post (above).

[Affinity Info Bot]

The issue "Unable to correctly set colour profile in Doc Setup> Colour" (REF: AF-360) has been fixed by the developers in internal build "2.2.1.2052".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.

[Affinity Info Bot]

The issue "[macOS] Changing the profile under Settings > Colour is not retained if an externally installed profile is selected" (REF: AF-369) has been fixed by the developers in internal build "2.2.1.2052".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.