Jump to content
squeezer

Photo Beta New Version .231 'Develop' does not work Properly

Recommended Posts

1 hour ago, squeezer said:

Mark,

 how many of us amateur photographers think of what we do as 'production'?

Dave

How would he or anyone know that? I think it would require some poling to even estimate that.

Quote

certainly had no inkling what what was meant, nor what what was implied by the the term beta

So why would anyone have knowledge of what you do or do not know or understand? Why should they? This is common practice for Beta testing, for the company to post disclaimers, warning, letting those who choose to download, install, and participate in Beta testing. I don't think it's up to Serif, Adobe, Corel, or any others to ensure you're level of understanding. If you were ignorant to these things, why in the world would you proceed? It's possible a Beta Release could totally screw up your entire system. I just completed a Private, by Invitation ONLY, Beta Testing for Corel's newly released version of VideoStudio. The last beta release even affected earlier stable versions. We (all beta testers), didn't like it, but we understand it could happen. It's brought to the attention of developers and hopefully corrected. I suggest you educate yourself a little more before you go willy-nilly downloading apps. It's going to cause you some serious headaches.

Quote

so why was this develop person issue not prioritised?

What??? Really?? I know @Mark Ingram probably does not need anyone backing him up, but I'm going to. Is it really for you to determine, or think that the way this was handled not correct? I was pleasantly surprised when I checked the forum this morning to see that only 4 mins earlier he had posted this next beta version, fixing two things. Yesterday was when the problem with the Tone Mapping was discovered and was a major, major problem since it was grabbing and not releasing memory. Maybe that is what caused him to make an immediate fix available.

The Develop issue didn't cause systems to freeze, and crash, and really hasn't been an issue very long at all. If fact I didn't experience it until the 240 Beta.  I might not have experienced if I was going through my normal workflow, passing developed RAW images from Lightroom.


Affinity Photo 1.6.5.123, Beta 1.7.0.243; Win10 Home 1803: Intel i7-4770, 3.40GHz, 16GB Ram, Nvidia GTX 645 

Share this post


Link to post
Share on other sites

Ron,

Perhaps you ought to review this thread, my comment was in reaction to someone else talking about how I should of known about what beta is and what is meant by 'production'. People brought up in the software industry or are young enough to have been taught software jargon at school would immediately have understood. The Seriff assumption is that everyone has these advantages. To non software tech people, or people from different environments or educations the jargon is not obvious. Perhaps a more generic phrase my have helped?  'for community testing and comment, may have bugs, do not use for important work' 

Either way I understand now. I don't think the situation was handled incorrectly, I have had to learn, presumably there are a lot of others like me out there. There was miss communication based upon the use of jargon which I did not interpret the way it was intended, I had no reason to question what was going off, I skimmed over the disclaimer and it rang no alarm bells to me. I wiped out 1.6 because I thought I had to so I had no workable Affinity Photo. My system did not crash, look at my first posts, 'Develop is not working properly'. the flag of a problem, I got a work around which I found irritating as 1.6 did not have the problem. Then everyone seemed to start scoring points. I went back to 1.6. Another beta release came out with a long list of fixes, but not addressing what to me was a fundamental issue, frustration. I have now found that yet another beta has been released today fixing my bugbear, excellent! I shall revert to 1.7 but with eyes wide open. 

 

Share this post


Link to post
Share on other sites
1 hour ago, squeezer said:

Perhaps a more generic phrase my have helped?  'for community testing and comment, may have bugs, do not use for important work' 

What they said was pretty generic, in my opinion. Quote:  This means that you should not attempt to use it for commercial purposes or for any other activity that may be adversely affected by the application failing, including the total loss of any documents. 


-- Walt

Windows 10 Home, version 1809, 16GB memory, Intel Core i7-6700K @ 4.00Gz
Affinity Photo 1.6.5.123 and 1.7.0.258 Beta
Affinity Designer 1.6..5.123 and 1.7.0.258 Beta
Affinity Publisher 1.7.0.257 Beta

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

×