Jump to content

Amateur John

  • Content Count

  • Joined

  • Last visited

Everything posted by Amateur John

  1. I wouldn't dream of running a batch of raw to jpeg. I run a batch of raw to afphoto. then edit and export to whatever format and size that I need.
  2. Affinity batch process works on raw files. Sometimes with a long list you will get a not responding as they load; just give it time. The running of the bath process has been reliable for several releases.
  3. FastRawViewer is a useful tool for quickly sorting through a batch of raw files before submitting them to Affinity Photo's develop persona. It is not a DAM and its authors do not claim that it is. Thanks for mentioning it. It is useful.
  4. I hope that you can get this 90 day trial viral amongst college and older school design students. You could end up with a lot of self taught users who know no other package. The potential sales as things come back to normal are enormous. It is very generous to allow people enough time to learn how to use the apps. It may also prove to be wonderful marketing. Thanks for all the development work. Take care and I hope that your home working stops you catching the virus.
  5. The database for DAM does not contain the editing information that is stored in xmp files in the Adobe system. The LR database keeps track of where files are stored and information about them that we want to add in order to find them. It also tracks duplicates which are made for further processing. In an affinity installation, should a DAM be produced, I would also expect it to keep track of files being used in other documents. For example photographs being used in publications. A database is an essential part of a DAM.
  6. I would expect an afphoto file to be at least twice the size of the high quality jpeg file from which it was generated, even if no editing was done, for two reasons. The jpeg file uses eight bits per channel per pixel whereas the afphoto file uses sixteen bits The jpeg file uses destructive compression.
  7. I do not need a DAM. I would like a DAM very much. I would expect it to use a database and accept that importing would be necessary. A browser like Bridge is not worth the effort of creating it. I am aware of the problems of creating such a system since a colleague and I created a system for controlling engineering drawings, which ended up as a product database. This system used an Oracle DBMS. I understand that Lightroom uses a light single file version of Microsoft SQL Server. These DAM systems are not trivial and require several man years to develop. I am still hoping but do not underestimate the resource needed. I would expect this, if ever created to be an add on at extra cost. This would be a huge project for a company whose expertise is in graphics, imaging, and desktop publishing.
  8. Thanks for posting. Starting the previous beta was not alerting the update which has gone live today. The Affinity team have even been working Saturday on this . I have tried the new beta on Nikon NEF and it is good. John
  9. There may be a combination of causes. One contributory cause, possible with Nikon NEF files is the effect of Active D-Lighting (ADL). This is intended for producing acceptable out of camera JPEGs in high contrast situations but does effect NEF. Exposure is reduced to reduce the burning out of highlights then the shadows are recovered in creating the JPEGs including the embedded jpeg in the NEF file which is also displayed on the camera monitor. An entry is made in the NEF EXIF such as "Active D-Lighting Auto". The in camera histograms are generated from that embedded jpeg so the deliberate underexposure is not obvious to the photographer. If the NEF file is opened in Nikon's own software such as Capture NX-D that software picks up the EXIF entry and acts upon it. Affinity does not seem to react to that entry so the image appears dark and the histogram is created from the real raw data. I see this as something that Nikon users need to be aware of, and not something to be fixed by Affinity. I agree with other users that something else is going on. ADL has affected files which I submitted on another thread.
  10. The behaviour with Nikon NEF is similar to that of cr3. At default Nikon Capture NX-D takes these NEF files to 16 bit tiff files that look like the embedded jpeg. Weather permitting I will take some similar pictures tomorrow on our park workday but with the camera set to raw + jpeg. Actually the difficulty is rapidly disappearing for me as I learn how to deal with the flat conversions rapidly on an individual basis instead of trying to develop in batch. I was only using batch from NEF to afphoto files because I preferred working only in the main persona rather than develop. _2019-12-18_10_52_27.NEF _2019-12-18_12_21_55.NEF _2020-01-15_12_53_57.NEF
  11. Thanks for an email. I will get back tomorrow. I am not exactly sober at the moment. I have a few files to illustrate the issue.
  12. This behaviour of Affinity Photo certainly gives some of us coming from LR or Nikon's NX-D and several other converters, difficulties. The Affinity default conversion is accurate. Most other converters by default attempt to give something a bit like an out of camera jpeg. That gives an easier image to work with in many cases. I have found that for some particularly difficult high contrast images increasing exposure in the 32 bit space of the develop module allows a good rendition of shadows without burning out highlights; those highlights can then be toned down before pressing the develop button. I guess that is all obvious to experienced workers. I am beginning to realise the advantage of starting from a flat conversion. If Affinity does at a later date allow batch processing to generate 'camera jpeg like' afphoto files then I also hope that we will still have the option of working from a flat conversion because there are cases where this approach, the present one, leads to a better finished image (albeit with more effort).
  13. I think that a glossary of technical terms would be a useful addition to the present documentation for all three of the applications. It is too easy for writers of documentation aimed at new users to assume more user knowledge than they have. I fell into that trap while documenting an engineering database. I was soon 'put right' because I worked in the same office as some of our users.
  14. A simple curve seems to do a reasonable job, but I suspect that the Develop Persona also makes more complicated changes which depend on the histogram of the original file.
  15. I also find this more of a bug than a feature. The macro workaround is fairly satisfactory but not ideal. Please, what do the developers say.
  16. Don't forget that a file could be copied and renamed at an OS level. Publisher could not act on that. I think that the program's action is correct. It would be helpful to draw more attention to the fields in the help documentation in the sections on document creation. We should be updating author and other fields. That is our responsibility not the program's. There may be times when we do not want the title to be the filename Elsewhere in the forums there are comments about transfering master pages from one document to a new document. Copying and renaming a file plus manually updating the fields is a simple way of achieving that and avoids further complicating the program. Again documentation, or even something in one of the tutorials would be helpful.
  17. Sorry folks. I was missing the fields panel. A default title is set according to the initial file name. I needed to change it when I changed the filename. I hope that I have not wasted anyone's time.
  18. I would like to save an existing afpub file as a new file and then work on it to create a new document using much content from the original file. This seems to work fine until I export a pdf file and open that file in Google Chrome or Firefox. The tabs show part of the old filename, not the new. This is not a problem with Acrobat reader or Internet explorer since they identify tabs by the new filename. I am not including history. Am I missing something?
  19. The afphoto file created by a default develop is an RGB 16 bit per channel non compressed file. No information from the raw file (typically 12 or 14 bits) is lost. That implies that HSL can be done just as well in afphoto as in ACR. I suspect that the detractors are hardened Adobe users who are very set in their ways. You may find that the afphoto file looks flat because the default curve applied during development is not aggressive. If you disable that curve then the result looks even more flat. Some people like to start from the flat state. Expert videographers, for example, demand flat files so they can create consistant colour grading. If you want to start editing from an image that looks like the jpeg preview on your camera screen, a perfectly reasonable way to work, then you can do your raw conversion to 16 bit tiff using your camera manufactures' software. Then use Affinity to do the real edit. If you go down that route then make sure that you avoid any form of jpeg as an intermediate file format. 16 bit Tiff files are big because they throw nothing away; Afphoto files are even bigger but huge discs are cheap so who cares. Affinity is an excellent alternative to Photoshop. It is not a replacement for LR yet. Hopefully it will soon replace both of them.
  20. I have wondered about this myself. My present approach is to do the least possible in Develop. I use the defaults in Develop Manager so I get lens corrections. Then I run a batch job on all the raws in the directory of new pictures saving as afphoto files. When you select a large number of files you may get a brief 'not responding' message. No problem; it just needs time. When you run the batch you can see progress and I used to watch it. The present release ( seems to be reliable, so now I go and make a cup of coffee while the batch runs. The batch uses all the cores of the processor. Its best not to try and do anything else on the computer while the batch runs. I would be interested to know how Serif developers intend it to be used.
  21. When Serif produces some form of DAM it will handle files from Designer and Publisher as well as Photo. It could also handle Publisher dependancies and give warnings when you attempt to change a design or photograph which has been used in a publication. The degree of integration possible in Affinity is likely to be market leading.
  22. Thanks Walt. That was the problem but I have no recollection of changing that default deliberately.
  23. OOPS Creating the flood selection does work. It was the next part of the exercise that failed to work as expected. When creating the new adjustment layer this is created as a child layer of the background layer rather than a layer above. In this case the adjustment of course works because the background layer has no layers below it. So no real problem except to someone learning from the book who sees something not working as described. Sorry for confusion.
  24. Please check that all the examples in the Workbook work as described. This is possibly a very basic check that nothing fundamental has been upset. Perhaps you could even recruit a team of keen users to do this check. Instead of releasing on a Friday, and expecting a member of staff to respond to queries over the weekend. Hold off until Monday while volunteers do that simple but time consuming check. Shared between around half a dozen people it would not be too onerous. For example 'Creating a flood selection' does not do so in the new release 1.7.2. It does work properly in (beta). A more positive issue. Congratulations of doing rather well in both Amateur Photographer's affordable alternatives to A***e and Practical Photography's Powerful editing suites for under £100. Knocking the opposition for four in both cases is very good. With an optional DAM or Library module I reckon that you would have hit them for six.
  • 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.