- #POWERDIRECTOR FILE DETAILS SAYS 240 FRAME RATE PDF#
- #POWERDIRECTOR FILE DETAILS SAYS 240 FRAME RATE FULL#
- #POWERDIRECTOR FILE DETAILS SAYS 240 FRAME RATE PRO#
So, 30fps source, ignore warning and accept default produce profiles, 12 dropped frames. On the other hand, since my timeline has true 30fps source footage in it and if I elect to ignore the message and simply proceed to produce and use a default profile, you see in the same pic I only have 12240 frames, since the default profiles playback is slower, 29.97fps, PD needed to remove frames since the source was 30fps, 12252*29.97/30=12240, a exact match to the frames in the file produced by PD. As seen in attached pic, if I produce with a true 30fps custom profile, I have not added or dropped a single frame, I get exactly 12252 frames in the newly produced file and at 30fps.
#POWERDIRECTOR FILE DETAILS SAYS 240 FRAME RATE PDF#
This 30fps clip had 2042 frames as documented in the pdf (bottom of page 3), 6*2042=12252 frames in my new timeline. I used 6 duplicates in the timeline to simply get the number of frames up so we are not talking a one or two frame delta. For proof I've copied 6 duplicates of the 30fps_Custom.m2ts file I showed and created in the pdf writeup. Thanks PD for prompting me my timeline footage is a little special and maybe I want to validate what I'm doing. However, if one has true 30fps video on the timeline and you create a custom profile at 30fps, you will not drop or add a single frame. Not sure why your view nothing the user can do, can you expand, give a timeline or step procedure example to replicate?Īgain, it's a warning for user caution, do as you wish with it.
I think it should always display the warning when you add any clips to the timeline that are significantly different, like 24, 25, 30 or 50fps when the project settings are 60. Quote: I'm all about making informed decisions, but I personally think PD should not display the warning for 29.97/30 and 59.94/60fps differences because there's nothing that the user can do. In my view, any of these would provide for a clearer user experience while still keeping the user fully informed. Maybe CL could even add those specific frame rates to project settings, especially if the intended output is BR or DVD so no interpolation would even be used or needed.
#POWERDIRECTOR FILE DETAILS SAYS 240 FRAME RATE FULL#
Jeff, as you pointed out there may be certain projects where it's important to know that the frame rates don't exactly match, and if CL added a two-step setting for when to display the warning dialog then the user would have full control over that. I can also ignore the message every single time it comes up with OP's message (which is what the general recommendation is here), but it seems to me that a change to have PD default to (or at least add an option to) ignore the unchangable fps situations would be helpful to most users. I know I can turn off the warning entirely, but then I'm not warned about any significant mismatches where there is something I might want to do. I'm all about making informed decisions, but I personally think PD should not display the warning for 29.97/30 and 59.94/60fps differences because there's nothing that the user can do. While technically 29.97 does not equal 30fps and PD will definitely need to do the work you've detailed, there is no 29.97fps (or 59.94fps) project setting, and this leads to confusion because the user cannot match the project to the clips to heed the warning. This still leaves the question about PD bringing up the warning dialog box in the first place. I agree! You've written up an excellent and completely understandable explanation of what the differences are between 30 and 29.97fps and why that matters.
#POWERDIRECTOR FILE DETAILS SAYS 240 FRAME RATE PRO#
If you have different frame rates in a project, I think you should match the project's frame rate to the highest frame rate of any source clips, especially if you're going to produce at the high frame rate and just ignore the warning (and you can even turn it off under Preferences!)ĭS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitorsĬanon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360° In that case, PD won't create any effects or transitions as smoothly as possible because it's not using every frame in your source clips.Īs far as I know, setting a high project frame rate with low fps clips might cause some delays when editing because PD has to increase the number of frames in the source clips to achieve the project frame rate. They are actually the exact same frame rate, but sometimes PD gets that little detail wrong on certain clips.Īlso, the warning is really meant to alert you that you might lose smoothness if you have 50 or 60fps source clips but have set the project frame rate to 24, 25 or 30.
Nina's recommendation is correct, especially when it comes to a warning of 29.97 vs 30.
0 kommentar(er)
