Jump to content

Search the Community

Showing results for tags 'value'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Affinity Support & Questions
    • Feature Requests & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • Report a Bug in Affinity Designer
    • Report a Bug in Affinity Photo
    • Report a Bug in Affinity Publisher
    • (Pre 1.7) Affinity Range Bugs Forums
  • Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 15 results

  1. A couple days ago I asked about the value of pdfTool in a Quark forum. One comment was unexpected in that they pointed out that the tool is especially good for adding to a Publisher workflow in that it hasn't been around as long and may need a little more help than mature products like Quark and InDesign. That one perspective alone almost justified it's $500+ price tag. I wanted to know have other people found that those two products work really well together? Publisher is the only tool in the suite I haven't explored extremely in depth and I haven't even installed pdfToolbox yet. I like how Serif keeps the price low which allows for workflows like installing it on non-designers computers as I mentioned a couple days ago. Since the work in my company needs to pass by me the more expensive product (pdfToolbox) only needs to be installed on my machine. At first I didn't understand the very low pricing that Serif was doing but now it makes sense. I have even grown to like the name in that it may confuse some Microsoft Publisher users to accidentally start using Serif Publisher.
  2. Thought I'd share some of the stuff I just started creating in AP. Took me a bit to get past some interface issue but I'm getting to where I'm comfortable with a workflow in AP. These are just studies and not intended as finished work. Enjoy. Value study of an eye: https://www.artstation.com/artwork/8labgn Value study of nude female (NSFW): https://www.artstation.com/artwork/dOlv5A
  3. Dear Serif Team and Affinity Photo users, I'm a VFX Compositor & Matte Painter and I'd like to move from PS to AP. I hope you can help me with some questions regarding the Implementation and proper use of ACES and 32-bit. My background plate is exported from Nuke as an ACES - ACES2065-1 16-bit EXR file. The import into AP (1.6.4.104) works fine - the file get's recognized as an ACES file and I get the same result using OCIO. But there are a few things I can't get my head around yet: How do I pick and paint high color values? Using the exposure slider in the 32-bit Preview I see that there are high values. If I pick and paint them back in, the result is way darker. (Changing the exposure doesn't effect the false picked color) picked in Nuke for comparison I moved from PS because there is a 16Bit limitation and I had to work with ACEScc files (log encoded) and use an ICC profile to check my work. I hoped to get around this using AP. Those threads are dealing with the same issue but the information is contradictory and I can't reproduce the method quoted first. https://forum.affinity.serif.com/index.php?/topic/49815-hdr-raw-pixel-values/ https://forum.affinity.serif.com/index.php?/topic/19787--/ What is the proper workflow of importing and edit JPGs in an ACES setup in AP? Unfortunately there's no way of assigning an IDT during import (as in Nuke) but I can reproduce Nukes behavior with OCIO Adjustment Layers, which seams pretty inconvenient. (Windows Photo Viewer as comparison) Bottom left: Two OCIO nodes in sequence [ACES2056-1 to Utility - Curve - sRGB] followed by [Output - sRGB to ACEScg]. Bottom right: Two OCIO nodes in sequence [ACES2056-1 to Utility - Curve - sRGB] followed by [Utility - sRGB - Texture to ACEScg]. This post deals with the question of the right IDT for JPGs in general. I guess going the Utility - sRGB - Texture way is better, isn't it? My color settings: If you need further information or I haven't made my questions clear enough please don't hesitate to ask. I'm glad about any help or further learning resources! Thanks a lot
  4. So far I've not found a way to determine the exact grey value of a particular pixel of a layer mask in Affinity Photo. The info panel only shows colour values of the underlying layers. This is a very useful feature, for example if you work with gradients to combine two photos and you want to refine a certain area of the mask and apply the same grey value as in other areas of the mask. If such a feature really does not exist in Affinity Photo I'd like to request it to be implemented. If it does exist and I've simply not found it yet I'd be grateful if somebody could instruct me how to do it.
  5. This week, this happened several times: when using (randomly) some boxes such as kerning, text size (and other settings in different panels), it makes jump affinity to another app, making Designer disappearing and focusing on another window. The only solution I found is to separate Affinity on new space (mac) and to open in a full frame mode. If not, I can reproduce this really annoying bug. N.
  6. Hello everyone! I have been running into this many times. When trying to create macros, the values saved sometimes change when trying to access the macro later. This is very bad. Especially since it completely destroys the purpose of using macros, which is saving time. So basically, I have to create some of the macros from scratch all the time. This happens especially after closing and opening documents or Photo itself. Also, especially transform and crop values seem to be very fragile. For example, scaling on X by 50% and on Y by 50% results in scaling by 200% on X and 200% on Y. If I remember correctly, values sometimes even store asymmetrically (for example, 50%, 50% resulting in 200%, 100%). To reproduce, please try to create a macro for scaling a layer by 50% and one for scaling it by 25%. Then, create a macro for cropping the document by 50% and one for cropping it by 25%. Those are 4 macros that I frequently use and which very frequently break. Can somebody look into this and confirm this as a bug? And maybe somebody can fix this? Or could I be doing something wrong? I do save the macros to the Library. Best wishes, Shu EDIT: Software used: Affinity Photo 1.5.1, Affinity Designer 1.5.1, OSX 11.6 EDIT 2: Alright, after posting this, I created a new macro. But it didn't take a long time for it to break. When creating it, the values were set to 50% and 50% for both X and Y, but now, after clicking on the macro without anything happening, I tried to edit the macro, which showed me the 50% values have been set to 100% by itself resulting in no scaling at all:
  7. fernandolins86

    [AD] Wrong HEX value?

    Looks like AD sets one value for RGB as HEX and another one for the HEX color code (4C, 4C, 4C versus #4D4D4D in the screenshot). If I step the RGB values up or down the value updates correctly, but every time I open the color panel for this color it shows that difference. PS: The forum doesn't allow me to search for "HEX" or "RGB" because it is less than four letters long, so I don't know if this has been posted before.
  8. shushustorm

    Affine 50% issue

    Hello everyone! Sometimes I need to offset an image on X and Y by 50%. After doing this, I need to get it back to its original offset (null). Most of the time, this works with just using 50% offset a second time, but sometimes I am running into a weird issue: The layer seems to get offset by a weird value (or maybe Affine doesn't offset the whole layer?). The only way around this is to use Affine on X and Y by -50% each. But I cannot use negative numbers to create a Macro for this. Anyway, I shouldn't even have to use negative values because when 50% twice doesn't work, something else seems to be going wrong. I guess I am not getting a 50% offset of the whole image then. I made a video of this, you can take a look here: Affine.mp4 Also, I have already tried to paint to each edge and select the whole image, so Photo should be forced to work with the full resolution of the image. Here is a file that includes the problematic layer from the video: 02_04.afphoto Best wishes, Shu
  9. I raise this thread from AD beta forum to here because I cannot find the same report by searching. It also happen to the current store version. Please fix it next beta. Cheers :)
  10. I have been an artist all my life. Although this has hardly ever been my employed status, I won a scholarship to the Swindon School of Art when I was in Secondary School, and although I never did attend due to family commitments, nevertheless Art has been and shall remain an important part of my life. To cut a long story short, I have in my later years advanced my skills, as a hobbyist into animation, design and photography. I purchased Affinity Photo, which I found to be great for getting the best out of images, and compares well with the more expensive brand names out there. So to say that I wasn't surprised that Affinity Designer was also a good investment would be an understatement. I originally bought it for designing backgrounds for my animation; for which I use Toon Boom Premium. However it has yielded so much more than I initially imagined for the price. It is a Premium Package at an affordable price. I therefore want to award it 10/10 and say a big thank you to Serif for such a fine piece of software. I also bought the accompanying book which was also a sound investment.
  11. I would love to see a feature similar to sketch's "exclude text values" option for symbols. This allows the user to have one symbol but stil be able to change the text content within the symbol without it changing the others. The text style, color etc... is still synced just not the actual value of the text. This would be extremely useful for buttons and inputs styles. Keep up the great work guys!
  12. I would like to have some control over how much noise I apply to an object. Currently I move the slider (which should be in the normal color panel as well, not just in the toolbar) as far as I want. But I don't know that value. If I have an other object and want to apply the same amount of noise, I have to move the noise slider to the point I think it was on the other object. Adding an actual number next to the slider would make it easier. I could enter a number (amount of noise), and I could copy that number and apply that exact same amount of noise to another object.
  13. Hey guys, I ran into this Photo beta bug, where the Gradient Adjustment Layer just won't accept my desired colour and changes it to something similar but still different. I also tried different approaches like setting the colour as a swatch in the swatches panel first and use it, but it’s the same. Copied the layer into a new document resulted the same – but the values of the changed colour where completely different again. I hope this short clip demonstrates the problem … https://youtu.be/DH1jj_Nv_Y8 Cheers and have a nice weekend Dennis ;)
  14. Dear (epic) people at Affinity, I have a feature request regarding consistency, example: when using the "transform" tab, you can easily adjust sizes by hovering over the options and scrolling up/down — could you implement this in the text tool as well? Possibly in every dropdown option that entails numeric options. Thank you. Kind regards, Jo
  15. Sorry to add to your probably huge and very long list of requests this is not a essential, but something that helps speeds up a daily process.... When setting up area as such as bleed and guides etc, after entering the first value in "other" programs hitting tab will fill all remaining boxes with the same value. Presently each box has to be manually entered. Not at all essential just a nice touch to add, when including the bleed options :)
×