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 discovered the workaround after spending 2 days uninstalling PD then resintalling (after cyberlink told me it was at MY END, and that PD worked fine for them). I was angry to have spent so much time, and that they told me the wrong thing. Their support is rubbish.

Also, they keep shifting features around so you have to go hunting for them!


Quote Wow, you aren't kidding. It's like the Produce Range button is treated as if the main Produce button was clicked instead

I was going to suggest that the desired timeline content can be copied and placed on a new timeline (File | New Workspace) and then produced, but after playing around a little I found a slightly easier workaround.

Take note of the starting time and the duration of the selection you want to produce, then when you click on Produce Range (or even the main Produce button) you'll be able to set the actual produce markers in the Produce room. Here's what I mean:



Once you've dragged the starting & ending markers on the Produce page, click on Start and PD will produce the selected range.

Note that it may be very difficult to precisely set the desired start/end frame positions, so you should start a little earlier and finish a little later so the produced clip can be trimmed to the desired length once it's back on PD's timeline.

This is a clear bug, and I've just reported it to CL on ticket CS002406264.

I think the produce markers are a nice idea, but they need to work in addition to Select Range/Range Produce, and not instead of that long-time feature.

There's also a new change regarding the preview option when producing. Previously, only SVRT wasn't allowed if the preview option was checked, but now hardware encoding will not be allowed either. Maybe that solves some issues that had come up in the past, but it's a big step backward in my opinion.
Go to:   
Powered by JForum 2.1.8 © JForum Team