Page 1 of 1
[RESOLVED] Coded frame dimensions are too large
Posted: Fri Sep 20, 2019 9:18 pm
by MeteorRain
So I have a 8K video but I don't have a 1030+ card. I borrowed a remote computer with 1050 from a friend and tried to load the video into DGIndexNV.
Code: Select all
---------------------------
Error
---------------------------
Coded frame dimensions are too large
---------------------------
OK
---------------------------
Code: Select all
Format : Matroska
Format version : Version 4 / Version 2
File size : 16.4 GiB
Duration : 28 min 59 s
Overall bit rate : 80.9 Mb/s
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L6.1@Main
Codec ID : V_MPEGH/ISO/HEVC
Duration : 28 min 59 s
Bit rate : 80.9 Mb/s
Width : 7 680 pixels
Height : 4 320 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 59.940 (60000/1001) FPS
Driver 436.30 Compute 6.1 sm_60. Video plays in a player.
What do you think is the problem? My friend is not tech savvy.
Re: Coded frame dimensions are too large
Posted: Fri Sep 20, 2019 9:51 pm
by Rocky
Need to bump up the internal frame buffer size. It will be in the next slipstream. Thank you for pointing it out.
If you could supply a small clip that would be excellent.
Re: Coded frame dimensions are too large
Posted: Fri Sep 20, 2019 10:00 pm
by MeteorRain
I knew you would ask. So
here you are.
Re: Coded frame dimensions are too large
Posted: Fri Sep 20, 2019 11:10 pm
by Rocky
Thanks!
Re: Coded frame dimensions are too large
Posted: Sat Sep 21, 2019 12:45 am
by Rocky
It's running fine after enlarging the frame buffers and fixing a bug in the HEVC parser. Slipstream coming...
Re: Coded frame dimensions are too large
Posted: Sat Sep 21, 2019 2:12 am
by hydra3333
Re: Coded frame dimensions are too large
Posted: Sun Sep 22, 2019 10:19 am
by Rocky
Fixed in slipstream 188.
Re: [RESOLVED] Coded frame dimensions are too large
Posted: Sun Sep 22, 2019 11:08 am
by MeteorRain
Now I'm getting this when opening 8k test.mkv.
---------------------------
Error
---------------------------
GPU decoder: Failed to create video decoder [2]. Exiting...
---------------------------
Tried opening a random 720p file, no error message though.
Card is
0x10de:0x1c81:2:7:GP107 [GeForce GTX 1050 LP] 1862
Any thought?
Re: [RESOLVED] Coded frame dimensions are too large
Posted: Sun Sep 22, 2019 11:41 am
by Guest
I just loaded your test file into the new DGIndexNV and it worked fine.
Here are the log and dgi file for the 64 bit version
- test.log
- (410 Bytes) Downloaded 512 times
- test.dgi
- (928 Bytes) Downloaded 502 times
By the way, is your card the 2 Gigabyte model?
Just tried the 32 bit version and no obvious issues
Re: [RESOLVED] Coded frame dimensions are too large
Posted: Sun Sep 22, 2019 11:47 am
by Rocky
Thanks for test results, gonca, but you should mention your card type. Tested successfully here on 2080 Ti, 1080 Ti, and 1050 Ti. All >= 4GB video memory.
MeteorRain, can you give the vendor card details? Name and model, etc. And how much memory is on it? Finally, what nVidia driver is installed? I looked at a random MSI 1050 LP 2GB and the technical specs say that it supports 8K video. So, hmmm?
Re: [RESOLVED] Coded frame dimensions are too large
Posted: Sun Sep 22, 2019 11:53 am
by MeteorRain
Unfortunately she's sleeping so I don't know exactly what brand and model she has.
But indeed it has only 2 GB memory. Would this card not be able to decode 8K video?
(And yes, I checked purevideo specs, and read 1050 does support 8K hevc.)
Control panel reads 436.30, and device manager reads 26.21.14.3630 on 9/5/2019.
Re: [RESOLVED] Coded frame dimensions are too large
Posted: Sun Sep 22, 2019 12:32 pm
by Rocky
Possibly with CUDA buffers and other stuff set up by DGDecNV, 2GB is not enough.
Re: [RESOLVED] Coded frame dimensions are too large
Posted: Sun Sep 22, 2019 12:38 pm
by Bullwinkle
Hey Rock error 2 means out of memory on the device.
1050 Ti that works has 4GB.
Re: [RESOLVED] Coded frame dimensions are too large
Posted: Sun Sep 22, 2019 12:40 pm
by Rocky
Oh yeah, duh. Thanks Bullwinkle!
Re: [RESOLVED] Coded frame dimensions are too large
Posted: Sun Sep 22, 2019 12:59 pm
by MeteorRain
So that means it can play back but cannot copy back full screen data back to ram?
Or it simply cannot decode such high resolution @ high bitrate?
I'll let her try playing the video locally and see if lavfilter could handle it. I'll report back later.
On the other hand, any options to turn off some CUDA buffers during indexing?
Re: [RESOLVED] Coded frame dimensions are too large
Posted: Sun Sep 22, 2019 1:01 pm
by Rocky
MeteorRain wrote: ↑Sun Sep 22, 2019 12:59 pm
So that means it can play back but cannot copy back full screen data back to ram?
Or it simply cannot decode such high resolution @ high bitrate?
Bitrate is not important as it fails at init. Need a research project to find out why 2GB is not enough here, but it's not likely to get high on the priority list as 8K users will likely have high-end cards. Memory is allocated on the GPU for the kernels that convert back to RGB24 for display in DGIndexNV. That could be the difference. Can't see making hacks to salvage 2GB cards. Can't even
think about CUDASynth in 2GB!
Time to deprecate 2GB cards?
Re: [RESOLVED] Coded frame dimensions are too large
Posted: Sun Sep 22, 2019 1:31 pm
by MeteorRain
That does make sense. GTX 1050 is the only card that falls in 8K capable and 2GB graphics memory. 1650 comes with 4GB so it's unlikely hit someone in the future. By the time 8K video is getting popular I'm sure we will have much better cards to use.
We are kinda pioneers at working with 4k and 8k videos at the moment. It's the first time I get a broadcasting 8k capped.
Re: [RESOLVED] Coded frame dimensions are too large
Posted: Sun Sep 22, 2019 3:48 pm
by Guest
Quick and dirty experiment to measure video memory during indexing
GTX 1080 Ti with 11264 MB of VRAM
DGIndexNV (latest) and HWMonitor used
When indexing a BD file (2K) DGIndexNV uses 2% of memory (~225MB)
When indexing a UHD file (4K) DGIndexNV uses 7% of memory (~788 MB)
If we allow a ratio of 3 for 8K to 4K (frame size is about 4 times) then 2364 MB are required to index this 8K file
I would say that 4GB is a safe minimum for 8K.
The test file is too short to get a reading on memory. It is finished too quickly
Re: [RESOLVED] Coded frame dimensions are too large
Posted: Thu Sep 26, 2019 10:16 pm
by Bullwinkle
Good stuff, thanks.
