- C:\Program Files\DxO Labs
- C:\Program Files\DxO Labs\DxO FilmPack 6
plugin DXO Filmpack 6 grayed out
Moderator: jsachs
-
- Posts: 420
- Joined: January 29th, 2019, 11:47 pm
- What is the make/model of your primary camera?: Nikon Z8
plugin DXO Filmpack 6 grayed out
I tried setting up the Filmpack 6 plug-in folder as either :
Re: plugin DXO Filmpack 6 grayed out
PWP is still on Film Pack 5 -- will update when I get a chance.
Jonathan Sachs
Digital Light & Color
Digital Light & Color
-
- Posts: 420
- Joined: January 29th, 2019, 11:47 pm
- What is the make/model of your primary camera?: Nikon Z8
Re: plugin DXO Filmpack 6 grayed out
It would be useful to let the user define plug-ins without intervention by the developer. This is how Nikon Studio and DxO Photolab interface with external programs.
Re: plugin DXO Filmpack 6 grayed out
PWP does not if fact support Photoshop plugins -- just those that include a stand-alone application that it can invoke. This makes it difficult to create a universal plug-in interface.
Jonathan Sachs
Digital Light & Color
Digital Light & Color
-
- Posts: 420
- Joined: January 29th, 2019, 11:47 pm
- What is the make/model of your primary camera?: Nikon Z8
Re: plugin DXO Filmpack 6 grayed out
I would very much appreciate if PWP could include an open interface to external apps like Nikon NX Studio or DxO Photolab. Please note that I am not referring to Photoshop plugins, but to external applications such as Microsoft Research ICE, DxO Nik collection, Viewpoint and Filmpack.
In DxO Photolab
the user simply selects "Export to application", and the interface allows the user to add applications to a list of recently-used applications. No special setup is required prior to use.
DxO's user interface for exporting to an external application is shown below: The list of previously used applications is stored in a user.config file. For example, an excerpt of DxO's Photolab user.config contains data for exporting to PWP8 and Microsoft ICE:
Code: Select all
<setting name="RecentApplications" serializeAs="String">
<value><ArrayOfanyType xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"><anyType i:type="a:Application" xmlns:a="http://schemas.datacontract.org/2004/07/DxO.OpticsPro.DopCommon"><a:FileName>c:\program files\digital light &amp; color\picture window pro 8\pwp 8.0.exe</a:FileName><a:LastUsage>2021-06-03T18:39:36.2601985Z</a:LastUsage><a:Version i:nil="true" xmlns:b="http://schemas.datacontract.org/2004/07/System"/></anyType><anyType i:type="a:Application" xmlns:a="http://schemas.datacontract.org/2004/07/DxO.OpticsPro.DopCommon"><a:FileName>c:\program files\microsoft research\image composite editor\ice.exe</a:FileName><a:LastUsage>2021-02-01T16:59:03.7928719Z</a:LastUsage><a:Version i:nil="true" xmlns:b="http://schemas.datacontract.org/2004/07/System"/></anyType></ArrayOfanyType></value>
</setting>
In Nikon NX Studio:
the user can declare the applications in user preferences as shown below:
Also, an application can be added on the fly as shown in the screen capture below:
-
- Posts: 239
- Joined: June 18th, 2010, 4:27 pm
- What is the make/model of your primary camera?: Pentax K1
Re: plugin DXO Filmpack 6 grayed out
Maybe some kind of Drag-and-Drop mechanism will do.
exec <external-program-name.exe> <filename>
exec <external-program-name.exe> <filename>
Winfried
-----
migrated to Windows 10 in Nov. 2019
PWP Pro 64
CUDA not available
-----
migrated to Windows 10 in Nov. 2019
PWP Pro 64
CUDA not available
Re: plugin DXO Filmpack 6 grayed out
I have had this on my things to do list for quite a while but you are the first one to ask for it. Integrating an external program into the non-destructive editing paradigm is clumsy at best as illustrated by the current plugin interface.
Jonathan Sachs
Digital Light & Color
Digital Light & Color
-
- Posts: 420
- Joined: January 29th, 2019, 11:47 pm
- What is the make/model of your primary camera?: Nikon Z8
Re: plugin DXO Filmpack 6 grayed out
As an initial implementation, the integration of external apps does not need to be complex, or "remembered" in the workflow. It could simply be an option similar to "save", whereby external image files are created, as usual, and then provided as input to an external program, defined by the user, and launched.
In the case of Microsoft ICE, or DxO's Nik Collection HDR Efex Pro, the input consists of a set of images. This set could be (1) selected images (2 ) all images produced in the branches stemming from a certain root node.
It should also be possible to launch an application using as input files that are already existing (no save required).
Pierre
In the case of Microsoft ICE, or DxO's Nik Collection HDR Efex Pro, the input consists of a set of images. This set could be (1) selected images (2 ) all images produced in the branches stemming from a certain root node.
It should also be possible to launch an application using as input files that are already existing (no save required).
Pierre