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

Gabe

Staff
  • Posts

    10,193
  • Joined

Posts posted by Gabe

  1.  

    Hi @MiLeung,

     

    Welcome to the forums. 

     

    You can have precise guidings, but you're "limited" to just the object itself and the canvas. Let's say, you cannot move an object Y/20 on Y axis of another object. You can, however, move it y/20 in relation to its current position. As for the guides, you can use other objects as guides, with centre guides and align guides. Have a look here - 12. Design Aids

     

    Thanks,

    Gabe. 

     

  2. HI @Kulashaker,

     

    Welcome to the forums. 

     

    The speed of the stack would be greatly influenced by the RAM, and by the file size of your photos. When you're stacking images, most of the info will be stored in RAM for the duration of the process. I suggest you give it a go with 10 images and see how it goes. But I'm pretty sure that 100 photos will take at least 15-20 minutes. I gave it a quick try with 90 images ( 300kb each ) and it took about 1 minute. If you're working with raw files( 30mb+ each file ), you can expect longer waiting times.

     

    Thanks,

    Gabe. 

  3. Hi @Mareck,

     

    You would be better off working in a sRGB across the board. Your final image is going to be Jpeg srgb anyways, and there's no real reason to go from linear to Filmic OCIO , and then from Filmic OCIO to sRGB. Try to set the working space in Blender to sRGB_OETF. In 32 bit preview, select the sRGB_OETF in the first drop-down menu, and sRGB in the second one. Or, you can leave it to ICC. Both will look almost identical. This way you will definitely export what you see on the screen.  

  4. I've had a look at the file attached. The reason why it's so slow is that you have got so many live filters applied. Live filters work a bit different, and they will have a big impact on performance. I suggest this workflow: Once you're happy with the result, open the live filter and click on "merge". The main "issues" are the layers parented your background layer. If you merge all of them one by one, the export only takes a few seconds to export. 

    Live Denoise.jpg

  5. Hi saikat,

     

    Affinity ( both Photo and Designer) tries to recover the file when you open that specific file. If you, however, were working on a new document and you have never saved it, the recovery won't work. If you saved the file at any point, it will try to recover it when you re-open it. But there is no guarantee you will always have a recovery file. 

     

    Thanks,

    Gabe. 

  6. I believe it's more to do in the "back end code" and how the software treats the text. The Frame text will have a solid line as it's fully synced. The artistic text I believe it's just a "Text frame with a frame=disabled tag( back-end), therefore the dashed line and the "unlinked attribute: Frame text " (front end). It's just a thought. Will log this as an improvement with our devs in the meantime. 

  7. I believe the Unlinked Text frame is because both text tools are technically the same, one being constrained within a box(frame text tool), probably with a tag in the code, while the other one is not. If this applies to the symbols, then the "tag being off" for the artistic text would be the Unlinked attribute. The symbol might look for all the attributes, and if any are "disabled" - Artistic text, it will display the unlinked "error". 

×
×
  • 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.