Announcement: Our new CyberLink Feedback Forum has arrived! Please transfer to our new forum to provide your feedback or to start a new discussion. The content on this CyberLink Community forum is now read only, but will continue to be available as a user resource. Thanks!
CyberLink Community Forum
where the experts meet
| Advanced Search >
Export Image - Default values on Saved Profiles not correct
AmeliaM [Avatar]
Newbie Joined: Oct 18, 2017 11:19 Messages: 2 Offline
[Post New]
This seems to have been broken for so long - I've been waiting for several updates now to fix this. I can't be the only one who has noticed this...

I have a saved profile on Export which includes the setting of "Image Sizing -> Resize to Fit" to "3600 Pixels"on the "Long Edge". The "Don't increase photo resolution" is NOT selected (but it shouldn't be affecting my particular problem). This problem doesn't affect the export, but the actual values retreived into the saved profile field.

Assuming orginial image is 6000 x 4000 pixels*

a) If I don't do anything to the image sizing, the saved profile works - defaulting the Long Edge value on the export to 3600 pixels.
b) If I crop the picture just alittle (eg 5819 x 3878 - ignore specific #'s just look at general trend) - the saved edge value changes to be 'close to 3600' - in this case 3599 pixels - it SHOULD STAY at 3600!
c) If I crop the picture even more (4701 x 3133), the Long Edge value defaults to the height - 3133 instead of the saved value 3600.
d) If I switch the photo croping to be portait (2665 x 3999) again the save profile defaults the Long Edge setting to the height of the actual picture- 3999.

Every time I export an image that has been cropped, I am having to check and override my 'saved' profile resizing. I saved my profile at 3600 pixels - I expect it to stay at 3600. Please fix this error in your program!


Thank-you!

Version: 12.2.2525.0
Version Type: 365
Windows 10
[Post New]
Hello AmeliaM,

Welcome to the PhotoDirector forum laughing

I can confirm the issue you've reported with cropping & exporting using custom profiles in PhD365 12.2.2525.0. PhD12 (perpetual) does not exhibit the same issue.

In the morning (when I'm more awake), I'll prepare a screen capture for CyberLink's reference and report the issue to the development team.

Thank you for posting. I was blissfully unaware of the problem.

PIX PIX YouTube channel
[Post New]
Hello again AmeliaM,

I was wrong in my statement above regarding PhD12 (perpetual). Exactly the same thing occurs in both versions.

Oddly, even though the details of the custom profile appear to change, the exported photo consistently matches the original saved profile.

e.g. I created a profile with "Longest side" = 3000px & used it each time I exported cropped photos. Every single exported photo has its longest side as 3000px, despite the changed numbers in the export dialogue.

I'm yet to test whether this is peculiar to the current PDR12/365 versions or whether the issue is present in previous versions.

PIX PIX YouTube channel
[Post New]
My testing has revealed that the same issue reported above applies noy only to PhD12 & PhD365, but to many previous versions. PhD11, PhD10 & PhD9 are all similarly affected. PhD8 retains its custom profile settings.

I stated above that, despite the issue of numbers changing in custom profiles, exported photos were always sized correctly. In my exhaustive tesing on 3 different PCs using multiple versions, this has most often been the case. In one session, however, the exported photos were NOT sized according to the profile set. This was corrected once a new project was started.

Here is an unlisted screen capture showing the issue. It was recorded using PhD12 (perpetual), but applies to the versions listed above.



The issue will be reported to CL for their investigation.

PIX PIX YouTube channel
AmeliaM [Avatar]
Newbie Joined: Oct 18, 2017 11:19 Messages: 2 Offline
[Post New]
Hi - Thank-you for all the work that you have put into investigating the issue / forwarding it on. I appreciate all your time!
Powered by JForum 2.1.8 © JForum Team