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

Gregory St. Laurent

Members
  • Posts

    191
  • Joined

  • Last visited

Posts posted by Gregory St. Laurent

  1. 1 hour ago, Mark Ingram said:

    I'm really not sure why you're all discussing this. We have never given out ETA on releases / patches / betas, etc (and never will, for obvious reasons). I realise you may be excited to try out the new version as an official retail release (or even get a new beta update), but complaining about slow development is not an accurate thing to say. The Windows version has massively improved performance in the most recent betas, and we continue to add new features, and fix bugs as we go. The time period between releases does not reflect the amount of work that is happening, it merely reflects the time delays between when I make a build, how it gets on with internal testing, and then when I release it to the public. We have builds that are never released onto the forum (which happened last week, build #308 crashes on Windows 7, so it was never released externally).

    And with regards to GPU Compute, yes it's something that's on my roadmap, but the complexities of implementing this on Windows are far greater than macOS. macOS has one GPU manufacturer, and Apple are in control of the drivers (you get the latest ones automatically). Windows has at least 3 GPU manufacturers, and the drivers are in a variety of different states and ages - we see that from bug reports here on the forum (i.e. crashes that are solved by merely uninstalling and reinstalling your GPU drivers).

    Aside from GPU Compute (and ability to load RAW files via Apple RAW engine), there are no feature differences between the macOS and Windows versions.

    Sorry I didn't mean to start a firestorm, I'm just anxious and look forward to the new version. I appreciate all the hard work you guys do and really enjoy using Affinity Photo.

  2. 3 hours ago, Jens Krebs said:

    Same on Mac, but everyone who bought the software can download and install a preview version (beta) for update 1.7 (avialble here in the forums) -- these betas are usually updates every couple of weeks simultaniously for Windows and macOS.

    A big update with version number 1.7 is going to be released together with the new Publisher, which is, why things take a bit longer than usual.

    But it seems the Mac version is further along and gets a little more love. The Windows version still doesn't have the GPU acceleration yet

  3. 14 hours ago, Wosven said:

    I really don't understand people asking about why we stay on an OS version when this forum is full of people staying on old OSes for running old programs, or because their companies don't want it for now, etc.

    It's not he purpose of this thread, the main question is why AP stopped working on his computer.

    There are cases where older programs may not work (which from 7 to 10 is very few) but there are very easy ways around that (virtual machines) so I know where you are coming from. My point is the majority of people that are staying on an older OS for no apparent reason is not necessary and then they wonder why they have problems running newer programs? No offense really just an observance.

  4. I really don't understand the resistance of people to not upgrade to Windows 10? It's free and in my opinion is faster and far more stable than Windows 7 ever was. It also must cause a lot of headaches for developers to maintain compatibility to a legacy OS, which is very counter productive to the very reason they hold on to the old version in the first place! Affinity Photo is a modern program so run it on a modern OS simple as that.

  5. 4 hours ago, Mystical said:

    I did not realize the windows version did not have GPU acceleration yet. I've only had Affinity Photo for a few days but it is so smooth and runs very well I assumed it did already. 1.7 sounds to be really awesome. I too heard about Adobe buying Allegorithmic, I mostly use 3D Coat over substance but like their texture creation tools. Been trying to distance myself from Adobe products lately and when I heard the news it made me decide to get Affinity finally after thinking about it for a while.

    You won't be sorry, I myself dumped Adobe I can't stand the idea of renting my software. Affinity Photo is an excellent product and is constantly getting better.

  6. 23 hours ago, MEB said:

    Hi PilleniusMC,
    Welcome to Affinity Forums :)
    Version 1.7 of Affinity Photo for Mac added support for Metal compute (GPU) acceleration for several tasks (besides displaying/rendering the image on screen) thus the frequent fixes for this platform (for issues that have been reported related with its implementation). Affinity Photo for Windows doesn't benefit from any GPU acceleration yet - this is still being worked on. All the other fixes/improvements unrelated with GPU acceleration should come in an upcoming Beta for Windows.

    Are the GPU accelerated functions coming in the 1.7 update for windows eventually  or are we going to have to wait for a later version?

  7. 22 minutes ago, Ztrby said:

    Its a fresh Portrait 18 install (i did'nt have the studio edition of 17). I used the manual install of plugin and pointed Affinity to the folder with the PortraitProPSFilter64.8bf and PortraitProPSFilter32.8bf . I don't understand the "do it manually" part. 

    As I said you don't want to use the .8BF plug-ins you want to use the ProtraitPro program itself as the plug-in. I'm not sure why you aren't seeing 2 plug-ins from within Affinity Photo, I helped someone else with this issue and they had the 2 same as me. Try removing the plugin from Affinity Photo and try reinstalling ProtraitPro and start over.

  8. 8 minutes ago, Ztrby said:

    This is great news, there is hope. But i only have it once with the three dots :(

    Did you install 18 as an upgrade from 17? That is what I did. and don't use the supplied plug-in installer do it manually within Affinity photo and you should see the 2 plug-ins. The plug-in with the 3 dots is a Photoshop .8BF plug-in, you want PortraitPro to start as the stand alone program within Affinity Photo as a plug-in

  9. 22 hours ago, Ztrby said:

    What version of portrait pro are you using? i can't run portrait pro 18 as a plugin at all. 

    I'm running Ver. 18 I initially had problems but I figured it out. If you look in your plu-ins you will see it is listed twice make sure you pick the plugin that doesn't have the dots (eg. PortraitPro... and PortraitPro)

  10. 26 minutes ago, rudyumans said:

    Hmm. I use several Topaz plug-ins (the old ones, non-studio), All of DxO's Nik, Corel's Particle shop, and some others and they all work fine. I don't encounter the same problem as you do. All the files are Tiffs or AP

    Do you have this only with Olympus RAW files?  

    Yes when I bring in a JPEG or TIFF It's fine. This is a new problem in the Beta for me , I never had this issue in the past.

  11. 2 hours ago, mike21 said:

    I have installed the new beta and ran a speed check, comparing it with the current version 1.6.5.135. I loaded a RAW (CR2 format) file of 27.5 Mb; the current version took 20 secs and the new beta 22 secs. I then immediately (without any processing) "developed" in each version - the "stable" version took 15 secs and the beta 1 min 22 secs, with almost all of that time without any sign of activity. I repeated the beta test with the same result. Saving the resulting jpeg in afphoto format and exporting as a jpeg gave virtually equal timings.

    My open speed has improved for ORF files, but I have to agree the develop speed is slower.

  12. 2 hours ago, Sean P said:

    Hi Gregory,

    Have you tried this in a 1.6 version and was it working correctly? It looks to me like your original source file has EXIF rotation metadata. Unfortunately there is already a known issue that this gets lost when handed over to plugins. You could try right clicking the Pixel Layer and selecting 'Rasterise' I believe this should then be rotated correctly.

    This never happened in 1.6 or lower, as a matter of fact this photo was from a shoot that I entirely edited and delivered to the client using 1.6 I chose a RAW from this shoot because of that, to see that it was a bug in the beta.

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