DxO ViewPoint compatibilty

[Jan Shim]

I'm evaluating PSP 2018 my first 64-bit PSP. I have a favourite perspective correction plugin that only works in 32-bit and the developer has no plans to release a 64-bit one so a research led me to realize that I already have a very powerful tool called DxO ViewPoint 3 that I use with my raw editor DxO OpticsPro. When I invoked ViewPoint 3 from within PSP 2018 to work on an image, the corrections made aren't applied to the image when I click Save. At the same time I tried the same with Photoshop CC 2.15.5 and it worked perfectly.

Has anyone had any experience with using DxO ViewPoint and also FilmPack as plugins?

[Jan Shim]

Dropped DxO Support a note and got this reply I wanted to know but unfortunately not what I needed. I think a script may get it to work like how it was done with NIK scripts once upon a time when they weren't made compatible yet.

Hello Jan,

Thank you for writing. At the present time, DxO ViewPoint cannot be used as a plugin or external editor with Paintshop Pro. We will be happy to pass along your interest in this capability to our development team for their consideration. A suggestion on your behalf will be automatically created and sent to the developers once this ticket is closed.

Thank you for contacting DxO Customer Support and please have a good week. If you should need additional assistance with other program related issues or have any other questions, please do not hesitate to use our online support system.

regards,

Seth
DxO Support Team

[JoeB]

If DXO Viewpoint is available as a standalone program (invoked by a .exe file) then the JSJ script used for the Nik plugins will probably work - no guarantees. Also, if Viewpoint is a plugin for your DXO Optics Pro than the Optics Pro program should be able to be run with the script and you can use Viewpoint within Optics Pro and - again probably - you should be able to run Optics Pro using the script and return the result to PSP.

IMPORTANT NOTE: KEN HAS PLACED A COPY OF THIS ENTIRE THREAD ON THE SCRIPTING SUB-FORUM AS OF EARLY JANUARY 3, 2018. SO ALL FURTHER DISCUSSION AND CONTINUATION OF THE THREAD SINCE THEN HAS OCCURED IN THAT SUB-FORUM. IF YOU INTEND TO READ/FOLLOW THE WHOLE DISCUSSION YOU MIGHT WANT TO JUST GO TO THE LINK BELOW WHERE THE COMPLETE - AND ONGOING - DISCUSSION IS AVAILABLE BECAUSE NO FURTHER POSTS HAVE BEEN ADDED TO THE THREAD IN THIS FORUM SINCE IT WAS COPIED TO THE SCRIPTING SUB-FORUM. FOR THOSE WHO WISH TO FOLLOW OR CONTRIBUTE TO ANY FURTHER DISCUSSION, THE LINK TO IT IN THE SCRIPTING SUB-FORUM IS HERE:

http://forum.corel.com/EN/viewtopic.php?f=104&t=62978

[Jan Shim]

Viewpoint is available both as a standalone and as a plugin. I don't know enough about scripting to experiment beyond replacing the line that executes Nik's .exe file. I gave that a shot (the v2 script) and I couldn't recall what I did but out of the 10 times or so I ran, there was just that ONCE TIME where it worked (edits were applied to the original image after leaving Viewpoint standalone). I haven't been able to replicate that since and have given up. There were also no error flags of any kind.

[JoeB]

Do you have Viewpoint available in your Optics Pro? If so, try editing the script to point to that program and use Viewpoint there and see if that works.

[Jan Shim]

Yes I do. I have Viewpoint in Optics Pro and also Photo Lab, common license for both programs. I'm not keen on launching Optics Pro OR Photo Lab to use Viewpoint because: 1) takes too long for either program to load 2) Viewpoint Standalone (and via .8bf) not only launches immediately but UI offers additional functions not available in OP/PL.

[Jan Shim]

Screenshot of standalone Viewpoint 3

[JoeB]

I hadn't used the standalone Viewpoint because it's already fine for me in Optics Pro, and I've only spent a short bit of time using Optics Pro as a standalone. So I tried out Viewpoint standalone, but it's v.2.5 and doesn't have quite all of the options that your image of v.3 has. However, using 2.5 and the script it works for me in both 32bit and 64bit PSP. However, when invoked with the script the CANCEL and SAVE buttons do not show - I only see them in Optics Pro, which I haven't scripted. So I have to go to File>Save and then File>Exit. Once I do that the script continues and applies the corrected image as a layer on the original in PSP. You can't use File>Save As because the script has its own save location, and you can't just use File>Close because that closes the image but not Viewpoint.

