Amateur John

Remember 'The Mythical Man Month' . It was a book published in the mid seventies about the development of an IBM operating system. The project ran late and IBM threw more and more people into the team. Progress slowed.
Much later Pro-Engineer, a CAD CAM company was founded by a very small team of software engineers who were fed up with their large employer. They produced a very successful innovative product which became more popular than that of their previous employer. I expect that there are many examples where small teams successfully challenge big teams.
A small expert and enthusiastic team in which everyone knows and understands what everyone else is doing can make rapid progress. Big teams get bogged down with lack of communication and lack of shared understanding. A small company like Serif does compete with the Adobe leviathan.
I have bought the full Affinity licence although I only use Photo (and Publisher occasionally). I wish the company well.

Walt's method works with Nikon Studio. Like LR it is necessary to change the default .exe file type to *.*

Yep. Tried it. Don't care for it. However, it's the best way of achieving on your desktop computer the identical results you'd get from the in-camera JPEG. So I agree... for free it's there as an option. However, it's nothing at all like a true DAM. It's simply for browsing, editing, and processing Nikon raw files.

I quickly learned to consult Help -> Tutorial... whenever something in Photo wasn't working the way I thought it should.  The brief videos are a collection of yellow explanation cards describing everything from basic operations to more advanced topics.
In this case, https://affinity.serif.com/en-us/tutorials/photo/desktop/video/365012457/ would help.

So was I. I am no longer trying it on the 1.9.0.932 release. You can use the program perfectly well without registering it. Have you tried it on the current beta?
I see that you are new here so I hope that you do not mind me reiterating that one should not use beta versions on live projects. Its best to work on a copies of your files.

I have started a new thread .Registration with Affinity Store versions of all Apps.
This was requested by Patrick Connor
 

Photo 1.9.0.876, Publisher 1.9.0.874, Designer 1.9.0.876 .
All seemed  to install correctly on my main computer. When I try to register the app, after the "Please wait a moment" message is shown for a few seconds The app crashes. The system is running Windows 10.0.19042. I have16.0 GB memory and plenty of space on my C and D drives.
The second time that I ran the programs all seemed fine until I clicked on the my account icon. This opened the window which invites me to login. When I attempt to do so then the app crashes.
I have also loaded photo and publisher on to my laptop, which is a much lower spec machine. It all works perfectly there. I have logged out of my account on the laptop and closed the apps.

I have sent 2 photo files, 1 designer file, and 2 publisher files.
The files which are under 2000 KB are from first attempts.
Those over 2000 KB are second attempts
 

When I checked out Eagle, I quickly abandoned it because of its "file Structure".  Not linking files is a deal killer for me.
So far I have been relatively happy with NeoFinder, I am still trialing it but it seems to work fairly well...  It simply links files.

Yes, you can run a batch of raw conversions to JPEG . However, to @Phojoegraphy's point, one cannot make adjustments to those individual raw files and then preserve those settings for batch conversion. Having such an ability would be a huge leap forward for Affinity Photo.

I hope that all you at Affinity and all members of the forums have a happy and well earned holiday.

DAM, or something that looks like it. I switched from Aperture to C1 and I'm regretting it, but like everyone else here (I assume) I won't do Adobe. Affinity asset management is a must.

This update is not of importance to me because I use Windows however I think it worth commenting that Affinity get honourable mention about it on Thom Hogan's ByThom website which has a huge following by Nikon users over the English speaking world.

Thanks for the update, much appreciated! The fact that you guys are still cranking on updates during these hectic, stressful, and unsafe times is amazing - 😎 
 
Have a great weekend and please stay safe.
 
-Terry

Big thanks to the people at Serif for bringing us updates despite the current situation.
Please keep staying safe and all the best to you, your family and friends!

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.

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.

That is not new. Files saved in 1.7 could not be opened in 1.6. As far as I know, fIles saved in 1.6 could not be opened in 1.5. Etc.
Configuration options in the Mac App Store and the Microsoft Store let you determine whether automatic updates happen, or not. If you purchased from Serif directly, then on Windows there is no automatic update. And on Mac there is either no automatic update or it's configurable.
I agree with some of your other points about quality control (as I'm sure many at Serif do, too).
Edit: However, given some of your complaints, if you haven't been participating in the beta program perhaps you should be. That lets you help with quality, and educates you about forthcoming functions and how they might affect your workflow if you update. If there are changes that you know your team won't appreciate, you can avoid updating.

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.

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.

Keep in mind this thread was not begun by Serif themselves. It was a consumer that posted the poll and comment thread based upon a number of rumors and a few isolated unofficial statements made by forum moderators. Very few companies pre-announce their future products at least until they are only weeks or months away from delivery. If they have nothing near delivery, then I don't expect to hear anything from them. 
This thread says less about Serif and more about how consumers' minds work. We don't "deserve" better treatment by Serif. They've already gained my trust, and I signal that by spending my $$$ on their imaging products. If and when they release a DAM, I'll be happy to check it out. But for now, there are other capable products that perform this function well enough for my workflow.
Creating a true DAM (which Lightroom itself is NOT) is difficult business. I hope Serif figures out how to define and design one that fits in with the aesthetic and capability of their rest of their tools.

Hi,
 
the behaviour of DPP 4 is as expected. The exported pictures are the same color / brightness:

(Exported by Canon Digital Photo Professional 4, maximum quality)
 
It doesn't seem to be limited to the JPEG-export, when I export as TIFF, the picture is also darker. It seems like one processing step that Affinity uses, when loading a RAW-image "by hand", is not applied when using batch processing.
 
Now the upload is working, so here is the RAW-file:
IMG_2651.CR2
 
I would like to hear from someone if he gets the same result. I tested it on three different devices, so it should be easy to reproduce.

Welcome to the Serif Affinity forums, Franzus.
Batch processing uses a simpler raw development process than the Develop Persona uses. Typically the result is darker images, but there will be other differences, too, as none of the Develop Assistant processing is done. You can compensate for that, to some extent:
Open a raw image from your camera with Affinity Photo, and develop it in the Develop Persona. Process the same image through a batch job in Photo. Open the image from step 2, and compare to the image from step 1. Determine a set of adjustments to make to the step 2 image to make it satisfactory to you, and record those adjustments as a macro. Then, when you run your raw images through a batch job, apply that macro. Your results should be more satisfactory, though perhaps not completely right.

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.

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.