henryb
-
Posts
108 -
Joined
-
Last visited
Posts posted by henryb
-
-
On 1/14/2020 at 5:54 PM, MacGB said:
After installing the 1.8.0.163 beta I can report following:
...
Extension "Edit in Affinity Photo" works for RAW but not for jpeg to save changes back to Apple Photo's....
so this problem STILL has not been fixed??? Are we serious now??..
-
31 minutes ago, Old Bruce said:
NO.
Do not trash the retail version, the beta won't run without it.
Thank you! (That was the answer I was looking for!)
So the idea is to install the beta but launch the regular ap?
-
12 minutes ago, SteveB523 said:
You know, reading is a great skill to have!
this really wasn't necessary
-
1 minute ago, Cecil said:
To try is your choice; however, as beta it doesn’t replace your AP. If it works for you, great.
what does "it doesn't replace your ap" mean? If I download it, it's a full AP app, isn't it? So I can then trash my current AP (since the beta is a full-app), and work on the beta henceforth (hence, replacing my current ap..). No?
-
On 1/10/2020 at 2:23 AM, markw said:
If you have not already found it the latest Photo beta can be found here: https://forum.affinity.serif.com/index.php?/topic/104964-affinity-photo-customer-beta-180163/
so does this beta work fine (and will save edits back into Photos)? If yes, then should we download this and REPLACE our current AP app? Or should we wait for the official release (whenever that will be)?
-
57 minutes ago, Herbjul said:
It works :-)
can you be a bit more specific?
-
3 hours ago, Patrick Connor said:
The potential fix for this is included in this beta build, However, we are still investigating some unexpected results in that it does not yet work 100% of the time and so it is not listed as "fixed"
Do we have any eta for the official 1.8 release that will finally fix the (horrendous) bug AP has had since May 2018 that won't let AP save edits directly back to Photos? (Maybe an eta approximation based on how long it has taken official AP versions to be released after the first beta was released?)
-
On 6/30/2019 at 2:42 AM, henryb said:
You used to be able to right-click on a photo in Mac OS's Photos app, select "edit with... Affinity Photo", make your edits in AP, press Save and FINITO, the edited/fixed file was directly saved into its original location in Mac OS Photos. Seamlessly, simply and FAST. Now this is no longer possible!!
I know this is a bug you have been aware of for over a month, but as we still have no feedback, I thought that writing it in the appropriate section would help AP's developers speed this CRUCIAL fix up ASAP (by reminding them)!
Dear Developers please hurry! One of the main reasons we love Affinity is because of its ability to work flawlessly & seamlessly with Mac OS.
Ok... In June, OF THE PREVIOUS DECADE (!!), Affinity knew about this a month before and they were not able to fix this bug of theirs which, essentially, ZEROES THEIR APP'S MAIN ADVANTAGE/SELLING POINT WHICH WAS COMPATIBILITY + FLAWLESS COLLABORATION WITH MAC OS'S PHOTOS APP. So this has not been able to be fixed since MAY 2019??? Seriously??
I wish I was happy about my original post being the most viewed, and most commented on, post on the ENTIRE AFFINITY FORUM.. Yeeehhhhyyy popularity!!
I mean, if I owned Affinity I wouldn't let anyone in my company sleep until they had fixed this with SOO many people in trouble with it!!. I am now beginning to think that Affinity either just doesn't care about the most "popular" bug topic they have, or they actually DON'T WANT TO FIX IT (maybe are in some kind of contretemps with Apple and they are using this issue as a "reason" to walk out on the collaboration through the back door...). Or maybe it's the other way 'round and Apple is the culprit. But one thing is for CERTAIN: Your customers are SIMPLY not getting what they've purchased. We, the customers DON'T CARE whose fault it is. We just want what we bought to work as it promised, and as it initially did.
I am still using Mojave - just as I was during the last May of the previous decade - so it's the same os... So why don't we just revert to whatever version of AP we were using before your software started skrewing everything up, and we can work on that now, and if you decide to release a fix to your bugs you can then let us know to download it. Hopefully by the year 2050.
Excuse the sarcasm, but I prefer it to rudeness. This is just NOT FUNNY ANYMORE.
-
12 hours ago, Andy Duffy said:
...release a hot fix just to fix this issue. ... If you've fixed it, RELEASE IT! You have 6 pages of people asking for help with this bug going back 6 months you must have a schedule for production release of 1.8, can you share it as I think your loyal customers and AP evangelists deserve better?
E.X.A.C.T.L.Y.!!! It's CRAZY that we've been unable to work properly on AP since JUNE 2019 (!!!!) and all we are getting is hints on a beta release, that "should" (not "WILL"...) fix AP's bug, at an unknown future date, and we will get new features with it... Like, seriously?? Release any new features you want, when you can, in order to remain competitive in the market. That's great. But we have been SERIOUSLY put back by this bug of yours for HALF A YEAR (in 10 days it will be a new DECADE for crying out loud) and still no fix!! If you have fixed it release it NOW. Please. Please. Please. Give us the new features LATER - that's not what's URGENT....
-
10 hours ago, MacGB said:
@ Brantc
It’s definitely not Apples fault. I am running at least 4 other apps with extensions that didn’t and don’t have this problem.
That makes no sense at all. If you are running at least 4 other apps ON APPLE'S MAC OS, and they DON'T have this problem, then - logically speaking - it's NOT Apple's fault, but AFFINITY'S (since, according to your findings, it's ONLY AFFINITY THAT HAS THE PROBLEM...). If it was Apple's fault, then you wouldn't be able to run the other apps either...
-
1 minute ago, Dizzypole said:
In Mojave, have you tried removing and re-adding the AP extension? that worked for me.
What?
-
On 11/19/2019 at 5:18 PM, brantC said:
I am also having this same problem. It's a real bummer because I just bought AP last month and then last week I downloaded the Catalina OS update. If I would have known about this problem I either wouldn't have bought AP or I wouldn't have downloaded Catalina. I imagine this is more Apple's fault than AP but still, this functionality is the main selling point of their product (at least for me).
Same problem in Mojave - so Catalina is not the problem - AP is. As for not having bought AP because of this - I guess that depends on WHEN you bought it. Meaning, if you have bought AP over the last 5 months that this bug has COMPLETELY DESTROYED OUR WORKFLOW, then yes, I would be thinking the same right now so you are right to regretting you bought this app that was meant to work hand-in-hand with Mac OS & its base photos' app, Photos (except that it DOESN'T, anymore). But, if you have had it for longer, you would have had time to have appreciated the app (BECAUSE IT IS AN AMAZING APP!!) and it's flawless collaboration with Mac * Photos (as was the case until June 2019). I guess that's the downside of PURCHASING a software (which is the MAIN reason many of us chose AP over PS) as opposed to renting it... If people were renting AP and AP failed to deliver on their promises then people would rightfully unsubscribe and that would push a "knife" on AP's developers' "throats" to fix it because the company will go bust because of unsubscriptions. But right now all they have to deal with is "nagging" customers who are no longer getting what they were promised. The only "knife" right now is bad publicity that will steer potential newcomers away from AP... And that is a great pity for ALL of us. I repeat, AP is JUST AMAZING. But they have just got to get it together and fix this NOW.
-
1 hour ago, Jeremy Bohn said:
Dude, have you even read this whole thread? Look a couple of posts higher up and you're given more than a "vague response."
“Dude”, I’m the one who started this thread… And yes, I have been following it throughout. And, again, all we have been getting so far are - exactly – “vague responses”. A vague response is “we are working on it“. This response, essentially, has been recycled over the last 5 months (!!) since June.
A clear response, on the other hand, would have been, for example, “Our developers have been working on it feverishly since June, and we hereby inform you that the bug in our software to be fixed by ?/?/19”. Or, another example of a clear response would be “our developers have been working on our bug since June, but regrettably, they are still unable to fix it because the problem lies in the issues x y z which have been the reason for the delay“.
A vague ”We are working on it“ says absolutely nothing with regards to the ETA of the functional release (especially when we are approaching December - and in six weeks we will be in a different decade of when the problem first occurred and has yet to be fixed). And all us customers of serif who have purchased the affinity photo app so that we can directly edit from our Mac photos app – because that’s the reason most of us purchased it since it is meant to work flawlessly with the Mac photos app - have been on hold since June. Maybe you are a casual user of this app, or maybe your photos are not stored in your Mac’s photos app, but if you did you would understand that your entire workflow has been put on hold for five months! So, no, that’s not good enough. And, no, experimenting with “workarounds“ would just not be acceptable for such an insanely long time, and you would expect something more than just “we are working on it“ by now.- HenkeJ and Barry Gibbs
-
1
-
1
-
On 11/11/2019 at 6:49 PM, Hugo Habicht said:
Dear all,
My work around for raw files is as follows:
- Export the raw files from Photos as unmodified originals to a folder on desktop
- Edit them in AP, export as jpeg in another folder on the desktop
- Back in Photos, choose edit with "External Editors for Photos" (from the App Store)
- Choose "Replace with File" (bottom right in window), choose the appropriate jpeg and click "Save changes"
Works quite well an fast if you first edit a bunch of pictures in AP and then "import" it back to Photos one after the other. I hope, this procedure will be of use for the one or the other
Thanks for the suggestion, but none of us want to be trying "workarounds", nor any other alchemies. We shouldn't have to. Affinity Photo should JUST WORK FLAWLESSLY WITH PHOTOS. That's why we bought it.
The bug in Affinity Photo appeared in June 2019, and we are now approaching the next decade and no feedback from Serif / Afiinity other than a vague "we're working on it" (which could mean anything really).... Dear Serif please tell us what AP version we can revert to so that we can work as we did, and how we can do this. It's NOT "Catalina" that's at fault - I'm using Mojave and since June it hasn't been working there either - it's Affinity Photo's bug. So tell us how to install an older version of AP that WILL work until your developers decide to fix your bug (in their own good time - as it seems).
Please excuse my last comment, but it's been nearly HALF A YEAR that we've all been waiting for you to fix your own bug and deliver a working AP version, and so far ZILCH. (And we don't want to be trying "workarounds", nor any other alchemies. We shouldn't have to.)
-
OK so it seems like we are not getting anywhere with this.. Your bug appeared in June 2019, and we are now approaching the next decade and no feedback from you other than a vague "we're working on it" (which could mean anything really).... Dear Serif please tell us what AP version we can revert to so that we can work as we did, and how we can do this. It's NOT "Catalina" that's at fault - I'm using Mojave and since June it hasn;t been working there either - it's Affinity Photo's bug. So tell us how to install an older version of AP that WILL work until your developers decide to fix your bug (in their own good time - as it seems).
Please excuse my last comment, but it's been nearly HALF A YEAR that we've all been waiting for you to fix your own bug and deliver a working AP version, and so far ZILCH. (And we don't want to be trying "workarounds", nor any other alchemies. We shouldn't have to.)
Thank you.
-
6 hours ago, MEB said:
Hi all,
The macOS Catalina update has brought up a few more issues than we initially expected. Some, as the Apple Photos integration/extension(s), are being a bit more difficult to sort out than others but we are actively working to fix them. Please bear with us. I will update this thread as soon as i have some news. Thanks for your support and understanding.I'm still on Mojave where the problem still exists - so the Catalina problem is not the only thing that need addressing.
-
On 1/20/2017 at 8:55 PM, m-b said:
Here are two free online converter which I use. Very good and fast for simple graphics.
thanks for these links! Always wondered whether that was possible..
I went to the first one, however, and it asks you what format I want to export my vector (?) file to: SVG, EPS, PS, PDF or DXF.
What is the difference between all these formats? What do I choose? What's the best/most common?
Will they all work with Affinity apps?
Is there a format that I can send to someone using adobe software, and then back to me to work further on in Affinity? (As long as Adobe rents software instead of just selling it I'm NEVER going there - I don't like monthly/yearly payments, especially when what you're paying for is never going to be yours). But would like to be working on formats that work on both Affinity and Adobe.
Also, does the quality of the original image matter (not "too" bad obv..)?
-
17 hours ago, jeffnles1 said:
"no eta" on a fix isn't really much of an answer either. It could mean it's right around the corner or there is no intention from the Affinity Team to fix it ever. For those of us who have invested in this software and the time to learn it, I think we deserve a better and more definitive answer from Affinity.
Thanks,
Jeff
EXACTLY!
-
18 minutes ago, MEB said:
Hi henryb,
The Edit With command issue is known for some time yes, the macOS Catalina issue (point 2) is a new and has (apparently) limited even more the workflow between the two apps (macOS Catalina and Apple Photos have both introduced quite a few changes/new features - as said above we are still investigating what's going on and hope to have both issues fixed as soon as possible. We are sorry for all the trouble this is causing you all unfortunately i can't give you any eta regarding a possible fix until both issues are correctly diagnosed/causes identified. Thanks for understanding.In Mojave, it's not JUST the right-click edit with "path" that doesn't save back into Photos - it's ALSO the alternate method you suggested (via the ellipsis button) that doesn't work most times. So, we should probably expect a fix in the next decade?
-
On 10/16/2019 at 1:10 PM, MEB said:
Hi all,
There's two ways to send the files directly from Apple Photos to Affinity Photo (without using third party extensions):1. Using the command Image > Edit With > Affinity Photo (or right-clicking the image or thumbnail - depending on your view mode - and selecting Edit With > Affinity Photo). This one doesn't work neither in Mojave nor Catalina and it's already logged to be looked at.
2. Using the Edit in Affinity Photo extension (clicking the Edit button on the top right of the interface - when seeing a single image, not the thumbnails view -, then the ellipsis button and finally selecting Edit in Affinity Photo. This method works in Mojave (for most users) but is now apparently broken in Catalina too. We are investigating this and will update this thread as soon as we have some news.
As all that you mention here has been known since June 2019, but nothing has been fixed till today, can you tell us whether this will be fixed in the next update? And, if yes, when this update be available?
)
-
On 10/11/2019 at 7:10 PM, Dizzypole said:
Right clicking on the thumbnail and choosing edit with Affinity Photo has never worked for me, have always maximised the photo, chosen edit then chosen Edit in Affinity Photo. Up until moving to Catalina it has worked. Now I find that if I have a photo that is 720x490px I can increase the size to 1469x1000 it will save, but resizing it to 2204x1500 will not, it gives the error 'unable to edit with "Edit in Affinity Photo" an unexpected error occurred." I have removed the external editors via the manage option and re-added, but still the error.
It used to work for me (and most people) up until June. Following an update, it just stopped. We've all been waiting for Serif / Affinity (or, at least, their developers) to jump in here and make an announcement about what they are doing about it, but, as you can clearly see in this thread that's monitored by them - ZILCH! We would all have very much appreciated an official reply from them (ANY REPLY - EVEN if it's that they CANNOT FIX THIS BUG, or that THEY ARE ACTIVELY WORKING ON IT). But nothing... All these months.
Very very very disappointed with Affinity. Although, I LOVE their software and think that they can be #1 in a few years (if they keep innovating), this incident that has lasted for so many months, ALONE, has made me feel very insecure as to how they would deal with future problems, when professionals will be DEPENDENT on Affinity & its support/problem-solving...
-
8 hours ago, plattis said:
Just wanted to chime in here. Same problem - not possible to save edits from Affinity Photo back to Photos App. Breaks my workflow! Please update us on when we can expect a fix, or if this is "Appple's fault.
It can't be "Apple's fault" lol - it's Affinity Photo that was made for (and sold to us as) working flawlessly & hand-in-hand with Mac OS and its BASE photos' app/system: Photos. Not the other way 'round... (If Mac OS was marketed/sold to us as working flawlessly with Affinity - and it stopped doing so after we bought it - then it would be Apple's fault. But the situation is in reverse).
So as long as this is not fixed, Affinity is simply not giving us what they promised / keeping their end of the purchase deal. We have all been waiting for Serif to fix their Affinity Photos's bug since June 2019 (!!!). So far, radio-silence...
-
9 hours ago, HenkeJ said:
An official update on this would be nice.
It would have been "nice" back in JUNE when this started happening... Now it's just "MONTHS LATE". I don't know what Serif / Affinity is doing and not positioning themselves with this bug of theirs. This forum is meant to be their developers' "hangout" (not hideout lol). But seriously, Affinity?... We LOVE your products, but is this silence going to be the way to deal with problems when they arise (problems occur with Adobe too, no one is perfect)?? No one is expecting ZERO problems - it's about how fast / professionally you fix them that matters!
-
1 hour ago, MacGB said:
The "develop" extension works fine with jpeg, but not RAW,
The "edit in Affinity Photo" is not able to save back to Apple photo's, not for RAW and not for jpeg.
to say that something "works", means it works for every format. If it doesn't work for everything, then it simply "does NOT work". And, since JUNE, Serif / Affinity has not even bothered telling it's customers when this SERIOUS bug in their product will be fixed... (It's "serious" because THOUSANDS of customers, such as myself, have bought Affinity products EXACTLY BECAUSE they advertised that they work FLAWLESSLY with Mac OS and its BASE photos' app/system: Photos. So as long as this is not fixed, Affinity is simply not giving us what they promised / keeping their end of the purchase deal.)
***And, don't get me wrong - I LOVE the Affinity software so far. It's just that this is not a "little glitch" that "should be fixed soon". It is a MAJOR flaw. So, for me, it's CRAZY that this hasn't been fixed after MONTHS of failure!!
So the idea is to install the beta but launch the regular ap? 
I went to the first one, however, and it asks you what format I want to export my vector (?) file to: SVG, EPS, PS, PDF or DXF.
Affinity Photo Customer Beta (1.8.0.163)
in [ARCHIVE] Photo beta on macOS threads
Posted
still no official version release that will save edits directly back into Mac's Photos app?