CliveH

If you know and like Bridge then why not continue to use it? You can get it without a subscription and link to Photo as your editor.

FWIW - I've just downloaded 2.4.2 and tried opening some old RAW files. A quick sample from an old Minolta camera (.MRW files), Canon 20D (.cr2) and Sony cameras (NEX-7, A7 and A7R IIIa - .arw format) all seem to work fine. OpenCL is on.

It seems more than premature to be talking about switching to other (non-subscription) products when we don't know what the future will hold. I prefer perpetual licensing but in the end you have to evaluate what something is worth to you. I have a universal licence but also an Adobe Photography Plan because the (under £10/month) is worth it to me for access to Lightroom (I use Photo not Photoshop for more in depth editing). What surprised me a bit is the use I make of Designer and Publisher. I'm a photo enthusiast so bought Photo initially but with access to the full suite I make use of it to design posters, produce a printed book etc. I don't use these every day but they are useful when I want them and I happily paid the price to get them. As an amateur user though it would never be worth it for me to pay a subscription at Adobe level for access to equivalent products. I wish all the Affinity staff well and hope that they continue to develop affordable products for many years to come. If the business model does turn to subscription in future then I will consider at the time whether it offers me good value for money or not - and if not then I will sadly have to give up. But, for me at least, it is about value and not just the principle of perpetual or subscription.

There are PDF files available on the learning section of the main affinity website which summarise the gestures that can used with the V2 apps. My main usage is the desktop versions with only occasional iPad use so I thought it would be very helpful to print out the gesture guides as I don't use them often enough to memorised them. The problem is that they are very low contrast and so almost unreadable when printed. I can darken the images etc to make it better but I can't be the only one seeing this. Am I missing something or do Serif just need to make them more legible?

It doesn't just relate to IDML - can also come from re-sizing a frame in a way you don't expect. Reapply text styles didn't work for me - Joe's method 2 did: copy all the text from the linked frames, delete and then paste back. See this thread for more info:

OK - I'm hooked. Where did this come from?

I just wanted to note that the latest change to the aflauncher.exe now works fine for me with Lightroom 6.14 - and, yes, all the paths to my image files have spaces in them so the new version has addressed that. Thanks to Serif staff (and others on the Forum) for helping to quickly sort this.

@Mark Ingram Sorry but just tried this and unless I'm doing something wrong it doesn't work with Lightroom 6.14 (last perpetual version - I'm still hanging onto that hoping for an Affinity DAM). Like theDakota it launches Photo2 but then just gives a series of failed messages. The only thing I've found to work is Walt's BAT file. Clive

I'm not an expert Gracie but I don't think you need to do that (or abandon Affinity for this). Can't you just select a group of images for an HDR in Lightroom, then export these as tiff files to a temporary folder? After that go into Affinity choose New HDR merge and just select all the exported tiff files from the single folder. That way your image selection is done in Lightroom and the stacking is easily done in Photo.

I can't say why it worked on one document but not another - perhaps a video to show what you're doing? On my system, if I have a text frame with too much text in it I have the red triangle displayed. Clicking on that triangle gives me basically two options: clicking in another text frame will flow the text into that frame, or click dragging on a page will create the text frame and flow text into it. Note that if the text overflows the second frame as well that will just show another red triangle and you'll have to repeat the process. Alternatively shift-clicking on the red triangle will autoflow the text - creating new text frames (as many as needed to contain all the text) and flowing text into them.

You need to set up a text frame before clicking into it (unless you use auto-flow). See this post regarding the change in text size

Have a look at this topic: Basically you've probably adjusted one text frame using the wrong handle (easy to do) which affects the formatting. Easiest way out of it is to copy all text in the linked frames, delete the text then paste it back in when it should be correct. Clive

Not that I've found. But if you copy the text, delete the text frames, re-insert the frames and then paste your text it should be sorted - or you can auto-flow from the first frame if that will work in your layout. Hope that helps.

Have a look at this thread:

In addition to the above, what happens if you open Designer and go to File ----> Open Recent? That should show you a list of recently used files - if it does then can you access them that way?

I had this problem today and the solution from Old Bruce seems to have fixed it (thanks!) but I don't understand why it occured in the first place. I have no recollection of using that resize handle (although the document is something I've been working on for a while so it's possible I did) but regardless is there some reason why it works in this way? It feels like a bug to me (as the text is clearly not respecting the format I've applied) but would love to know if there's a reason for this behaviour and if there's anything I can do to stop it happening in future (other than being extra careful not to use that handle). Thanks

