Jump to content

Ronald N. Tan

  • Content Count

  • Joined

  • Last visited

About Ronald N. Tan

  • Rank

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Los Angeles, CA, USA

Recent Profile Visitors

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

  1. Apologies if I overlooked the lists of approved hardware for OpenCL. If not already, will you please provide some sort of a list or prelist with preliminary testing of GPUs? I currently have AMD Radeon RX 460 (current up-to-date WHQL certified) and it suits my needs and I don't plan to upgrading to another GPU. Additionally, I'm currently a Publisher user and like the software. I have been curious about the hardware acceleration in a forthcoming version of Photo.
  2. I think I may found a bug concerning margins on making a new master page. Please repeat the steps. 1. Make a new master page. While the dialogue prompt comes up specify the following margins (as an example with page/document size of 1080 x 1920) Left: 120 px Right: 120 px Top: 250 px Bottom: 250 px Click OK. You will notice the bug, such that the margin specifications for "Left" and "Top" seems to be switched. To fix this, you'll have to go into Guides and fix the "switch" between "Left" and "Top." Once you press OK, you'll see the intended margins aforementioned. I was able to verify the bug by making another master page and purposely substituting "Top" margin as "Left" and vice versa. Once you OK, you'll see this new, master page looking as correct and intended and going into Guides Manager, you'll see the margins correctly correspond as intended.
  3. Dear Affinity, Thank you for your recent decision to allow 90-day free trials of your software and 50% discounts. I recently purchased the PC license to Publisher and so far, I'm enjoying the easy to use and intuitive functionality. One thing that is "kind of" annoying at the moment is the inability to customize or change the default "_" in filenames to indicate pages into "-" or however additional filename delimiters the end user desires. If not already, will you kindly include the Publisher export file names to be more customizable? I know Affinity Photo as the option to rename or set desired options in the Export interface. If customizing delimiters are too intensive at the moment, at least please consider the end user (like me) to change the default underscores into dashes to indicate page number, when exporting to PNG, JPG, EPS, etc. Thank you, Ronald
  4. Hi Walt, I export to JPG, PNG, and EPS. I do wish (unless I overlooked something), Publisher will allow the end user to provide additional delimiters in exported filenames. For example, somewhere in the preferences so say use "dash" instead of the default underscore.
  5. Hi Gabe, Apologies for the delay. As I'm a current subscriber to the Photography Plan of Creative Cloud, I don't need Affinity Photo. With that said, I recently purchased my PC licence of Publisher to show support for Serif's recent decision to help creatives struggling during this current odd times indeed! Back on topic, I am currently trying out the latest version 1.8.3.X of Affinity Photo and the lag I describe is there. What's more odd is that things seems to be "okay" on a single pixel layer. The curves tool for adjustment seems ok as intended. However, as soon as I purposefully duplicate that same pixel layer...say 10 or 20 times to simulate several layers of work in real time setting, the curves refresh on screen lags. In other words, the manipulation of the curve lags as well.
  6. Dear Sir or Ma'am, Thank you for the recent decision of Affinity to allow 90-day free trials of software and discounting to 50%. I recently bought Publisher license for Windows and it's the latest stable version of I'm unable to figure out how to change the underscores "_" in the files exported from Publisher into dishes "-" or whatever elements/parameters I like to rename on export. In other words, ALL files exported from Publisher is FileName_1, where 1 indicates the page number. On modern computers and file nomenclature, underscores are irrevocably grotesque. I'm familiar with batch naming via Adobe Bridge; however, I rather not perform the second step. Unless I missed something, please let know how I could change the underscores into dashes. Additionally, please consider allow users to rename however they wish automatically for Publisher. Thank you for the privilege of your time. Best in health and warmest wishes, Ronald
  7. Greetings Sir and/or Ma'am, Thank you for reading. I'm curious, if you're experience a similar oddity on the current 1.7.3.X Affinity Photo for Windows such that there is an unusual lagging involved when make a new curves adjustment layer on a 16-Bit layered TIFF file with size about 2GB+? Another test that you can duplicate is to create an arbitrary file, say 20 megapixels in size in 16 bit. duplicate that layer several times and add arbitrary adjustment layers. Then finally, add curves adjustment layer and you should see the lag in both the rendering on screen and movement of mouse. I still have a few more days until my trial of Photo expires. I'm currently on Photoshop 2020. I don't experience that oddity in PS2020. Thank you once again for reading and for the privilege of your time. Cheers, Ronald
  8. I tried with both my Wacom Intuous Photo (intro line to Intuous) and I tried all possible options. I set my viewing preview to closest neighbor. Retina is set to fastest My files are HUGE. Exceeding 2 GB and multi-layer. I don't experience any lag with mode on current later. It lags to the point of not workable on mode current and below. The workaround I mentioned is for my to select and copy on to its own later so that healing brush could sample on current layer. This is annoying me. Mainly....Photoshop Trial version does not lag. I think Serif needs to test more on Windows since I think the Windows is a port of their native MAC iOS program.
  9. I tried this beta and the oddity I noticed with lagging for Healing Brush on "Current Layer and Below" still persists. Has anyone aware of this? Am I the only one experiencing this oddity. The workaround for me to so select an area I was to heal and CTRL + J to make the selection on their own layer. Then, use the healing brush on current layer. This seem to fix the lag. As in...everything seems to be OK with this workaround. I work with 16-Bit large files, e.g. exceed 2+ GB. Additionally, I tested with fresh exports from my Capture One Pro 11 16 Bit TIFF files and same thing. If the healing brush is set to "current and below" there is a nuisance lag and seems to induce freeze of the latest beta.
  10. I'm at the current stable version of Affinity Photo for Windows and I'm experiencing a lag, when using Healing Brush on "Current Layer and Below." Has anyone experience this? I'm using Wacom Intuos Photo with the latest WACOM drivers installed and I just reformatted and reinstalled everything on Feb. 4, 2018. Thanks for reading, Ron
  11. Hi Dominik, In my screenshot example, I saved that template with the already sliced out into (2) 1080 x 130 PNGs. Uploading these in the native 4:5 aspect ratio in Instagram will allow me to create the seamless diptych panoramas. Unless, I overlooked something, slicing up manually in my example screenshot is easy. What if I need to slice up 20 each at 1156 x 1920 to upload as a presentation for my Instagram Story? In this screenshot example, I wanted to use the Instagram Story to display about my creative reimagining of wet plates. In Photoshop CS6, I managed to create a 5780 x 7680 @ 300 PPI and arranged my presentation. The next part is easy. I used the Knife tool and ordered to be cut into 4 slices down and 5 slices across. Each slice is 1156 x 1920 pixels @ 300 PPI. Next, I use the Save As Web and PS automatically cut all those slices and place them in a folder of my configuration. I repeated this exact process in Affinity Photo. I opened my PSD and figured out AP's way is to manually slice up using simple math, transform panel, and drag/drop. I had my guides on so I know where to roughly use AP's slice tool to make the rough slicing selection. If needed, I entered 1156 x 1920 into the transform panel and used simple math to check the position of the slice relative to the document. I then batch-export these manual slices. It was the EXACT result in the end in AP software. The process in AP was work. —Ron
  12. I'm a recent user of Affinity Photo and I'd like to submit and place in my vote for an automatic knife or slicing tool. Basically, I'd like an ability for an inverse panoramic stitching. For example, in Photoshop, I can use the Knife Tool for the following working example: 2160 x 1350 Pixels Using PS's Knife tool, I can right-click and slice up the image into (2) pieces of equal 1080 x 1350 images. Finally, using PS's "Save for Web," I can automatically export this onto my Desktop and upload to my Instagram to create the seamless panoramic diptych. In Affinity Photo, I have to manually slice and position. Please see the screenshot. With some simple math for perfect alignment and drag/drop. It's doable, but takes some effort and manual work. In an imaginative working scenario, I'd like AP an option to automatically create slices. In the screenshot, example, remember that my image is already sized 2160 x 1350 pixels for seamless panorama on Instagram's album post. I would simply enter 1 row and 2 columns for the automatic slicing to take effect. These slices are perfect and equi-sized 1080 x 1350. When uploading on Instagram's album post—as an example—I'm able to create a perfect, seamless diptych panorama. I do believe that this request for automation is practical tool and usage scenario. This automation is essentially and inverse of the AP's panoramic function. Starting with a image sized at X by Y dimensions and breaking or slicing into equi-sized P rows and Q columns. Another Usage Example: Instagram Giant Squares or Instagram Grid Art Let's suppose that I want to create an Instagram grid art comprising of 12 tiles at 3 squares horizontal and 4 squares vertical, e.g. [4 3] matrix. Each Instagram square will be 1080 x 1080 pixels. Therefore, the starting image has to be 3240 x 4320. You can imagine that the current slicing tool in AP will require work (and time). Manually creating 1080 x 1080 slices and using drag/drop for alignment or using the transform with some simple math for perfect alignment of the slices. Thank you for considering my feature request. Cheers, Ronald N. Tan | Photographer https://ronaldnztan.com
  • 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.