NathanC
-
Posts
2,738 -
Joined
Posts posted by NathanC
-
-
Welcome to the forums @Rentner,
I'd like to see if this unresolvable sandbox error can be reproduced internally, any chance you could send us a copy of the file, along with the resource? I've included a private upload link below if you don't wish to share the document publicly.
https://www.dropbox.com/request/yRvd9SEeFSnjDZM8MJvK
Thanks
-
Hi @Sulsa,
If you've got a display with a dedicated G-Sync module i'd suggest turning this off completely in the Nvidia Control panel, as this can cause the app to flicker and stutter.
If it persists could you upload a screen recording demonstrating the problem in the app? The FAQ below details some methods to record.
-
Hi @George UK,
There's a known issue in 2.4.0 on Windows which has been recently logged regarding images printing out with a red tint which can be perceived as an increase in saturation, this can occur in CMYK documents which contain RGB images so it's possible that you're encountering this issue.
This bug is a regression and as such is not present in the 2.3.1 app, so to confirm if this is the issue you're seeing you could remove your existing app version via Windows Settings > installed apps and then install V2.3.1 available from the link(s) below under 'Previous versions'.
-
Welcome to the forums @Brian Alexander,
Can you confirm at what point you're encountering the crash, does the app start screen appear at any point, and if it does is it immediately closing or freezing or does nothing happen at all?
If you go to Windows Settings > Windows Updates > Update History could you upload a screenshot of the updates list that shows your most recently installed updates? I've also just updated Windows 11 to the latest possible version but I'm not running into any app crashes on startup in the MSIX or .EXE version of the apps.
Also, from the Update settings could you check if you're part of the insider program?
Finally, if you could provide any recent crash reports generated from the app since you've had this issue that would be great, the FAQ below details how to find these.
Many thanks
-
10 minutes ago, Cloudfactory said:
Thanks for your reply! I already cleared all background apps and rebooted in several ways. I am going to upload the File. Do you need the resources as well? What do you need, to recreate this behavior?
If you could send the file over in addition to the external resources used that would be best.
Many thanks!
-
Welcome to the forums @User1773,
It's possible that you are running into the Hardware/memory limitations of your iPad, 400+ pages is certainly a large document and if you've now reached 900 and also included images and embedded resources this will put more strain on the device. We do generally suggest closing all background apps running on your iPad but you've likely reached a point where this is irrelevant due to the sheer size of the document. If you could provide the document this will help confirm if this is the case, I've provided an upload link below.
https://www.dropbox.com/request/vFTxQ6lifuFuHRw7ZMOF
----
Welcome to the forums @Cloudfactory,
I'd start with just rebooting your iPad and clearing the background apps active to confirm if that allows you to work in the document, and if not feel free to upload it to the link below and I'll take a look.
https://www.dropbox.com/request/fbSBnz9XvDqb89ihw577
-
Happy to hear that it's all working again, to be honest at this stage i'm not sure what's causing this as I can't replicate it but I do have another user who's also encountering a similar problem, i'm waiting to hear back from them. I wouldn't put it past iCloud to be involved if it's been syncing, in System Settings > iCloud > Photos what was your iPad set to, Keep originals or Optimise storage?
Can you recall anything else being done on the iPad since Sunday? If not no worries 🙂
-
Welcome to the forums @Thrawn,
Has this only started happening since the 2.4 update and can you confirm what IOS version you're running?
On 3/3/2024 at 7:44 PM, Thrawn said:Going to privacy and setting for photo there is no way to change affinity photo away from private access.
Apparently there's a bug in IOS 17 relating to this as it affects a number of apps. On one iPad, Photo 2 allows me to freely change between full access and None/Private Access in the System settings, but on another IOS 17 iPad we have it's not allowing it to be changed in the system settings, but regardless of this setting i'm still able to freely import photos into the app on both devices. I've linked the post on Apple's community page below for reference.
https://discussions.apple.com/thread/255145186?sortBy=best&page=1
To confirm, is the problem specific to RAW files or if you opt to open a standard HEIF/HEIC/PNG/JPG file stored in your library, does the same error occur? Have you got your Photos synced to iCloud, and if so is it set to optimise or download and keep originals? This can be checked in System Settings > iCloud > Photos.
I'd also suggest performing a forced restart as this can occasionally resolve unusual errors, FAQ containing instructions is linked below.
If the error persists, Could you possibly capture what happens on a screen recording when opening from Photos?
Many thanks
-
Thanks @Demys I've now updated the issue internally to reflect that it's still a problem in the latest version for the attention of the devs.
-
Hi @Hangman,
It looks like the devs need to have further discussion internally regarding the State panel's interaction with master page elements so they've requested this to be logged internally which QA have now done. At this time I don't have any more info/details to share but i've tagged the thread and dependant on what the outcome is we'll report back.
-
Welcome to the forums @Fred Grube,
Unfortunately the brush artefcating issues shown in your screenshot/recording is a known bug in V1 and IOS 17. The issue is fixed in the V2 iPad apps but is still unfortunately outstanding in V1 with no known workarounds. I'll bump the existing issue with your report.
-
Thanks for sending the profile over, i've ran the check and have observed the same preflight error, and I believe this relates to the original sRGB profile used by the images in your document. Image layers retain all their original data, which includes their own embedded colour profile which remains intact on export provided that 'convert image colour spaces' is not checked in the PDF export settings, which isn't enabled by default on the PDFX3 preset.
Take the image below for example, this is flagged by the preflight check as a 'noncomplaint version 4 or newer' ICC profile on the X3 check as the image is sRGB 2.1.
If I inspect that image's metadata outside of Affinity I can confirm the profile v4.3.0, and since the image colour spaces are not converted on export to PDFX/3 this sRGB colour profile data and version is just maintained on export for that image. The app doesn't have the function to automatically convert the v4.3 profile to a v2 profile on export, this would need to be done manually by converting the images to a compatible V2.0 profile first, such as 'sRGB2014' (https://www.color.org/srgbprofiles)
If 'Convert image colour spaces' is checked this converts all images within the document to the document output profile, which likely wouldn't be desired on a document like this. In addition there is a known bug on PDF/X formats which prevents selecting RGB colour profiles, but this will hopefully be fixed in a later version.
-
Thanks both, I still can't re-produce on my Mac from opening the RAW files provided however we do now have it logged internally with the developers as the issue is visible in a developed .afphoto file which is a linked RAW layer found in the linked thread below. I've now bumped the existing issue with your report. 🙂
-
Hi @Grum,
On 3/2/2024 at 11:40 AM, Grum said:1. Double-clicking a file in the Finder doesn't switch to the application's Space so it seems that the file hasn't opened.
Thanks, I can also replicate this so I've updated the existing issue internally and bumped it with your report.
On 3/2/2024 at 11:40 AM, Grum said:2. Dialog boxes occasionally don't appear when in full screen mode.
I've not been able to re-produce this in fullscreen mode so far so it will be quite tricky as you say to get this logged, i'll keep trying a few things but if you do notice anything which can cause this to happen let me know. 👍
-
Welcome to the forums @renerowland4,
On 3/2/2024 at 1:54 PM, renerowland4 said:then the screen suddenly starts flashing black or the screen gets really pixelated whenever I move my mouse
This is likely to be hardware related, if you've got any overclocks applied (RAM,GPU,CPU) this is a sign of system instability so i'd suggest reverting them to stock settings and also doing a refresh of your Graphics card drivers (links below dependant on the model).
I'd also suggest disabling Hardware Acceleration in the app under Edit > Preferences > Performance and then restarting the app for it to take effect and then see how it goes.
-
Welcome to the forums @JSP75,
Some users are experiencing artefacts on RAW files in the develop persona following an upgrade to 2.4 when OpenCL is enabled, so perhaps your problem is related. I'd suggest unticking the setting (last checkbox) under Edit > Preferences > Performance and then closing the interface and restarting when prompted to see if it occurs going forward.
-
Hi @robrecord,
Without the problem/affected document or a recipe to replicate the problem from scratch with it's going to be quite difficult for us to look into this further and get it logged with the devs unfortunately. If it's that you do not wish to share the file publicly that is understandable, though I can provide a private upload link.
-
Willkommen in den Foren @Dennis Schmidt
Das kann mit der Liste der letzten Dokumente zusammenhängen, dass die App immer noch auf das alte Laufwerk verweist, wenn Sie auf Datei > Letzte öffnen > Menü löschen gehen und dann neu starten, um zu sehen, ob das die Meldung verhindert.
Ich sehe, dass Sie V1 verwenden. In V2 gab es ein bekanntes Problem mit dem Hinweis auf ein nicht verbundenes Netzlaufwerk, das behoben wurde, aber die Datei mru.dat gibt es in V1 nicht (zumindest nicht an derselben Stelle), so dass es nicht dieselbe Problemlösung gibt.
-
Thanks for sending over your files, although I don't have the PDF/X-3 preflight profile used in your last screenshot, is it a custom profile that was imported into Acrobat? I can see that your document is just using the standard U.S web coated SWOP (V2) as the output profile which to my knowledge is supported, which makes me think it's something more to do with the preflight profile used in Acrobat.
If you could upload a copy of the exported profile to the dropbox link as well that would be great. You should be able to do this by selecting the Preflight profile > go to options at the top right > export profile > save the .kfp profile and upload it to the link.
Thanks
-
Hi @GrandadC,
RAW file format support and specific lens correction/profile support are separate from one another, the 2.4 update added RAW support allowing for files from the DJI Mini 3 to be decoded and imported correctly into the develop persona, but this doesn't necessarily mean the specific lens profile used on that Camera will be available.
Lens profiles for correction are provided by a separate 'Lensfun' database which is also updated periodically with the app, but it's also possible to manually update your lens profiles to ensure that you always have the most up to date profiles from the database, the tutorial below details how to do this (It is for V1, but the same process applies to V2).
1 hour ago, GrandadC said:I now assume I need to wait for FC3682 & compatibles to be added to the lens profile list ?
I think this will be the case unfortunately, as I can't see this lens profile listed in their current supported lens profile list even if the above manual update was done.
-
Hi @waltonmendelson,
On 2/29/2024 at 12:47 PM, waltonmendelson said:Exporting to PDF (Digital High Quality) converts linked JPGs to images with transparency.
The Pre-flight check in your screenshot is picking up on Images that exist as a part of a transparency group, exporting to transparency supported version such as PDF 1.7 appears to always export out with these non-knockout transparency groups applied to images if there is an object which exists on that page which is transparent/has partial transparency or a blend mode applied applied. This doesn't necessarily mean the JPEG image on the page itself is transparent.
The adobe community post linked below has more info on this.
Acrobat's preflight separates out semi-transparent images into a separate 'filled object with constant alpha value smaller than '1.0' subsection and images with a transparent background in a 'soft mask in image' section.
On 2/29/2024 at 12:47 PM, waltonmendelson said:PDF/X-3 is not PDF/X-3 compliant
The preflight error appears to relate to the use of a non-compliant ICC profile on elements throughout the PDF file, so we can investigate further could you possibly provide a copy of the exported PDF and original .afpub file? I've included an upload link below.
https://www.dropbox.com/request/TccpXZZ76MzWSXsTUcHu
Many thanks
-
Hi @oskar3579 @Helmi Amirudin,
Any chance you could provide a copy of the .afpub file where you're running into this export failure with Tagged PDF enabled? This will help us confirm if it's related to an existing bug with the tags function, or something new which needs to be investigated. I've provided a private upload link below if you don't wish to share the file publicly.
https://www.dropbox.com/request/3CW78yaOtfG5VrpvV1sr
Many thanks
-
Hi @Phree_ed,
I'm not seeing this on a Monterey mac when opening a sample RAW image from the EOS R7 on Apple core RAW, it loads in full colour as expected. I've also checked this on a separate M1 Mac Mini that was running Sonoma with the same expected result.
Could you confirm if the same occurs with Metal compute turned off in Preferences > Performance? Chances are it will be the same result, but just want to confirm if metal compute is related.
In addition, could you provide a few sample RAW files where you're seeing this? I've included a private upload link below if you don't want to share them publicly.
https://www.dropbox.com/request/OEqwXwLEPogsQSUTw6Bv
Many thanks
-
The RAW Camera support list was updated to include RAW support for the newer iPhone models but this is completely separate to the supported lens correction list which can be found below. This still only lists the XS and XS (Tele) as supported corrections, is it possible that you have the two confused?
Shortcut's are not working the same in 2.4
in V2 Bugs found on Windows
Posted
Hi @calebcudjoe,
This does look like a localised issue, as I also cannot replicate a problem with chaining shortcuts one after the other in 2.4 in either the .EXE or MSIX version. However, it is quite unusual that there's no issue in v2.3.1 in the same environment.
Have you tried limiting all background apps open to just Photo 2 on 2.4 to confirm if that permits the shortcuts to function? To help rule out any local user issues you could also try creating a temporary windows user and seeing if the issue persists on that user.