Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by Achim63

  1. I'd also like to see this supported. I tried to point AP to the .lrplugin that I have installed, but that didn't work. It also works from within Apple Photos, just not in AP, which is disappointing.
  2. I think my error was an issue with Photos, I still used a very old Aperture library. So after building a new Photo library and reimporting all pictures that issue was gone. I can reproduce the original report, though. Photos "thinks" the picture is still being used by another app and doesn't update it (as can be seen when trying to edit it within Photos after changing it in AP). Not very relevant to me, since I use Lightroom usually (... as long as the no-subscription version will work ... now would be a great time for a replacement from Affinity ).
  3. I cannot use it at all, as Photos just throws an error trying to edit in AP.
  4. I can reproduce this on an "iMac (Retina 5K, 27'', ultimo 2014)" with the 4 GB Radeon R9 M295X. Metal can be selected from the popup menu, but the filters don't seem to work any faster. The bottom area for Metal is greyed out as well.
  5. I had the Nik filters installed (may have been an older pre-Google version). I reinstalled them after using the ctrl-startup and deleting my user data. Now everything seems back to normal.
  6. First of all, thanks a lot for the update! I tried the light GUI in AD and it's much easier on my eyes than the dark theme. On both my iMacs (an older one at work, a new Retina one at home, both on macOS 10.13.1, German), AP crashes as soon as I try to open the preferences (from the menu or with Cmd+,). I tried deleting the user .plist to no avail. Here's the relevant part of the crashlog: Process: Affinity Photo [4211] Path: /Applications/Affinity Photo.app/Contents/MacOS/Affinity Photo Identifier: Affinity Photo Version: 1.6.6 (1.6.6) App Item ID: 824183456 App External ID: 824080612 Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: Affinity Photo [4211] User ID: 502 Date/Time: 2017-11-02 16:38:49.625 +0100 OS Version: Mac OS X 10.13.1 (17B48) Report Version: 12 Anonymous UUID: 0323F9B2-201F-275E-6096-238AE356C7D4 Sleep/Wake UUID: 84798B34-6573-4739-B888-B52D424F4C2D Time Awake Since Boot: 36000 seconds Time Since Wake: 19000 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Exception Codes: 0x0000000000000001, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Termination Signal: Illegal instruction: 4 Termination Reason: Namespace SIGNAL, Code 0x4 Terminating Process: exc handler [0] Application Specific Information: Crashing on exception: NSConcreteAttributedString initWithString:: nil value Application Specific Backtrace 1: 0 CoreFoundation 0x00007fff4179953b __exceptionPreprocess + 171 1 libobjc.A.dylib 0x00007fff681a8942 objc_exception_throw + 48 2 CoreFoundation 0x00007fff418297e5 +[NSException raise:format:] + 197 3 Foundation 0x00007fff43801c27 -[NSConcreteAttributedString initWithString:] + 135 4 Foundation 0x00007fff4380b4b4 -[NSConcreteAttributedString initWithString:attributes:] + 27 5 libcocoaui 0x00000001025f1a5f -[PreferenceController tableView:objectValueForTableColumn:row:] + 2239 6 AppKit 0x00007fff3eeb3bfb -[NSTableView _dataSourceValueForColumn:row:] + 202 7 AppKit 0x00007fff3ef6c591 -[NSTableView preparedCellAtColumn:row:] + 471 8 AppKit 0x00007fff3ef6c21f -[NSTableView _drawContentsAtRow:column:withCellFrame:] + 50 9 AppKit 0x00007fff3ef6bf2a -[NSTableView drawRow:clipRect:] + 2186 10 AppKit 0x00007fff3ef6b3a0 -[NSTableView drawRowIndexes:clipRect:] + 527 11 AppKit 0x00007fff3ee89be0 -[NSTableView drawRect:] + 1522 12 AppKit 0x00007fff3f5d3e3d _NSViewDrawRect + 83 13 AppKit 0x00007fff3f5e10d4 -[NSView(NSInternal) _recursive:displayRectIgnoringOpacity:inGraphicsContext:shouldChangeFontReferenceColor:] + 1578 14 AppKit 0x00007fff3f5e0aa4 -[NSView(NSInternal) _recursive:displayRectIgnoringOpacity:inContext:shouldChangeFontReferenceColor:] + 56 15 AppKit 0x00007fff3ee73374 __46-[NSView(NSLayerKitGlue) drawLayer:inContext:]_block_invoke + 289 16 AppKit 0x00007fff3ee72f08 -[NSView(NSLayerKitGlue) _drawViewBackingLayer:inContext:drawingHandler:] + 1577 17 AppKit 0x00007fff3ee728d9 -[NSView(NSLayerKitGlue) drawLayer:inContext:] + 77 18 QuartzCore 0x00007fff4c81d6dd CABackingStoreUpdate_ + 279 19 QuartzCore 0x00007fff4c81d5bc ___ZN2CA5Layer8display_Ev_block_invoke + 54 20 QuartzCore 0x00007fff4c81cd9f -[CALayer _display] + 1824 21 AppKit 0x00007fff3ee7189e _NSBackingLayerDisplay + 556 22 AppKit 0x00007fff3ee66715 -[_NSViewBackingLayer display] + 242 23 QuartzCore 0x00007fff4c80ea61 _ZN2CA5Layer17display_if_neededEPNS_11TransactionE + 633 24 QuartzCore 0x00007fff4c80e50f _ZN2CA5Layer28layout_and_display_if_neededEPNS_11TransactionE + 35 25 QuartzCore 0x00007fff4c80d641 _ZN2CA7Context18commit_transactionEPNS_11TransactionE + 319 26 QuartzCore 0x00007fff4c80d1f5 _ZN2CA11Transaction6commitEv + 487 27 AppKit 0x00007fff3f61c6e4 __65+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayRefresh]_block_invoke + 283 28 CoreFoundation 0x00007fff417324d7 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23 29 CoreFoundation 0x00007fff417323ff __CFRunLoopDoObservers + 511 30 CoreFoundation 0x00007fff41714f08 __CFRunLoopRun + 1240 31 CoreFoundation 0x00007fff41714797 CFRunLoopRunSpecific + 487 32 HIToolbox 0x00007fff40a29866 RunCurrentEventLoopInMode + 286 33 HIToolbox 0x00007fff40a294df ReceiveNextEventCommon + 366 34 HIToolbox 0x00007fff40a29354 _BlockUntilNextEventMatchingListInModeWithFilter + 64 35 AppKit 0x00007fff3ed26a23 _DPSNextEvent + 2085 36 AppKit 0x00007fff3f4bbe6c -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3044 37 AppKit 0x00007fff3ed1b831 -[NSApplication run] + 764 38 AppKit 0x00007fff3ecea9d2 NSApplicationMain + 804 39 Affinity Photo 0x00000001007acf54 Affinity Photo + 8020 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 com.apple.AppKit 0x00007fff3f051520 -[NSApplication _crashOnException:] + 109 1 com.apple.AppKit 0x00007fff3f61c923 __65+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayRefresh]_block_invoke + 858 2 com.apple.CoreFoundation 0x00007fff417324d7 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23 3 com.apple.CoreFoundation 0x00007fff417323ff __CFRunLoopDoObservers + 511 4 com.apple.CoreFoundation 0x00007fff41714f08 __CFRunLoopRun + 1240 5 com.apple.CoreFoundation 0x00007fff41714797 CFRunLoopRunSpecific + 487 6 com.apple.HIToolbox 0x00007fff40a29866 RunCurrentEventLoopInMode + 286 7 com.apple.HIToolbox 0x00007fff40a294df ReceiveNextEventCommon + 366 8 com.apple.HIToolbox 0x00007fff40a29354 _BlockUntilNextEventMatchingListInModeWithFilter + 64 9 com.apple.AppKit 0x00007fff3ed26a23 _DPSNextEvent + 2085 10 com.apple.AppKit 0x00007fff3f4bbe6c -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3044 11 com.apple.AppKit 0x00007fff3ed1b831 -[NSApplication run] + 764 12 com.apple.AppKit 0x00007fff3ecea9d2 NSApplicationMain + 804 13 com.seriflabs.affinityphoto 0x00000001007acf54 0x1007ab000 + 8020
  7. I'd define the snap grid according to my needs. Then turn snapping on. Draw first horizontal line, alt-shift-drag to next grid line and then press cmd+j as often as needed. Repeat for the vertical lines. It's faster done than written down. Though I'd also like to see a grid tool somewhere down the line, I see more important things on the roadmap.
  8. To find your RAW images, do a right click on your Photo library file (usually located in ~/Pictures/), select "Show package contents". In there there's a "Masters" folder which contains the JPG and RAW files next to each other in the subfolders which are ordered by date.
  9. Yes please - I tried to set the touch ring on my Wacom to change brush size with no luck yet because of this oversight.
  10. Whenever I saved an AD file to desktop, it showed up with an all white icon. Previewing by pressing the space bar works, also Cmd+i shows the contents. Now I found out why: in OSX 10.10 there's a checkmark in the preferences for each folder (Cmd+j, "show icon preview", "Symbolvorschau einblenden" in German) - setting the checkmark makes the icon appear as expected. Maybe that's the issue that many users experienced.
  11. Thank you, that's what I was looking for - but not on the other end of the context bar. This should rather be near the fill color selection - or the fill color field might be disabled or somehow greyed out while that checkmark is not set. I don't really get the sense of the checkmark, since I can set the fill to "none" regardless. So now this is an improvement request by a user blinded by a very crowded UI ;-)
  12. I think this topic came up already, but I couldn't find it, so sorry if this is already answered: If I use the pen tool ("P" in the Draw Persona), set its stroke color to "none" and the fill to any color, on the second click of the pen tool the fill color switches back to "none", so I get an invisible object. I tried all kinds of color selections (context menu above and color wheel on the right) - after closing a form and starting the next, on second click it's back to none. It shows the previously selected color in the context menu bar again after finishing a shape or curve, but doesn't use it. This is very counter-intuitive - I can e.g. draw multiple rectangles without loosing the selected fill color - for the predefined forms it works as expected. Maybe I missed a user setting for that? I think it behaved differently before 1.2.1.
  13. Since AFAIK emf doesn't support drawing of splines, Affinity wouldn't to themselves a favour with this - the exported files might look worse than the original. I think having SVG and PDF should be sufficient for all platforms.
  14. Why then do you press Esc too many times? Sounds like "If I fill my glass of wine too many times, I end up over the pan puking" and trying to blame someone else for it. But I also think that using ESC to exit full screen was a very bad decision of Apple, maybe we should all open support tickets to make them change it.
  15. This sounds like a handy feature indeed. I'd like to have it.
  16. I think this could end up very confusing. Why not simply cut your path with the node tool and Action:Break Curve before giving different attributes to each part? If you want to keep your fill, copy/paste the object before cutting it up. The app wouldn't know what exactly (between which nodes) to fill if your suggestion would be available. What would be nice, though: for now only one node can be broken at a time, it doesn't work on multiple nodes - I think it would make sense to be able to hit Cmd-a while the node tool is selected and then with the break action all selected nodes would be broken apart.
  17. Draw the three big triangles, convert to curves (if you used the triangle tool), copy all three and paste, then select Divide from Operations in the toolbar - voilĂ , there are your new triangles that you can color differently.
  18. No, unfortunatly not - that's one of the reasons for my idea to have it in AD itself.
  19. Then you're right - snapping to the middle of near objects is not in (yet?) as far as I know. But the alignment tools work fine in such a situation.
  20. As a good and affordable 3D app I'd recommend Cheetah3D. AD is not made for this and probably never will.
  21. I just tried this and for me the green and red lines on the rectangles show up when drawing a circle between them. I started at the upper right corner of the left rectangle and dragged to the lower right.
  22. Nice, thank you! Let them be coming!
  23. Sorry if I sounded impatient and thanks for the reply. I actually searched for similar discussions in the forum, apparently with the wrong key words. I also experienced those blobs, but infrequently and couldn't reproduce it reliably. Let the devs take their time - better a stable and complete release than some hurried patches that might lead to more problems later. If I need to, I can always switch to Painter, iDraw, Intaglio and some other apps that I have available, but hope that one day AD will be the first tool to go to for each of these cases - so far I'm pretty happy with the whole user experience and UI of AD. Working in the software business as QA engineer (though not in the graphics field), I know how difficult it is to please everyone - and AD seems somewhat stuck between the needs of artists and those that like to make technical drawings with exact measurements. I'm sure it will all fall into place eventually, hoping it will lean more towards the artistic direction.
  24. I wonder somewhat that there's no reply yet - didn't I make the issue clear enough? It might even be a bug, since long lines like in the spiral loose nearly all of the thickness variation that was still there while drawing it.
  • 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.