This is strange:
Here is the sample download: http://leteckaposta.cz/912397968
I have the same problem in V16 and V17 (I / O: ON)
Intel Xeon 3.40Ghz (4core)
Mediainfo
General
Format : MPEG-4
Format profile : JVT
Codec ID : avc1 (avc1/isom)
File size : 143 MiB
Duration : 8 s 292 ms
Overall bit rate mode : Variable
Overall bit rate : 145 Mb/s
Encoded date : UTC 2019-09-14 10:37:06
Tagged date : UTC 2019-09-14 10:37:06
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L5.2
Format settings : CABAC / 1 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 1 frame
Format settings, GOP : M=1, N=8
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 8 s 292 ms
Bit rate mode : Variable
Bit rate : 138 Mb/s
Maximum bit rate : 135 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 59.940 (60000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.277
Stream size : 136 MiB (95%)
Title : XiaoYi AVC
Language : English
Encoded date : UTC 2019-09-14 10:37:06
Tagged date : UTC 2019-09-14 10:37:06
Color range : Full
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
Codec configuration box : avcC
Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : mp4a-40-2
Duration : 8 s 277 ms
Bit rate mode : Constant
Bit rate : 128 kb/s
Nominal bit rate : 48.0 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 46.875 FPS (1024 SPF)
Compression mode : Lossy
Stream size : 129 KiB (0%)
Title : XiaoYi AAC
Language : English
Encoded date : UTC 2019-09-14 10:37:06
Tagged date : UTC 2019-09-14 10:37:06
59.94 no problem here on my 10 year old PC.
Didn't even have to make a proxy (I still think proxies are the beest way to handle this, however.)
59.94 no problem here on my 10 year old PC.
Didn't even have to make a proxy (I still think proxies are the beest way to handle this, however.)
what is your processor?
See signature for system. i7-980x (from 2010)
i7-980x is 6 cores.
two more cores than my processor. That will be the reason.:-)
I don't think it's a processor. I have a 4.5Ghz CPU. This behavior is strange. I think I never had a stable 60fps preview, but it was 45 ~ 60fps. With a project set to 30fps(half from footages) it was okay without slowing down footage and stable 30fps. Now fps drops rapidly(59, 22, 13, 8, 5, 3...) a few seconds after play. It behaves as if it couldn't read from the disc. But I tried several SSDs, including an SD card.
Download is blocked by me by Google and Norton.
So owner must upload on a safe site.
I don't think it's a processor. I have a 4.5Ghz CPU. This behavior is strange.
It does behave in an unusual way. I notice Resolve is not able to Hardware decode video file, offloading on to cpu, and does not play smoothly for me, vegas17 can't decode either?, Incompatibility with Nvidia hardware decode? except when I play in media player, hardware decode works fine. Also I think your cpu should be able to play it without hardware decode
if you change profile it fixes problem with no hardware decoding. I do not have vp17 but it should work
use this command ffmpeg -i original-file.mp4 -vcodec copy -an -sn -vbsf h264_changesps=level=51 Fixed-File.mp4https://sourceforge.net/projects/direct264/files/Related%20Programs/ffmpeg%20%28demuxer_muxer%20only%29/ffmpeg_git_31792.7z/download
First clip is original, 2nd after fix. Cpu use drops dramatically
I don't think it's a processor. I have a 4.5Ghz CPU. This behavior is strange.
It does behave in an unusual way. I notice Resolve is not able to Hardware decode video file, offloading on to cpu, and does not play smoothly for me, vegas17 can't decode either?, Incompatibility with Nvidia hardware decode? except when I play in media player, hardware decode works fine. Also I think your cpu should be able to play it without hardware decode
XiaoYi AVC is blacklisted from so4compoundplug by C:\Program Files\VEGAS\VEGAS Pro 17.0\so4_blacklist_vp15.xml (unfortunately with "vp15" still in the filename, despite applying to vp17) so I don't think it would be decoded by the GPU anyway unless you un-blacklist it.
Playing back with CPU-only (my GPU is ancient) I get this performance with AlesCZ's file:
So @AlesCZ, which decoder plugin is being used to playback your file? Part 2 of this post explains how to find that out, if you don't already know.
XiaoYi AVC is blacklisted from so4compoundplug by C:\Program Files\VEGAS\VEGAS Pro 17.0\so4_blacklist_vp15.xml (unfortunately with "vp15" still in the filename, despite applying to vp17) so I don't think it would be decoded by the GPU anyway unless you un-blacklist it.
When you rewrite the profile level with that command via ffmpeg it removes the XiaoYi AVC reference and in the 8seconds of video it causes no problems with hardware decode on Resolve, but it must be deliberately blocked on Davinci as it is on Vegas17 for good reason
Remove the so4_blacklist_vp15.xml file from Vegas 17, and your file will play smoothly.
You must have a nvidia card and turn on I / O: ON
DJI.AVC, GoPro AVC and XiaoYi AVC playback will improve.
No tearing and dropping frames.
It's like a miracle!
Remove the so4_blacklist_vp15.xml file from Vegas 17, and your file will play smoothly.
You must have a nvidia card and turn on I / O: ON
DJI.AVC, GoPro AVC and XiaoYi AVC playback will improve.
No tearing and dropping frames.It's like a miracle!
Ahah! So it seems the default so4compoundplug blacklist functionality should be modified in future versions of Vegas so that it only applies when hardware decoding is OFF. Otherwise DJI AVC, GoPro AVC and XiaoYi AVC will never benefit from hardware acceleration, which (I assume) requires so4compoundplug. Very few users know about modifying that file.
I delete so4_blacklist_vp15.xml file, I don't understand why, what, how ... but it only works!
It's alright?
Anyway, thank you very much for dealing with this problem guys!
Thanks to your problem I solved tearing and low fps with DJI AVC.
:-)
Are you serious? Many cameras were blocked from hardware decoding for no reason due to an old blocklist from vegas15 before there was Nvidia decoding?
Well that's embarrassing
Please improve Slow Motion, at least here, slow motion is really very slow, but only in preview playback and final rendering. It takes forever to see the final result in the preview even using Dynamic Ram Preview (Shift+B) and another eternity to render the final video (Render As).
It takes forever to see the final result in the preview and another eternity to render.
There are in Vegas Tools to accellerate preview and render
There are in Vegas Tools to accellerate preview and render
This is the problem. It takes forever even using these options.
I delete so4_blacklist_vp15.xml file, I don't understand why, what, how ... but it only works!
It's alright?
Anyway, thank you very much for dealing with this problem guys!
Explanation is on this thread, which I've updated regarding hardware decoding. Best if we continue further discussion about this issue on that thread.
Are you serious? Many cameras were blocked from hardware decoding for no reason due to an old blocklist from vegas15 before there was Nvidia decoding?
Well that's embarrassing
Please @Former user, I find absolutely nothing to be embarrassed about. I think it fair to say that you might not really know the details of any of this. Rest assured, it's not quite as easy as your summation here. Please follow @NickHope's thread (from his previous post above) for more detail, but even that doesn't fill you in on what's really going on deep in the code. In any event, we know what to do next.
But hey... Knee jerk jumping to conclusions is always wayyyy better than methodical logical problem solving.🙃
And don't you know... half the guys on this forum are "expert" software developers who would happily explain to you how to fix the code that they have never seen but "know" the answer by some kind of magical divination.