Jump to content


  • Content Count

  • Joined

  • Last visited

  1. I agree with the points made in your posts and have similar issues with high volume workflow. I have been testing the Affinity Photo + NeoFinder combination and made some notes on the attached file, in case people want to read about my experiences.workflow affinity and neofinder.pdf
  2. This is a very difficult subject and everyone has their own workflow and valid opinion. Nevertheless, I am going to risk wading in and give some of my experiences. I am not making a recommendation, just saying what I think is important and what works for me. I was a full time professional photographer and latterly videographer for 10 years. I have closed my company but have a back catalogue of 100,000+ photos and videos. I still actively submit work to Alamy. During those years I largely worked on PCs, but a few years ago switched mostly to Macs, which I now much prefer. But I have data and programs on both platforms. In catalogue terms I started using a small PC program about 10 years ago and gradually moved to MS Expression, Media Pro, the original beta Lightroom then versions of Lightroom up to CS6. I have the entire CS6 production suite and updated every new release, but once Adobe switched to a subscription model with no backward compatibility I vowed never to touch an Adobe product again. Lightroom is the last program to be turned off - and I am getting there. For several years I have used Lightroom 4,5,6 as an essential tool in cataloguing and initially processing my images. All my images from about 2005 onwards are Canon RAW, converted to DNG, and since I take care to get most things right in the camera I can do about 95% of my processing only in LR Developer and leave the RAW files untouched, with few jpg or psd copies. I have produced books, albums and prints directly from here, so a huge productivity gain. I have now been using Affinity Photo and Publisher for some time and they are both fantastic products. I have for a long time kept my eye open for a LR replacement and in the last few weeks actively tried lots of them. I finally (and with some difficulty) found NeoFinder (same product on Windows with a slightly different name). You can have a free version or, for a modest charge, an unlimited version. Within minutes I had imported loads of files from various network drives (something severely limited in LR). I could easily jump directly into Affinity Photo or Publisher for editing. But here is the missing link. With RAW processing the viewer changes the view of the image, but nothing changes on file. So NeoFinder and APhoto cannot write back changes. Those changes are the things that LR or Apple Photos stores, and you can easily revert original - the beauty of RAW. This gives me an awkward workflow. If I process the RAW image in aphoto I have to develop and save as aphoto, jpg, psd or whatever, increasing my storage and file viewing complexity. I also have to jump in and out of APhoto. Interestingly, Apple Photos is tightly integrated with APhoto. You can do basic image corrections through Apple Photo with APhoto, and Apple Photo then represents these changes in the latest view. In this respect the system works a little like LR. If only Serif would create the same integration with NeoFinder as with Apple Photo my problems would be solved. I'd have more or less the equivalent of LR, but with far more extensive searching capability and some extra good bits with Apple Photos sharing images in iCloud if I wish. They would save a lot of development time and be able to tap into a good DAM almost like a plugin. As things stand I'll probably continue with NeoFinder (handles all file types including video with metadata), does not create sidecar files (other than with aphoto format). Since I can almost simultaneously import a folder into both Neofinder and Apple Photos I'll use this approach so that I can quickly go through all my RAW images using the Apply Photos interface, then use the power of Neofinder for finding, geotagging, things with Apple Script and so on. Sorry it's such a long post but I have used many generations of DAM and my experience has led me to where I am - still searching.
  3. Jon Thankfully I have now rebuilt the file. I started by recovering a backup from a couple of days earlier when things were going well. I deleted all the pages, modified a few master pages and created a new template. I recreated from there and successfully managed to add many new pages. With the old file I did quite a lot of changing master pages and replacing photos into the new formats. At one stage, when I clicked on a photo frame I could not get the 'replace image' box to appear unless I restarted. I also played around with modifying a photo using the photo persona, and things gradually went downhill. With the latest file I kept to a stricter regime. I created all of the master pages first then went through the book in sequence adding photos and text. I saved after each page, and the save happened very quickly. I did go back and insert a few pages, but all seemed to work well and I have just created a pdf for printing. So I don't think that you can help further with this one, but I thought it worth reporting. As I use Time Machine I'll make sure that it is running and I should always be able to get back to a working version of a file if I start to hit problems. Stuart
  4. I have been working on a publisher file for several days. I created a new template and have been using that. The book is a photo book with lots of images linked. Things worked well for a few days, but today Publisher started crashing every time I tried to use the file. I cannot save it under a different name. I can create a new blank file, but I now have many hours invested in my new photo book with its template. I cannot save a new template from that book, so I appear to have lost everything. This is my first major project with Publisher, which I purchased mostly for this job, moving from another supplier. Any ideas on how to get out of this? Crash report attached. I am using MacOs 10.15.6 and Publisher 1.8.3. After typing the above I created a new, blank file and everything was fine. I also managed to restore a version of the file from 4 days ago using Time Machine and that opened and worked fine. I was able to save it and also delete all pages and save a nearly empty file, as well as create a new template file. So I have now almost rebuilt my document and new template, but am concerned that I'll get further into this project and lose it. All images used in the project are linked. The Resource Manager shows them as linked and nothing is missing. There is minimal text in the file. crash report.rtf
  5. Thank you to all who replied. This does seem to be a fairly active forum, which is great. To summarise: I have had 000s of photos accepted by Alamy, but I have to follow their rules. Only once or twice in those thousands have I been less than careful and had photos rejected for file size (mostly something that I have cropped). Whatever the logic of this their rules state a minimum of 17MB uncompressed file size and suggest using the figure shown by Photoshop at the bottom of the document. All images submitted to them are jpg, so I convert them first, then check the size. Because every photo compresses differently looking at the actual file size is not a good guide. Any jpg of 6MB or more is generally safe, but for the rest I have to open the file and check. The best answers were from those who suggested the formula of multiplying the pixel count by 3. That comes pretty close to the figure in Photoshop. Thanks for the comments. I can now close this.
  6. I submit photos to Alamy and need to check the uncompressed file size before sending. I can do this in Photoshop (it appears at the bottom of the document) but am trying to wean myself off Photoshop. I can see the document size at the top of an image in Affinity Photo, but it does not correspond to the size in Photoshop. For example: a dng image in Lightroom has a file size of 12.51 MB If I open this in Photoshop the uncompressed image size is shown as 72.8 MB. If I open in Affinity Photo it creates a tif file with a size of 12.72 MB. If I export this to a jpg the actual file size is 12.72 MB. If I re-open this in Affinity Photo the file size is shown as the same, the compressed file size. I need to identify the uncompressed file size as this is the measure that Alamy uses. Any idea where I can find this information in Affinity Photo? Or am I stuck with Photoshop?
  7. Having some basic page layout templates for photo books is a feature sorely missing. I design and produce photo books in Lightroom, Graphistudio and other programs and most come supplied with basic layouts that can be customised. Of course you can create your own, but a professionally designed, modifiable starter kit would be a great help.
  8. DAM requirements for Affinity Photo Some background on why I need a DAM - sorry for the length, but I am sure many fellow professional photographers are suffering from similar problems. I am a professional photographer and videographer. I have been using Adobe products (mostly Bridge, Photoshop, Premiere Pro, After Effects, Lightroom) for the last 15 years. I have around 75,000 images in my active catalogue and boxes of about 500GB of archived wedding photos on DVD/BluRay. In addition I have about 1 TB of video footage. I am trying to keep on top of this lot. I started to move away from Adobe products when they introduced their subscription service and am stuck at CS6 for the remaining products I use. At the same time I moved from PC to Mac. I still have a PC with my main Lightroom catalogue but am desperately trying to move everything to my Mac, both because I love the experience and because I want to ditch all things Adobe. I recently bought both Affinity Photo and Affinity Publisher. I love the software and the integration between the two packages. But I am stuck with Lightroom and keep getting warnings that it will not work in future OSX releases. The maps module has already stopped working, so I am running out of time to find a replacement. I have completed the poll, but wanted to add some specific points on what I really need to keep an efficient workflow going. A Lightroom type view of my images. I always start from a thumbnail preview and all of the initial review and rating before going deeper is done there. It just about works now with doing the bulk of the work in Lightroom then editing in Affinity, but a simpler switching in and out of deep editing would speed up the workflow considerably and reduce errors and duplications. A referenced file system rather than a database, although either is acceptable. But either way it is vital that network drives can be included in the catalogue. I take my Mac on travels and use a temporary catalogue which I import into the PC. But I often want to refer back to my main catalogue (a copy with reasonable resolution is too big to carry), or to share data between my various computers. I have a mixture of 4 iOS, Mac and PC systems that use where convenient. Sidecar files create thousands of extra files, so if the only way to avoid this is a catalogue then that is the better way. Post Photoshop and since Lightroom I do 95% plus of my editing in Lightroom. I rarely need to drop into Photoshop or Affinity Photo. I’d like to be able to do this with a DAM/Affinity photo integration. I use RAW on all cameras bar one, and keep everything in RAW, but the editing needs to be indistinguishable between RAW and other formats. Metadata is critical and this is what is currently stopping me from moving to another package. I frequently search on any of the metadata items. I have built up a huge library of keywords for use with Alamy. This needs to be on display and editable with the image. The usual range of flags, ratings and so on goes without saying and must be there. The ability to print directly from the DAM interface with ICC profile options, as in Lightroom. A map view (as taken away from non cc versions of Lightroom). Essentially this is Lightroom on Affinity, but there is a good reason that Lightroom is the market leader. A halfway house, and one that would let me move away from Lightroom right now, is to use Photos on Mac for the basic file structure and viewing and to add a strong metadata and searching model to Affinity Photo. Photos already allows for network files as well as files integrated into the Photos library.
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.