Jump to content


  • Content count

  • Joined

  • Last visited

About aitte

  • Rank
    Advanced Member

Profile Information

  • Gender

Recent Profile Visitors

377 profile views
  1. Thanks for the ability to remove embedded thumbnails. Makes it really nice to store Affinity designs in a git repository without bloating it with a binary preview image constantly. There's a bug in the setting though: - Preferences : General : Uncheck "Save thumbnails with documents". - Saving a document now works. No thumbnail will be stored. The filesize will be small. - Restart Affinity Designer. - Save a document again. A thumbnail will be stored. - It's possible to disable thumbnails again by opening Preferences and Re-enabling and re-disabling "Save thumbnails with documents". The bug seems to be: The state of "Save thumbnails with documents" is not applied when the application restart. The checkbox itself stays unchecked but thumbnails themselves will be saved. I am using Affinity Designer 1.5.4.
  2. That would be the best way! Then all other techniques would also be non-destructive! What's needed in Affinity - Being able to create a "Virtual copy" layer and choosing to set the copy to "visible image below this layer" or to a specific layer or group. - Live filter version of edge detection. Then we could insert an Unsharp Mask, create a Virtual Copy pointed at "visible image below this layer" (below the unsharp mask), drag the virtual copy to be its mask, then apply live filter/adjustments to the virtual copy to make it into an edge mask. Wow......... that's more steps but still non-destructive and is way more powerful than what i proposed. No more need to constantly copy layers. Affinity, are you paying attention? :P
  3. aitte


    That is very smart. I can see lots of uses for that and hope Affinity implements it. Here's another new sharpening idea that would be so good in Affinity: https://forum.affinity.serif.com/index.php?/topic/28722-amazing-idea-do-it-now-edge-aware-unsharp-mask/
  4. This GENIUS figured out a method that does edge-aware sharpening. The method is to do edge-detection on the image, and then using the detected edges as a mask to avoid sharpening the edges. It lets you massively sharpen textures while completely avoiding all halos around edges and it is the most amazing thing I have seen in a decade of photography. It's the biggest revolution since the invention of the Unsharp Mask. This technique is like the Yin to Unsharp Mask's Yang. The results are preferrable almost 100% of the time you want an unsharp mask. Because "haloed edges" are the bane of sharpened photos. If this is implemented, I would probably never use the regular Unsharp Mask again. Please consider creating a new "Edge-Aware Unsharp Mask" filter, which internally does all the work of finding edges and avoiding them when sharpening. So that we can keep all of the non-destructive power workflows of Affinity Photo, but still achieve this AMAZINGLY USEFUL new effect. www.youtube.com/watch?v=iVgfbiH4-fw PS: I don't see the embedded video above. If someone has the same problem, type this URL manually instead, to see the technique: youtube.com/watch?v=iVgfbiH4-fw PPS: Here is how to currently achieve this in Affinity Photo, with many minutes of very destructive pixel-based steps: youtube.com/watch?v=7EVXy6fc_rE This incredible technique begs for a built-in non-destructive filter.
  5. I hope you add a "background dim" slider from 0 to 100%. It is very distracting to try to crop while seeing the whole image at equal brightness.
  6. I think they've announced that Affinity Designer will have this feature, but not Photo. If I recall correctly, they said something about making it possible to stack multiple outline effects on a single layer.
  7. I agree that it's a nasty bug. I haven't checked other formats, but since PDF was revealed to have the issue too, it may affect more formats.
  8. It actually exports like that, and it's stored in plaintext as a metadata entry in the exported PNG file created by Affinity Photo. The screenshots are from the Xee photo viewer app's info panel, looking at a PNG made with both Photo and Designer in the exact same way (open a BMP file from disk, export to PNG). Only Photo puts the original source file's path in the metadata. But Designer leaks it too when saving PDF files; as mentioned earlier in the thread. Thanks a lot. :-)
  9. Thanks for this information. MBd posted a message in my thread showing that my bug report is related to this one, so I am bumping yours with a backlink to my thread too: https://forum.affinity.serif.com/index.php?/topic/19065-affinity-photo-puts-sensitive-data-in-png-output/
  10. @MBd: Thanks for that additional information, ouch that's equally serious and very weird. Good to know Designer is affected too. I was always happy with Affinity's stance about never including metadata in exports (it's more private that way), so these two issues seem like bugs to me. They go against public staff statements on this forum saying that they don't want private metadata in the output, at least not without any user-control over it. These two bugs have no user control and I hope they're reviewed to make sure it never leaks unintentionally again. There's no reason to have the original source-file's path in the output. ;-)
  11. Affinity Photo's PNG export (both via menu-Export and the dedicated Export persona) will put the full path to the original file in the XMP "About" metadata tag of the resulting PNG file. Affinity is responsible for adding it, because no metadata existed in my source BMP file. This leaks personal information like the username and project path, for no reason whatsoever. Why does the end-user on the web need to see what my username and project path is? Speaking of which: When you make edits to a file and change the canvas size etc and export as PNG, Photo still puts the old canvas size as the XMP "Exif width/height" tags. This can be verified by making two screenshots of the desktop (like I just did below), and opening both, expanding the canvas of one and pasting the other into it, and exporting the result as PNG. The result will have an Exif width/height XMP tag that contains the old pre-expansion size. You can download my attached screenshot PNG and look at its metadata to see that the XMP exif tag is wrong. So there are many issues with the XMP metadata in Affinity. The treatment of XMP metadata tags is very bizarre in Photo (and maybe Designer too). Please look into what XMP metadata is being written, why, and if it's even correct (like the exif image size being wrong). The particularly serious "About" path-leak seemingly doesn't happen with Affinity Designer. Only in Photo, from what I can see. The attached screenshot shows the metadata of the same image that was opened in Designer and Photo and instantly exported without any changes. Only Photo leaks the private information. Imagine if that "XMP About" said something like "C:\Users\Edward Snowden\Desktop\NSA Secrets\slides.bmp", and he exported the PNG. That'd be a problem for him. :-) I am no Snowden but I don't think private paths belong in the final web-files.
  12. *tumbleweeds...* That's why the discussion drifted on to f.lux and iOS. There wasn't more to say without an official reply about the forum design. :lol: By the way, giving users access to directly submit bug reports is a disaster (look at large open source projects). They never fill them out right. They make 200x duplicates. They lump 15 issues into 1 bug report, etc. The reason is simple: The skills necessary to properly fill out a bug report are the same skills necessary to program a solution for the bug. It's better to let people talk about bugs on a forum and then developers can add them to an internal bug tracker if they're real, and simply tag the discussion threads with the internal bug IDs (which is often more than one per thread). It's so far working very well for Serif's Affinity division, a small company with only a few support staff. They could start adding volunteer/community moderators if things grow out of control. That works well for 1Password's forums, where several long-term members have been given moderator access to help out. But so far the community here is really mature and well behaved. :)
  13. That's perfect. Great to see that we can set manual daylight times and the display temperature. I bet they will get the smooth, gradual cooling/warming curves at dusk and dawn "just right" too. I would not be surprised if it comes to OS X too. The f.lux developers haven't really got a product. In the words of Steve Jobs; "that's a feature, not a product". He said it about Dropbox trying to sell document syncing, which isn't unique, cannot be patented and most people wouldn't pay for it. F.lux is in the same spot. It's one of the best "feature, not an app" ever, and they deserve credit for being the first to do it. But they never took it beyond "screen dimming" to paid product. It could have been expanded into a product by integrating lifestyle management like reminding you to sleep, take computer breaks to do recommended stretches, and other things to help our health at the computer. I never knew why they didn't charge for it even on the Mac, but I love them for being gracious enough to give it out for free for all these years. I would have paid up to $200 for it. It's such an instant relief to see the screen soften at night, and I'll never uninstall f.lux unless Apple clones it. :P