AiDon

I believe it is similar to what we did in PhotoPlus. Paste as New Layer would paste the object offset and I think this is what our old customers were asking for. Whether it is the right decision or not is up to development. We are not a Photoshop clone.

Still need work on Shadow Recovery, Highlight Recovery is fine.

@Neubigerg
Opens in 10 seconds on my Windows 8 PC using latest beta
 
62 seconds on my Win 10 PC (running released version 1.5)

Betas will always start more slowly than the release version, as we have extra checks at startup. Are you referring to slower speeds compared to previous beta, or compared to released version?
RAW loading should be faster (as an example, I have a 22MB CR2 file I used for testing the improvements, the original load time was 10 seconds, it's now down to 6 seconds on my machine).
Installer shouldn't be affected.

Try using the File -> Export... option where there are many different formats.
 
 

Hi amazme1,
Welcome to Affinity Forums :)
Lightroom is not a photo editor but a RAW developer. It's editing tools are not up to what Photoshop offers. Affinity Photo is both a RAW developer and photo editor.
We already announced plans for an Affinity DAM software which will work seamlessly with Affinity Photo.

Hi verysame,
I understand what you mean but it's not only about direction no matter how we want to look at it. This is a commercial software and to keep it profitable and sustainable in the long term (in particular considering the prices we have) we need to rely on sales. Some commercial opportunities cannot be simply ignored - a demo on WWDC or supporting emerging (popular) platforms - all help to spread the word about the app, raise sales and fund further development. If we were relying exclusively on professional users and their needs (in particular in this initial phase), most of which dependent on heavily tested/safe workflows it would be really hard to move forward. We must find a balance between fulfilling their demands/requirements and sustain the development through sales/marketing for a larger user base. Things may move a little slower this way but they move at a steady/solid pace. I think most of the frustration comes from the high expectations some users have when they change from Photoshop or Illustrator - programs which have been in development (and fine-tuned) for decades - and start with Affinity. It's completely impossible to cover everything in such a short amount of time with the resources we have. The same regarding achieving stability on such a large and diverse platform as Windows. 
 
Popular platforms / a larger user base help us to sustain Affinity's grow. We have and are still fixing bugs reported by users in order to increase stability and performance on Windows and hopefully things will become better as we fill the gaps to other apps/add more features for professionals as time permits.

It also uses 'automation' which is a bit tricky to emulate outside of PS, such as the brushes with NIK filters.

Hi, 
 
Happens on my PC too, with both GPU's. Never recovers.
 
Both Develop & Photo Persona's seems to be associated with image size as 5DsR & Fuji X100T don't recover.
 
 

The Beta app seems to have corrupted this file during editing and now I cannot duplicate layers as, using Ctrl+J to duplicate any layer, results in a layer as in the attached screen shot being created. The process undertaken was:
 
Import from a multi-layered TIFF  Save as .afphoto file Turn off visibility on all layers except Background Duplicate Background layer Select a Mask using the Selection Brush Tool Mask using the Mask Layer icon Refine the mask ... Smooth 2 pixels and Feather by 4 pixels Move the masked layer up by 2 layers Turn on visibility of all layers except layer labeled ReMask Save the file  
Next try to duplicate any layer and the layer is duplicated as in the screen shot.
 
The AfPhoto file can be downloaded from: https://www.dropbox.com/s/hj7la7d4zm14mhj/EOS%205DS%20R172267.afphoto?dl=0
 
 
 
 
 
 
 
https://www.dropbox.com/s/hj7la7d4zm14mhj/EOS%205DS%20R172267.afphoto?dl=0

Hi abphoto, 
The reason we made these changes was to allow us to use input points direct from the tablet driver, instead of through the Windows mouse API. The benefits of this approach are: 
 
1. Increased input point precision, independent of screen resolution and zoom level.
2. Increased input point frequency (especially under load), resulting in smoother lines. 
 
We are reverting this feature because to make it work reliably, more extensive changes are needed, which we have decided are unsuitable for a minor patch.
The feature will hopefully appear in 1.6. 

I notice that a few people are having issues with Wacom Tablets and Pens, most of these issues are caused by the drivers ... I guess that was a major factor in Microsoft dropping Wacom in favour of N-Trig.
 
Wacom Drivers have had a long history of having issues because of the way driver updates are applied ... the way to make sure that driver updates don't affect the stability of your Wacom tablet is to follow these simple steps every time you update your driver:
 
Delete ALL user preferences using the Wacom Tablet File Preference Utility and select the Remove button in the "All User Preferences" section. Note that if you have Personal Preferences you can Backup and Restore using the same utility via the Backup and Restore buttons in the "My Preferences" section. Make sure you do the Backup before Removing all user preferences. Uninstall the "Wacom Tablet" entry in the "Control Panel\Programs\Programs and Features". Reboot Install the current drivers Reboot and, if necessary, restore any Personal Preferences using the Tablet File Preference Utility  
NOTE: The important thing here is that the complete uninstall including the preferences. 

Firstly I would like to say that the improvements are really noticeable with faster opening times, not exceeding 20 seconds, even for large images such as 5DsR or X-Trans images. I am not sure if this is simply personal preference or not but I use quite a few RAW processors and find that the AP conversions are a little too saturated and don't have enough brightness in the midtones.
 
Here are comparisons of AP vs C1 with both Canon and FujiFilm RAW images with simple basic conversions, AP on the top and C1 on the bottom where you can see the differences in saturation/vibrance and brightness:
 
 

Thank you, I appreciate the help ... I understand the duplication process but I just couldn't find the selected area as I couldn't see it. It took me a while to find it after you explained as they are large files and viewing at 100% is the only way to find it.
 
