• Content count

  • Joined

  • Last visited

About WMax70

  • Rank
  • Birthday 04/29/1970

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    The Netherlands
  • Interests

Recent Profile Visitors

91 profile views
  1. Thanks, This now turned out to work. Problem fixed
  2. The function (live) High pass filter is not working anymore in v No matter how high or low I put the slider, there is no change. This is one of the default functions I for every picture.
  3. Ahw.... this hurts. So many request to get Nik tools working. Now it is acquired by DXO. But we still want to have Vivenza2 working... please ensure it will... It will be continued. But there are competitors stepping in. They will add value here. https://photorumors.com/2017/10/25/breaking-dxo-acquires-nik-collection-from-google-will-continue-development/
  4. Question -> bug -> improvement Within v1.5, opening a RAW image does not not assign the active present. Boring because I made profiles for my Nikon matching the original camera settings. However, when a new raw is loaded, I always have to select another one first and click back on my profile again before it applies those settings. Same is still valid for the Beta versions. I would suggest, or jump back to default when opening a new image or apply the last active preset. The current situation is incorrect: Showing the present as if applied, but it applied the default.
  5. Same here. Windows 10, Ryzen 1800+, Nvidia 105Ti
  6. Looks like this beta is working more stable now. Great :-) I did not work too long with it to say if it is also faster than the previous versions, but on some parts it looks as if there is performance increase noticable. However, I noticed some non-reproducible issues using the gradient tool. 1) 2x application crash 2) 1x Jumps to "mother" layer above during working on the mask 3) Really slows down the machine, sometimes waiting for 30 sec or more before it comes back, No clue what it is doing in the background, all processors are doing nothing and no services are active in the background. (This I also notices many time during high pass filters) General remarks: 1) Why takes saving to a affinity file so long? Compared to export to a PSD, this one is twice to 3 times faster...?! (Yes I know I loose detailed info about filter adjustment settings when saving to PSD, but I guess this mus be converted which also should take time. For Affinity you could direct save it w/o conversion time)
  7. For speed testing I used : Cinebench and saw in speeds tests online that they used Adobe Photoshop for tests. What I did is a photo stacking test and when done just curves, live high pass filter. The PC often shows, "pc is not reacting". So I have to wait until the processing is finished. In my experience, this is nothing faster on any of my PC's I have hardly any noticeable speed difference. If you compare it into eg cinebench, or on Adobe you'll see noticeable rendering difference so there is a serious difference the way they access / use the processor performance.
  8. Working with Layers and brushes is completely messing up now. Used Brushes (light rays). Wanted to see the difference with and w/o. Here i show this is messing up. Only the last merged layer is shown or the brushes, but the original layer w/o the brushes does not appear anymore. :-( -> Real - Estate brochure photography.
  9. Started perfomance testing for langer real estate work. Worked with two machines in parallel: I7 5575 3,6GHz, integrated video card, 8GB Ram AMD Ryzen 7, 1800x 3,6GHz, liquid cooled, Nvidia 1050Ti, 16GB Ram Both running from SSD Sandisk extreme 960GB You would expect a serious faster response from the AMD, because this one can work with up to 16 cores. I hardly found speed differences. The Intel was ofet loaded to almost 100%, the AMD up to 60 percent. I've no clue why this is not going any faster. I guess, Affinity is not optimized to use all processor cores. (limited to 8) which might result in a max 60% load of the AMD. Using all cores would serious increase speed on those newer AMD processors which are especially designed for rendering these kind of thing. Unfortunately Affinty is not getting the max out of it which turns out in no difference between many processors having 8 cores running around 3,5GHz. I think serious performance increase is possible just by enabling the use of more cores.
  10. Wrt a wish on the develop part; (also not solved in Beta v1.6.0.79) The exposure access Up and Down, go by steps of +1 and -1. For photo editing this is quite unusual because many will never under or over exposure with +1 and and -1 steps. Better would be to have at least half exposures steps. (+ 0.15 EV instead of + 1 and - 1) I expect these arrows to be fine adjustments as UX. If possible the up- and down arrows should be possible for each singe increase of decrease step possible. The current arrows for exposure are imo unusable at the moment. Render speed using Graphic cards: I tested the rendering from the video card vs the processor. Tested NVIDIA 940M, MSI AMD R9 380x and Intel integrated IRIS Pro graphics on a I7 5775R core (Gigabye Brick) I hardly see any load added to be added to the graphic cards when images are rendering, processors instead are loaded very high in many case. The rendering on the graphic cards are set. Can you explain when de cards are being used for rendering? I thing some performance improvements can be done here.
  11. Just started to play around with the Beta. Not sure if those are wanted parts, but: 1) Drag and drop from my Windows File explorer does not work any more.. This would be very bad if this is not working anymore. 2) Plugin Vivenza 2 is still not working 3) With the Develop / Raw presents, the white balance is still not taken in account for a preset. It's still ignored. 4) Setting and profiles from v1.5 are not taken in V1.6. (Manually? or Redo?) Using i7 5775 Core 3,2GHz. I did not really noticed performance differences up to now. But I will play around some more with it.
  12. Somehow, the high pass filter does not seem to work using the marco recorder. I use very often the liniar light + 0,3 high pass filter on my picture, however I do not see that it is applied when I start it from the library. Denoise and other settings are running fine.
  13. Hmm, separate from the rotation bug, there is something strange with the color. The moment I zoom in 2 100% in Vivenza, the color turns to be correct. And edit here is als correct transferred to Affinity. However, any other scale other than 100% messes all up. Looks like a scale bug which does not provide the right color settings. If the rotation & Color bugs are solved, I think I can leave Photoshop Elements. Up to now it is pretty hard to get the production to a fast level.
  14. I've the same problem here. Some NIK plug-ins work perfect, others (like vivenza) does not. Color is really purple. Second problem I have is the orientation in all NIK plugins. Whatever I do, the orientation only drops the landscape in, the Portrait is somehow not working. (All pictures are turned back) Vivenza2 is one of the tools most used by me with Photoshop. Local editing and correction work perfect inhere.
  15. Main topic is about image rotation 1) Canvas Rotate Raw Currently missing the Canvas rotate in RAW. At this moment I have to click at least 6 time to get a 90 degrees rotate. For production adjustment this is not very practical 2)Nik tools images not rotated The moment the canvas is rotated, and a layer is sent to Nik tools, the layer is set back to it's original position in NIK tools) Within Photoshop (and Elements) this worked perfect. Think this is a missed opportunity. Plug-ins are not working properly 3) Raw multiple correction (Rotate, light etc) I could not find an option to open multiple RAW files and adjust them at ons (all same temperature, light and lens correction) This is a very often used feature from Adobe on my side whioch pulls me back to Adobe for Raw editing. Then I doe this local light corrections in Nik tools in adobe and only then I move to Affinity. This is not very practical... So please have a look at this.