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 >
I have to admit to being (previously) blissfully unaware of Stable Diffusion. From what I've read and watched, it's unlikely to ever be incorporated into PhD.
Stable Diffusion has very little to do with photography. It's a process that involves generating images based on text prompts (e.g. "a painting of a whale & a goldfish in a beachside cafe") where the user can set parameters to modify how the image is generated.
QC2.0 is right to point out the AI Style tools. They have some similarity with parts of the tools (PC or online). i.e. you can set the style of painting in the example above e.g. "a painting of a whale & a goldfish in a beachside cafe" & set the style to "Van Gogh"
It looks like fun to play with, but I can't see it ever being part of a photo management package.
Essentially, if photos have been previously resized on export (as I know you do), capture dates are somehow reset.
Further testing reveals that other photo editing apps interpret the capture date from exported photos correctly, so the capture dates aren't "reset". They're misinterpreted by PhD.
There's no need to feel "older by the minute". It's reasonable to be confused or baffled, but I don't believe it's anything you're doing wrongly.
I've filed a report with CyberLink explaining the results of some testing I've done here. It's up to the CL development team, now, to investigate further & resolve the issue.
As an afterthought I've imported some pics from a more recent folder. It has saved by capture date!
That statement perfectly reflects what I've found here.
Essentially, if photos have been previously resized on export (as I know you do), capture dates are somehow reset. That's why they're being imported showing "today's date" as the capture date.
The investigation continues, but thank you for raising it here It's important for the developers to be made aware.
Some other thoughts on your question about capture dates...
1. Are they original photos from the camera or have they been edited previously. In PhD, the default setting is to retain EXIF metadata but that can be changed in the Export settings.
2. I'm aware that some online photo storage facilities (like Google Photos) have been known to "not recognise" the date created/taken and insert "today's date" instead. I don't know if this may have been a factor in your case.
3. PhD, as you'd be aware, does recognise the date created & is displayed as Capture Date in the Metadata tab. That's what leads me to suspect something may have happened outside PhD.
4!!! Paul, I've just discovered something disturbing. Still investigating so no conclusion yet.
Photos I'd exported from PhD which (a) previously imported showing the correct capture date) & (b) show the correct capture dates in Windows Properties, now get imported into PhD showing the WRONG capture date. When imported using "by Capture Date" th're filed under today's date. Importantly, I did not check the option to remove EXIF metadata om export.
There's something strange going on. I'll gather more evidence & report this to CL, even though it may not relate to your problem.
I've had clarification from CL about this question.
CDR9is the most recent lifetime license/perpetual version released.
Why is there an update patch avaiable for CDR10? There is a special product called PowerDirector Ultimate Suite (only sold in Japan) which includes CDR10 (perpetual). That's what the patch is for
I'm sorry to hear the issue is persisting for you. It seems this problem is bigger than both of us!
Can I suggest you contact CyberLink Technical Support. Please provide them with a link to this thread so you don't need to explain the issue again. They may be able to offer some more productive guidance.
I just went through the same process with PhotoDirector AI Style Pack Vol.6. Uninstalling via Windows leaves the App Data >>> Content Pack folder unchanged. i.e. the folder "PhotoDirector AI Style Pack Vol.6" still contained the same files after uninstallation.
I deleted the folder manually... then reopened PhD to redownload the Textures.
That process deletes the .json file you referred to. It's regenerated once you open the PhD module again.
Firstly, thank you Jeff for adding your knowledge & insights into this thread (& all the other threads to which you contribute). It's always much appreciated.
Here, ADR has no problem importing the MP4 you attached. There's no "white box". Do you mean the screen stays frozen & you cannot import the file, or does it disappear & allow import?
Like optodata, I'm unable to replicate the issue here (even on an older PC I'd expect to exhibit issues).
I've checked the PCs where PhD365 is installed & the file path for installed files is as shown in your screenshots, with installed files showing in C:\Program Files (x86)\CyberLink & in C:\Users\UserName\AppData\Local\CyberLink\PhotoDirector. Where "effects" have been downloaded, the pack is listed in Settings > Apps & Features.
It would be a very frustrating issue & I can see you've tried a number of things to try to understand & correct it.
Questions:
When you uninstalled PhD after optodata suggested it, did you also uninstall the effects packs separately?
Has the issue only appeared recently (e.g. after an update)?
I'm afraid I have no concrete suggestion to correct it but, perhaps, uninstalling the effect packs might "clear the decks".
The most recent lifetime license/perpetual version of CDR I have installed is CDR9 (released in 2020).
This time last year (2021), when PDR20, PhD13 & ADR12 were released, I was informed that the perpetual version of CDR had been discontinued. I have never seen or heard of CDR10, optodata, so I'm confused by the fact that there's an update patch available for it.
It is a little confusing when there are different versions available, but I think it's important to correct something.
PhD14 is NOT a trial of PhD365.
PhD14 has a lifetime license (i.e. you'll have it for life once you've paid for it).
PhD365 is a subscription for 1 year (i.e. you'll have it for 365 days, after which the subscription must be renewed)
I'd suggest you have a look at this comparison chart before making your final decision.
Agreed. The thumbnails of the Stickers & Overlays are slow to load, particularly the animated ones.
Personally I'm not much of a user of these features of PhotoDirector, so I had to go exploring to investigate your issue. From your post, it sounds like your experience has been more annoying than mine.
I found that once I'd downloaded a number of stickers/overlays & placed the in "My Favourites" (purely for easy access), the thumbnails loaded readily.
This was on a Win 11 laptop, 16GB RAM, i7-11800H @ 2.30GHz, NVIDIA RTX 3050 Ti
Firstly, thank you for attaching the photos. They've provided some useful information. Secondly, there's never any need to apologise for asking questions. It's a sign of intelligence & the best way to learn & improve what you're doing.
Both your Nikons (D7100 & D5000) output photos at 300PPI. There's absolutely no need to increase that when you're exporting. I'd leave that setting at 300.
When you get some spare time, & if you're inclined, you might like to have a read of this PPI explainer (which I think is very good!).
I understand your need to reduce file size to ~5MB to meet the requirements of the organisation.
The export settings you use will depend on (a) which camera you've used & (b) your camera settings.
(a) D7100 can output 6000 x 4000 px, which equates to 20 x 13.333 inches (300PPI)
(b) D7100 can output 4800 x 3200 px, which equates to 16 x 10.667 inches (300PPI)
(c) D5000 can output 4288 x 2848 px, which equates to 14.293 x 9.493 inches (300PPI)
For (a) I'd use the setting below, which will give you a 2850 x 1900 px image <5MB
For (b) & (c), I'd use the settings below, which will give you a 3000 px (wide) image <5MB
Cyberlink.com uses analytical cookies and other tracking technologies to offer you the best possible user experience. By using our website, you acknowledge and agree to our cookie policy. For more information on cookies or changing your cookies settings, read CyberLink’s Cookie Policy.
It's important for the developers to be made aware.
Paul, I've just discovered something disturbing. Still investigating so no conclusion yet.
Perhaps it's because the DPReview samples are from a pre-production model (?).