I just pointed the script to the Viewpoint 2 executable in Program files.

[Jan Shim]

Are you using the v2 scripts from http://forum.corel.com/EN/viewtopic.php ... 92#p275433

If not, you mind letting me try your script to see if it works with Viewpoint v3?

[Jan Shim]

This is what I tried that didn't work

from PSPApp import *
import os
import subprocess
import tempfile
import uuid

def ScriptProperties():
return {
'Author': u'JSJ',
'Copyright': u'Copyright (c) 2013 Login:',
'Description': u'Procesa la imagen actual con Color Efex Pro 4 y devuelve el resultado en una nueva capa (script v2.0)',
'Host': u'PaintShop Pro',
'Host Version': u'16.00'
}

def Do(Environment):
# DxO Viewpoint 3
nombreCapa = 'Viewpoint'
# 32 bits
#filtroExe = u'C:\\Program Files\\DxO Labs\\DxO ViewPoint 3\\dvpv3.exe'
# 64 bits
filtroExe = u'C:\\Program Files\\DxO Labs\\DxO ViewPoint 3\\dvpv3.exe'

# formato del fichero temporal: JPEG | TIF
formatoFichero = 'JPEG'

# fichero temporal
if formatoFichero == 'JPEG':
extensionTmp = '.jpg'
else:
extensionTmp = '.tif'

ficheroTmp = os.path.join(tempfile.gettempdir(), tempfile.gettempprefix() + str(uuid.uuid4()) + extensionTmp)

# EnableOptimizedScriptUndo
App.Do( Environment, 'EnableOptimizedScriptUndo', {
'GeneralSettings': {
'ExecutionMode': App.Constants.ExecutionMode.Silent,
'AutoActionMode': App.Constants.AutoActionMode.Match,
'Version': ((16,0,0),1)
}
})

# guardamos la imagen en un fichero temporal
if formatoFichero == 'JPEG':
App.Do( Environment, 'FileSaveCopyAs', {
'Encoding': {
'JPG': {
'Variant': App.Constants.JpegFormat.Lossless,
'CompressionFactor': 1,
'ChromaSubSampling': App.Constants.ChromaSubSampling.YCC_1x1_1x1_1x1,
'EXIF': True,
'EmbedJPGICC': False
}
},
'FileName': ficheroTmp,
'FileFormat': App.Constants.FileFormat.JPG,
'FormatDesc': u'JPG JPEG ',
'WorkingMode': 0,
'GeneralSettings': {
'ExecutionMode': App.Constants.ExecutionMode.Silent,
'AutoActionMode': App.Constants.AutoActionMode.Match,
'Version': ((16,0,0),1)
},
'DefaultProperties': []
})
else:
App.Do( Environment, 'FileSaveCopyAs', {
'Encoding': {
'TIF': {
'Compression': App.Constants.TiffCompression.LZW,
'Channels': App.Constants.ColorChannels.RGB,
'EmbedTIFICC': True
}
},
'FileName': ficheroTmp,
'FileFormat': App.Constants.FileFormat.TIF,
'FormatDesc': u'TIF Tagged Image',
'WorkingMode': 0,
'GeneralSettings': {
'ExecutionMode': App.Constants.ExecutionMode.Silent,
'AutoActionMode': App.Constants.AutoActionMode.Match,
'Version': ((16,0,0),1)
},
'DefaultProperties': []
})

# procesamos la imagen con el filtro
print "FILTRO: " + filtroExe
print "FICHERO TMP: " + ficheroTmp
args = [filtroExe, ficheroTmp]
subprocess.call(args, shell=True)

# cargamos la imagen procesada en una nueva capa
App.Do( Environment, 'FileOpenAsNewLayer', {
'FileList': [ficheroTmp],
'GeneralSettings': {
'ExecutionMode': App.Constants.ExecutionMode.Silent,
'AutoActionMode': App.Constants.AutoActionMode.Match,
'Version': ((16,0,0),1)
}
})
# pone un nombre de capa más "legible"
App.Do( Environment, 'LayerProperties', {
'General': {
'Name': nombreCapa
},
'GeneralSettings': {
'ExecutionMode': App.Constants.ExecutionMode.Silent
}
})

