Jump to content

Search the Community

Showing results for tags 'external editor'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support Forums
    • News and Information
    • Affinity Support & Questions
    • Feature Requests & Feedback
    • Bugs in Affinity Designer & Affinity Photo
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Affinity Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 7 results

  1. Hi everyone! I'm wondering if there's a way to configure Windows 10 Store version of Affinity Photo as external editor? As it's not an ordinary program I cannot just find a path to the executable file and use it in 3rd party software as path to external editor. I tried several workarounds and none of them worked. If it's not possible, then I have another question - is it possible to install ordinary Windows version if I alredy own Windows Store version? Best regards, Andrey.
  2. Hi, so, I am reporting a rather obscure error. It may be difficult to reproduce unless duplicating fairly exact conditions, so I will be specific. System / Software Operating System: Windows 10 Pro 64-Bit 1709 Build 16299.371 Hardware: Gigabyte 15X - i7-7700HQ / 16GB Ram / 1.5TB NVMe SSD / Nvidia GeForce GTX 1070 Max-Q GPU Affinity Photo: v 1.6.4.104 Capture One Pro: v 11.1.0.140 Issue Description Using Capture One (C1) 'Edit with' to edit an existing NEF raw file, a 16-Bit uncompressed TIF file is generated and saved in C1 and then sent to Affinity Photo (AP). Once this file is updated and saved within AP, the TIF file is successfully returned to C1. However, on trying to edit the filename in C1 immediately afterwards, C1 says that the file is locked by another process. This happens on all successive similar edits of NEF files. If one exits C1, and goes back to those files, they are no longer locked and can be renamed. To Duplicate 1. In C1, select a file such as a raw NEF file named IMG-1234567.NEF.2. In C1, right click the image thumbnail, and use 'Edit with' to edit in an external app, selecting Affinity Photo.3. In C1, this creates a TIF file in the same directory, in this case naming the file IMG-1234567.TIF.4. In AP, this TIF file is opened up. The image is simply adjusted (such as brightness or curves) and the image is flattened.5. In AP, use 'Save' in the File menu (or Ctrl-S) and then Exit (you can alternatively just exit AP using the close window button and confirm saving changes to the file on exit).6. In C1, after being returned from AP, the image thumbnail looks okay, updated and all looks fine. 7. In C1, however, it is not possible to RENAME the file, as C1 says the 'item is being used by another process'. Essentially the file is locked from file-based operations, unable to be renamed or deleted. Investigation 1. This occurs when a raw file is converted to a 16-bit TIF files that are uncompressed, using any ICC profile, 300 px/in. fixed 100% scaling, before being sent to AP. This problem does not occur when converting to and sending 8-bit TIF files, jpegs, PSD files or any other from C1 to AP. 2. It only seems to occur when raw files are converted to 16-bit TIF prior to sending. Editing an original jpeg or TIF file, where a 16-bit TIF is made and sent to AP does not produce any issue. 3. I have tried out this problem on a similar hardware system, with the same operating system (Windows 10) freshly installed, and the same issue occurs. However, on a Windows 7 system, this issue does not occur. 4. Using SysInternals diagnostic software, I have ascertained that when the TIF file is returned from AP to C1, the process that has locked the image file is in fact C1 itself, as though it has stalled on some operation on the file once returned from AP, thus locking the file until the software is restarted. 5. Sometimes, when I have tried this, 10% of the time there is no issue, but I cannot determine the reason for this variation. 6. Using 'Edit with' in C1 to call other editing software, such as Photoshop or OneOne PhotoRaw, using a 16-bit TIF is not an issue. Using software, such as Lightroom, to call AP is also not a problem. It is specifically when pairing C1 with AP, using a 16-bit TIF as the round-trip file format. 7. I have had one other user say that they were unable to duplicate the issue, although I cannot be sure that the exact operating system, software and GPU setup were the same. While I do not expect much of an outcome on this issue, I place it here for reference should the issue ever hit another user with similar hardware, operating system and software versions. In many cases, when people try to duplicate such an issue, one of the common reasons that the issue is not duplicated is due to some variable, environmental condition or procedural steps not being mirrored. However, should anyone with this setup like to report back their own findings, I would certainly welcome the information. Thank you, Cass.
  3. Hello Does anyone know how to save a picture back to Foto 3.0 after having edited the file with Affinity 1.6? The changes won't be accepted in Foto 3.0 when I simply "save" the file in Affinity and go back to Foto 3.0. When I do the same workflow with the nik-filters, everthing works without problems. What do I do wrong? Thanks for help Kind regards Hans Pauli
  4. This is a repost - I posted earlier in bugs, but this forum seems more appropriate... How to make "Round-trip" edits from Apple Photos to Affinity Photo and back again: In AP, open the desired Apple Photos image via the media browser (scroll down left hand side bar in "open..." dialogue until you see the Photos "Camera" icon, then select that, then navigate to your image for editing) Note 1: if you double click here to select a photo for editing, it will not open in AP! - this may be a bug. But if you single-click (select) the desired photo then click the "open..." button, it will open in AP, ready for editing. Edit away in AP. When done editing, to save back into Apple Photos, just hit "Save...". The photo will be saved in its original file type on top of (overwriting) the original in the Apple Photos Library. You may also want to save a copy in Affinity Photo format to your desktop, just for safety. BUT! Apple Photos will not yet know the photo has been edited, and will display a proxy image of the unedited original. Don't despair. To quickly rectify this, find and select the image within Apple Photos that you just edited in Affinity, now click the "Edit..." button. Suddenly your Affinity edits will appear, and you can now cancel out of the edit mode in Apple Photos. Ta Da. There is the edited image in Apple Photos. Note 2: If you try to "Save As..." from Affinity then you cannot navigate to the media browser. So you must "Save...". Note 3: You may want to duplicate your photo first in Apple Photos before editing in Affinity, in case you want to save the original. Not sure if this will always work as sometime duplicates are only proxies of the original in Apple Photos. Note 4: Affinity lets you "Save Editing History" but haven't tested if this works via the round trip method above. You're welcome.
  5. Looking to implement an iPad workflow... I would like to cull & do basic edits in Lightroom mobile, and use 'affinity photo'as an external editor. I have had success sending the image to 'photo' from Lightroom mobile, completed the edits to the image, but how do I return the image to Lightroom mobile to view it with the rest of the collection?
  6. I just purchased Affinity Photo but how can make it as the External Editor for Photo app, OSX El Capitan. Thanks.
  7. I posted this in the wrong place (i.e. not in Feature Requests) - sorry! Being able to add AP as the external editor in Aperture is great - it means that I can continue using Aperture to manage my libraries but use AP for image editing from start to finish, as AP send the edited image back to Aperture. However, to continue with the "round trip" analogy, the return drops me off at a different (but nearby) station as the edited image goes into a New Project, rather than being added to the originating one. (I know that Pixelmator sends the edited image to the originating Project/Album and have seen a post to the effect that A***e thingy does so too). Also, I'm not clear what the Batch processing function will do when implemented - will it / could it be used to round trip multiple images from a single Aperture project? Thanks
×