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

vjsouza

Members
  • Posts

    76
  • Joined

  • Last visited

Reputation Activity

  1. Confused
    vjsouza got a reaction from Pšenda in Affinity Designer 2 for Windows - (2.4.0)   
    It still continues, since the beginning, without the tool to create QR-Code. How long will we have to use Inkscape to create QR-Codes and import them into Affinity? Huh? Until when?
    When opening an SVG file, ALL objects still contain a 0 pt black Stroke, even if the original, created and exported as SVG by Affinity itself, does not have any objects with a stroke. This is a BUG!
  2. Like
    vjsouza got a reaction from PaoloT in Please make Batch Job for ALL supported export formats   
    Hello, guys at Serif. I am a happy user of Affinity Suite 2.0.4 (Publisher, Photo and Designer)
    But, today I wasn't so happy with the Affinity Photo program
    In the past, in version 1, I needed to convert an entire folder from WEBP to PNG. It worked!
    But today I need to convert a folder with PNG files into JPEG XL files. I was sad to see that Affinity Photo only Batch Jobs JPEG, PNG, TIFF and EXR.
    Currently, Affinity 2.0.4 can export to PNG, JPEG, GIF, TIFF, PSD, PDF, SVG, WMF, EPS, EXR, HDR, TGA, JPEG XL and WEBP.
    I cannot understand why Batch Job exists only for JPG, PNG, TIFF and EXR. Why is there no Batch Job for the other formats? Did you guys at Affinity forget to include these formats?
    I have a folder with 261 PNG files and I urgently need to convert them all to .JXL and converting one by one is going to be an arduous and super tedious job. Oh! What a good batch job is missing!
    Unfortunately, Xnview MP crashes when doing a batch job, and so does IrfanView. GIMP doesn't even have a Batch Job. I can only appeal for the help that only the guys from Affinity can provide. Help! Please!

  3. Like
    vjsouza got a reaction from laurent32 in THE FIRST AND VERY OLDEST AFFINITY BUG, SINCE 2016, NEVER FIXED!   
    There is a "workaround" (in Brazilian Portuguese: "GAMBIARRA") to avoid this BUG (yes, as much as they insist on saying no, this is a BUG!"
    1. Group everything in the "unpurgeable" file
    2. Copy the group
    3. Do "File / New From Clipboard"
    4. In the new fresh file, ungroup
    5. Save as other name.
     
    Although not an elegant solution, it has worked for me, because the "phantom information" is not copy/paste possible.
    But it is extremely tedious to have to do this every time you save a final file in Affinity. The EDIT/PURGE command is extremely necessary to implement.
  4. Like
    vjsouza got a reaction from Sun2Son in Affinity V2: GLYPH BROWSER no longer exist!   
    In the previous version it appeared in the Text menu. Who was the brain that thought hiding this menu item would be beneficial for the user?
  5. Thanks
    vjsouza got a reaction from max1josef in THE FIRST AND VERY OLDEST AFFINITY BUG, SINCE 2016, NEVER FIXED!   
    Unfortunately, there is no way to copy guides into the new document. In CorelDRAW the guides are on an exclusive layer, but I also don't know if it's possible to copy them to another document.
  6. Haha
    vjsouza reacted to carl123 in THE FIRST AND VERY OLDEST AFFINITY BUG, SINCE 2016, NEVER FIXED!   
    The snapshot problem comes up all the time when investigating file size issues
    Here's one from last month
    https://forum.affinity.serif.com/index.php?/topic/173157-huge-difference-in-file-sizes-with-no-edits-photo/
     
     
    Wow, that's spooky, I actually called it a "black-magic-ritualistic-procedure"  back in this post from almost 3 years ago
    https://forum.affinity.serif.com/index.php?/topic/86287-huge-file-size/&do=findComment&comment=572357
     
  7. Like
    vjsouza reacted to carl123 in THE FIRST AND VERY OLDEST AFFINITY BUG, SINCE 2016, NEVER FIXED!   
    @vjsouza
    It's the same old snapshot problem...
    Open the (70MB) file you uploaded to the forum
    Delete the snapshot
    Save the file (Not save as...)
    Close the file (Important)
    Open the file
    Make a small change (e.g. add a 1" rectangle)
    Save the file (Not Save as...)
    File is now 8MB
     
  8. Like
    vjsouza reacted to Dan C in THE FIRST AND VERY OLDEST AFFINITY BUG, SINCE 2016, NEVER FIXED!   
    Thanks for letting me know and I'm sorry to hear this - I've tested this with other files and it appears to be working correctly for me - however I'm able to replicate this issue with your file, indicating a bug with this specific document rather than with the app. 
    I'll be logging this file directly with our developers now for further investigation.
    In the meantime, you can use Snapshots as a workaround to this bug - I've included a quick screen recording of these steps below, and the resulting file was 8.82MB:
    2022-12-12 12-09-43.mp4
    I hope this helps 
  9. Like
    vjsouza got a reaction from BartonFink in THE FIRST AND VERY OLDEST AFFINITY BUG, SINCE 2016, NEVER FIXED!   
    Please, before do your commentary, see the video til the end.
    This is the very oldest Affinity BUG. Perhaps the first of hundreds. Outlived all Affinity updates since 2016. It was never fixed.
    Unlike Photoshop, Affinity has no EDIT/PURGE menu. I know, because I've been working with Affinity since its launch in 2016. I've reported this BUG before, but nothing has been done.
    Please, please, please, please, add a EDIT / PURGE menu in Affinity Photo, Designer and Publisher, like Photoshop do.
    What is the problem?
    Create any file with Affinity Photo, with several objects (bitmaps and vectors), save the file, close Affinity. Then open Affinity again and try making changes to the file, like deleting bitmap objects, for example. You will notice that the file size does not decrease even after deleting all the objects. Watch the video until the end.
    I mentioned it to a friend, and he recommended that I post the video on YouTube, so the people at Serif take action. But I decided to give the people at Serif one more chance, to see if this time they fix the first Affinity BUG, which has survived undefeated for seven years until today.
    Affinity does not decrease file size after exclusion of objects.mp4 01 Original file.afphoto
  10. Like
    vjsouza reacted to TSE in Affinity V2: GLYPH BROWSER no longer exist!   
    I love Affinity Photo.  However, their 'help' and instructions for using the software are pathetic at best.  PLEASE Affinity Photo, spend some time on your help menus.  Users waste a lot of time with poorly written documentation (such as the Glyph Browser Not being available until toggled on under the 'Window menu item).
  11. Like
    vjsouza got a reaction from IPv6 in THE FIRST AND VERY OLDEST AFFINITY BUG, SINCE 2016, NEVER FIXED!   
    There is a "workaround" (in Brazilian Portuguese: "GAMBIARRA") to avoid this BUG (yes, as much as they insist on saying no, this is a BUG!"
    1. Group everything in the "unpurgeable" file
    2. Copy the group
    3. Do "File / New From Clipboard"
    4. In the new fresh file, ungroup
    5. Save as other name.
     
    Although not an elegant solution, it has worked for me, because the "phantom information" is not copy/paste possible.
    But it is extremely tedious to have to do this every time you save a final file in Affinity. The EDIT/PURGE command is extremely necessary to implement.
  12. Like
    vjsouza got a reaction from deeds in THE FIRST AND VERY OLDEST AFFINITY BUG, SINCE 2016, NEVER FIXED!   
    There is a "workaround" (in Brazilian Portuguese: "GAMBIARRA") to avoid this BUG (yes, as much as they insist on saying no, this is a BUG!"
    1. Group everything in the "unpurgeable" file
    2. Copy the group
    3. Do "File / New From Clipboard"
    4. In the new fresh file, ungroup
    5. Save as other name.
     
    Although not an elegant solution, it has worked for me, because the "phantom information" is not copy/paste possible.
    But it is extremely tedious to have to do this every time you save a final file in Affinity. The EDIT/PURGE command is extremely necessary to implement.
  13. Thanks
    vjsouza reacted to herhey in THE FIRST AND VERY OLDEST AFFINITY BUG, SINCE 2016, NEVER FIXED!   
    I think it should be implemented as an automatic process when saving the file. I don't find any reason why the user should do it manually.
  14. Like
    vjsouza reacted to Dan C in THE FIRST AND VERY OLDEST AFFINITY BUG, SINCE 2016, NEVER FIXED!   
    Thanks for your report and our sincerest apologies for the delayed response here. We are exceptionally busy following the release of V2 and we thank you for your continued patience and understanding here.
    As confirmed above, this is not a bug within the Affinity apps - and Walts description is correct, when using File > Save the file itself will not be 'trimmed' until more than 25% of the files data is redundant. This is further explained in the below posts from our devs:
    I will however move this thread to the Feedback section of the forums, for our devs to consider adding an 'Edit/Purge' option in the future.
    I hope this clears things up!
  15. Like
    vjsouza reacted to affinian in THE FIRST AND VERY OLDEST AFFINITY BUG, SINCE 2016, NEVER FIXED!   
    An "Edit/Purge" option is a good idea!
  16. Like
    vjsouza reacted to 4dimage in THE FIRST AND VERY OLDEST AFFINITY BUG, SINCE 2016, NEVER FIXED!   
    Did you ever watch e.g. Photoshop saving an open file. No matter how big it is. PS creates a temp file, writes the actual RAM content to it and then - on success - replaces the existing file with the just created temp file and the same name. Writing the temp may even be faster because the old file structure has not to be reorganized. And if something goes wrong during the temp file write process, you still have the old original untouched. This is done on EACH save. By the way - this sounds like intrinsic defragmentation as a bonus on top.
    There is no magic with this simple file logic - isn‘t it.
  17. Like
    vjsouza got a reaction from 4dimage in THE FIRST AND VERY OLDEST AFFINITY BUG, SINCE 2016, NEVER FIXED!   
    Please, before do your commentary, see the video til the end.
    This is the very oldest Affinity BUG. Perhaps the first of hundreds. Outlived all Affinity updates since 2016. It was never fixed.
    Unlike Photoshop, Affinity has no EDIT/PURGE menu. I know, because I've been working with Affinity since its launch in 2016. I've reported this BUG before, but nothing has been done.
    Please, please, please, please, add a EDIT / PURGE menu in Affinity Photo, Designer and Publisher, like Photoshop do.
    What is the problem?
    Create any file with Affinity Photo, with several objects (bitmaps and vectors), save the file, close Affinity. Then open Affinity again and try making changes to the file, like deleting bitmap objects, for example. You will notice that the file size does not decrease even after deleting all the objects. Watch the video until the end.
    I mentioned it to a friend, and he recommended that I post the video on YouTube, so the people at Serif take action. But I decided to give the people at Serif one more chance, to see if this time they fix the first Affinity BUG, which has survived undefeated for seven years until today.
    Affinity does not decrease file size after exclusion of objects.mp4 01 Original file.afphoto
  18. Like
    vjsouza got a reaction from Archangel in THE FIRST AND VERY OLDEST AFFINITY BUG, SINCE 2016, NEVER FIXED!   
    Please, before do your commentary, see the video til the end.
    This is the very oldest Affinity BUG. Perhaps the first of hundreds. Outlived all Affinity updates since 2016. It was never fixed.
    Unlike Photoshop, Affinity has no EDIT/PURGE menu. I know, because I've been working with Affinity since its launch in 2016. I've reported this BUG before, but nothing has been done.
    Please, please, please, please, add a EDIT / PURGE menu in Affinity Photo, Designer and Publisher, like Photoshop do.
    What is the problem?
    Create any file with Affinity Photo, with several objects (bitmaps and vectors), save the file, close Affinity. Then open Affinity again and try making changes to the file, like deleting bitmap objects, for example. You will notice that the file size does not decrease even after deleting all the objects. Watch the video until the end.
    I mentioned it to a friend, and he recommended that I post the video on YouTube, so the people at Serif take action. But I decided to give the people at Serif one more chance, to see if this time they fix the first Affinity BUG, which has survived undefeated for seven years until today.
    Affinity does not decrease file size after exclusion of objects.mp4 01 Original file.afphoto
  19. Like
    vjsouza reacted to herhey in THE FIRST AND VERY OLDEST AFFINITY BUG, SINCE 2016, NEVER FIXED!   
    Even if you delete all the content and resize the document size to 1 x 1 px the file size will not decrease. This is ridiculous...
  20. Like
    vjsouza got a reaction from herhey in THE FIRST AND VERY OLDEST AFFINITY BUG, SINCE 2016, NEVER FIXED!   
    Please, before do your commentary, see the video til the end.
    This is the very oldest Affinity BUG. Perhaps the first of hundreds. Outlived all Affinity updates since 2016. It was never fixed.
    Unlike Photoshop, Affinity has no EDIT/PURGE menu. I know, because I've been working with Affinity since its launch in 2016. I've reported this BUG before, but nothing has been done.
    Please, please, please, please, add a EDIT / PURGE menu in Affinity Photo, Designer and Publisher, like Photoshop do.
    What is the problem?
    Create any file with Affinity Photo, with several objects (bitmaps and vectors), save the file, close Affinity. Then open Affinity again and try making changes to the file, like deleting bitmap objects, for example. You will notice that the file size does not decrease even after deleting all the objects. Watch the video until the end.
    I mentioned it to a friend, and he recommended that I post the video on YouTube, so the people at Serif take action. But I decided to give the people at Serif one more chance, to see if this time they fix the first Affinity BUG, which has survived undefeated for seven years until today.
    Affinity does not decrease file size after exclusion of objects.mp4 01 Original file.afphoto
  21. Thanks
    vjsouza reacted to walt.farrell in Affinity V2: GLYPH BROWSER no longer exist!   
    In the menu: Window > Text > Glyph Browser
    In the Help (online version): 

  22. Like
    vjsouza reacted to walt.farrell in Affinity V2: GLYPH BROWSER no longer exist!   
    It's a kind of panel, and they're all controlled by the Window menu now, I think.
  23. Like
    vjsouza got a reaction from ashf in RICH BLACK, K=100, please!   
    As a FEATURE REQUEST, please, let Affinity (photo, designer, publisher, etc) show CMYK 0,0,0,100 as RICH BLACK (or pure black RGB 0,0,0)
    Today, this appear a rgb 32,32,32.
  24. Haha
    vjsouza reacted to debraspicher in Please, remove the DEAD WOMAN splash screen in AP 1.10.5   
    It may be cultural difference in how body is made up after. Not a conversation I expected to see on AF though.
  25. Haha
    vjsouza reacted to Pšenda in Please, remove the DEAD WOMAN splash screen in AP 1.10.5   
    I must strongly protest against the gender imbalance of the splashscreen in APublisher - I recommend adding DEAD MAN to it.

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