illusie

hi, i did not try out everything new in version 1.8.1 (mac), but i immediatly tried to use luminar 4 as a plugin. and no, it didn't work. nothing has changed at that point since the former version. luminar is a rather popular piece of software, i would think. i almost can't believe it's ignored in this new version. regards jan

as far as i can remember, i had no problems with my x-trans raf files in earlyer versions of this beta. and in my regular affinity program it works fine too. i read that the problem will be fixed in the next update.

hi, the beta .112 crashes not only on raf-files, but on my jpg-files (generated from raf-files) too. there's no problem with tif- or dmg-files. jan

it seems i made a stupid mistake. i thought i was sure to be running the latest beta version of affinity photo, but i think it must have been my regular program. it's as MEB says: only dfine, viveza and both sharpeners work. and for instance my favorite silver efex pro doesn't.

thanks. your overview-graphic made me try again. and to my surprise: it works. i tried it just after i installed the new affinity photo beta version (1.7.0.109). but i think it's not the new beta that makes the difference. i presume it's the new version of osx i installed last week (macos mojave version 10.14.3). problem solved. thanks everyone for your comments.

i have the google nik version. payed 112 euro for it, a few years ago. bought the packages before google decided to give it away for free. i'm afraid i will have to spend another 69 euro since serif says it's something dxo has to fix.

i know the workaround, puck. i often use the nik filters as plugins in adobe lightroom. but using them as plugins in affinity makes it possible to assign separate plugins to separate layers. and in affinity photo i can assign filters to (different) selections. i'd like to continue working like that in my workflow. but when the affinity software developers do not implement the use of the current version of the nik filters, it will be the end of my favorite workflow when the update will be released. do we have to accept it, to be deprived of functions we had?

well, thanks a lot, affinity-builders. i bought my nik collection before the software was sold to google. though i paid approx. 100 euro's for it, dxo does not give me free updates. and now i can't use my favorite plugins in combination with affinity photo any longer after the update. what about backwards compatibility?

hi, in my affinity photo version 1.6.7. i use de nik plugin set. i'd wish more plugins would be compatible. i mentioned this long ago while testing earlier beta versions. but in this new beta i still can't get this done. but my more important complaint is that now my installed (see attached screenshot) nik plugin filters don't work any longer. when i select a filter in menu/filters/plugins/nik collection i get the message 'Updating fonts...' (see attached second screenshot). the only thing i can do after that is to violantly force affinity photo to stop. regards jan van de ven

hi, i don't think you're wrong. i have the same problem with the greater than signs in the page number fields when the imported .pdf file is generated by pages (and the page numbers are generated automatically). in my case i used the font georgia. in publisher i removed the page number text fields by hand. i thought the solution would be to make a master page with only a page number field and to apply i to all my pages, but that doesn't work. regards, jan van de ven

no, i meant what i said. but it's all rather complicated and there's this language barrier... let's call it a day and - following your advise - pretend it never happened, though that means i have to apologize for bringing up the problem in the first place.

o, o, next problem. after detaching the text layers, i can't save the file any longer. after closing it without saving and double-clicking it, it can no longer be opened in affinity publisher. see the attached screenshots of the warning messages. you might try this yourself unsing the file 'testbook-a4.afpub' i uploaded earlier in this thread. what exactly did i do with this file? after opening i selected the right master page (called 'rechts') i selected both text frames in the layers tab and clicked 'detach' in the symbols tab. i did the same with the second master page (called 'links'). then i did a cmd-s to save the file and i got the message 'failed to save', after which reopening the file was impossible (and of course it was not already open in another application) and eh... after that 'save as' doesn't work either. in the meantime i've set up a new document and tried all the things that might have occurred to the text fields (i.e. switching to symbols and back) and saving the document without any problems. so i think the file 'testbook-a4.afpub' must have been corrupted in one way or the other and i'm afraid we'll never fint out what caused this corruption.

i'm sorry, Chris_K, but i really don't know. in the above attachment i saved the history, but it's not the complete history. what i did wrong, i must have done wrong in an earlier stage. until now i wasn't even aware of the use of symbols in affinity publisher. seems to be a powerful tool though. who knows, my cat did step on the keyboard of my imac when i looked the other way, as was suggested earlier in this thread. after detaching the text fields as symbols, the problem seems to be solved, but i can't get rid of the orange lines next to the text fields in the layers. don't they show the text layers still are behaving as symbols?

but who says my mistake (if it is a mistake i made) could not accidently be replicated too in some way?

and yet... here i'll attach the document that causes the problem - and still does. it's named testbook-a4.afpub. i saved the history with it. i was able to retrieve it from my time machine. as i send it, the right master page (rechts) is as it should be. now double click the left page (links). you see the text frame and page number frame too far to the right. try to correct this by aligning them to the left of the photo frame. oké? now double click the right master frame again. and what do you see? both text frames have moved in the same way you moved the frames of the other master page. try to change the text in one of the frames and you'll see the same change in the frames of the other page. i'm not sure if this is caused bij some mistake i made, but i really don't know what mistake that might be. the problem doesn't occur with picture frames. testbook-a4.afpub

i just made a new book. exactly the way i did before. but now i can't seem to be alble to reproduce the problem. everything works as it should. my mistake, i presume. my apologies for bringing this up. case closed, i hope.

i'm using the same version on my imac.

i just created a new but related topic: i tried this work-around to create mirroring pages, and found this problem.

hi, duplicating a master page in publisher includes duplicating the behavior of the text frames on that master page, i experienced. the situation: a master page with a photo frame, a text frame and a page number. it's a right page, text frame and page number aligned to the right. now i duplicate the master page, alight the text frame and the page number to the left. but on the original master page the same happens. the text frames of both pages seem to be corresponding in some way. my work-around is creating a new page and placing new image and text frames mirroring the first master page. but that is rather laborious. anyone else experienced the same problem? or is the behavior of the frames done on purpose? why? regards, jan van de ven

this only works for elements on a page, not for the page itself. i'm looking for the possibility to mirror the full page (i.e. the master pages), grid and guidelines included, to get exactly symmetrical pages. i can't find that option in affinity publisher.

i just heard from my publisher that the problem is solved after i selecte all text seperately and for every selection ste the ligature on off. in the main menit would be handy to have an option to turn all ligature in any text in the document to 'off' in the main menu.

i'm not an expert. i don't know where to find the specifics of my georgia version.

ah... i only changed 'ligatures' in the main menu (menu/text/ligatures/use default). i'll have another try following your sugestion.

turning ligature off does not help in my case. the ff's still disappear on my publisher's windows machine.

hi, i made a document in publisher using 'georgia' as the standard font. after exporting it to pdf, i shared it with two windows users. they both were confronted by the same problem with words in which a double-f occurred on their screens. the ff's were replaced by spaces. no problem whatsoever on my iMac, iPad of iPhone. it wil probably only occur on windows machines. i don't know if it's a affinity publisher only problem. maybe it's caused by the font itself (or the translation of it by windows machines). but i thought it might be useful to mention it. i'll attach three files: booklet.afpub, booklet.pdf and 'example as seen in windows.png'; booklet.pdf is the export to pdf from within affinity publisher. the .png file was sent to me by one of the windows users. kind regards, jan van de ven booklet.afpub booklet.pdf