|
|
ps. optodata - you have a sick computer configuration ..... 
|
|
|
Quote
Raw file uploading right now. It will be 10-15 minutes from now at least. You can see the creek starting at 30 seconds.
Thank you in advance.
Seems like its failing the upload - could be too big of a file. Would have to use some ftp to send that over to you.
Bottom line with HW Accelerator OFF & Video Rendering Disabled the artifacts are the smallest - NOT as original footage but slightly noticable. Which will definatelly suck because CPU gets a hit and you can't use your good GPU for it. I'm not in the professional league but there is definatelly something wrong with PD17.
I mean why such a huge difference in file size? It will definatelly hit on the quality. Is this normal or bad software?
I might be picky but degradation of the original footage is there. So this is definatelly settings issues (even though they were customed) or software limitation - which is more likely.
|
|
|
Quote
I think you mean that with a constant 100Mbps bitrate, the 24p video will have more data per frame (4.16Mb/frame @ 24p vs. 3.33Mb/frame @ 30p). In theory, more data allows for higher quality in each frame.
Yes, I'm sorry for not being clear. Thank you.
Quote
You've got a very clear encoding test for pixelation and detail quality here. Can you also upload your original drone clip to the OneDrive folder? I know that it's 4GB in size, but I'd like to see how it captured the creek to compare it with the produced samples you've shared already.
Raw file uploading right now. It will be 10-15 minutes from now at least. You can see the creek starting at 30 seconds.
Removing the Video Rendering definatelly helps, still little artifacts but way better. Even by just looking at the rendered size tells you something.
Thank you in advance.
|
|
|
Quote
24, more data? You mean you think you can record longer duration? If you are capturing both at 100Mbps, then the duration and the end video file is the same size. The lower framerate will just result in a softer somewhat blur that some editors like.
Probably be best to do some experiments for yourself and determine what you like.
Jeff
yes you capture more image at every fps.
100mbps /30p about 3.33/sec
100mbps /24p about 4.16/sec
|
|
|
Quote
Yes. You can uncheck the hardware decoding in preferences and produce say 30 sec. of video as a test. If you still have pixelation, then uncheck the fast video rendering technology and produce another 30 sec. There should be no pixelation.
.
Here are findings - VERY interesting!
It seems that Fast Video Rendering technology OVERRIDES bitrate from the profile selected causing the pixelation.
Let me give you an example:
- Render Test with ONLY profile adjusted (23.97 + 100Mbps bitrate) && (HW acceleration enabled + video rendering enabled)
-No changes pixelation still exist
-File size 99.4MB
-Bitrate overwritten to 22.59Mbps (from 100Mbps)
https://ibb.co/VB1fd23
- Render Test with profile and HW acceleration disabled (vide rendering enabled)
-No changes pixelation still exist
-File size 99.4MB
-Bitrate overwritten to 22.58Mbps (from 100Mbps)
https://ibb.co/VB1fd23
- Render Test with profile and HW&video rendering disabled
-Still see pixelation but seems to be improved - could be my monitor. I'll try upload it and test on 4k tv
-File size 452MB (difference from 99.4MB with video rendering enabled)
-Bitrate 102.76Mbps
https://ibb.co/1KQqR4k
[/list]
Render Test with profile and HW Acc Enabled and Video Rendering Disabled
-Still see pixelation but seems to be improved - could be my monitor. I'll try upload it and test on 4k tv
-File size 418MB (difference from 99.4MB with video rendering enabled)
-Bitrate 99.80Mbps
-Definatelly something about Video Rendering being enabled.
File samples here(uplading right now):
https://1drv.ms/f/s!AmASekm8DZ8mgoxLjoXJUifDF8aJSg
Can somebody explain to me what is happening? Without video rendering CPU gets a hit. Is this a flaw in the PD17 or what?
|
|
|
Quote
Yes. You can uncheck the hardware decoding in preferences and produce say 30 sec. of video as a test. If you still have pixelation, then uncheck the fast video rendering technology and produce another 30 sec. There should be no pixelation.
.
Let me create a 30 seconds and test it out.
I'f that works I will be confused why degradation happens because of hw acceleration. I thought this supposed to help speed up but it has a downside?
Quote
If the camera only allows capture at 24p then a custom profile can be created to produce since one is not available as a default. 50 Mbps is 50000 Kbps in the custom profile. One is M and the other is K.
Camera supports 30fps but I'm shooting at 24 because of more data being able to be captured vs 30.
|
|
|
Quote
Additionally to 100Mbps vs 50Mbps.
What are the units used in PD17?
https://ibb.co/HNQFTsC
I have a number of 48500 as Bitrate but doesn't say is this kilobits etc... Is this the equivelent to 50Mbps? If that is the case I what would it be for 99.92Mbps i.e?
Possibly represented in Kilobit?
Just noticed. It is in Kbps.
100Mbps == 102400Kbps
|
|
|
Additionally to 100Mbps vs 50Mbps.
What are the units used in PD17?
https://ibb.co/HNQFTsC
I have a number of 48500 as Bitrate but doesn't say is this kilobits etc... Is this the equivelent to 50Mbps? If that is the case I what would it be for 99.92Mbps i.e?
Possibly represented in Kilobit?
|
|
|
tomasc,
thank you for the reply. Couple follow ups>
Quote
Your original footage is 23.97 fps. You can change the settings to 29.97 or 59.94 fps for a smoother drone viewing experience.
- Do you mean I should export as 29.97 or 59.94 and not to original fps? I was trying to be as close as possible to the original fps (23.97) to get the smooth cinematic flow. The export was set for 25 to be as closed,
https://ibb.co/vzYL0Cx
Probably modify the profile type?
Quote
More than likely the pixilation is due to the use of hardware decoding in the preferences and possible use of hardware acceleration in rendering on the laptop.
Are you talking about Fast video rendering technology?
https://ibb.co/rQCzrsR
https://ibb.co/ZmR8T6r
I thought this is the fuction that allows faster render. Are you saying it may degrade the quality because of this? If yes please advise what settings I should have setup?
Lastly what about 100Mbps of original source vs 50Mbps export?
https://ibb.co/bNW93xy
Thank you in advance.
|
|
|
HI,
Footage shot at 3840x2160@ 23.98 (anafi) @ 100Mbps
Exporting the video after edit (powerDIrector) It seems it creates that artifact.
Settings used on PD:
h.264[/list]
mpeg-4 4k 3840 x 2160/24 (50Mbps)[/list]
Focus on the creek pixelation
https://ibb.co/ZcnqDDT
exported as 3840x2160 25p - no edit, plain
https://youtu.be/KQ0A5KAOBqQ
exported as 4096x2160 24p - no edit, plain
https://youtu.be/eGeXntVdhVI
original-settings-from-drone
https://ibb.co/bNW93xy
exported-video-settings-on-power-director
https://ibb.co/vzYL0Cx
On Reddit somebody mentioned that it could be issue related to transcoding from 100Mbpls(drone) to 50
"Its most likely due to the transcoding of your video editor going from 100 Mbps to 50. There are a few causes. This is what is known as macroblocking. This is caused by too much compression in certain areas and your editor's codec may not be able to compress that area adequately due to limitations of lower bitrate H.264 AVC. It also could be due to the playback function from 4K to 1080 on your screen which compresses it further for Youtube compatibility. You might want to edit and render in a higher bite before converting it to a youtube format for playback, if you do not have a 4K monitor it might make sense to render it in native 1080 if that is the intent for the final playback on youtube, due to bandwidth constraints."
If that is the case HOW can I fix that on PD17 or the software is too weak?
Thank you in advance.
|
