Jump to content

timlt

Members
  • Content count

    24
  • Joined

  • Last visited

  1. That makes sense--everybody has to know what their requirements are and if those include a file format that's unsupported, that has to factor into your decision. In fairness, sounds like very few RAW processing apps, whether OSS or commercial, support CR3 yet. Those that do will have a leg up for users of newer Canon cameras like yours and the upcoming 2019 models, but it's highly likely that all these popular apps that handle RAW processing will add CR3 support soon. Not suggesting this would change your mind in the short term, and I'm not evangelizing for Digikam at all, it's just what I happen to use. But I just checked their forum, it sounds like Libraw (the OSS library that Digikam and other open source apps use to handle RAW formats) plans to add CR3 support. I see similar comments in forums for Rawtherapee, and some of the commercial app forums. The takeaway being, if you have a DAM app that you like (not just Digikam, but *any* DAM app) and it hasn't added CR3 yet, it might be worth considering a workaround until support for CR3 is added, so that you can use whatever DAM app that you like, feature-wise, versus having to switch apps strictly due to support for CR3. For instance, I would expect that there's a utility app by Adobe, maybe even Canon's own RAW software, that would allow you to bulk-convert from CR3 to DNG format. Which would get you by until one of your preferred apps supports CR3.
  2. Well my thinking there is Affinity allows you to use many file formats, including the 'open' ones that are non-proprietary. I don't use the Affinity formats at all. As long as whatever DAM I'm using can handle the common open image formats, then I can use it with Affinity.
  3. Yes totally true, Digikam lacks support for .afphoto format. For me, this was not a requirement. I've been avoiding storing files in any proprietary format so that, well, I don't have to deal with the limitations of proprietary formats. :-) I've been trying to work with generic raw format like DNG, and using jpg or PNG respectively for web artifacts or quality archival copies, or .tif if needed for higher res printing or even a 'working' copy of an image with layers intact. Also XnviewMP has very poor file format output quality and control options, for me at least, and I personally was looking for a FOSS app for my DAM and RAW processor, whereas XnViewMP is neither truly freeware nor is it open.
  4. Darktable - best RAW processor (or Rawtherapee) if you just need powerful RAW handling, some basic batch workflow functions. Digikam - can process raw, AND can function as a full DAM much richer feature set than XnViewMP and truly free and open software. ETA: My expectation is Affinity will not have time/resources currently to add a DAM in the near future, as commented earlier in thread. And I'm ok with that. There are such outstanding FOSS tools out there. If you need RAW + batch processing, with very lightweight cataloging features: Darktable or Rawtherapee alone will do it. And these can work nicely with Affinity products, you can specify AP for example as the hand-off editor for processed raw files. If you want a true DAM, I think Digikam is unbeatable and in fact, has some capabilities that even LR does not have. Further, Digikam integrates pretty good raw processing, good enough for most non-pro users although pro users will again, want one of the above specialized raw apps. Personally, a combination of the following apps gives me everything I need, and then some: * AP * AD * Darktable for detailed raw touch-ups and a batch workflow to rename and apply a set of common changes to a folder full of images. * Digikam as a DAM. For creating a highly organized, tagged, searchable database with very powerful full IPTC metadata support, rich batch processing functions, upload to a lot of common cloud sources, and more features than you can shake a stick at. Works great on Windows. Works AWESOME on Linux!
  5. I posted earlier that I'd like an integrated DAM as some others do. And still wouldn't complain if we get one. But the more I read about it and experiment with some 3rd party DAM apps, I see your point and am starting to wonder whether (a) I really NEED an integrated DAM, and (b) Whether it's realistic to expect Affinity's small team can build that in the near future, while also completing their other development priorities. While I agree with your overall point (that some of us may not NEED an integrated RAW + DAM app, and that they are complex and will take serious effort to develop), I'm less sure about this supporting argument. If I follow, you are saying that it took other RAW + DAM app developers X years to build a solid mature product, thus we should expect it'll take Affinity roughly the same amount of time. I'm not sure that this line of reasoning holds, for software development. There are so many factors that go into building software, you cannot assume a simple apples-to-apples comparison on how long it'll take to build a certain type of project. Some examples of these factors include: the effectiveness of the app design and architecture (a simpler, more elegant design from the start can speed development by orders of magnitude), the total amount of man-hours (aka 'resources') they have to devote to the effort, the skill and experience of the devs themselves (a great dev will often complete a project several times faster than a mediocre one, at the same time building it with higher quality), whether they are starting with a 'clean slate' or having to build on some legacy functionality (clean slate is often faster), what kind of design-build-test-deploy pipeline and tools they are using, what awareness they have of existing apps in the same space which can speed the development of their own (example: the AP team had a good awareness of what functionality they needed to build by looking at mature competitor apps--versus having to sit down and invent from scratch all the functionality that AP would need to include), and so on. Basically, given the analogy of the rapid development of AP and AD, it wouldn't surprise me if the Affinity team could build a solid RAW + DAM app fairly quickly if they have good devs, sufficient resources to devote to it, a good design, and so on. I suspect that today, the main thing blocking them is simply the resources. They may be able to grow and add more devs, which would let them eventually tackle this. But for now, I'm moving ahead with a 3rd party app. I tried XNview and liked it for pure DAM, but it is VERY weak in the quality of the output and the "preferences" options you have to change that, when you are processing files and exporting them to other formats. I do not see Xnview as a viable choice for anything other than viewing, sorting, tagging, basic file renaming, stuff like that. I'm experimenting with some commercial apps, ON1 is one that I liked. And some FOSS alternatives. They are all quite good, though for different reasons. My 2 leading FOSS options are DigiKam and DarkTable. Both have good (DK) or excellent (DT) RAW processing that exceeds the basic tools in AP. They both have the ability to do powerful batch processing, plus they are both very good DAM apps for my needs. Not quite as slick and easy as Xnview for simply viewing/tagging/sorting kinds of stuff, but FAR more powerful in bulk graphics processing while still more than adequate for the DAM aspect. Right now I'm torn between which one I like better, but leaning slightly toward DT as it seems to hog less system resources, and has much more powerful RAW processing that gets great results. What I'd really like to see in the near future--and might be more realistic than to expect Affinity to build a full DAM app with their current small team--is if Affinity would simply partner with some viable 3rd party app, and provide smooth integration between it and the Affinity apps. I'm not sure if partnering with a FOSS DAM app is viable, given that Affinity is commercial, there may be some kind of licensing conflict. But the principle is the same, whether you integrate with a FOSS DAM app like DT, or a commercial one like DxO or ON1. GIMP has been doing something like this, partnering with both DT and RawTherapee so that you can open RAW files in GIMP, which pops open the appropriate RAW app, then hands the processed RAW result back to GIMP. I think Affinity could do something like this, and do it much better than it works in GIMP.
  6. What @John Rostron said. To add some other detail, I can confirm that the current version of Topaz Studio (which I downloaded recently as a complete trial version) works as both a standalone app, AND as a plugin in AP (it also works in Paintshop Pro 2019, which I tested as well). I was impressed with Topaz Studio and if I had the $500 at hand to shell out, I'd love to get the whole thing and use it to clean up and beautify my whole photo collection. It even has RAW editing now, though it appeared to be somewhat crippled in the trial version, so I'm unsure how well that works. But I did use the trial version to cleanup and make the best of some crappy old JPEG files where I valued the contents but did not have a better lossless source file to use. I thought Athentech Perfectly Clear was a pretty impressive plugin too as far as cleaning up those photos, but Topaz Studio is even better and having tried both, I'd probably only get Athentech as the 'budget' option. Which I may end up doing anyway, since I'm unlikely to get approval from my, uhm, 'personal finance manager' to shell out $500 for Topaz.
  7. Well an update: used the Designer trial for a few days, and liked it so much I went ahead and bought Designer. I'm loving how easy it makes it to create vector graphics for the web. So I guess I'm an official Affinity fanboi now that I own 2 of their apps. :-)
  8. I guess on the plus side: they're both surprisingly affordable for high-powered graphics apps, so one would hardly go wrong getting both! :-) One more question. With a tool like Designer, is there any big value in buying a bunch of add-on brushes, such as those offered on the Affinity store, or the Corel Particleshop dynamic brushes (I already have a few of the latter) that can run as a plugin to PS, PSP 2019, and Affinity (I confirmed this)? Or do you just use the 'vector brush tool' mentioned above, and kind of roll your own?
  9. I had a similar question, as a new Photo user. I am interested in vector art, and learning to do some digital drawing and painting as an amateur. It looks like you can create vector art and refine it quite a bit even in Photo. Is there any call for me to try out Designer too at this point, if I don't have a specific need for it? Or is Photo really the primary workhorse app, and Designer is more of a niche app for designers?
  10. +1 on using Digikam with Photo. The combined set of cataloging/tagging files, handling metadata, RAW editing, and really powerful-but-simple batch processing, make Digikam a pretty incredible tool considering it's free and open-source software. I like it better than all other FOSS software, and better than most paid software apps of this type. An app with similar features, but much more focused on specialized RAW editing and not nearly as much on the media file cataloging and management features, is RawTherapee. Use that one if you want to edit and batch process a lot of 32-bit RAW files with a lot of nuanced editing features.
  11. Hey @SrPx, thanks that's a good write-up, exactly the feature-level comparisons I was looking for. Interesting to hear this apparently long-running issue about color management in PSP, and the fact that in your usage, AffPhoto does a noticeably better job. Also interested in this comment about using Photo, PS, or even PSP as an all-purpose work horse editor: This is really what I'm looking for as well, though for slightly different reasons. I'm not a pro or even an experienced amateur when it comes to actual photography, or in working with graphics software editors. Goal right now is to learn more, and to build skills working with one primary do-it-all graphics editor that is less than $100 US. I don't mind having a couple of add-on, specialized apps that do certain things I need, it doesn't all have to bundle into the main workhorse app. For example, I don't mind having an app like the free/open-source (aka, "FOSS") Digikam, which is a great tool that combines 3 things I need: (1) Media file management/browsing/metadata, (2) RAW editing, and (3) Powerful but easy-to-use batch processing workflow. I also use a FOSS app named ShareX for advanced screenshot functionality, which gets used in my day job. But in general, I don't need or want to end up with a large set of specialized graphics apps. Ideally, just a work horse as you said--something I can master and keep using for the long haul--and then a couple of specialized apps if needed. For me, best candidates for work horse graphics apps costing < $100, are the 2 listed in the OP (PSP 2019 and AffPhoto). Yo could also throw in FOSS apps like GIMP and Krita. I've tried all of these recently, all are actually pretty impressive and could be valid options. But I've come down on the side off AffPhoto when you consider all the factors listed in the OP. Would really like to hear more comments from experienced graphics users similar to yours, where you look at support around a specific type of graphics functionality that a medium-to-advanced user would need, and how well that feature is implemented in PSP vs AffPhoto.
  12. OK, sorry to hear about your woes on the trial. I don't have my trial edition anymore (installed over a month ago), but to confirm, I IM'd Corel support with the Chat Now option on top of their main site page. They said in the trial installed off that page anytime recently, you should get both 32/64 versions (my trial had them), and should be able to import scans. They suggested if having issues with the trial, ping them via that IM support option, and if possible, take a screen shot of your disabled Import menu. If you have time to get the trial working, as per the OP, I'd be interested to hear any side-by-side evaluation you can offer on features.
  13. That would make sense why it works, and if so, would invalidate Vuescan as an example of a 64-bit app that works with the Canon drivers. I pinged Canon driver support for more info on their x64 drivers, definitely has my curiosity going.
  14. @walt.farrell: Yes, the docs in PSP 2019 also have that blurb about full WIA and TWAIN support in the 32 and the x64 PSP. However...it's also interesting that other 64-bit apps I have on hand seem to recognize the Canon scanner drivers and work (two I just tried are the included Windows 10 x64 Scan and Fax app, and a 3rd party app called Vuescan). This, plus a number of other PSP x64 user complaints about this same issue of not recognizing their scanner, leads me to think that that Corel really has an issue with their TWAIN and WIA implementation in the x64 version. But regardless, it shouldn't be a blocker for anyone who wants to use PSP x64. If you have decent native scanner software (like Canon's), or if you can use a solid x64 app like Vuescan, you can still send your scan output directly to any graphics app including PSP x64. Of course what would really rock though, is if we could get true WIA scanner support in AffPhoto 1.7. :-) @John Rostron: Definitely PSP gives you that true B&W option you're looking for, directly from the scanner and without need of conversion. Agree with you, that aspect doesn't work in AffPhoto. To get the latest version of PSP 2019 for comparison (this should include both 32-bit and x64), I got my free trial here before I purchased it.
  15. @John Rostron, some additional info: My second scenario above, using my scan software with AffPhoto 1.6 for Win10 x64, worked. I was able to do the same thing as with PSP 2019. Using the Canon Pixma 9120 native scan software, when the drivers scan a doc or photo, they will launch AffPhoto and send a scanned JPEG, PNG, or TIFF image directly to it. For my 9120 printer at least, the Canon product drivers page indicates the drivers are providing full x64 support on Win10. So I still suspect that the fault of scanner not being recognized in PSP 2019 x64, is likely due to PSP not using the new model in Windows which is no longer TWAIN, but rather requires a WIA driver model, as here. They likely either have a bug, or they haven't implemented WIA yet in x64. However, the good news is that you don't need to 'acquire' scans from within the application anyway, using the approach above, you can just send your scans from native software to your 64-bit graphics app, whether PSP or AffPhoto.
×