2.5.5 (2613) is available to Beta test

[Patrick Connor]

We have released a beta build to try and address a number of issues found in 2.5.3/4

We would like to release 2.5.5 to customers very soon. If you are suffering from any of the 22 issues mentioned in this 2.5.5.2613 beta post then please (sign up for and) install the latest beta build 

 

[Gerarbara]

I am using the Beta version as my go-to, as the "stable" version regularly freezes my Windows 11 PC. So far, the Beta version has been very stable.

[lowerider]

The current beta has been stable for the type of work I do.

The platform I use:

• PROCESSOR: AMD Ryzen 7 4700U with Radeon Graphics 2.00 GHz (HP laptop)
• INSTALLED RAM: 16.0 GB (15.4 GB usable)
• SYSTEM TYPE: 64-bit operating system, x64-based processor
• OS: Windows 10 Home Version 22H2 (build 19045.4780)

I've been using the current beta for my regular projects.

[MikeTO]

FWIW I've been using the beta as my production environment with no new issues either. It works for me.

[walt.farrell]

Works for me, too, except for the iPad issue I posted about which makes it pretty much unusable.

[Petar Petrenko]

AFAIK, betas are not recommended for production use because there might be some structure changes in the apps that will not allow you to open the documents in newer versions.

[Ron P.]

1 hour ago, Petar Petrenko said:

AFAIK, betas are not recommended for production use because there might be some structure changes in the apps that will not allow you to open the documents in newer versions.

That's correct. However I'm positive Walt and Mike are fully aware of the risk, and choose to assume that risk. Anyone is free to use the Beta versions for production. It's just a recommendation by Serif not to. When something like files getting corrupt, don't be surprised, and don't fault Serif or the apps.

Save often and backup keeps major catastrophic events from occurring.

[Petar Petrenko]

10 minutes ago, Ron P. said:

It's just a recommendation by Serif not to.

Just what I said.

10 minutes ago, Ron P. said:

Anyone is free to use the Beta versions for production.

I didn't say it is forbidden.

[carl123]

Controversial?

..maybe but if we don't use the beta for production work, how can we fully test all the functions we each use?

If we catch the big bugs in beta we would have less people complaining about a new release having a bug that affects them now that didn't before

[Petar Petrenko]

3 minutes ago, carl123 said:

..maybe but if we don't use the beta for production work, how can we fully test all the functions we each use?

You should use it with documents considered for testing (copied documents, dummy text...), not for final use that are important for you.

[Gerarbara]

My understanding is that any file saving from the Beta version can't be opened in the "stable" version, which is understandable. Perhaps Serif can give a definitive answer?

[GarryP]

1 hour ago, Gerarbara said:

My understanding is that any file saving from the Beta version can't be opened in the "stable" version, which is understandable. Perhaps Serif can give a definitive answer?

This isn’t an official answer but I would recommend assuming that all files saved with the current (at the time of testing) beta will be ‘lost forever’ once the beta testing of that version has completed, unless you are lucky.

Sometimes the files saved with the current (at the time of testing) beta simply won’t work with any subsequent beta/commercial version, and sometimes they will, but there’s often no way of knowing which it will be until you try.

If a file is important, and/or can’t be easily reproduced, don’t even open it with a beta, just in case; save a copy with the commercial release and open the copy in the beta.

Always beta test with copies of ‘real’ files rather than with the ‘real’ files.

[walt.farrell]

1 hour ago, Gerarbara said:

My understanding is that any file saving from the Beta version can't be opened in the "stable" version, which is understandable. Perhaps Serif can give a definitive answer?

There is no definitive answer on that, but the general answer is that file compatibility is determined by the release number. So, consider that right now we're on beta 2.5.5, and consider that as a generic number x.y.z. Then you should assume that:

