Jump to content

aitte

Members
  • Content count

    147
  • Joined

  • Last visited

Everything posted by aitte

  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. 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.
  3. 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
  4. 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/
  5. So, I'm using Affinity Designer on my Commodore 64, and I want to send a vector design to my friend, but even simple files with just some vectors and zero raster data are astronomically huge - in the 100-150kb range! It fills up almost an entire 170kb 5" floppy disk! This is simply too much time to transfer on my 300 baud (0.0375 kbytes/s) modem. Before I upgrade by adding another 128kb of RAM and a CPU with more megahurts and a 1200 baud modem to my Commodore 64, I thought I'd ask: Why are the files so freaking huge to just describe some vector X/Y coordinates and layer FX? :D I bet I could design the same file format to take less than a kilobyte for that. Is it storing some sort of raster-based preview image or something? If so, can you please allow us to disable that? I need vector designs to be super small for steganography, since I work for a secret government that's so secret that you've never heard of it. Edit: Real info here: https://forum.affinity.serif.com/index.php?/topic/14277-vector-files-massive/&p=65016
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. 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. :-)
  11. 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/
  12. @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. ;-)
  13. This is something I used to do a lot on Photoshop (which I've now deleted, thanks to Affinity Photo! ;)). 1. Browse the web and find some image. 2. Click and drag the image on the webpage onto Affinity Photo's main window. 3. Expected result: The image is opened as a new document, that's how Photoshop handles it. But what Affinity Photo does: It creates a new Text layer in the current document and puts the web URL of the image in it (lol). It *is* possible to open images if I instead drop the web image onto the Affinity Photo *icon* in the dock. But that's annoying when you've got an auto-hiding dock (like I do) and it just seems *weird* to have it create a text-layer when you drop an image onto the main window. I guess the reason it creates a text-layer is that the application takes dropped *text* and creates a text layer, or dropped *image files* and loads the image, but lacks specialized "dropped image URL" detection and reverts to the text-handling.
  14. aitte

    Responsive forums

    *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. :)
  15. aitte

    Responsive forums

    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
  16. aitte

    Responsive forums

    @MBd Wow thank you for that news. I have missed f.lux on my phone ever since I quit using jailbreaks. Every time I have to check my phone at night I wish I still had f.lux, and I have very often wondered why Apple never copied it. http://www.techtimes.com/articles/125029/20160116/f-lux-to-apple-let-us-back-in-developers-plead-for-ios-app.htm I bet Apple's Night Shift will have the usual Apple polish, and it sounds like it will have all of the major f.lux features: Setting the normal/night color temperatures manually if desired, being able to adjust the hours (so that it is not just following the sunrise/sunset of the geolocation), and being able to temporarily disable it. If it does all that, I'll be a very happy iOS user. Thanks for the news! :lol:
  17. aitte

    Responsive forums

    Looking at a white background is literally the same thing as staring into a lightbulb or the sun. The displays are tuned to the same color temperature. The backlit LCD display fires at maximum brightness when displaying white. That is why all the "flashlight" phone apps display a white background. It is horrible for your eyes and eyestrain. That is also why the iBooks app for iPhone has various white-on-black and dark gray backgrounds to help avoid burning eyes when reading. Black text on a white background is perfect for a newspaper, because a newspaper isn't printed on a lightbulb. A screen is. When I said that a tiny majority complained about the dark UIs of Affinity's products, I'm just reporting what I saw on this forum. The thread was very long but it was only a handful of people talking about it. Affinity has won Apple design awards and have tens of thousands of customers, so the white on black GUI is working for most people. And it's the defacto standard color scheme of pro apps, including video editors, 3D modeling and photo management. White on black has been confirmed in studies to cause less eye fatigue and helping make better decisions about color/photo editing. However, the same studies also revealed that black on white helps people with astigmatism (irregular corneas) when reading. Blurring black text on a white background is easier for them to read than blurring white text on a black background. It makes sense when I think about it. A blurred white blob on a dark background is less distinct/recognizable than a blurred black blob on a white background. Especially after a life of getting used to the shapes of the blurred black text in newspapers. I haven't got astigmatism and greatly prefer darker color schemes to avoid burning eyes, but there's actually another solution for this "staring into the sun of a white background" hell: Install https://justgetflux.comto protect your eyes from the white backgrounds, by making the computer screen reduce its color temperature to avoid damaging your eyes. They've got hundreds of links to research about the effects of white, bright computer screens on melatonin (sleep hormone) production, and how it actually inhibits the production, leading to worse sleep and later hours: https://justgetflux.com/research.html I recommend installing f.lux no matter what you guys do. It's free. :) I used to have it on my phone and had forgotten about it until now, and remembered that they have a Mac version too. I Installed it now and... WOAH! Instant relief from this forum and all other bright windows currently on the screen. Seeing the screen temperature fall to a natural, gentle color felt like I was sinking into sweet honey and the burning eyes stopped immediately. This will be a permanent installation on my machines from now on, and I'll only turn it off when editing photos. Wow. Even if this forum stays "black on white", try a darker background. I am a regular reader of the largest music production forum in the world at https://www.gearslutz.com/and while it isn't the prettiest forum theme, the colors themselves work very well. Most of the site has dark backgrounds, except the posts themselves, and those are slightly gray/blue which avoids some of the excessive brightness.
  18. @MEB: Cool, I didn't know about that option. It's Preferences > Tools > Tool UI Size. Putting it on Smallest is helpful. What I hope for is being able to disable the tool helpers completely, but easily enable them again. Via a view-menu dropdown option, or in the "Assistant" window. And have it bound to the keyboard too. Something like Shift+Spacebar to toggle the entire square frame + all the little balls permanently on/off so that we see no guides whatsoever. I realize that newbies may accidentally hit that, though. I also hope for something like this: " ctrl+drag = scale, ctrl+alt+drag = rotate, so that we can permanently work without the blue outlines. " Thanks for the temporary workaround MEB. It makes the problem better at least.
  19. aitte

    Responsive forums

    It can be quite hard to change colors since other GUI elements often clash as a result, and you end up making lots of deeper theme edits and compromises, but I hope they do something. Their main site is so slick and the forum is so bright. :D I've thought that from day one of joining this forum. PS: LOL I had forgotten about the complaints about the Dark UIs for the Affinity Apps. Those users were in a tiny minority though. There's nothing better than dark UIs for photography. It lets the content pop from the screen without distracting you with a bright "frame" around it.
  20. aitte

    Responsive forums

    Hehe, check out what I just found. A dark photography theme. Imagine this with a custom Affinity background. Slick slick slick, and its responsive design works on all devices: http://www.xenfocus.com/skins/aperture/index.php In use: http://xenfocus.com/demo/index.php?misc/style&style_id=17&redirect=/demo/index.php Example of a thread (there's only one demo user posting, it'd be even better with lots of different avatars): http://xenfocus.com/demo/index.php?misc/style&style_id=17&redirect=/demo/index.php%3Fthreads/this-is-the-topic-title.1/ And you can do tagging of threads in XenForo which seems to be the way Affinity links threads to bug reports. Best of all? https://xenforo.com/help/importing/ You can import all current IP.Board users, threads, tags, etc to XenForo. It can even redirect all old forum traffic to the new one (see the bottom of the last link).
  21. aitte

    Responsive forums

    I hope Discourse has other themes, because the default one is just a huge wall of text on a white background. It burns my eyes, I get dizzy and blinded and don't have energy to read anything in the example thread I linked to (https://discourse.omnigroup.com/t/omnifocus-vs-2do/13882/). The issue is that Discourse lacks contrast. There needs to be contrast, colored headers/dividers for each post, bigger avatars, etc, to make the content easier to skim through (knowing when to stop scrolling , seeing at a glance who wrote something, etc). If I want to read a Discourse forum, I need to constantly keep my eyes on the avatar column to the left to see where the post dividers are, and then skim back to the right to check if the post seems worth reading, then back to the left, etc. I think that's why I get dizzy and fatigued so quickly on their forums. It has really modern features like infinite scroll, but it's honestly the worst readability of any forum I've seen since the internet first arrived. I can't think of anything worse ever before. Maybe that is why it's so rare to see it used by companies; I've only seen it by the Omni Group and I was active on their forum in 2014 and it was absolutely tedious to constantly have to scroll around and try to follow the discussions. Forums are tedious enough, with so much useless noise in all discussions. Let's not make it even harder to follow what's going on. I wouldn't mind seeing Affinity re-skin their current software, though. A dark, "pro photography" theme matching their slick website would be awesome. It's glaring to say the least, to go from https://affinity.serif.com/en-us/to this bright forum. I browsed many other alternative forums now and discarded them all until I found XenForo, here are examples of responsive themes for it: http://xenfocus.com. If I started a forum I'd use that one. It's got great contrast and the link I provided is just one of many theme makers. Discourse on the other hand has no themes, just some people doing CSS reskins manually.
  22. aitte

    Responsive forums

    The current forum isn't optimal but it's pretty good, even on mobile. Despite what you say, it has a mobile theme. Discourse is very modern looking and out of the ones you list above, it is the one I'd pick. But it feels very disjointed to me. Just scroll through this example thread. I find it hard to follow who is talking to who, etc: https://discourse.omnigroup.com/t/omnifocus-vs-2do/13882/
  23. Everyone at Affinity should look at your attached thumbnail, @laneallen. "Adjust, spacebar, adjust, spacebar, zoom, move to different location, spacebar, zoom out, spacebar, adjust, spacebar..." represents my workflow too. It's silly.
×