Grumpy Hec

Thanks Walt.
Interesting and logical. I'll do some more tests including comparing to afphoto as a matter of interest. In terms of a way to use a DAM to manage my 100K plus images with AP2, going down the tiff route is looking increasingly like the best option.
Assuming that is the case the next step, of finding a DAM which I can convert to from LR, is the real challenge. Lots of collections, smart collections and keywords to export/import which has proven to be a challenge. In many ways the DAM issue is the real deal breaker in adopting AP2 after LR/PS if you have a large portfolio. Rumour has it that if you stop your Adobe subscription you can still use LR as a DAM only (Library module)without all the other modules. If that is still the case that may well be the answer whilst using AP2 with tiff files. 
 
All good fun.
 
Thanks again for your input.
 
cheers
Martin
 
 

Agree with all the comments on this decision. Back in 2020 I had a very serious look at APV1 but after a great deal of investigation I decided not to switch for three reasons.
1) - insufficient luminosity/zone/colour/saturation/vibrance masks
2) - not convinced about the Raw Editor
3) - a lack of Affinity DAM and the lack of adequate .asphoto support in other DAM applications including Bridge.
Number 1 has been largely resolved and is in fact very good at first glance. Number 2 I'm still unconvinced. 
Number 3 though is now even more of a problem as the lack of support for the affinity file format is compounded by the fact that I cannot now even point Bridge at the .exe to get it to use it at the editor due to it not being visible. Add the fact that, unless there have been substantial changes since 2020 which of course may well be the case, I cannot find a DAM which meets my needs and it amounts to a deal breaker for me.
So, inspite of really liking AP V2 and thinking it is better in a whole range of ways than PS, I am probably going to uninstall my trial version of V2 as it is clumsy to use in the real, day to day, world, especially if, like me , you have grown use to the high level of integration I enjoy with the LRc/PS combination. This is such a shame as I really do want to make the change but slowing down my workflow from it's current position is not a positive step forward.
Please, please Serif. Get a DAM sorted either inhouse or by working with another software house. At the very least sort this Windows App v programme file silliness out. In the absence of either action I will abandon any thought of switching.

Agree with all the comments on this decision. Back in 2020 I had a very serious look at APV1 but after a great deal of investigation I decided not to switch for three reasons.
1) - insufficient luminosity/zone/colour/saturation/vibrance masks
2) - not convinced about the Raw Editor
3) - a lack of Affinity DAM and the lack of adequate .asphoto support in other DAM applications including Bridge.
Number 1 has been largely resolved and is in fact very good at first glance. Number 2 I'm still unconvinced. 
Number 3 though is now even more of a problem as the lack of support for the affinity file format is compounded by the fact that I cannot now even point Bridge at the .exe to get it to use it at the editor due to it not being visible. Add the fact that, unless there have been substantial changes since 2020 which of course may well be the case, I cannot find a DAM which meets my needs and it amounts to a deal breaker for me.
So, inspite of really liking AP V2 and thinking it is better in a whole range of ways than PS, I am probably going to uninstall my trial version of V2 as it is clumsy to use in the real, day to day, world, especially if, like me , you have grown use to the high level of integration I enjoy with the LRc/PS combination. This is such a shame as I really do want to make the change but slowing down my workflow from it's current position is not a positive step forward.
Please, please Serif. Get a DAM sorted either inhouse or by working with another software house. At the very least sort this Windows App v programme file silliness out. In the absence of either action I will abandon any thought of switching.

Interesting point as our visiting IT guy disabled the Store on all of the Win10 PC's - apart from mine as I'm the boss. So we'll stay with V1.
Funny how Adobe and Corel (yes they are still going) installs to the Program Files directory but Affinity are trying to convince folks that they had no choice. So please Affinity/Serif cease treating your customers as though they are dummies. There are too many experienced contributors around here so stop digging. Just man up - we made a mistake - here's the *.exe file.

Thanks Len. I was aware of that method to discover the full path but unfortunately that does no address the permissions problem. That is a swine as I am not sufficiently knowledgeable about current Windows versions to feel at ease altering security settings to enable third party programmes to read & execute. Sadly it is not like Unix which was a joy in that area.
 
The idea of creating a .bat file has some merit although I thought I'd left those behind years ago!. I also suspect that some third party applications will expect to be pointed at a .exe so will not accept a .bat anyway. 
 
It also, of course, still leaves the basic lack of a DAM although I fully accept that there are options out there. It is just that they involve going backward in terms of integration compared to how LRc & PS work together. Some people will be fine with that which is excellent but it is a deal breaker for me even though my first impressions on trying AP V2 are very favourable.
 
Hector

Agree with all the comments on this decision. Back in 2020 I had a very serious look at APV1 but after a great deal of investigation I decided not to switch for three reasons.
1) - insufficient luminosity/zone/colour/saturation/vibrance masks
2) - not convinced about the Raw Editor
3) - a lack of Affinity DAM and the lack of adequate .asphoto support in other DAM applications including Bridge.
Number 1 has been largely resolved and is in fact very good at first glance. Number 2 I'm still unconvinced. 
Number 3 though is now even more of a problem as the lack of support for the affinity file format is compounded by the fact that I cannot now even point Bridge at the .exe to get it to use it at the editor due to it not being visible. Add the fact that, unless there have been substantial changes since 2020 which of course may well be the case, I cannot find a DAM which meets my needs and it amounts to a deal breaker for me.
So, inspite of really liking AP V2 and thinking it is better in a whole range of ways than PS, I am probably going to uninstall my trial version of V2 as it is clumsy to use in the real, day to day, world, especially if, like me , you have grown use to the high level of integration I enjoy with the LRc/PS combination. This is such a shame as I really do want to make the change but slowing down my workflow from it's current position is not a positive step forward.
Please, please Serif. Get a DAM sorted either inhouse or by working with another software house. At the very least sort this Windows App v programme file silliness out. In the absence of either action I will abandon any thought of switching.

Thanks for the heads up on Neofinder.
Since my last post I have had to do a complete OS vanilla build plus all software so I am nice and clean again. Tedious but always a good idea. One spinoff from this was that it prompted me to look at ACDSee again and re-do the config/catalouge stage by splitting it into small chunks. This worked much better so I now have a full conversion from LR to ACDSee which has excellent speed, much better than LR. on that basis and also that it has so many options, few of which I have properly explored let alone mastered, I have purchased a copy at an offer price. 
So I am now Adobe free.
Loving AP and I am already liking ACDSee now that I have it set up correctly.
 
Grumpy Hec