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

dmstraker

Members
  • Posts

    829
  • Joined

  • Last visited

Everything posted by dmstraker

  1. There's been something of a gap since the last update was issued. To me, this suggests either that Serif are in financial difficulty (hope not!!) or are gearing up for the release of Version 2.0 (very much hope so!). I bought Affinity Photo in 2017 and have happily received updates since then, while trying to do my part in supporting the product through 800+ videos in the InAffinity YouTube channel. It does seem time for a whole-version update, though what new features might appear I can only guess. For me, it's already the best photo editing software out there. Whatever, thanks and good luck to you smart Serif folks!
  2. It would be neat to have a Wiki for Affinity products. Start it off using current Help system, then let users extend it. As with Wikipedia, encourage a community of experts to sustain it
  3. Don't know if it is the right place, but I posted a note about money as below. It seems an important topic, so I've dropped a link in here, if that's ok.
  4. Using the Blur Brush, the preview under the cursor is the checkerboard when Transparent Background and white otherwise. Should this not show the proposed blur?
  5. Dear Serif I first bought Affinity Photo as version 1.5 in 2017. I can't remember how much money I gave you, but it didn't seem much. I'd been using Photoshop (hereinafter called 'the former product') but then Adobe introduced a taxation system (ach, ptui!) so I started looking around and found you. James Ritson's 200-odd videos got me to a new level and I was off to the races. It's probably a common story. Since then, you've made all kinds of improvements to the product, often through listening to the requests of bods like me wittering on in the (very fine) forum. As a keen photographer and old techie, APh is now a permanent partner in my artistic endeavours. But I'm worried. I want and need you folks to both survive and thrive. I started my InAffinity channel on YouTube as much to spread the word as to learn and build a beer fund. Other good people have done likewise. But I don't know if this is enough. During expansion, when Serif products are finding new customers, market penetration pricing can work to keep you going. However, a time comes when you may need to rethink your price policy. I'm not suggesting going to an Adobe model, nor the Luminar smoke and mirrors. In fact I'm not suggesting any magic formula, because magic is an illusion that can get you into trouble. But I am asking and hoping that you have a financing strategy that your customers will buy and which keeps you at the leading edge for the forseeable future and beyond. And I, for one, would be ok with paying a bit more. Yours sincerely Dave
  6. Just a note: I went to stokpic.com and a friendly little popup-looking thing offered to do a free virus scan for me. How nice. How worrisome. I clicked away.
  7. Shame about the Unsplash removal, but I totally understand why. It makes you wonder if Pexels and Pixabay might do the same. There's also a possibility for M&A in the photo sharing world. A thought. Unsplash wants donations of photos from photographers (as do Pexels and Pixabay). What if there was a way for Affinity users to easily submit images to them? If their API could handle it, then good. But if not, perhaps even a link would help. Or maybe Serif could even pre-emptively build value (including for Affinity users) with some half-way interface. This could be a significant lever in negotiations. Regarding this, I notice through my InAffinity channel that many of my users are older. Like me, there's a pattern of folks retiring and getting deeper into photography (just look at the demographic of the average photographic club). This might indicate a greater average willingness to freely share images and less need to make money, as these are retirees who have made their mark and hav sufficient pension at least to indulge in camera kit. This would be a splendid source for the photo sharing sites, and making it seamlessly easier to contribute would be of great value to them.
  8. The Bilateral blur has a bug whereby when the tolerance is set to zero, the whole image disappears (becomes transparent). This looks something like a divide-by-zero issue. This bug has now been transferred to 1.10 Frequency Separation in the Bilateral tolerance slider. Also, using straight Bilateral blur lets me knock out fine detail such as jpg artefacts, while the Bilateral in the Frequency Separation seems much weaker in this.
  9. Small celebration. I've just passed the 700th video in my InAffinity YouTube channel. There's also a web-based index, including videos sorted by time and category, plus free resources. I'd also like to take this opportunity to pay tribute to Serif and all of its people, including devs, QA, and everyone else. You folks have created an amazing product that has freed many of us from the Adobe taxation system and indeed that stands on its own as an excellent photo editing and graphics system. Having worked in software development, quality, marketing and other areas, I have some inkling of the effort and sheer dedication that it takes. Thank you and well done.
  10. See also other report I've recently added -- also still happening in latest beta.
  11. Note: I tried it with latest beta 1.10.0.1127 and it's still happening.
  12. I tried it with 1.10.0.1127 and it's still happening.
  13. Create document with Document/Transparent Background set, and a layer with black and white. Set Blend Ranges, adjust left graph so you can see transparent background checkerboard. Add Gaussian Blur as child layer. Adjust radius. The moment radius goes off zero, the transparent background goes white. This effect does not happen when blur layer is above pixel layer. Example file attached. blend ranges and blur.afphoto
  14. Don't know if this is a bug, but it does seem odd. See attached file. Different effect of gaussian blur when at clipping child position vs. at mask child position. At clipping position it gives dark effect at edges of hard alpha (including with Preserve Alpha) while at mask position it's more as expected (and same as when blur layer is above pixel layer). blur on alpha.afphoto
  15. Oh yes. Not looked at that before. Fade seems to be like Opacity but for just-applied destructive filter (and also allows Blend Modes). I very largely use non-destructive. But there are some destructive-only, so this can be useful. Thanks!
  16. Just a tiddler. In creating a macro, do something that will create a long line of text in the macro instructions list, such as renaming a layer with a long name. The name disappears under the right border of the macro panel. All well and good. However, if you have an adjustment where there is a 'Set adjustment parameters' line in the macro listing, the 'Edit' cogwheel disappears. Resizing the macro panel reveals the cogwheel has been justified right using the length of the longest text rather than the width of the window. Edit: Same issue with the checkboxes. I also just had a variant where the checkbox disappeared but the cogwheel remained. May be due to length of text string.
  17. Further data: Tried it with other groups, even a stack of them. Any selected group (even in the middle) always get rasterised. Key cause is when you have 'set adjustment parameters' in the macro which allows run-time adjustment, plus group selected.
  18. Start with pixel image. Run attached macro. It creates a group containing a few adjustments. Run the macro again. The assistant decides to rasterise the group. As the group only contains adjustments, the result is that the adjustments made by it are lost. Doing it all by hand rather than macro results in no problems. monadic blue 2.afmacro
  19. I think this is as follows: In maths, 'modulus' is the same as 'remainder'. In programming, this is often abbreviated to 'mod'. Other versions here. The C++ version of fmod is here. I think Affinity uses this. In brief, fmod(a,b) divides a by b and returns the decimal (floating point) remainder, so fmod(7.5,5) is 2.5 In the usage above, fmod (x/(w/a),y/(h/b) is presumably assigned to R, G and B, and: x and y are the number of pixels from the left and top w and h are the width and height of the viewport in pixels a is set as 13 and b as 4 For convenience, assume w=1300 and h=1000 So w/a=100 and h/b=250 Now formula is fmod(x/100,y/250) Take one row, say y=250. Now we have fmod(0.01*x,1) When x is less than 100, the result goes from 0 to 1, giving black to white, which is the left border When x is 101, the result is 1.01, which is clamped to 0..1 for display and so appears white. This repeats until x=199, giving the white band. When x gets to 200, the remainder now returns to zero, so we return to the gradient. As y gets larger, the white band get wider. And so on.
  20. A few other videos on masking here: http://changingminds.org/disciplines/photography/affinity_photo/categories/ap_masking.htm
  21. Love your use of PT formulae. There's been a bunch of moans of the forum about a lack of documentation of the functions therein. Do you have a reference for where to find more about these? I've heard tell that there may be info in places like GitHub and StackOverflow. Tx
  22. Brilliant! Love the PT adjustments. Interesting use of blurs, too. When starting from a stock photo, try: File/New then just hit 'Create'. Doesn't matter what shape/size the canvas is. Find and drag in image from Stock tab. Document/Clip Canvas. Layer/Rasterise. The Clip Canvas will automatically resize the canvas to fit the image. I'm guessing 'Fade' means reduce Opacity of layer. If Median Blur is for edge-preserving blur, you could also try Bilateral Blur, which can give a bit better results for this.
×
×
  • 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.