Jump to content


  • Content Count

  • Joined

  • Last visited

About Burndog

  • Rank

Profile Information

  • Gender
  • Location
    Dana Point, CA USA

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Files uploaded as well as a new set with single layer version and both exported and downsized images includes. Downsize to 1200px at 85% jpg from both Affinity Photo and Photoshop 2020
  2. Yes, you are correct but it's the same case for all. I have multiple images which show the 3 adjustment blocks all in one file then downsize and animate the results. I can assure you the problem is not related to which image but rather the lack of how an image is downsized and loss of quality that results. I've attached a new sample for clarity and to remove any concerns.
  3. I really like the features of AF Photo where it can build vectors within the same document. But... I'm trying to move from Photoshop and now find that there is a significant issue with image quality when you try to downsize an image. Shooting product and converting to final images sizes for websites is essential in my business. I need full size images for print and downsized image for websites. Take a look at the attached image. Upper right corner is working from the full size and exporting to jog @80% and resizing to the intended 1200 px wide. Terrible results. An improvement is to duplicate the parent document and resize prior to export. That is the example in the upper left corner. Still not very good and shows an overall issue with downsizing images. I've tried all the different options and see little if any difference. Conversely, look at the image in the lower left. THAT is how it should work (Photoshop Export As, resizing on the fly). Is this a known issue that we may see improvement on in the future?
  4. True, but in the context of this discussion we are talking about "Google Pagespeed" which is related to the web. Does the Affinity development team ever weigh in on these discussions? It would be of interest what the difficulties are in implementing webP either natively or as a plugin. For instance, is the format propietary? Is there a licensing fee from Google or?
  5. JPEG XR seems useless unless you're on a Microsoft box: https://caniuse.com/#feat=jpegxr And JPEG 2000 is a Safari only resource: https://caniuse.com/#search=JPEG 2000 Dump both these and add webP would be a better and wiser choice IMHO
  6. It seems that there is little viable argument to ignore webP if Google places favoratism on it in regards to our client's end products. Additionally, the end product/image quality from webP is really good. So regardless of if you like Google or not, webP is an opportunity for Affinity to stay current with its user's requirements (at least those needing to display their images on web browsers and provide SEO for their clients).
  7. I use the Android application (on Mac) which then has a right-click to convert to webP. Works just fine but....would be nicer as an export option in Affinity Designer or Photo.
  8. Any updates on when we'll be able to export to WebP format??? This is essential for those of us doing SEO on websites as performance is a greater than ever metric for SEO.
  9. Hi Walt, I agree but realistically, I'm not wanting to beta test this product. The solution of restarting works, and I can get back to work on my own projects. I merely wanted to let the Developers know this old problem still exists in the current 1.7.2 version. But, I will continue to post bug reports for Publisher to help both the Developers and Community. Thank you for your help in the forums!
  10. Same issue here... But as suggested, restarting the program solves the issue. Version 1.7.2 Affinity Photo
  11. Hey Jon, Originally I had problems with Tables not properly parsing pasted tab-separated data. The data comes from an accounting program that allows copying to clipboard. It provides too many columns so I need to delete some. In the original problem (earlier version of Publisher) the raw copied data would not work unless taken into a text editor then exported as "stylized text". I've created a file that has the original text formatted within (attached). Currently, I only use a contextual click command for Merging cells. Otherwise, I am using the headers to click and use the resulting options for deleting columns. ExportedData.txt
  12. Hello, I don't have the old file as I wasted too much time trying different things and then moved back to InDesign to complete the task. BUT I have tried to recreate today and just run into other issues with tables. The general workflow is to use the Table Tool from the vertical tool palette to draw out the initial table. Then select a couple of rows and columns and paste in the data. Next, I Cut the text in the first row and column to put back in (via paste) after removing superfluous columns. Now the issue is I can no longer select row/column #1 which is Merged so as to only be 1 row with all merged columns. I have attached the file, video and a screenshot that also shows some other issue in row 3 column D. Screen Recording 2019-09-02 at 12.36.52 PM.mp4 tableTest.afpub
  13. I expect these problems are not isolated but here is another example... Recreate problem table. Delete Column A Result: Row 2 and 3 stacked after the deletion of Column A
  14. The following screenshot shows a number of issues... Note the top three rows showed up on their own. The Second column can not be resized or the App goes into a spinning beach ball and requires a Force Quit. It seems Tables are not ready for Primetime, unfortunately. Running the latest version of Apple OS. :-(
  15. CMD-R did the trick on the Updates page in App Store. Thanks and now the apps are linked.
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.