# eliminamos el fichero temporal
os.remove(ficheroTmp)

[JoeB]

I am using the script that was translated into English by AK, which should otherwise be the same script. I'm attaching a zip file of my script. Just change the line 26 to reflect the path to your Viewpoint 3 executable. The layer being returned to PSP will be named DXO Viewpoint. Remember, it will be cropped by Viewpoint after the perspective correction so will be a smaller visible image layer.

[Jan Shim]

Same result, unfortunately.

Tested with 'Save, Close, Exit' and no difference.

When Viewpoint screen closes (after clicking Yes and selecting JPEG quality) I immediately see very quick flashes of screen activity, a new layer is created (like before) but neither layer reflects change.

[JoeB]

Well, I had an issue this evening but now it seems to have cleared up. I'll start by saying that yesterday I tested that script many times in both the 32bit and 64bit PSP2018 and it ran flawlessly. After seeing your last post I fired up 64bit again and tried it and it failed with a script error saying the file type was unsupported. So I closed that and fired up 32bit PSP2018 and ran the script again. It worked flawlessly, several time in fact. And because the script I sent was coded to save in .tif format I changed it to save as .jpg which is what you seem to have done, and ran that and again it worked flawlessly. So I closed 32bit and reopened 64bit PSP. Both the script using the .tif save and the .jpg save worked flawlessly with several different images.

So at this stage I'm stumped for you because it's working again for me and, when it first failed it did so for the strange reason that it found the file type it was trying to pass back to PSP was unsupported and didn't even produce a layer. And that's strange because, of course, both .tif and .jpg are supported.

So the failure I did experience (running it a couple of times) seemed an anomaly and cleared up after closing and reopening PSP. And it wasn't the same as your issue because the script then failed to return the image to PSP as a layer.

To be specific as to my procedure (I'll give it using the .jpg version I tested tonight) that is working again is as follows:

1) Open image in PSP 2018 64bit (or even 32bit).
2) Click to start the script.
3) The image appears in Viewpoint and I adjust the perspective.
4) I click on the menu item File>Save.
5) A dialogue pops up where I can choose the jpg compression level (or tiff compression) if that's the script I use).
6) Click OK on the compression option dialogue.
7) Click File>Exit and the image returns to PSP as a layer.

I will test several more times again tomorrow after a reboot and reopening those PSP versions again and let you know if I have any issues.

[Jan Shim]

Ok, curious, I ran the the same script that wouldn't work in PSP 2018 64-bit in PSP X9 32-bit and it worked beautifully. ONCE. Running it again produced the same results as PSP 2018 — just leaves a layer of unmodified image. Weird.

[JoeB]

Ok, curious, I ran the the same script that wouldn't work in PSP 2018 64-bit in PSP X9 32-bit and it worked beautifully. ONCE. Running it again produced the same results as PSP 2018 — just leaves a layer of unmodified image. Weird.

I'm afraid I can only agree that what you are experiencing is weird, because I simply do not have that issue with my system, PSP2018 64bit and Viewpoint 2.5. I fired up PSP again this morning, opened an image, invoked the script with the .tif save option which opened Viewpoint, changed the perspective, clicked Apply button, went to File Save, got compression popup and clicked OK, went back to File>Exit and the new layer appeared on the image in PSP. I tried it with two different images. I also tried it when the image in PSP was a background layer, regular raster layer, and a further duplicate layer. I get the same results if I use the script with the .jpg option.

And here's the thing. If the script runs fine the first time you run it then that indicates to me that the script actually works, even with you using a different version of Viewpoint than I am using. Something is happening (something being stored in some cache, etc???) that the script is running into after its first successful run that causes it to not find the copy of the image saved from Viewpoint. From your description it is only finding and returning the original image that was sent from PSP to Viewpoint.

Maybe someone else more knowledgeable than I am about computer operations can come up with a reason this is happening. From my experience with the JSJ script it tends to work calling almost any external image editor. I have a version that, if I use PSP 2018 64bit as my main program, will call my 32bit version of PSPX9 to allow me to use the 32bit plugins in that program and then return the resultant image back to PSP 2018 64bit. I'm nowhere near an expert but I can't see why it shouldn't work for most if not all external editors that can be run from an executable (i.e., it won't work if you're trying to call an 8bf file).