Nicely done, I'm pleased to see you fly nice and low, so many people shoot their videos as if they're map making and seldom have a dominant element in the shot. Color looked pretty good too.
Hey there, Unsharp mask is definitely the way to go when you want to sharpen something in Premiere Pro CC. That being said, I actually use the regular Sharpen tool instead only because Unsharp mask really increases my render time. See I also use a Denoiser plug in from Red Giant, and when I combine this with Unsharp mask the render times are kind of crazy. I once had a 4 minute video take close to 18 hours to render, and that’s with a good computer and fast graphics card. I heard though that the new Premiere Pro update helped to shorten render times when using Unsharp mask, so I’ll have to test that out sometime soon.I have recently started editing with Premiere Pro CC and just starting to get to grips with it. I agree that you will need to sharpen in RAW format, as you do with stills, out of interest which sharpen technique is your preferred. In Photoshop I tend to use High Pass. In Premiere I have been using Unsharp mask?
If you have good footage in raw it should look bad. A flat profile is what you want and that should look bleached and washed out. It is supposed to as it is capturing as much dynamic range as possible. This does not look good in its raw form so to speak.
Good footage always requires post processing. This is how you edit video.
If you get great footage out of the camera it is being artificially sharpened and color corrected in camera.
To me, this is not good. I want it to look bleached out.
Take that bleached out footage in Premiere, color correct it and it should be a big difference. That extra bleached out data gives you more room to work in post, especially in shadows etc...
Only the highest bit rate I've seen out if the camera is 50Mbps
I think people are mixing up MB and Mbps. DJI uses Mbps and states the Phantom 4 is 60 Mbps. Yuneec uses MB and states the Typhoon is 100 MB, which is actually more like 80 Mbps (if my math is correct). The noticeable difference should be in shots like panning. If you pan up too quickly with the Phantom 4, you may get small artifacts beginning to appear in the video. You should see less of these on the Typhoon H. Unfortunately to achieve a better picture or video than a Phantom 4 you also need a quality lens, processor and software. These are the three areas it appears the Typhoon is a bit weak on even though it has a high Mbps rate.
With the latest firmware I did some testing that shows total bitrate for Gorgeous at 50074kbps, Natural at 49933kbps and RAW at 47590kbps. In another thread on this forum that was confirmed as well. Though not great not as bad as 29Mbps or 29696kbps.So, when Yuneec and DJI says 60Mbps, this is 60/8 = 7,5 MB/s
Unfortunately Yuneec's footage looks blurish because it slows down the frame rate and looses detail of the captured image, especially in RAW, (29Mbps = 3,6 MB/s)
Maybe it is software problem and can make it with a firmware update or hardware's capability
It's very small but it's still there. Typhoon H with Intel® RealSense™ nearly half way down the page.
They have changed the figure to 60MB on the Advanced version but still have it for the 'Pro' which is sure to get people's backs up if they bought the Advanced based on misleading advertising but new customers get the advertised 100MB.
So, when Yuneec and DJI says 60Mbps, this is 60/8 = 7,5 MB/s
Unfortunately Yuneec's footage looks blurish because it slows down the frame rate and looses detail of the captured image, especially in RAW, (29Mbps = 3,6 MB/s)
Maybe it is software problem and can make it with a firmware update or hardware's capability.
Just to be clear, RAW mode changes the image *less* than any of the others (that's a good thing!). All small sensor cameras produce slightly 'blurred' images out of the sensor - then usually in-camera software puts in sharpening to make it look more detailed. This happens with all action cameras - from GoPro though to DJI and 'no-name' brands. RAW switches off the artificial sharpening, it doesn't 'loose' detail.
The point here is that the little processor in the camera only has so much power. It uses the 'simplest' compression algorithm that does the job and might do basic sharpening, but that's never as good as you can do in professional software on a desktop PC. For the best quality output, you want to make sure the camera does as little as possible, then do it properly afterwards. RAW may look 'blurry' but it has all the information you need for the best possible final image.
Not all compression is the same. I can compress video much more on my PC in post processing than a little GoPro can whilst it's filming and still get better looking results. Making the bitrate higher by turning up sharpening in the camera doesn't give you more information, it just makes the video harder to edit later.
So, if you don't want to edit the video, feel free to turn up sharpening and use Natural or Gorgeous modes to boost the saturation. It'll also give you higher bitrates, but that doesn't mean much.
If you do plan to edit the video and want the best possible image quality, shoot in RAW and expect to add a sharpening effect (unsharp mask or similar) and colour grading in post processing.
DerStig, I hadn't seen the comparison of the different camera codes before, thanks for posting that. I think you have some of your information backwards, though. The thing that stands out to me is that Yuneec uses a much longer GOP than DJI does (24 b-frames vs. 8 b-frames between i-frames). That makes it more efficient at the same bitrate than DJI's implementation. As you undoubtedly know, encoding a full i-frame (independent frame) takes much more bandwidth than encoding b-frames (differential frames). The DJI codec has three times as many independent frames as the Yuneec codec, which takes fewer resources to encode and decode, but requires more bandwidth. On the downside, every differential frame has to trade off fidelity for efficiency, so having a GOP that is too long will result in loss of quality between independent frames.
DerStig, I hadn't seen the comparison of the different camera codes before, thanks for posting that. I think you have some of your information backwards, though. The thing that stands out to me is that Yuneec uses a much longer GOP than DJI does (24 b-frames vs. 8 b-frames between i-frames). That makes it more efficient at the same bitrate than DJI's implementation. As you undoubtedly know, encoding a full i-frame (independent frame) takes much more bandwidth than encoding b-frames (differential frames). The DJI codec has three times as many independent frames as the Yuneec codec, which takes fewer resources to encode and decode, but requires more bandwidth. On the downside, every differential frame has to trade off fidelity for efficiency, so having a GOP that is too long will result in loss of quality between independent frames.
Is he still posting? Yes, he gets a lot of his information back to front I'm afraid. He's an expert though, so we're not allowed to contradict him.The DJI and Yuneec codecs have very different characteristics, but I've not seen any evidence yet of quality issues that can be attributed to the codec of either platform. Unfortunately the fixation on bitrates is a bit like the fixation on pixel counts that dominated camera marketing a decade ago - it's a convenient number that consumers can latch on to. I'd be more concerned about sensor size and Nyquist Limit but these are things that marketing guys can't sell and that show up the hard limits of the sort of cameras you get with this class of drone.
The implementation may be different, but they use the same ISO-standard video format and profile. The implementations are constrained by the same specifications.only there is a discernible degradation due to temporal error and yes MP42 is an older codec.
Your analogy doesn't make any sense. We are talking about an international standard that guarantees interoperability. There are no doubt small differences in the way the codec implementations handle the detection of inter-frame changes, but these are likely not perceptible by the average user -- realistically you would have to subtract one frame from one implementation from the same frame of another implementation to visualize them. And most of the differences would be hidden by the 4:2:0 chroma subsampling that these codecs use.it's Ford vs Chevy, the both use V-8's they both are rear wheel drive therefore they are the same. No but hey if it makes you feel better go on and think that
I think your wording is wrong as you've written MBps twice.
Your analogy doesn't make any sense. We are talking about an international standard that guarantees interoperability. There are no doubt small differences in the way the codec implementations handle the detection of inter-frame changes, but these are likely not perceptible by the average user -- realistically you would have to subtract one frame from one implementation from the same frame of another implementation to visualize them. And most of the differences would be hidden by the 4:2:0 chroma subsampling that these codecs use.
We use essential cookies to make this site work, and optional cookies to enhance your experience.