A bit late: I updated right now, and: Yes it is fixed.
SVPlayer for 🍎 iPhone | iPad | Apple TV and 🤖 Android
SVP 4 for Windows and macOS: 30 days FREE TRIAL.
Read FAQ & follow SVP @ Facebook, Twitter
Pages 1
You are not logged in. Please login or register.
SmoothVideo Project → Posts by Joachim Otahal
Pages 1
A bit late: I updated right now, and: Yes it is fixed.
Here a 59 seconds snippet showing the issue: https://joumxyzptlk.de/tmp/svp-green-test.mkv
More than one, but not many. The screenshot is from Postpect (2018), 4K.
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@Main
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : V_MPEGH/ISO/HEVC
Duration : 1 h 39 min
Bit rate : 7 157 kb/s
Width : 3 840 pixels
Height : 2 028 pixels
Display aspect ratio : 1.893
Frame rate mode : Variable
Frame rate : 23.976 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.038
Stream size : 4.99 GiB (86%)
Writing library : x265 3.5+9-bf91444e0:[Windows][GCC 10.2.0][64 bit] 10bit
Encoding settings : cpuid=1111039 / frame-threads=6 / numa-pools=32 / wpp / no-pmode / no-pme / no-psnr / no-ssim / log-level=0 / input-csp=1 / input-res=3840x2028 / interlace=0 / total-frames=0 / level-idc=0 / high-tier=1 / uhd-bd=0 / ref=4 / no-allow-non-conformance / repeat-headers / annexb / no-aud / no-eob / no-eos / no-hrd / info / hash=0 / no-temporal-layers / open-gop / min-keyint=23 / keyint=250 / gop-lookahead=0 / bframes=4 / b-adapt=2 / b-pyramid / bframe-bias=0 / rc-lookahead=25 / lookahead-slices=4 / scenecut=40 / hist-scenecut=0 / radl=0 / no-splice / no-intra-refresh / ctu=64 / min-cu-size=8 / rect / no-amp / max-tu-size=32 / tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / rdoq-level=2 / dynamic-rd=0.00 / no-ssim-rd / signhide / no-tskip / nr-intra=0 / nr-inter=0 / no-constrained-intra / no-strong-intra-smoothing / max-merge=3 / limit-refs=3 / limit-modes / me=3 / subme=3 / merange=57 / temporal-mvp / no-frame-dup / no-hme / weightp / no-weightb / no-analyze-src-pics / deblock=0:0 / no-sao / no-sao-non-deblock / rd=4 / selective-sao=0 / no-early-skip / rskip / no-fast-intra / no-tskip-fast / no-cu-lossless / no-b-intra / no-splitrd-skip / rdpenalty=0 / psy-rd=2.00 / psy-rdoq=1.00 / no-rd-refine / no-lossless / cbqpoffs=0 / crqpoffs=0 / rc=crf / crf=20.5 / qcomp=0.60 / qpstep=4 / stats-write=0 / stats-read=0 / ipratio=1.40 / pbratio=1.30 / aq-mode=2 / aq-strength=1.00 / cutree / zone-count=0 / no-strict-cbr / qg-size=32 / no-rc-grain / qpmax=69 / qpmin=0 / no-const-vbv / sar=1 / overscan=0 / videoformat=5 / range=0 / colorprim=9 / transfer=16 / colormatrix=9 / chromaloc=0 / display-window=0 / master-display=G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(50,10000000) / cll=1000,516 / min-luma=0 / max-luma=1023 / log2-max-poc-lsb=8 / vui-timing-info / vui-hrd-info / slices=1 / no-opt-qp-pps / no-opt-ref-list-length-pps / no-multi-pass-opt-rps / scenecut-bias=0.05 / hist-threshold=0.03 / no-opt-cu-delta-qp / no-aq-motion / hdr10 / hdr10-opt / no-dhdr10-opt / no-idr-recovery-sei / analysis-reuse-level=0 / analysis-save-reuse-level=0 / analysis-load-reuse-level=0 / scale-factor=0 / refine-intra=0 / refine-inter=0 / refine-mv=1 / refine-ctu-distortion=0 / no-limit-sao / ctu-info=0 / no-lowpass-dct / refine-analysis-type=0 / copy-pic=1 / max-ausize-factor=1.0 / no-dynamic-refine / no-single-sei / no-hevc-aq / no-svt / no-field / qp-adaptation-range=1.00 / scenecut-aware-qp=0conformance-window-offsets / right=0 / bottom=0 / decoder-max-rate=0 / no-vbv-live-multi-pass
Language : English
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primar : Display P3
Mastering display luminance : min: 1000.0000 cd/m2, max: 0.0050 cd/m2
Maximum Content Light Level : 1000 cd/m2
Maximum Frame-Average Light Le : 516 cd/m2
Thank you for your lightning fast reply!
Just reporting, nvidia hardware acceleration causes a green screen in one HDR movie, even when reencoded through ffmpeg from h265 to h265.
If it is an SVP setting that can help, besides deactivation hardware acceleration, please tell. Without hardware acceleration "recoder HDR colors" is not available. Deactivating "try to recoder HDR colors", but leaving hardware acceleartion still on fixes that problem too...
Might be a MplayerHomeCinema problem as well, MVP does not have that issue. But switching from "dvxa2 (copy-back)" to "none" doesn't help there.
Any hints what I missed?
This is, up to now, the only video, for a very long time, exposing such an issue issue.
please check - do you have the "HKEY_CURRENT_USER\SOFTWARE\AviSynthFilter\AviSynth Filter" key?
Yes.
and HKEY_CURRENT_USER\SOFTWARE\AviSynthFilter\AviSynth Filter\RemoteControl must be set to 1
No.
I've manually added that DWORD value now, changed to the new AVFS, and interpolation works.
Question:Can I manually start that update script to test?
A possible reason: For quite a while svp-maintenance has been trowing an error during each update, that unregister.bat and register.bat exited with an error. But each time I run them from an elevated prompt they work fine. If only I could see what it does different during svp-maintenance run.. One thing that might unusual about my box: UAC is set to the highest value.
Attached: installation log (and all other files with the date/time of the last update).
Yesterday morning an "AVSF 1.0.0.0" or something similar update came for SVP. Result: No frame interpolation.
Worked perfect with the version from before. It there a rollback feature or a way to select "version from yesterday please" ?
My solution in "C:\Program Files (x86)\SVP 4\avsf":
1. Manually run unregister.bat.
2. Copy the "C:\Program Files (x86)\SVP 4\avsf" away, all files date 2021-05-14, avisynth_filter_64.ax size 399872.
3. Get yesterday morning shadowcopy, where all files have the date 2021-05-03, avisynth_filter_64.ax size 398336. Copy them back.
4. Manually run register.bat
Done! I don't even need to close SVP control panel, old version works. Side effect: The "Active log" states:
17:31:42.342 : AVSF: found 64-bit version 1.0.0.0 [C:\Program Files (x86)\SVP 4\avsf\avisynth_filter_64.ax]
which is wrong by the time it successfully worked after doing the steps above and rolling back AVFS without restarting SVP control panel:
17:45:52.296 : AVSF: found new player instance
Have fun debugging! And yes, I love windows shadowcopy.
kind regards,
Joachim Otahal
First: Thanks for including me in the "AviSynth Filter" test people group, made the change today.
It did not work at first, and thanks to your wiki-page, I found the reason:
Even though I did let it install via SVP, and not manually, SVP did not set the registry key in HKCU. Even complete removal and reinstall did not set it. So I set RemoteControl = 1 in the registry at HKEY_CURRENT_USER\SOFTWARE\AviSynthFilter.
Result: Works like a charm. Instead of taking about a second to switch to high framerate, as with ffmpeg, it instantly starts at high framerate with FullHD, and near instantly with 4K input. That includes seeking, which is now a lot more stable. With ffmpeg there was always a chance for MPC to get stuck.
A fix might be: Check for that value when SVP-Manage starts, and recommend to set it when the AviSynth method was installed (i.e. ask "Should I set it?).
PS: ffmpeg version git-2020-04-03-52523b6
I just found several threads and bug reports about ffmpeg (or rather libav as some say) not transferring the HDR flags in quite some situations, even with x265. And those discussions are not old, looks like I have to check with newer ffmpeg as well...
Thank you for the hint. Did I miss an encoding option? The original is HDR, but with 80 GB way too big.
My command line is this:
c:\prog\ffmpeg\bin\ffmpeg.exe -stats -n -i "x265.10bit.HDR.mkv" -max_muxing_queue_size 1024 -map 0:v:0? -map 0:a? -map 0:s? -map 0:t? -acodec aac -b:a 384k -c:s copy -map_metadata 0 -vf hqdn3d=2:1:2:1 -vcodec libx264 -preset:v veryslow -tune:v Film -crf 20 "x265.10bit.HDR.crf20.aac384.filter.mkv"
As far as my search goes: x264 does support 10 Bit, but not the HDR flag as far as I can see here http://www.chaneru.com/Roku/HLS/X264_Settings.htm, even though it seems to be possible. I haven't found it yet. x265 has plenty of documentation on HDR flagging, but it is so slow compared to the little space gain (when disabling the strong intra filter) that it is rather worthless, the HDR is the only thing that actually seems to make a difference.
I'd rather run in through latest svt-av1 https://ci.appveyor.com/project/tianjun … v1/history than x265. Especially since they fixed my various "These sample make it crash reproducible" bug reports... The fixees are not included in SVT-AV1 0.8.3, probably will be in 0.8.4.
http://joumxyzptlk.de/tmp/h264-10-bit.mkv (10 MB) if a short test file is needed.
It works fine for h265, but not for h264.
x264 vide properties: h264 high 10 L6.0, yuv420p10le, 3840x2160.
Detailed properties:
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High 10@L6
Format settings : CABAC / 16 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference fra : 16 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 1 h 46 min
Bit rate : 4 898 kb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.025
Writing library : x264 core 159
Any hint? I could use ffdshow to color correct that, but the SVP routine gives better results.
Sorry I wasted your time: It is simply "out of ram" error.
Using a manual .avs script with virtualdub gives me the 120 fps interpolation, but it eats over 16 GB just to display the video. Which does not leave enough RAM to do the encoding. x264 alone takes ~48 GB when encoding 12800x7200. And I have "only" 64 GB.
BTW: I am suspecting an input problem here, when encoding to xvid I end up with an distorted 4608x7200 video instead of 12800x7200. And 12800 - 8192 is 4608. Would fit...
Nope, I have to correct myself. It still failes.
Thanks!
core.max_cache_size = 2048
is enough.
I am trying to transcode high resolution videos from 60 fps to 120 fps.
By "High Resolution" I mean: 12800x7200 60 fps as source.
This is "coder.log":
20:41:31.164: ===== Starting mpv ======
20:41:31.164: Command line: C:\Program Files (x86)\SVP 4\mpv64\mpv.exe D:/tmp/Bandicam/Asteroids 12800x7200.avi -o C:\tmp\out/Asteroids 12800x7200..SVP.temporary.mkv --no-audio --no-sub --no-sub-auto --input-ipc-server=mpvencodepipe --input-media-keys=no --vf=vapoursynth:[C:\Users\Jou\AppData\Roaming\SVP4\scripts\ffff.py]:4:16 --of=matroska --ovc=libx264 --ovcopts=preset=slower,crf=21,level=5.2,threads=16
20:41:31.211: Playing: D:/tmp/Bandicam/Asteroids 12800x7200.avi
20:41:31.505: (+) Video --vid=1 (h264 12800x7200 60.000fps)
20:41:35.252: Script exceeded memory limit. Consider raising cache size.
20:41:39.959: VO: [lavc] 12800x7200 yuv420p
20:41:39.959: [vo/lavc] Opening encoder: libx264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 [libx264]
20:41:39.964: [ffmpeg] libx264: frame MB size (800x450) > level limit (36864)
20:41:39.964: [ffmpeg] libx264: DPB size (4 frames, 1440000 mbs) > level limit (0 frames, 184320 mbs)
20:41:39.964: [ffmpeg] libx264: MB rate (8640000000) > level limit (2073600)
20:41:40.016: [encode] Opening output file: C:\tmp\out/Asteroids 12800x7200..SVP.temporary.mkv
20:41:40.018: [encode] Opening muxer: Matroska [matroska]
20:41:40.150: V: -00:00:00 / 00:02:49 (0%) {21.9min 6.3MB}
20:42:40.365: V: 00:00:01 / 00:02:49 (0%) {139.9min 1.1fps 0.1MB}
20:43:08.629: out of memory: 460672000
20:43:21.540: (!!!) Intermediate file may be broken: C:\tmp\out\Asteroids 12800x7200..SVP.temporary.mkv
20:43:21.540: ===== mpv exited with code -1073740791 =====
A hint from https://forum.doom9.org/showthread.php? … p;page=155 says:
Try core.max_cache_size = 32768
When looking at coder.log I guess core.max_cache_size = 2048 or core.max_cache_size = 4096 might already be enough.
How do I integrate that into SVP trancoding?
To my surprise the 8k version of that video seems to work.
I made a short version (130 MB) of the 12k source video available on this (not yet public) page, see the first link:
http://joumxyzptlk.de/nvidia_asteroids.html
Any good hint would be nice.
Pages 1
SmoothVideo Project → Posts by Joachim Otahal
Powered by PunBB, supported by Informer Technologies, Inc.