CyberLink Community Forum
where the experts meet
| Advanced Search >
Quote By the way, just to be clear, I am still using the trial version of PD.

Wow that's a pretty key detail to leave out. The trial version has severe limitations, especially with high resolution clips, but that wouldn't explain why you can't preview the sample clips without difficulty.

If you want, you can uninstall the trial version and buy PD21 or subscribe to PD365 to get the actual program. Cyberlink has a 30-day money back guarantee so you can get a full refund if you and tech support can't get things to work smoothly.

That would rule out a whole bunch of ssues with the trial version
I never use any of the "creator" modules (which used to be called "Magic whatevers") for the exact reasons you stated.

In my opinion, they're tools to get content into a fancy-looking video with very little editing effort, but that simplicity comes at the expense of not being able to make the kinds of tweaks you're looking for.

It's SO much easier to put your images on the timeline, ppick a transition (or a set of them), lay down your audio/music track and set the duration of each image as needed. It certainly is more work to initially set that up, but you'll then have 100% control over every aspect of your slideshow.

With time and more experience, it gets even easier and I don't think you''ll ever look back
If you can share the clip you're having trouble with there might be a clue there. You can upload it to OneDrive or Google Drive and paste a publicly shareable link to it here. See the Share a file publicly section in this Google FAQ or this OneDrive support page.

Alternately drag the clip onto the MediaInfo online tool and attach the text details here so we can see the technical details of the clip.

Otherwise try converting it using a free app like Handbrake and see if that solves the issue.

Last step would be to contact CL tech support here.

You shouldn't be having any trouble previewing, but your DxDiag results show that you've had several LiveKernelLeak 141 errors which might be related to your nVidia driver.

Try following all the steps in this post to check Windows core system files and to do a clean reinstall of your current nVidia 531.41 driver.
You have to use the Attachments button below the forum's text box to share a JPG or PNG image here.

If you're seeing a watermark, that's almost certainly because you're using the free/trial version. If you paid for PD21 or have a subscription to PD365, you first need to uninstall the free/trial version as it cannot be upgraded to the paid/subscription version.
No version of PD will do that. Your best bet is to make multiple copies of the first set of of finished pop-ups, then drag new clips onto each one from the media room and use the Replace option.

That will keep all the existing editing and formatting intact while replacing the original content with the that from each new clip, altough you may need to manually adjust the duration (and keyframe timing) if any are different from your "master" copy.
There's no reason to overthink this. Install PD13 on your C: drive where it will be able to load very quickly from the SSD, and install any of the included extra content packs on your D: drive.

With that said, the total extra content is likely only a couple of GB so there isn't much to gain by installing it on a different drive.

The main issue is that PD13 can't do any hardware encoding/decoding on modern GPU hardware, and if you're still using the original PC the last nVidia driver you can use is 411.70 from 2018, which can be downloaded from here.
Quote Yes, I was aware it was the Intel driver (c 2018). I installed the Intel Driver & Support plug-in and it reports all my Intel drivers are up-to-date. (I agree with you that four years with no update is a little suspicious ... like maybe they've dropped support for that hardware.)

Download and install the driver I linked to like I wrote. Don't use the auto-detect tool.. Your i7-8750H CPU is 8th gen and that driver is for gen 6-10, so it will work.
Contact CL tech support here.

You can include a link to this discussion in your support request, but be prepared to answer a couple rounds of boilerplate questions before getting into anything significant.
To be clear, I was talking about your Intel GPU driver, not the one for your nVidia GTX 1060. That one was current in your DxDiag test report. I still suggest that you update the Intel driver from the link I provided.

If you suspect that the issue is related to the latest nVidia driver, follow the steps here to force a clean (re)install.

Along with the repairs that SFC made, maybe a clean nVidia driver installation will solve your issue.
You haven't given us much to work with. Maybe share a screenshot of the timeline and preview window, or a screen recording of you previewing the problematic clip and then what happens when you added the (produced?) clip to the original project.
The first thing I'd do would be to update the video driver for your Intel UHD Graphics 630 processor, as your version is more than 4 years out of date. Get the latest version from Intel here.

The next thing I'd so would be to run the commands shown in this post to see if there are any underlying problems in Windows.
I have PD14 installed on Win11 and don't remember ever seeing anything like that. Are you trying to save to a removable drive, like a USB stick?
Playing back videos in a media player is different than previewing them on the timeline. Do you see the same slowdown with the raw clips without any of the cropping and resizing? You may want to create a new project for testing.

I see that PD365 has hung several times (as shown in the DxDiag report). Some of those entires show "AppHangB1" and the RADAR_PRE_LEAK_64 events seem to point to an issue with how PD is handling memory. Have you tried uninstalling it, rebooting then installing it again? You won't lose any work or projects.
PD will always play back the clip at the recorded speed regardless of how many fps. You can choose to produce at a different rate, but that only affects how many frames per second there are in the finished video, No speed changes will occur unless you:

a) Intentionally change speed in your PD project or
b) record using the built-in slo-mo feature in your phone (or in FiLMiC Pro)

In other words, if you record at 60p but then choose to produce to 30p, PD will drop every other frame and you will possibly lose some fidelity and smoothness, especially if there's motion. Otherwise the video remains unchanged.

On the other hand, if you record at 30fps and choose to produce at 60p, PD doesn't have any new information so it will simply double the existing frames to fill the additional ones needed.

Here are screenshots for setting the frame rate, which is only available from the Produce screen:

I don't see any issues when my project's frame rate and the FX FPS are both set to 30. I see the counter advance by 1 second per frame whether I count up or use the Reverse time option and count down.

It works the same whether I have the dragged the FX directly onto a clip (black numbers in the below video) or if I place it on a separate FX track (shown with yellow numbers):

This was done on a 60p clip.

I also tried setting the inital value to 20:00:29 and 20:00:24, and both timers work exactly as expected
Many tutorials have been made in the 2 decades that PD has been out. Up until a couple years ago it was only available on Windows, so unless the video says it's PD for Mac you probably assume that it's about the Windows version and those features may or may not be available for Apple users
The Mac version is much more limited compared to the Windows version as can be seen here.
JL_JL answered while I was typing
You might need to download and install the free QTLite pack to fully support Apple QuickTime videos
Go to:   
Powered by JForum 2.1.8 © JForum Team