This has been mentioned before in a thread, but that was a year a go, and it didn't get a solution, so I am doing a new thread about a long-standing problem in the hope you guys might be able to shed some light on a potential answer...
I am having a very frustrating problem at the moment. Previously, all my videos from the H have been shot at 1080 / 29.97 or 59.94 FPS, which plays back fine directly from the RAW files, and also fine in any edited and graded output. I always output to MP4, using H.264, and usually that is totally fine too.
Yesterday I thought I'd give 4K a go, so dutifully drove myself to some suitably picturesque landscape, saw the no drones signs (boo hoo ! ), moved 2 valleys down the hill to where there was a public footpath, and tried again !
When I got the footage home, copied it to hard disk and viewed the raw video files, the quality was very nice, and playback utterly smooth in Media Player Classic / Windows Media Player. All good so far...
Upon loading the files into DaVinci Resolve 15 Beta (by far my favourite editor) playback seemed largely Ok there too. So I did my grade, output a test file, and it's all gone horrible
Did a YT search, and found this, which is a perfect demonstration of the problem, but most annoyingly doesn't say how to fix it !
I have read the comments there, but the one solution suggested I am already doing. My project settings have 29.97 in all 3 places, and I am making sure to render out at that frame rate as well. I have tried at all ranges of bitrate, and the result is the same...
I think my PC should handle 4K video OK - It's quite old, but reasonably specc'd (AMD FX8350 / 4 GHz / 8 core / 32 GB RAM / NVidia 650TiBoost, Win7-64 bit) - well it does, as theoretically proved by the flawless playback of the raw files on MPC. I wouldn't mind, but I'm not even trying to get 4K video out ! And I KNOW that PC can deal with 1080, so I guess the problem is something DVC is doing...
Anyone else found a way to make this work in DVR ? I'd like to continue using that if I can, but very much open to other suggestions and workflows as well if we can't solve it here...
Thanks for reading, and sorry it was so long-winded !
J
I am having a very frustrating problem at the moment. Previously, all my videos from the H have been shot at 1080 / 29.97 or 59.94 FPS, which plays back fine directly from the RAW files, and also fine in any edited and graded output. I always output to MP4, using H.264, and usually that is totally fine too.
Yesterday I thought I'd give 4K a go, so dutifully drove myself to some suitably picturesque landscape, saw the no drones signs (boo hoo ! ), moved 2 valleys down the hill to where there was a public footpath, and tried again !
When I got the footage home, copied it to hard disk and viewed the raw video files, the quality was very nice, and playback utterly smooth in Media Player Classic / Windows Media Player. All good so far...
Upon loading the files into DaVinci Resolve 15 Beta (by far my favourite editor) playback seemed largely Ok there too. So I did my grade, output a test file, and it's all gone horrible
Did a YT search, and found this, which is a perfect demonstration of the problem, but most annoyingly doesn't say how to fix it !
I have read the comments there, but the one solution suggested I am already doing. My project settings have 29.97 in all 3 places, and I am making sure to render out at that frame rate as well. I have tried at all ranges of bitrate, and the result is the same...
I think my PC should handle 4K video OK - It's quite old, but reasonably specc'd (AMD FX8350 / 4 GHz / 8 core / 32 GB RAM / NVidia 650TiBoost, Win7-64 bit) - well it does, as theoretically proved by the flawless playback of the raw files on MPC. I wouldn't mind, but I'm not even trying to get 4K video out ! And I KNOW that PC can deal with 1080, so I guess the problem is something DVC is doing...
Anyone else found a way to make this work in DVR ? I'd like to continue using that if I can, but very much open to other suggestions and workflows as well if we can't solve it here...
Thanks for reading, and sorry it was so long-winded !
J
Last edited: