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 >
Quote: Finally got around to installing the PD13 trial. Looks like for the most part a HUGE improvement over PD12 when it comes to high res displays. Plays quite nicely with my 15.6in 3200x1800 display in it's native resolution. I would say the only part of the GUI that still could use some work on high DPI is the timeline 'ruler' (or whatever it's called). The font/numbers here is still rather small (IMO).

I'm going to play with the trial some more, and will likely purchase an upgrade soon.

Screenshot included:


Thanks for posting up your screenshots.

Glad to hear the GUI is readacble on a 15.6 display. I got rid of a Yoga 2 pro with the same resolution of 3200x1800, but only 13". I need the mobility of a smaller laptop.

Are there any Yoga 2 Pro users out there who've tried PD13? Are the UI elements as improved on the 13" display?

[SOLVED]

Thanks for the reply Tony.

I just stumbled on the solution. The error message is misleading because it's incorrect.

When I was creating my custom animation, I had the "Downloaded" PiP effects tag selected.

Well, turns out I don't have any downloaded PiP effects. And, PD12 thought I was trying to use a downloaded effect (aka imported template) despite the obvious selection to create a new hand drawn animation in the Paint Designer. It didn't matter what aspect ratio I had set. PD would throw the error. If my project was 16:9, it would say the imported template was 4:3. If my project was 4:3, it would say the imported template was 16:9. In either scenario PD was requiring me to change the project's aspect ratio. At least that's what the error message led me to believe.

What I needed to do was select the "Custom" tag before clicking on the pencil icon to create the hand drawn animation. Hand drawn animation using Paint Director are considered *Custom*, and that tag must be selected. Actually, I went ahead and tested creating a hand drawn animation object with all the other default tags and it works just fine. Only when the *Downloaded* PiP tag is selected did I get the error.

As you said, the template is created and stored under the custom tag, but that error message sure is confusing, and annoying. I wasted waaaay too much time trying to figure out what was wrong.

Is this a bug? I could sure make the argument that it is. A more user friendly response would be to either: 1. say that you must select any other tag in PiP designer besides the Download tag, or 2. Just have PD automatically switch to the custom tag where the custom template is saved anyway (my choice).

So if you Cyberlink folks are reading this, please add that to your punch list of annoyances to fix please.
It is set to 16:9. I'm afraid you misunderstand the nature of the problem.

The problem is that PD12 is telling me...

'The imported template's aspect ratio is 4:3, while you're project's is 16:9. You must switch you project's aspect ratio to 4:3 to use this template."

I'm not using an imported template. I don't even know what PD12 is referring to by imported template -- either in the context of the project, or in the context of Paint Director.

Just as a test, I opening a new, empty project with aspect ratio 16:9. I got to Paint Director and attempt to create the drawing animation. I get the same error.

In my project, I have a slide, a static picture where I want to use Paint Director to animate the drawing of a circle around something on the image. In this case, I'm circling the price on an Amazon sales page.

I open Paint Director, select the pen, adjust the line widtch, color, etc and record the drawing of the circle. So far, so good.

However, when I SAVE the animation, I get an error. PD12 say the "template" is 4:3, but my project is not and I must change my project to match the template. Huh?

What template is PD talking about?

This is a new project with just a simple video bookended by a couple of pics. The project AR is set to 16:9. I didn't use any predefined template.

Seems like every time I want to do something simple, PD freaks about something that makes no sense.

Any ideas?

Screenshots are attached.
Quote: HighRise - the truth is, that most of the content packs (as holiday, weddings, etc.) are utter crap. Who would use so 80ties looking amateur cartoonish looks anyway?

Also - as for modern transitions, all you imo need is clean cut, fade and maybe blur/glow, and that's it.

...

What I absolutly hate though, is that you can't influence things like slideshow - no ability to tweak the templates, set the duration time. I would really welcomed, if it would generate real timeline content, not just one content block with zero ability to further tweak it.

...



I completely agree. I'm reluctant to give PD13 a try just to see if there are any improvements in rendering speed, but I haven't seen any release notes on that point.

The Title Designer and it's kludgy text editing are horrendous. I often find myself wanting to jump to a paint type program and create static text slides because PD's text editing takes so much effort for even the simplest tasks.

Yes! The trial version is online. I'm downloading now.

However, I no longer have a high DPI display. I got rid of my Lenovo Yoga 2 Pro ultrabook (13" display @ 3200x1800) because PD12 didn't scale User Interface (UI) elements in the program. Icons and menus were impossibly tiny. I tried every conceivable way to scale the screen and zoom the desktop (Win8.1) with no satisfactory results. I was completely disappointed and went back to my ultra-poratable 11.6" screen @ 1366x768, which is very usable with PD 12.

So, if someone has a super high resolution screen that's 11.6", 12", or 13" and can try PD13, please post your results. Thanks.

This seems like such a simple function and should be intuitive, but it's not. I simply want to delete a track that has clips on it I no longer wish to use. There's seemingly no way to do it short of deleting all the clips on the track. WTH?

If you right click on a video/audio track in PD12, the context menu shows the an option to "remove track" but it is is grayed out and not available. I can't figure out any situation or combination of circumstances that make that option available. I thought that maybe you have to delete all the clips on a track first, which would be poor design, but even deleting all the clips on a track first doesn't enable the remove track option.

I then thought that maybe it was just video/audio track 1, since PD seems to protect other things about the 1st track. But I can't use remove track on track 2, but for some weird reason video/audio track 3 showed the remove track option.

All I can do for now is select all clips on a track and delte them all. I'm still left with an empty track and the empty space is annyoing. Why can't I just remove or delete a track, and do so in a simple intuitive fashion.

Any ideas?

So what's up with that? There are some things on PD I find should be easy and intuitive, but just aren't. Don't get me started on touchpad gesturing to scroll and resize in PD12. It's clunky at best.

Any ideas?
Nope. Turned that off, created a new project, put the same video on the timeline and got the same exact error.
PDR12
Win7, x64
Build 2109

The first thing I try to do with PDR generates an error. What's up with that.
This error has been reported several times before, but the only solution seems to be to turn off the warning and proceed. Why not jsut fix the problem.

I imported a video with the characteristics shown in the Media Info screen below...



Note that it's 30 fps, the same as my General preferences setting as showing the screenshot below. I tried creating a new project and importing the video, yet every time I drag it to the video line I get the "Timeline Frame Rate Conflict" error dialog.



So, what's up with this error? It seems like it would be a simple issue to resolve.


wi
Still an bug that should be addressed. It's annoying to say the least.
Go to:   
Powered by JForum 2.1.8 © JForum Team