• If x increases, software with a smaller value of x will not be able to open a file created by a higher x. Thus none of the 1.y.z releases can open 2.y.z files. (V1 cannot open V2 files.)
• If y increases, software with a smaller value of y will not be able to open a file created by a higher y. Thus, 2.0.z cannot open files created by 2.1.z, or 2.2.z, etc. 
  (This is not always true, and sometimes depends on exactly what functions in the new release were used. That's why the answer cannot be definitive. But it is usually true.)
• The value of z does not matter. 2.5.4 or 2.5.3 should be able to open files saved by 2.5.5, for example.

[garrettm30]

6 hours ago, Petar Petrenko said:

AFAIK, betas are not recommended for production use because there might be some structure changes in the apps that will not allow you to open the documents in newer versions.

That is generally true, but not always. For example, the first beta to 2.0.0 came with this official recommendation (emphasis in original, source😞

Quote

This beta is an update to the 2.0.0 version recently released to all customers and will form the basis of our first patch for 2.0.0. We recommend that you use this beta in preference to the release version if you are affected by any of the issues listed below.

I think I have seen that a few times (I’m not sure of it), but it would mostly be true only of the sub-point updates. To best be sure, watch the official recommendation for the specific beta in question.

 

-------------

 

4 hours ago, Gerarbara said:

My understanding is that any file saving from the Beta version can't be opened in the "stable" version, which is understandable. Perhaps Serif can give a definitive answer?

Although I must preface what I am about to say that it may not be advised, I do want to clarify that it is not strictly true that documents saved in betas cannot be opened with previous stable versions. In my experience, there is usually (if you want to chance it) compatibility between the sub-point updates. For example, the current release Publisher 2.5.3 can open a document saved by beta 2.5.5. [Side note: I had to double-check on those numbers since it looks like 2.5.4 is missing.] I would say that the definitive answer is the big warning that comes up when you try to open a document from a release version in a beta:

Quote

Editing it in the Beta could add new features to the file that make it unusable by the Release version.

 

-------------

 

4 hours ago, carl123 said:

..maybe but if we don't use the beta for production work, how can we fully test all the functions we each use?

Ah, there’s the rub. I often open up a beta and try a few things for a few minutes, but I keep my main work on the release versions. And, yes, it does result in bugs that I could have caught in beta that instead I catch when I start doing real work. For example, a real variable fonts showstopper issue (for me) that I only discovered as soon as variable fonts hit release, leading to the comment:

On 5/23/2024 at 5:33 PM, MikeTO said:

Good catch, I wish we'd caught it during the beta.

It’s a catch-22 situation, and I don’t have an answer for it. If I am about to work on a document that does not matter too much, then often I will try it in a beta just to have an opportunity to catch something, but how often does that really happen?

[AiDon]

No issues with this latest beta … both PC’s in the signature below.

PS: With the current surge in apps using AI, or machine learning models which it really is, it is good to see that the Affinity products don’t require you to update your hardware every 6 months or so. 😀

[Suburbian]

I've used Luminar Neo and Affinity for quite some time, Affinity Photo much longer. It depends on taste and preference for me when it comes to posting or printing, cameras and lenses, filters and flash, etc... Affinity Photo has always been my go to final look, no matter which RAW developer I choose to open a file and develop. I've been using the Beta versions for a year now. My licensed version sits idle and not only that, I've weaned myself off the addiction a gimmicky Neo creates in my brain, manipulating it to see unnaturally? Also Neo auto crops High Res m4/3 files Affinity Photo does not, Neo struggles with my 5dsr files period, Affinity Photos a little bit depending how involved or layer heavy I get mostly but it doesn't crash. Long story short, I cancelled my subscription with Neo this day because I can faithfully rely on and trust Affinity Photo for not secretly juicing my images, my brain, and for paying close attention to the little things by allowing me more controllable choices . I shoot high res landscapes in natural light mainly, darn right I examine images closely (aka pixel peep). I've never taken the perfect picture yet, but "when" I do I'll be looking at it with Affinity Photo guaranteed...