|
|
haha great. And yeah I noticed that it was now 3000 kbps.
Am I correct in assuming that, other things being the same (resolution, bitrate, etc), the quality will be better with MP4 than say AVI?
|
|
|
Hey Tony,
Yeah I tried that to produce a 960x540 video at 3000 kbps but PowerDirector crashed when I tried to use it :/
EDIT: This document is perfect, thanks. Maybe I had some other settings screwed up. I'll play around with it.
|
|
|
|
Quote:
2. Set the bitrate at 6000kbps (which is the minimum allowed)... or whatever bitrate you want
Tony, sorry to drag this up, just found it.
Why is 6000 kbps the minimum allowed?
I'm trying to encode a relatively small filesize video and I imagine the newer codes (i.e. H.264) will give better video quality in a smaller filesize. However I have limitations on the size I can upload, hence I would like to encode at, say, 3000 kbps.
Thanks
|
|
|
|
Quote:
I have just tweaked an mp4 template to create a 3000kbps video bit rate (+audio). It is a do-able and reasonably simple procedure.
Dafydd, sorry to drag up an old post, but is it possible to create a 540p MP4 template?
It seems PD13 doesn't come with any native 16:9 profiles for encoding MP4 with either H.264 or H.265 lower than 720p.
I'm trying to produce the highest possible quality 16:9 video under 100 MBs. I understand the newer codecs produce better video quality with smaller file sizes, hence I'd like to use H.264 if possible; unfortunately there are profiles for creating 16:9 (widescreen) MP4 video at lower resolutions such as 960x540 or 640x360
Thanks
EDIT: questions answered in another post:
http://forum.cyberlink.com/forum/posts/list/13225.page#255765
|
|
|
Hey ynotfish, I just watched your video link. What program did you use to open the profiles?
I've been using Notepad which works but I don't know what a lot of the values are stored as.
Also can we modify MP4 profiles the same way?
Thanks
EDIT: I'd like to make more 16:9 MP4 profiles such as 540p output, which is currently not available even if I try to create a custom profile.
Possibly similar to this method:
http://forum.cyberlink.com/forum/posts/list/17939.page
but when I tried that and changed the resolution (i.e. to 540x960), PD crashed 
|
|
|
Awesome thanks Tony.
To be honest I'm not even sure what video bitrate means. Maybe you could enlighten me?
There were some links to tutorials that evidently explained how to make the .PRX files although they are not working for me:
|
|
|
|
I would also like a 24p version of 1280x720 if possible. Thanks!
|
|
|
I agree wholeheartedly that PowerDirector should come with more native 16:9 formats. I am running PD13 and I still don't see 16:9 output with most of the formats unless I want HD or full HD (which I don't).
Could someone please make .PRX files of the top 8 or so resolutions here?
https://en.wikipedia.org/wiki/16:9#Common_resolutions
The link above to the tutorial is no longer working.
Also how do we get 16:9 output on H.264 or H.265? Again I am looking for lower resolution (i.e. less than 720p).
Thanks!
|
|
|
|
Yeah again I set it to 1080p and 30fps. Is there another setting I can try? Not sure what you mean by "bitrate" other than the resolution and the framerate.
|
|
|
|
Quote:
As you've discovered, you can't be guided by the snapshot resolution, unless it's a snap of a produced video (after stabilising or cropping). As far as the "snapshot machine" knows, it's 1920x1080... until you render it. It's the same in PDR14.Tony
Hi Tony, Sorry but I'm still a bit confused. If you produce the cropped video, the output resolution BECOMES 1920x1080 because it gets upsampled to whatever you set the output to be (no way to set the output to the current native res). How do you take a snapshot of a produced video then, and determine the cropped resolution?
I guess what I'm saying is, are the resolutions below the actual resolutions of the snapshots, or were they based on estimated custom resolutions which were based on estimations from using the grid?
Quote:
- Stabilser set at 20 = 1842 x 1036
- Stabiliser set at 30 = 1806 x 1016
- Stabiliser set at 40 = 1760 x 990
- Stabiliser set at 50 = 1728 x 972
Cheers - Tony
Thanks, the grid could help.
|
|
|
|
Quote:
These calculations were made by applying the standard PDR stabiliser at different settings, taking snapshots & measuring the degree of cropping.
Tony, in PD13 at least, when I apply the stabilization and subsequently take a snapshot, the snapshots have the same 1920x1080 resolution as well :/ although they do appear to be zoomed in to the same degree, which is confusing.
I'm trying to use a stabilization setting of 20 with rotational shake and enhanced stabilizer both check to yes.
|
|
|
|
Quote:
And yes - in Video Crop - calculating the degree of crop has the same level of guess work/estimation.
Using the process I described above, I stabilised & cropped a 1080p video & produced to 720p.
Hmm.. interesting. How did you get the crop to be the exact number of pixels you wanted though? Trial and error? Or is there a way to numerically enter how much to crop?
|
|
|
Tony,
Awesome thanks. No you're not overthinking and this is what I was going for. It's nice to know the proportion of the video that gets trimmed using the stabilization tool. I wonder if this varies video to video though, and with the rotational tool selected or not.
The problem now is figuring out how to take off exactly, say, another 316 pixels using the crop tool, haha.
Anyway, yes that's what I'm looking for, it would just be nice if we could get PD to "do the math" for us.
|
|
|
That's what I thought. The problem with that approach is that step 1 will result in a slight amount of upsampling, then with step 2 you still don't end up with the native resolution you desire.
Let's say you start with 1080p video. Applying image stabilization will trim a few pixels off the borders (who knows how many), resulting in slightly lower than 1920x1080 native resolution. You can't simply save the video file(s) as-is (without producing) or produce at whatever the existing resolution actually is, you have to select the output resolution (say 1080p again); hence the result is upsampled to a degree to get back to 1920x1080 when you produce.
Then once you import this slightly upsampled video and apply a crop, there's no way to achieve, say, exactly 1280x720 of the original video pixels. The end result will always result in some amount of up/down sampling to achieve the production resolution (720p in this case).
Why can't we just tell PD what our end-goal is (in terms of pixel dimensions) and let it figure out how to optimally apply the cropping and stabilizing?
Another idea would be to have a stabilizer tool embedded in the crop tool, such that when you crop the video you can select an option to apply stabilization as well, but outside of the cropped frame instead of inside.
A third idea would be an option to set the number of pixels that are removed during stabilizing, so that you know exactly what the resolution is after the stabilization, and you could then adjust for this. I don't like this idea as much however because with PD there's also no way to set the number of pixels that are removed during cropping.
|
|
|
Currently when we crop in PD13 all the applied effects are ignored. As a result, if you stabilize before you crop (or vise versa) you don't know what the final video resolution will be.
Thing is, when you crop the video, you have all this excess, waste footage on the periphery of your video. Hence is there a way to tell PD to apply the stabilization using this excess, rather than cropping even more inside of the already cropped frame?
Ultimately what I'm trying to do is apply image stabilization and crop the video to zoom in thus ending at a video of 720p native resolution.
Thanks
|
|
|
I have been using PD13 now for over a year and I love it. I typically edit video filmed at 1080p and 30fps.
We recently purchased a GoPro for filming and I used the same settings for filming - 1080p at 30fps. Now when trying to edit the video the preview is painfully slow and choppy, to the point that I cannot edit the video.
Does anyone have experience with using GoPro videos in PowerDirector? Is the MP4 container somehow different to the point that PD chokes on it? Any other pointers for editing these?
Thanks
|
|
|
I want to accomplish something very similar usind PD13.
I have video that was filmed at 1080p (1920x1080) and I'd like to crop it to 720p (1280x720), thus zooming in.
I don't care about the panning because I'll use key frames and may move the video around, I'd simply like to crop the video to exactly 1280x720 so there is absolutely no scaling in the product.
I made a PNG that's 1920x1080 with a rectangle 3 pixels wide that's 1280x720; however the overlay apparently doesn't show up in the crop video tool.
Also, perhaps the video crop tool has changed with PD13 because I couldn't find any scaling options associated with the keyframe.
Any other ideas?
|
|
|
|
Looks like that did the trick. Thanks!
|
|
|
|
Also it can read the video because it plays the source video fine and displays the thumbnails on the clips within the timeline. It just won't play these clips!
|
|
|
|
Quote:
Usually a codec problem I believe. I take it this is on a different machine. If you Google "K-Lite Codec Pack" and then install that, it will probably resolve the issue for you.
Thanks for the suggestion, but that didn't do the trick. Yes it's a different computer - as I mentioned I created this project on my work computer then transferrred (incorrectly I take it from above) to a flash drive and now I'm trying to edit on my laptop. My work computere uses Windows 7 whereas my laptop is running Windows 10 (which sucks btw).
I installed the codeck package (basic version, then normal install) and I still have green clips.
It's odd because literally every other clip - from the same source video - is green whereas the rest play normally. Clips 1, 2, 4, 6, 8 and 10 of the same source video are green. Clips 3, 5, 7, 9 and 11, again from that same original video, play normally.
|
