Jump to content
You must now use your email address to sign in [click for more info] ×

Search the Community

Showing results for tags 'Bug'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.4 New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Member Title

  1. Hi there. I have posted before and even got a tech to look at the problem, but no joy, so hoping the community can help. I scan images using an Epson graphic arts scanner. The images are 48 bit depth, uncompressed TIFs, typically about 1 GB off the scanner. I edit in Affinity and have done so through both Version 1 and 2. FIRST: my latest image, same parameters as described, has caused Affinity to choke twice, as I near completion in editing (which takes WEEKS). The file tries to load, and then I get a message that reads "failed to load document, document appears corrupted" Here is the response I got: "Hi Sandra, I just wanted to let you know that I've downloaded your file. It also fails to open for me, so I've logged it with our developers to see if anything can be done. However I can't give any timeframe as to when this may be. In reference to your other post and files getting larger, when this occurs try using File > Save As to create a new file. As this process should get rid of anything not being used and streamline the file." So I started editing it again, and again, near completion, Affinity has choked. I have a Dell Precision laptop, 32 gigs RAM, 2.57Ghz processor. There is no reason that affinity should be choking on this. I have worked on scores of similar images. SECOND: (and alluded to in tech response above): the uncompressed TIFs come off the scanner at just under a GB. But as I work, the image bloats to 5 or 6 GB. I tried the advice above, of saving iterations under different names, but they are ALL bloated. Why does this happen? I thought maybe all the history was saved with every edit, but not so. I don't work in layers either - the document is flattened. I do need to routinely zoom to 400% for editing (painting in a true black back ground with the clone tool, using a WACOM tablet and stylus). So. Any advice? Now Affinity got bought by Canva, let's hope it doesn't do a Boeing. Please advice why current version of Affinity chokes on large files, and how to stop the constant bloat in size. TIA.
  2. Affinity Photo recompresses JPEG images when metadata is edited even though the image itself has no changes. Steps: 1. Make a copy of a test JPEG image as backup. 2. Edit metadata in one copy of the image in Affinity Photo. 3. Stack before and after images in layers and view as Difference.
  3. Hi everyone, I was working on a project for a client in Affinity Designer 2.4.0, and suddenly, while I was testing different fonts for a logo, it crashed Windows 11 (blue screen of death). When I restarted the computer, Affinity Designer didn't open the file anymore, stating that it appeared to be corrupted. I'm a professional branding and packaging designer. I charge hourly, and I've already worked 15 hours on this project. In other words, this file is extremely important, and I need someone from the Affinity team to jump in and help me urgently. I've attached the file to this message. Please, anyone, help! Thank you in advance. Tres Five logo.afdesign
  4. Screen Recording 2024-03-10 at 14.49.02.mov Same for cog tool and probably others. V 2.4.
  5. Applying the states takes almost 5-7 minutes! I have to mention that I have 16067 layers.
  6. - looks like Smudge tool still not working when applied on pattern-layer. Instead of smudging it add more and more original background color. Steps to reproduce: create pattern layer and fill it with random color. Then apply smudge tool, - instead of no-changes observe white (original document background color) stroke: early report for v1: Note that Blur-brush tool have similar issues when applied on/close to pattern border area.
  7. Problem: When exporting to TIFF, any of the Subject, Tags, Comments metadata fields are corrupted (changed to Chinese characters). Usually the Subject and Tags or the Subject and Comments fields are corrupted depending on scenario. Steps (Scenario 1): 1. Add metadata tags to a TIFF file in File Explorer. 2. Open in Affinity Photo. 3. Export to TIFF unaltered (with ZIP compression). Steps (Scenario 2): 1. Add metadata tags to an image in Affinity Photo. 2. Export to TIFF (with ZIP compression). Steps (Scenario 3): 1. Add tagged TIFF files to Batch process in Affinity Photo. 2. Use Batch process to export TIFF files unaltered to TIFF (with ZIP compression). The goal of resaving the file with ZIP compression is to workaround the bug in File Explorer that saves tagged TIFF (Zip) as TIFF (LZW) at about three times the size. However, I currently have no editors available that can save a TIFF file with metadata intact without corrupting it (this is also a bug in all Adobe products last time I used them, which was quite some time ago, and the reason I would attempt to use File Explorer to add metadata after editing). Side discussion: Compression is an interesting problem. On top of the metadata tagging in File Explorer roughly tripling the file size by converting to LZW, simply embedding a TIFF in an AFPHOTO file roughly doubles its size, and if the layer is rasterised with no modifications whatsoever, the AFPHOTO file doubles in size again (even when saved as a fresh copy to compact it). All of this adds up to massive (and expensive) storage waste. They say storage is cheap, but it isn't cheap enough to want to buy three times as many hard drives at several hundred dollars a pop to do the job of one. For the sake of not sharing family photos, examples are a frame exported from Blu-ray movie for desktop wallpaper. Tags made up to be "typical" (with Unicode characters). [Explorer bug has been reported to Microsoft.] export.tiff original.tiff
  8. Handy Pinning panel is listed in Studio/Text but it seems it does not exist in (exceptionally badly done) Shortcuts settings. Anyone knows where did that little Pinning rascal go?
  9. I have uninstalled and reinstalled Affinity Designer v2 multiple times. I have tried to repair, reset, and even uninstall the old apps to figure out whats wrong. I do not have this issue with affinity photo v2. The moment I hit "export" on Affinty Designer v2, the entire program freezes and will no unfreeze so I have to kill it in task manager. I can open the same files and export them just fine in Photo, I don't know what the issue is. Please help! (I have been using affinity products for years and this is my first issue I have had with any of the programs)
  10. Hi I have tried to stack different light files with different kinds of settings. But they all keep stopping a third into the stacking and nothing furter happens.. Anyone else having this problem? Best regards Lars
  11. I'm having some trouble with cross-references in an Index. I have one cross-references (where in the index it says See and shows another index item) that doesn't show up in the index at all. I have many cross-references that show up in the index, but instead of saying See and showing the name of the other item, it repeats all the page numbers that the other item has. And then finally I have a few that properly say See and show the other index item. How do I get them all to display properly?
  12. EDITED to make clear file 1 and file 2 remained open the whole time, at the same time. Still think the problem is with the "embedding" logic. EDIT 2: now I understand the resource manager correctly, I can clear that description up... Designer 2 version available as of today, 2.3.1 methinks, MacOS 13.latest Ventura intel 2019 MacBook Pro 16inch 1. Open ai file download from domestika.org design course 2. Save to native file .afdesign we shall call this file 1. 3. drop in .psd files 4. make some art boards around all the assets (those already in the file, and those dropped in as PSD's) SIDE NOTE on STEP 4: (weirdly the objects within the ai file didn't appear to have an artboard at first opening in designer, a black bg in designer around all the files, but then dropping in new psds, they were only visible in the overlapping area with the including objects, invisible if dragged off the overlapping area of the original objects. So I had to make an artboard around them, then the document bg became gray (I later changed this since I didn't like that) but then I noticed in layers panel, there was only 1 artboard, the one I had created.... weird to me that there was an invisible "implicit" artboard from the original ai conversion/import? Let me know if this is supposed to happen? I have LOTS of ai files to deal with (as I'm sure we all do, sigh)... not just this project. 5. make a new design file, we shall call file 2, with several artboards 6. copy (command-c) one of the mb? embedded psd's in file 1 (resource manager lists the path of original file), but, "make linked file" is not available.! 7. paste into file 2. 8. click away until I am using pixel persona tools on the pasted in embedded file in file 2.... unfortunately, all changes I make there ALSO affect the embedded psd object in file 1. 9. confused I open resource manager in file 2 now. it shows the path of the same original psd object/file supposedly "embedded" in file 1.... Again, I cannot "make linked file", its grayed/ghosted/not available. But resource manager already considers it embedded in the file list, just as in file 1... on the other hand, since designer thinks it's correctly embedded, I cannot MAKE it actually embedded. So files can neither be properly embedded, nor linked in these two files. I played with another new afdesign file, dropped a jpeg in there, and it's fine, it says embedded, but the "make linked file" IS AVAILABLE. In the meantime, I will simply drop a new copy of the file from finder... but that sucks... b/c I Did some work already on a half dozen such objects in file 1.... which now is not copyable without "linked" editing behavior... I've done my best to be clear here. Hopefully this can be explained, or if not, squashed like a bug! Thanks for giving adobe a run! Things like this sorta suck though... sad face...
  13. I am having difficulty adding a rectangle as a background in Publisher. It appears to be impossible. I have checked the settings, but something seems to be amiss. The white background behind the text is preventing me from seeing what is behind it. There might be a bug causing this issue. This situation is quite frustrating. CleanShot 2023-12-19 at 08.40.28.mp4
  14. I'm using Affinity Publisher 2 on windows but the issue is with the entire Affinity line. I got this free font Aquire Free Font - Download Free Font (befonts.com) Inside the software the font is rendered like this But after export to pdf for example it looks like this The font renders without letter spacing in other programs as well. It's only Affinity issue. What could be the problem? Is there any setting I can change to fix this? This makes the software basically unusable because the final exported image never looks like the edited image...
  15. Hi, I'm Rawi, I usually draw illustrations for cars. there is something in my designer affinity today I don't know why this happened, before I updated to 2.3 it was safe for the shape builder tool. I used to select all the lines then tidy them up with the shape builder but after I updated to 2.3 I can no longer do that. and not just the shape builder tool, when I use the feature to fill in color it just doesn't work even though it could before. I hope to find a solution here.
  16. I have noticed that many times when I have multiple objects close to each other they seem to have a small gap when I zoom out. I just now zoomed all the way in and there appears to be a gap. This occurs both when I have the "Move by whole pixel" enabled and disabled in the snapping tool. Here you can see a small gap when I am zoomed out and when zooming really really close you can see the gap be there clearer . Does anyone know why this issue occurs and how to set up the settings to eliminate it. I know the issue goes away when I export the image since the gap is less than a pixel wide but it is annoying not being able to preview your picture without exporting it.
  17. Hi everyone, I'd like to bring back a bug report that has been totally ignored since 2021, which I think is urgent and deserves to be discussed. Below you can find two very old threads talking about it. to summarize: the white balance tool is not working properly for non-raw files both in the develop persona and in the photo persona (through the adjustment layers). -what the tool should do: colour pick a pixel and equalize the RGB values to convert the colour of the pixel to a neutral grey (RGB values equal to each other) then apply the same RGB shift to the whole image. -what the tool really does: in develop persona with a raw file it works properly, when used on tiff, png, jpg (etc.) it does not work. What we observed: -the sliders in the develop persona with a raw file open are called "temperature" and "tint" and both of them are properly moved automatically when using the white balance tool, in this case it works properly; -however in the photo persona (white balance adjustment layer) they are called "white balance" and "tint", and only the "white balance" slider move when colour picking the image, we don't see why they should be called and behave differently since it is the same tool that already works properly for raw files in the develop persona. A possible way to fix the bug: -just apply the same rule applied for raw files (in the develop persona) also to non-raw files (both in the develop persona and photo persona adjustment layers). kind regards: Riccardo
  18. Hello, I find it very irritating that files which were edited with Affinity Photo and saved in .afphoto format are suddenly displayed as Affinity Publisher files, i.e. with the .afpub extension and associated symbol. When I click on the file, it automatically opens in the publisher software. But I 100% never opened and saved the file in question in Affinity Publisher. The whole thing gets even stranger: When I view the properties of the file, it shows up as an Affinity photo file! (See photo evidence). This is all totally weird.
  19. If you drag an image (eg: *.png) from a .ZIP file onto a document in Publisher v2.2.1 the application will crash. NOTE: Worked in v1.0. ***Also crashes in beta Publisher 2.30 (2114) MacOS: Sonoma v14.1.1 (23B81)
  20. I just updated to Affinity Publisher 2.2.1 and my styles are all messed up now. I'd like to revert back to 2.2. Here's the problem. All my text eg, titles, lists, paragraphs display as text using character style hyperlink blue. I use a lot of styles and I don't want to have to correct every single one. Please fix. Thanks.
  21. I've noticed that APu 2.2.1 tends to hang after updating modified images with the Resource manager. I can save the file (though it doesn't actually save the changes) and close the file. But after reopening I am prompted to recover the files. When I do that, the updates are no longer there. If instead of update I use the Replace option (I have to save, close and reopen each time), the file saves OK although a recovery option is still presented (I ignore it). I believe something is broken in the Resource manager.
  22. hi there, finally, with sweat and blood, i understand how the constraint group works, but i nothice 1 issue here, after i'm happy with my "CGroup" . i adjusted it and do stuff. and then i need just the background of this CGroup, so i went to layers panel, and i select the bg object, i copied, then pasted it . weird thing it didn't appear nearby, but after zoomed out a bit, the object become so big it covered the whole 2 artboard i made. thankyou
  23. To my surprise, I didn’t have to install the colour profile ISO Coated v2 300% (ECI) on a new Macintosh (M2, macOS Ventura); it already shows up in Publisher 2.2.1. I want to verify if the existing profile matches the one my printer (Flyeralarm) recommends. But the existing .icc file is nowhere to be found, so I can’t double-check this. Maybe this isn’t an issue, but I’d rather be sure than mess up an expensive print job. The .icc file isn’t in one of these places: /Library/ColorSync/ /Library/Application Support/ ~/Library/ColorSync/ ~/Library/Application Support/ Publisher’s app bundle (which contains several other .icc files) So, I ran a system-wide search with Spotlight (using the “System files are included” setting). I found several other .icc profiles, but not the one I’m looking for. Here’s what I like to know: Are there different versions of ISO Coated v2 300% (ECI) in circulation, or is it always the same .icc file from 2009? Where does the mysterious profile come from? Is it preinstalled with the Affinity suite nowadays, or does it come from an existing .afpub 2.2 document (that uses this profile) that I moved from my previous Mac? Where can I find this .icc file on my computer? Thank you!
  24. Hi Guys, I believe that this a bug, but correct me if I'm wrong. When I move my image on the screen anywhere it stays intact. No weird pixels added, when I use the mouse, but when I use the alignment tool then strange pixels are created in my image. Bug or something I'm doing wrong? I'll show this in a video! Thank you in advance! IMG_0224.MOV
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.