Jump to content
You must now use your email address to sign in [click for more info] ×

JasperD

Members
  • Posts

    142
  • Joined

  • Last visited

Everything posted by JasperD

  1. Actually, I reacted because I downloaded what I thought the new beta from the 1.3.5.15 thread, verified, installed and backed it up. It was quite some time before the newer ´16´ thread became visible; hence the confusion.
  2. Adding to the previous instead of editing, as (I think) I found some improvement. A few distributed applications are running permanently on my Mac, taking up to 98% of processor. I don´t usually have to shut them down - they take care of themselves, including stop processing if needed. However, when running Bridge and Photoshop CS6 plus Photo Suite 9 and possibly NIK all at the same time, I do, it really makes a difference. These distributed applications have seen a major update last Wednesday. So, unlike before, I stopped them to see impact on AP: opening a RAW X-Pro1 image now is back to 22 seconds. Still an awful lot, but at least as usual. Better yet, with Apple´s RAW engine, it´s down to 10 seconds or less, depending on the picture; I have actually seen 6 seconds!!! Now I wish even more for that issue to be solved: there was no success with rendering alas, still the totally meaningless and useless canvas. Just a note on the AppStore version: that one now shows 34 seconds (not 22 anymore, nor 44) with the distributed stuff running at the same time, so I´ll definitely have to stop that from now on, alas. I can adapt to that though.
  3. I don´t know the answer to your question Joachim; I would like to see confirmation from a developer that this is the way as intended though. With the AppStore release, I use Adobe´s recommended ProPhoto RGB for all though - mainly because I´m sticking to PS at the moment - maybe try that? I don´t have any success with Apple´s RAW engine though... Probably needless to say, but just in case: everything from PS CS6, via LR 4.4, Aperture 3.6, not to mention a few other quite heavy ones, all work perfectly OK (and a lot faster) on my older iMac. Really everything, as far as I am aware of it. Just not AP.
  4. This is getting worse, must be a joke?! :( :wacko: :angry: Not by a small margin, actually 44 seconds (!!!) - instead of the usual 22 since initial 1.3.4 AppStore release. Consistently, I opened several, canceled everything, reopened, canceled, closed AP Beta, relaunched, always the same on my stopwatch. Everything using Serif Labs RAW engine. Doing the same but with Apple´s RAW engine active still takes 22 seconds ´only´, but as I don´t see anything after that, just a partial black or transparent canvas, that´s not really helpful either; see https://forum.affinity.serif.com/index.php?/topic/14808-no-image-shows-up-after-opening-raw-file/?p=66275. Just installed Beta 1.3.5.10, after trashing the previous one completely, nothing done at all before open the files. I picked Fuji X-Pro1 files again, so that the comparison with old is actually valid.
  5. Bump... Two newer betas meanwhile: any progress on this, sometime soon?
  6. Now that´s fast! Yesterday´s ink was not even dry, so to speak. :)
  7. The A7R II and A7S II are not on the list of supported cameras (yet) - just like the A68... Too recent I suppose, no time to cope with them so far. The A77 II is, but at a logically awkward position. I guess it will be done soon, but do not know when.
  8. :) Not only the beta, the AppStore version was showing it as well. There must be something for each one, it irritated me as the cats are too slim to show the differences well, like the gears do. I agree it´s just cosmetic though. ;) Makes you wonder, what happened? I´m not aware of anything updating last night, yesterday they still were there. Is there a timer baked in making them vary?
  9. I´m not really in for a debate on RAW image editing / performance / features / quality etc... My personal take is that it´s no match to my usual tools, yet. I do hope it will become it though, up to really and totally replacing Adobe´s Photoshop CS6, ultimately. Right now, it´s not there alas. My personal deal-breakers are with RAW processing and the file sizes of the AFPHOTO file format. I always use ACR to start with, over 80% of my processing stops right there, does not see Photoshop at all. However, AP does not offer persistent savings with some small footprint ACR-like sidecar. It is already on the roadmap though, but I don´t know what approach will be taken for it. If it comes close to Adobe´s solution, the deal-breaker with the file sizes would probably vanish with it as well. For now, I have processed a few hundred RAWs with AP and doing so gave me a good idea of what I would need for diskspace to have the same comfort that I am enjoying now: 2TB external for all images (RAW and processed) would be 16TB at least, my 3TB external Time Machine backup should then be about 20TB... It is about 8.5 times more for me, the 550GB now used on my dedicated photo drive would extrapolate close to 4.6TB. That´s the deal-breaker I am talking about. Processing is a bit slowish compared to my PS, not everything is working as it should (or so I think), but will be dealt with given some time, I expect. OTOH, it is full of really brilliant features that I already do like a lot, so even if feeling more like a beta tester at the moment, I will probably continue to use it for that part of the workflow, when useful, but only as needed; not always as I hoped, far from it, I simply cannot afford that.
  10. It does not matter Joachim, don´t worry about it. Especially as in your case, you were nice enough to ask (although a bit lucky that I did). For all I care, you could continue to write in your language as you wish, you might be surprised at the number of responses you get, that notwithstanding, and from a lot of people. Reactivity could be a bit less though, so if you can and want more and faster answers, it´s usually better to try with English.
  11. Don´t worry, I think that you are pretty understandable, no issues.. You forgot to attach the RAWTherapy and Iridient ones, or you reached the max file size before posting. Anyway, I do not have an answer for you, don´t even mention a solution. If it´s not related to the next El Capitan, as far as AP is concerned, I think this is something by design. However, only a staff member can confirm that with certainty. Maybe someone will chime in to that effect. I´m taking advantage of this for a personal message; enjoy your break! ;)
  12. It´s no bother at all, I wish it had helped and I would be quite happy if it did! Creating an addendum now, after checking exactly what you did, opening the first after the reset (so with the Serif Labs engine) and keep it open. Then changed the RAW Engine back to Apple´s and opened a few other files. I added five new ones. Four of them all show the same, like the first screen print below; note that there is no black right side ´border´ this time. The last one is in Portrait orientation, it shows part of the picture, on top! Partial success, so to speak. :) I´d be really surprised if it shows differently your side, when you perform these actions. I expect (and think) that the change of engine does not apply on an open picture. Loading files with that engine active shows confirmation of it and frankly, I wouldn´t like it to be any different (although I shall adapt if I must).
  13. That works perfectly, I now see again what I hoped to see. However... the reset has the effect of also activating Serif Labs as the RAW Engine (checked that after it opened), it´s not Apple´s core. So I changed it of course, back to Apple (Core Image RAW), then canceled the develop stage, closed the file, opened it again (to have the last settings applied) and bingo: same disaster, partial transparent canvas with a black addition at the right side. Have a look at actual screen print of that below. I grabbed the histogram with it, as it shows accordingly. To be honest, there would have been blood on my walls now, from banging head on it, if the reset had been all it took. There have been a few updates to other stuff the last few days, some quite heavy, I imagined one of them being the culprit. So I trashed AP and AD Betas, downloaded and installed them from scratch this morning. I need to file a feature request BTW: for these Develop Assistant settings to possibly be enabled without any file open, so before loading any... ;)
  14. This is an attempt to show what I meant in another thread: the difference between setting Tone Curves to Apply (more vibrant picture) or not (rather neutral picture), everything else the same. I haven´t processed anything at all and just created screen prints for simplicity sake. I think it is meant to be that way to be honest, but I could be dead wrong of course. I am not sure that this is what you have stumbled over, it looks a bit the same? As said, this is with Serif Labs RAW Engine, as I don´t see anything using Apple´s core.
  15. Hi MEB, awfully nice from you to pick it up. I had already one in preparation for Jonas14, which is an X-Pro1 one. If you´d prefer one for the Sony A900, just let me know please. Just so you can see what I might be doing wrong my side, below is what I see with the Apple core selected, as a screen print for simplicity; notice the dark black border there, at the right side. Neither it nor the transparent canvas should be there though. The Fuji RAW is coming your way right after this.
  16. Sorry, I deleted something earlier as you already replied before I finished. Here it is again: PS: I think I know this GaryC; if it´s the same guy, someone who loves Google Translate, not always to the point though. Then it´s easy to claim Google made the mistakes. In this case, I ´m not in for that debate, so I´ll leave you to answer it, if you´d like to: No, I don´t know what issue is with your initial post quoted above; subdued, ´flatter´ and boring (some would say neutral) rendering is usually what I see when Tone Curve (right below RAW Engine) is set to not apply. Not sure that is what you show here, though. I linked to something happening with my cameras, here it is again as full address: https://forum.affinity.serif.com/index.php?/topic/14808-no-image-shows-up-after-opening-raw-file/?p=66275
  17. Are you sure you do reload them? Meaning you closed the image that you saw before (otherwise it will not open, as it already is)? If so, that could be of some help for the developers: I never see anything when opening a new picture with Apple Core set, from the two cameras stated...
  18. Ich bitte um Entschuldigung Joachim, leider bin ich Deutsch nicht völlig mächtig. Ich bin auch nicht Schweizer, aber Holländer, so das is es auch nicht. Ich spreche nur das Niederländische und das Französische, Englisch ausreichend und ein bisschen Griechisch dazu. Ich lese und verstehe Deutsch Gut genug. In short for everybody else, I´m not fluent in German, alas. Will read and understand quite OK though, but writing it is a disaster with me and that usually shows. Joachim, did you reload the image after switching to Apple? I´m asking because that´s what I have to do to activate it and so, see the effects of it. When you do, I´m no quite sure, but it could be disappointing for you as well: I see absolutely nothing when set to Apple (Core Image RAW), only a wrongly sized canvas. I have already posted about that in another thread.
  19. Just reporting this here, as I didn´t see mention of it yet, nor found any thread about it in this forum. I half expect the issue to be well known already though, so this is just in case it´s not. I just noticed: when I set the RAW Engine to Apple (Core Image RAW), then open a RAW file, almost nothing shows up, but something either like an all black or a transparent canvas. It usually does not look like the correct size either, more like 4/3, but that aside. When I set RAW Engine back to Serif Labs, then reopen the same file, the image displays as usual. I checked only with files from two of my favourite cameras at this moment, a Sony A900 and a Fujifilm X-Pro1. Both show the same mishap but I didn´t check any other.
  20. Not a stupid question: Iridient was the first doing it that way that I knew of, when I tested it long time ago. This allowed its developer to offer RAW processing for my Fujifilm X-Trans files, long before Apple´s Digital Camera RAW was finally updated with that also. Affinity is using that concept as well, but it is only with the current Beta for now. It will propagate to the AppStore later this year - staff says hopefully before Christmas.
  21. Please stop looking for something that does not exist. When I write initial install or right after install of AP or AP Beta, I mean exactly that, IOW nothing has been set at all, so there is nothing withheld either. When you then launch AP, there is still nothing at all. Next is then to open a RAW file from this specific camera - yes, an A900 FF image will be quite a bit faster, but at the same time still slow to my standards. You don´t have any issue with the time it takes when you do the same (I suppose, you don´t say)? That´s fine and good for you, but it does not take any of my disappointment away. I am not seeking any help or advice about supposedly better tools out there. I am not interested in people´s experiences with the Photo Persona, as that´s not in scope here. I did want to share my disappointment with something stated by the developers - ´400% performance in most cases´ which is simply absolutely not true for me - you are right about that. However, I do not really need anyone to hold my hand, substitute to staff or whatever to relay information about the issue. The developers probably understand pretty well what I am talking about, or they would have asked themselves, like they usually do when there is something to clarify. I have shared numerous of my RAWs and their processed files already... To be honest, I´m getting a bit sick of these denial type of posts. They certainly don´t contribute anything on topic either.
×
×
  • Create New...

Important Information

Terms of Use | 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.