Jump to content


  • Content count

  • Joined

  • Last visited

  1. I could as a workaround until this bug is fixed, copy the exif data from the original file and paste it into the exported file using ACDSee Photo Professional 2018 (My Lightroom/RAW editing replacement) I realise that Photo does RAW editing but it appears to be a destructive action ie once you've developed the file you can't go back and edit RAW settings or have I missed something? Cheers... P.S. I haven't tried the copy/paste EXIF thing myself..
  2. Thank you! Cheers
  3. Okay I am confused... I have a NIKON D3300 with a 24mpx sensor, when I open and develop the NEF raw file, and I check resize document, I get 6000 x 4000 (or weirdly lately 6016 x 4016) @ 300dpi.... If I go back into Resize document and uncheck resample and set it to 72dpi then export the file to jpeg, not changing the pixel size.. ie same 6000 x 4000px then open that jpeg document in Photo... and check Resize Document, it's still showing 300dpi when it should be 72? I have tested this by creating a 6016 x 4016 72dpi image and placing the previously created image into it and it fits and the information at top left says for placed image 6016 x 4016 @ 72dpi.. So is Photo incorrectly showing the resolution of the opened (not placed) 72dpi jpeg file? or have I missed something here? Thanks for any clarification.. Cheers
  4. DegasBrush

    EXIF file loss and DPI not holding after changing

    Oh.. .sorry my bad.. I'm having a game going the other way! my NEF file comes in at 300dpi and I'm trying to export to 72dpi I think I've opened myself a can of worms here!! LOL!
  5. DegasBrush

    EXIF file loss and DPI not holding after changing

    No no no I found it!! I found out what you need to do... Step 1. Open the RAW file to the develop module (it will do that automatically) Step 2. Edit the RAW file or just click on develop to Photo.. Step 3. Resize Document: Uncheck resample and select 72dpi and hit Okay.. Step 4. this is where the magic happens go to the layers palette and right click on the image and click on RASTERIZE.. Step 5. Export to Jpeg at current dimension or new dimension and save.. You should now have a 72dpi jpeg WITH EXIF... can you try that please?? Cheers!
  6. DegasBrush

    Crash When Using Pen Tool

    I'm glad I found this thread though not before creating my own about the same issue! What I did want to add was that in Designer I tried starting a new document at 72dpi with and without the artboard and simply took the pen took and added lines and nodes and in each case kept crashing at various numbers of nodes added.. in the project I'm trying to work on I had a couple of instances where the app crashed after adding only three or so new nodes!! I hope that helps further with fixing the issue.. Cheers
  7. DegasBrush

    Crashes and CPU spike using Pen tool

    ooops didn't see the other thread!!!... my bad for not searching or turning the page first... I also didn't mention that this issue still occurs in the current beta also... My issue is exactly as @tipforeveryone If you stop the video on the frame when the crash occurs you will see in the performance chart GPU is at 100%.. Good to see you're on this issue...
  8. I'm currently having two issues with Affinity Designer... Purchased copy The beginning scenario is this, I have 40 something mb Affinity Photo file placed into a designer document and I am attempting to trace the image with the pen tool (No auto trace tool yet) as I do this between every three to ten minutes the app just closes! and I have to reopen the app and my file each time to continue. ctrl-s is my friend! I ran it with task manager performance charts visible while working and noted that while idle CPU use is very low while this document is open, and memory is flat at 3gb.. (Installed is 8gb) and no other apps running on the system. However every time I place a node with the pen tool I noticed that the CPU spikes between 80 and almost 100%.. GPU use is low however at the moment of the app crashing/closing I noticed that the GPU spiked to 100%... It drives me nuts but for the time being I am tolerating it as it's a personal project and using Photoshop/illustrator is no longer an option. Is this a memory management issue buried deep in the code??? is anybody else having similar issues? I am happy to provide my file and screen shots of the performance graphs if required. Cheers... Machine specs as follows: Windows PC - OS - Windows 10 Pro 1803 build CPU - i3 8100 (Quad core Coffee Lake) Ram: 8gb DDR4 @ 2666Mhz GPU = Nvidia GTX 770 2gb Vram SSD - Samsung 960 Evo 500gb NVME
  9. DegasBrush

    EXIF file loss and DPI not holding after changing

    Hi there, just tested this... this is the fix ... Where you're going wrong is placing the raw file into a new document.. and that would eliminate the EXIF.. What you NEED to do.. is open the raw file directly in Photo... it will open directly in the Develop module, make any raw edits if needed and hit the develop button.. if you check the image specs through the Document menu (resize document) you will note that the image SHOULD be @ 300dpi and if you invoke the EXIF studio you will still find the exif info still present, then if you export that file to jpeg, it will export to a 300dpi jpeg with the exif in tact.. I assume that's what you're after! I hope that helps! Cheers!
  10. I've just been trying too get an offset of a path (dieline off a shape that's a few mm larger than the shape) and using the stroke-> expand stroke work around isn't great as extra nodes get added over the top of nodes creating issues with strange bumps and lumps and gets worse when trying to remove the extra nodes which then throws out the whole path shape. Can we or is there coming an "offset path" option coming such as there is in Illustrator? and a corresponding tidying of the nodes? And while I am here, will it be possible to reflect a shape around a moveable point as one can do with rotate? Using symbols to reflect about a particular origin seems to be an un-necessary amount of work to achieve something that should take a few seconds? Are either of those features set in the pipeline? Cheers
  11. Okay I've been noodling about with the Wacom driver and playing with the memory settings.. and here's what I found.. I got the to work pretty well in both vector and pixel mode... I got varying amounts of success with the other two - apart from Photo (beta) which works wonderfully.. Which leads me to believe that it may be more suggestive that Affinity isn't playing nice with my configuration including Fall Creators Update, current GPU driver, that my current CPU and installed memory and GPU may not be up to the task but doesn't really explain why Photo Beta works so well and the others not so much.. But I will say that initially Designer was working great in both vector and pixel mode.. then I started playing about in Designer Beta and Retail Photo getting pretty poor results.. then I went back to Retail Designer and started getting the same issues with that..as the others.. I might try getting a mate to download the trials on his machine (much higher spec Desk Top) and hook the tablet up and see what happens there.. it's going to be a few months before my new desktop is built and ready fortunately/unfortunately due to work commitments I need to use illy and PS and the tablet works perfectly with those.. sigh... thanks for listening.
  12. Hi I'm back! I finally managed to make a video.. it was my first go at recording the screen and editing it down.. so I hope you get the gist.. The machine this is occurring on is a late 2014 HP Envy 17" i7 5500U/550 integrated gpu (which I've been using) there's no difference if I switch to the GTX - 8gb DDR3 Ram, 750gb 5400rpm hard drive with an nvidia GTX840M gpu laptop is connected to a 27" Dell 2k Monitor via HDMI I'd understand if the issue was application wide, but it's only the actual work area! as you can see from the video I can use and access the menus and tools.. as soon as it's the edge of the ruler and further in.. toast! Oh in the video the last one Photo Beta, while it appears choppy in the video it's working as it should - the screen recorder was sucking up a lot of ram! And as I mentioned earlier it's working fine over every other application and the OS.. Wacomstylusaffinityissues.mp4
  13. Yes it certainly is odd behavior - especially that I am getting the same issue with three apps and not a fourth plus everywhere else on the system works fine.. anyway yes I'll do my best to get a video made describing the behavior... be back in a day or two!
  14. Mark - Interesting.. yes I did as you suggested - completely removed the wacom driver and software, and reinstalled.. no dice with a caveat, Neither the current version of designer nor the current beta nor the current version of Photo HOWEVER the current Beta of Photo Does work properly as it should! go figure?? In the other three applications, the stylus works as it should in the tool areas ie vertical left, across the top and down the right hand side, but once it crosses into the paste board area, it sort of drops to like 1 frame a second in it's movement across that area.. bearing in mind that the stylus works perfectly across the Adobe software I use (Illustrator and Photoshop) as well as GIMP - is it possible that it's an issue generated from the Fall Creators Update?? Is anyone else with an Intuos Pro having similar issues?? Cheers
  15. Hi - I just installed the above beta, and found my wacom Intuos pro stopped working with it (same issue as the retail version) I tried uninstalling it and reverting back to the previous beta which worked (but now I really need that functionality) but the previous beta now won't work either.. my previous to current beta of Photo still works fine with the Wacom... disappointed.. Symptoms are - just extreme lag so extreme as to be totally unusable - when I tried the previous beta, 33.98 btw the curser was fine until I opened a new document.. I won't be updating Photo beta in the meantime. Cheers