I just wanted to add my comment here. Until I saw this topic I had never understood why, despite setting my language as UK English, the spell check worked on the US flavour (with a 'u' of course!!). Now at least I know how to change this but it's very cumbersome (and I'm not a power user). I get that some documents will have paragraphs (or even sentences) with different languages - so putting Language under Character has some use. However, I don't understand why I would have to go into each Style that I've used in a document and change US English to UK English, and do this for every document. When I've selected UK English under Preferences surely that should set the default for each text style in each new document to UK English (rather than the US version it now imposes on me). This feels like a bug to me - that the default for text styles in new documents isn't inherited from the Preferences language - but if it is working as designed then it seems extremely unusual design. Clive

Thanks for the feedback. This document did originate as a pdf file so maybe that's the underlying issue. I'll try setting it up again.

I have a problem with formatting text which occurs a few times in a large document. I haven't been able to pin down what causes some linked text boxes to have the problem and others not but the attached afpub file consistently shows the problem. The document has two pages with a text box on both pages and the second box linked to the first. The final paragraph on the first page exceeds the space available and so spills onto the box on the second page. This final paragraph is intended to be all body text (with a style set up for that) but as you can see the first two words (The designated) show a paragraph style of 'body+' and the font size is increased. If I place the cursor in those two words and apply the 'body' paragraph style the whole paragraph is set to body style - except for the words left on the second page which now have a much smaller font. If I then place the cursor in those words and apply body style they increase to the correct size - but the first two words in the paragraph again have their font size increased. It doesn't seem to be related to the specific paragraph - if I insert more text on page one (so that the whole of this paragraph is 'pushed' onto page two) then it is formatted correctly in all body style but the paragraph which is split between the two pages shows the same symptoms of different formatting. This is on Win 10 - Pub version 1.7.3.481. I've also tried on the latest (518) beta and get the same behaviour there. Am I doing something wrong or is this a bug (and if so any ideas on a workaround)? Thanks Clive Test doc.afpub

The thread referenced by Psenda suggests that this is a historical issue which has been resolved. However, I've just checked and found recent autosave files in those folders (for all 3 products) despite not having had a recent crash and each product having been successfully opened and closed several times without problems (all on 1.7.3). It seems that there is still something odd going on if I have files only a few days old still hanging around (as well as some from much longer ago).

I think that it's very unlikely that anyone can help you until you've provided more information. Which Affinity product are you talking about and what are you trying to do (if updating then which versions are you trying to go from and to)? Exactly what is the error message that you are seeing? Where does 64 bit come in? Newer versions of Affinity products won't work with older releases of Win 10 - have you checked that your system meets all the pre-requisites for the version of the product you're trying to install?

Hi Longtimer, your original problem is hard to diagnose remotely - you've had a few suggestions which haven't worked so need to keep trying until you find the cause. For example, you are saving onto a USB connected drive - but does it work correctly if you have a file on your main C drive? If a file won't save to your USB drive, can you open one from there (download an afdesign file from these forums if you don't have one that you know is not corrupted). You say you can see an icon for the file in explorer but have you looked to see what the file size is (as an indication of whether or not it is corrupt)? Have you tried creating a very simply file in Designer (eg just a square or circle on a background) and then tried saving that? Your problem is not a common one on these forums so seems likely to be something to do with your specific set up - unfortunately it just means trying lots of different things to narrow down what the underlying cause is. Alecia - sorry but I've not had to use the file recovery so can't help you with that.

Bob, Affinity is working very similarly to other applications (eg Word). If you go to File - Open, it will bring up a Windows box for you to find the relevant document - in this you would navigate to the folder where the document is and then click on the document to open it. I'm not aware that the files used in the instruction videos are available for general use, so you probably won't see that particular file - however there are some sample files you can download from the Welcome screen (go to Help - Welcome if it doesn't show automatically on start up) - these would open into Designer, you can then Save them to a folder on your PC and then open them later (using File - Open). Other ways to get files would be to create them yourself (start with File - New) or download files that others have created from the internet (some can be found on these Forums in the Resources section). Finally, if you want to follow instructions to make changes on a demonstration file then perhaps getting the Designer Workbook would be a good idea? This gives you a number of projects to work through, and has links at the start of each section to download the files used. You can then work through the instructions on the same file.

If you aren't that great with computers then I would wait until the release version comes out and not worry about the Beta unless you have a desperate need for a new function it offers. Beta's are generally only suitable for those who are more comfortable with the software and who don't mind coming across (and helping to diagnose) the odd problem that may still exist within the software. Hopefully by the time the Release version of 1.7 is available, the bugs that you might come across will have been fixed. Clive

The size of your image (shown at the top left) is 160 x 120 pixels so it is, understandably, pixelated and it does not look like an Affinity problem. Where did the image come from? If a jpeg from your camera have you got it set to an extremely low quality setting? You should find that if you open a higher resolution file that you don't have the same issue. Clive