Benege

I don't really know but it feels like a macOS thing. A search for "macos preview open pdf link access right denied" shows a bunch of results, some in the Apple discussions.
I did not get this access rights message in Acrobat Pro – but right now I got it when trying one of my test PDFs in macOS Preview. Then I tried the other PDF first and the message doesn't occur again + the links work, now between both PDFs (... as if Preview.app would have to "learn" first, though it doesn't make much sense).
Do the links in my uploaded PDFs work for you? If yes then take a look in the .afpubs to compare the ways the links are set.

If it helps for investigation, the attached Zip contains 2 .afpubs + accordingly PDF exports. Each of them contains a set of the 5 available Affinity hyperlink types, with the link on the text "file" in both PDFs pointing to the other PDF.   (ignore "cross reference" in the file file name, in fact it's hyperlinks only)
hyperlinks cross reference.zip

Ok I see, but if your cam/lens combination is recognized by that lensfun library which AP uses, then there maybe are also some lens profil data entries according to distortion corrections inside that. I mean things like these here from the GitHub project, though these entries here look much fewer than what the Adobe .lcp files in your video do contain as data:
<lens> <maker>DJI</maker> <model>Phantom Vision FC200 & compatibles</model> <model lang="en">fixed lens</model> <model lang="de">festes Objektiv</model> <mount>dijPhantomVisionFC200</mount> <cropfactor>6</cropfactor> <type>equisolid</type> <aspect-ratio>4:3</aspect-ratio> <calibration> <distortion model="ptlens" focal="5" a="0.02707" b="-0.10021" c="-0.09787" /> <tca model="poly3" focal="5" vr="1.0002" vb="1.0007" /> </calibration> </lens> BTW I've seen that this GitHub lensfun project also contains an entry for an Python3 app named lensfun-convert-lcp, which seems to allow to convert Adobe LCP files and their content to one Lensfun XML file, see here ...
 
 
However I don't know how much distortion information is used here from a .lcp file for those lensfun XML profiles. But maybe you can use that Python3 script in order to convert your "PHANTOM VISION FC200.lcp" into a better working lensfun XML profile file for AP.  Meaning you can give it a try, or ask in some drones forum etc. if somebody maybe already tried to do so and with what results, since that lensfun database is also used by other software than AP for performing lens corrections!
 
NOTE: that the above are just some points/hints to software related informations about that stuff, you must see yourself if it is of any help for you or not.

Hello,

does anybody know, if there is a possibility, to use Adobe Lens Correction Profiles (*.lcp) in Affinity Photo? I use an UAV (DJI Phantom 2 Vision+) for taking pictures. Because it has a fish-eye lense, i have to correct them, before i can use them (for taking measurements). Therefore, DJI has released an Adobe Lens Correction Profiles (PHANTOM VISION FC200.lcp). In Photoshop, i can open Filter / Lens correction and choose this file, to eliminate distortion from the pictures. Is there a possibility to do it in AP, too? Maybe with an Plugin?

P.S.: See the pictures below. They show the original picture (before) and the corrected picture (after). It is very important for me, that the exact values from the Lens Correction Profile are used, because afterwards, i have to take measurements in the pictures.
        Picture-Before:       https://www.pic-upload.de/view-32675627/before.jpg.html
        Picture-Afterwards: https://www.pic-upload.de/view-32675621/after.jpg.html

Best regards
Thomas

Hi @dominik,
Thank you for your reply despite this being an old thread. Your explanation and reply was very helpful!
Wonderful, I will look forward to trying this out and it definitely helps!
All the best,
chau

Hi All,
Unfortunately, we are hearing many stories from the creative community about how they are being severely impacted by the effects of the COVID-19 pandemic. We know we can’t solve a lot of these problems, but we do want to try to offer as much support as possible.
That’s why we’re announcing three measures that we've just put in place. They are:
A new 90-day free trial of the Mac and Windows versions of the whole Affinity suite A 50% discount for those who would rather buy and keep the apps on Mac, Windows and iPad A pledge to engage more than 100 freelance creatives for work, spending the equivalent of our annual commissioning budget in the next three months (more details of this will be announced next week). The introduction of the 90-day free trial and deeply discounted pricing is done in the hope that this will make life a little easier for people who rely on creative software to make a living, but may be stuck at home without their usual tools, or for students who might not have access to their Affinity apps on their personal devices. In addition, by increasing our spend on commissioning work from freelancers we can also put some extra money into a part of the industry which will be particularly affected. 
We plan to make the free trial and additional discount available until 20 April, but of course we will continue to review the situation as time goes on.
We have put posts on Facebook and Twitter about what we are doing if it's something you would like to share.
We're now all working from home
In terms of the team here, we have all vacated our Nottingham offices and are now working from home. Naturally this is causing us some disruption, but we continue to type code and expect to carry on making good progress with our development efforts. 
Support is a bit trickier though. Firstly, we can’t accept inbound telephone calls right now, and there are also going to be challenges for our staff to work their normal full-time hours – especially with imminent school closures in the UK. We’re obviously going to do our very best but hope you will understand if we are not as fast to respond to email as usual.
Of course, if a question you have is something which could be answered by our community, then we’d also greatly appreciate if you put that here on the forum rather than contact us directly. It would definitely help us out a lot. 
Frankly it’s hard to know what to say or do in this unprecedented situation. But more than anything else, we want to use this opportunity to wish good health to you and your loved ones at this incredibly difficult time.
All the very best,
Ash

Hello @Chaumurky and welcome to the forum.
This thread is relatively old. Own template files were introduced recently. This also works for master pages.
You would create a file with a couple of master pages you need. The document itself can be empty but it has to consist of at least one page. Then you go to 'File > Export as Template...' and save it to a directory of your choice.
In the 'File > New' dialog there is a button at the left side that reads 'Templates'. There you once add the folder where your template files are stored. If you then open the before created file with only the master pages in it you have these basically as a starting point.
I hope this helps 🙂
d.

While I like the new ability to create file presets, I consider that different from templates. A template file would have master pages, styles, and other important document aspects already defined. One can simulate that today by creating a file with those characteristics but without real data and saving it for later reuse. But true template files would be nice.

I have problems using master pages
There is a menu way to "show master pages" However it is always greyed out
I want to create a master page that I can then choose to use in a new file
Questions
1) Is there a way to produce a template file?
2) How do I import a Master page of my choice into a new file