Also, there have been complaints about the size of your AfPhoto files but in this particular case the TIFF (uncompressed) is 1.27GB and the AfPhoto file is 0.97GB. So thank you for all the work being done.

I know a lot of people that want to 'start' with the jpeg-output in a RAW editor, and tweak it from there. That is what I meant.
The same with all the (early) x-trans users that just plain liked the jpeg output more but couldn't get ACR to match it closely :). Anyway, it was just a way to explain _what_ was happening, and that it is not a fault _in theory_.
 
But you absolutely have a point that 'more pleasing out of the box' will help, specially when people start comparing raw converters. It's nice that it can produce great results, but if you need a lot of tweaking to get there, people tend to start using other stuff. Specially in the pro world, where the mantra of 'time is money' is simply true. A raw converter that needs 3 sliders tweaked a little bit vs a raw converter that doesn't is very clear in my mind :).
 
I also think the 'pleasing from the start' comes from supporting different camera's and raw files. Some people have been complaining that their raw files start out way too dark and it appears a new (Beta) update fixed it. I believe (as an example) people not thinking the raw development was OK from Olympus OM-D E-M5 mark2 files, but my OM-D E-M10 mark1 files came out great from the start. So it depends on camera body and everything.
 
Maybe make an official 'support' request with a sample raw file from you so they can tweak the default response? Wouldn't be the first time they did that from what I read on the forum.

Not sure what you are talking about quoting "CR and color profiles being very far from the original ones laid by the manufacturer" as Canon only creates a JPEG in sRGB or AdobeRGB from the RAW image. If you are talking about Picture Styles then they are only for DPP.
 
This is DPP's interpretation which is similar to C1.

Carl, on every beta post this is the first sentence:
 
 
There will be a new beta available soon. Hopefully today. One was scheduled to be released last week, but due to a bug, we couldn't release it.

Error using NVIDIA GeForce 745M GPU with Driver version 381.65 note that this error doesnt happen if I use the integrated GPU which is an Intel HD4600.
 
Only happens using Gunny Rewritten Font (Jan 14, 2014) at 72 pt, also seemed to cause the display driver nvlddmkm.sys to stop responding. (NVIDIA Kernel Mode Driver 22.21.13.8165)
 
Faulting application name: Photo.exe, version: 1.5.2.63, time stamp: 0x58de6274
Faulting module name: ucrtbase.dll, version: 10.0.15063.0, time stamp: 0xaf2e320b
Exception code: 0xc0000409
Fault offset: 0x00000000000734be
Faulting process id: 0x3160
Faulting application start time: 0x01d2b7215d05039f
Faulting application path: C:\Program Files\Affinity\Affinity Photo Customer Beta\Photo.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
 
Eventually can cause a BSOD with VIDEO_SCHEDULER_INTERNAL_ERROR if repeated often enough.
 
Repaired the NVIDIA drivers by doing a clean install and first-time start-up of Affinity Photo Beta caused the same crash but after that first-time crash it starts OK:
 
Faulting application name: Photo.exe, version: 1.5.2.63, time stamp: 0x58de6274
Faulting module name: ucrtbase.dll, version: 10.0.15063.0, time stamp: 0xaf2e320b
Exception code: 0xc0000409
Fault offset: 0x00000000000734be
Faulting process id: 0xf6c
Faulting application start time: 0x01d2b7282005adfb
Faulting application path: C:\Program Files\Affinity\Affinity Photo Customer Beta\Photo.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
 
Attached the WER report and a DMP file. The dump (DMP) can be downloaded from https://www.dropbox.com/s/pex5d9qa5fggi5j/APB%20Photo.exe.5752.dmp?dl=0 
 
Note my system specs are:
Win 10 x64 System with Intuos Pen & Touch 
* Sys :Intel i7-4700MQ @2.40Ghz x 4 core/8 thread, 16GB RAM
* GPU 1: Intel HD4600, 1GB, OpenGL v4.3, OpenCL v1.2
* GPU 2: NVIDIA GT 745M, 4GB, OpenGL v4.5, OpenCL v1.2
APB BEX64.wer.txt

Hi AiDon,

As I mentioned in the other thread we're collating a list of Windows 10 1703 crashes for development to take a look into!

https://forum.affinity.serif.com/index.php?/topic/30168-cropping-staying-within-the-boundaries-of-the-image/ is the post that first refers to this.
 
As explained there, the necessity to make at least four additional move-and-click actions, one for each "edge", could be avoided if the crop marks always "automatically" stayed within the boundaries of the image.

That's a good suggestion. I've just made the change now, you should be able to find the plugins in:
 
C:\ProgramData\Affinity\Photo\1.0 (Beta)\Plugins
 
When it's out of beta, the folder will just be:
 
C:\ProgramData\Affinity\Photo\1.0\Plugins

Thank you, and it seems to work fine ...

Thanks Aidon, My mistake.
Might be worth grouping the 1D X together to avoid anybody else doing the same.

I have created a post about this in the Feature Requests section of this forum; the thread is https://forum.affinity.serif.com/index.php?/topic/30443-photo-cropping-of-rotatedstraightened-image-crop-marks-to-not-be-outside-image-boundaries/
 
Perhaps posters here and others who think this would be a great improvement, might like to add their voices to this request by posting their agreement to that thread?
 
Jeff

Hi,
 
Using the Crop filter it automatically stays within the boundaries of the image when you crop to the Original Ratio but when you straighten the image with Original Ratio selected the Crop can be, and usually is, outside the boundaries of the image.
 
Is there an option, or a plan to include an option, to constrain the crop to the boundaries of the image?