Jump to content

0Kami

Members
  • Content count

    14
  • Joined

  • Last visited

  1. dmstraker, Thank you for creating and sharing this valuable reference. If anyone is interested, the YouTube channel PiXimperfect just presented a video that complements this PDF very well. It’s title is: The Science of All 27 Blend Modes in Photoshop: https://www.youtube.com/watch?v=i1D9ijh3_-I
  2. 0Kami

    Free brush packs - Both Vector and Raster

    Thank you!
  3. Mikerofoto, You are welcome. Since I use the Nik collection more for landscapes edits rather than portraiture, its Luminar functionality serves me well. I hope that it does the same for you. Since none of the Affinity staff has given an update to their progress toward fixing the Nik/Apple/High Sierra issues, I was just writing a direct note to the moderator of this section of the Forum. I will post whatever news they share. Take care.
  4. Mikerofoto, I am a firm believer in workarounds, however, I do not have the old Google NIK collection installed and don't believe that it should be necessary to install it in order to access the new DXO version . . . call me old-fashioned but I think that the Affinity engineers' should be willing and able to make AP compatible with the "new" DXO NIK. The new DXO version works just fine with my Skylum Luminar software. And, it seems that AP Windows users are not having the same problems as Apple users with the upgrade. For these reasons I have to think it is an Affinity Mac version compatibility issue. Thanks for your post and your participation in the Affinity Forum discussions. Endeavor to Persevere.
  5. Can someone at Affinity please give an update regarding the company's progress toward solving the NIK Collection compatibility issues being experienced by Mac High Sierra users. Thank you.
  6. MEB, thank you for the response. Please keep working on the Mac version of the NIK Collection. Many loyal Affinity Photo users would like to use the more stable/supported software (and take advantage of the price reduction until July 1). Have a good one!
  7. Mr. Smith, thank you for sharing your research/findings about Affinity's compatibility with the "new" NIK collection. I'm surprised that you have not gotten a response, or at least an acknowledgment, of your post by the Affinity staff. They are usually very good about addressing these comments. I am following the various NIK collection discussions and the Affinity team has been unusually silent about their progress (or lack thereof) in finding a solution to these problems. Hopefully, the team is hard at work on the solution, talking with DXO/Apple, etc to get it fixed.
  8. Mr. OldRadioGuy, I cross-referenced your findings to another post of the Affinity forum (Will Viveza (Nik) be fixed for Affinity?). Here is their response: "We only support .8bf plugins, we do nothing specific for Nix plugins and nothing we can do to support them directly. They definitely changed something in the new release as they worked fine with the old "Google" plugins." I'm not trying to start any "war of words" on the forum but would love to see a single thread where the Affinity Folks address the software's problems and their efforts to address it/create a workaround. At least tell us if they are working with DXO to resolve the issue.
  9. Are these questions in reference to the “old” free NIK collection, or are they referring to the new DXO paid collection? I ask because of the reference to the statement: “as it crashes in their code and not ours.” This assessment conflicts with the research of another Affinity Photo user who tested the new DXO NIK collection release across several non-Adobe programs. Below is their statement posted on the DXO forum: “Affinity Photo – The programmers of this increasingly popular editor need to do some tweaking of their app, because it won’t run the new Nik-DxO plugins. Since both PhotoLine and Luminar will run the filters, I believe the problem is with their code, not DxO’s.” I would like to purchase the more stable NIK collection (and support DXO’s efforts to keep the software alive) but I would like to know that Affinity will support it. Thank you for any information you can supply.
  10. Hello Affinity Support, There are several active threads about the newly released NIK collection. This demonstrates how many Affinity Photo users are interested in updating our NIK software collection to stabilize the software and support DXO for keeping it alive. Could Affinity please keep us updated about its progress in making internal adjustments to AP to get the NIK software working? It would also be comforting to know that Affinity is reaching out to/working with DXO on how to make the “new” NIK Collection AP compatible. Perhaps it would be worthwhile to post your findings not only on the Forum but also on the company’s Facebook page. Thank you for your consideration.
  11. Certainly glad to see the DXO update, but the website only mentions Adobe products and Aperture. Does anyone know if the updated apps will work with Affinity Photo?
  12. DM1 - Thank you for the example of using the Perspective Filter to make image adjustments. Great job! I think the use of the Perspective Filter will work on images that are straight on shots, as is the one used in the Perspective Skew Correction tutorial. Or, even angled shots using the two plane option on the Perspective Filter. Unfortunately, most architectural shots that I am required to take are interior photos using an extreme wide-angle or fisheye lens. In these cases, neither the single or two plane perspective tool (in combination with the lens distortion tools) is adequate to make the corrections required for marketing use and/or client satisfaction. It is for this reason that I hope that Affinity will create a Mesh Warp tutorial that addresses this more complicated issue. As you can tell from my image samples, I have experimented with the tool but would really appreciate a short overview from the software developers/experts to ensure I'm using the tool correctly and efficiently. Again, thank you for your reply. Happy Editing!
  13. As a follow-up to the recent Perspective Skew Correction Video by Affinity Photo, I attempted to take the perspective correction one step further by using the Mesh Warp Tool. Below shows the original image used in the video, the application of the Source Mesh, the resulting Destination Mesh, and the resulting image. If the experts at Affinity know an easier way to do it, please let me and the other Affinity Photo devotees how . . . .
  14. I am new to the Affinity and the Forum. I'm trying to make the full transition to AP from PS and have found only this issue that I cannot overcome or find an in-program workaround. Since this post is 4-months old, has there been any additional insights into the problem? I can resize the image to a print standard 300 dpi by adjusting the pixel ratio and dpi to the output size I need, the resize without resampling. The "new" document can even be saved at that resolution as an 300 dpi AP document or exported as a 300 dpi TIFF. Unfortunately, when I attempt to export either of those documents as a JPG the result is, as everyone here is commenting on, still at 72 (but the pixel size remains true). Sorry, to reiterate the problem, but thought I should share my experience with AP in full. Thank you for your time. Please post if a solution or workaround is available. **An update (before the moderator could approve the original post) I continued to explore the other AP forum contributors and discovered another question that resolves the problem of keeping the preferred higher dpi at export. Here is the workflow that was successful for me: 1. Imported 72 dpi image 2. Changed the dpi to 300 and unchecked resample image* *(this allows the pixel size remains the same) 3. Resize the image to the ratio/size that I need using the 300 dpi setting and then keep the resampling checked. 4. Export JPG (prefer the Bilinear setting) 5. Click “More” below the Export guides. 6. Uncheck “Embed Metadata” and close 7. Export When I opened the saved JPG it retained the 300 dpi resolution. I hope this is helpful.
×