Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
30th March 2017, 00:23 | #21 | Link |
Professional Code Monkey
Join Date: Jun 2003
Location: Kinnarps Chair
Posts: 2,555
|
This isn't a Linux test
__________________
VapourSynth - proving that scripting languages and video processing isn't dead yet |
31st March 2017, 10:00 | #23 | Link |
Professional Code Monkey
Join Date: Jun 2003
Location: Kinnarps Chair
Posts: 2,555
|
There shouldn't really be a difference. How much did it decrease?
__________________
VapourSynth - proving that scripting languages and video processing isn't dead yet |
2nd April 2017, 09:57 | #24 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Would it be possible to also export the HDR metadata (SMPTE 2086)? Specifically the gamut and min/max luminance of the mastering display?
That would be helpful for handling of HDR videos. FWIW, LAV Splitter/Video Decoder already exports them, so maybe you can find out how from the LAV source code (if the license permits)? |
2nd April 2017, 10:39 | #25 | Link | |
Professional Code Monkey
Join Date: Jun 2003
Location: Kinnarps Chair
Posts: 2,555
|
Quote:
__________________
VapourSynth - proving that scripting languages and video processing isn't dead yet |
|
2nd April 2017, 11:38 | #28 | Link |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
Decoding speed using a UHD h.264 clip:
Code:
[OS/Hardware info] Operating system: Windows XP (x86) Service Pack 3.0 (Build 2600) CPU: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz CPU features: MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX* (* CPU feature not supported by OS) [Avisynth core info] VersionString: AviSynth+ 0.1 (r2294, MT, i386) VersionNumber: 2.60 File version: 0.1.0.0 Interface Version: 6 Multi-threading support: Yes Avisynth.dll location: D:\WINNT\system32\avisynth.dll Avisynth.dll time stamp: 2016-10-26, 17:29:37 (UTC) PluginDir+ (HKLM, x86): E:\Apps\VideoTools\AvisynthRepository\AVSPLUS_x86\plugins PluginDir2_5 (HKLM, x86): E:\Apps\VideoTools\AVSPlugins\AutoLoad [Clip info] Number of frames: 1000 Length (hh:mm:ss.ms): 00:00:20.000 Frame width: 3840 Frame height: 2160 Framerate: 50.000 (50/1) Colorspace: i420 [Script] FFVideoSource("420_4K.264") AssumeFPS(50, 1) Code:
[Runtime info] Frames processed: 1000 (0 - 999) FPS (min | max | average): 3.638 | 632.4 | 23.84 Memory usage (phys | virt): 500 | 531 MiB Thread count: 17 CPU usage (average): 88% Code:
[Runtime info] Frames processed: 1000 (0 - 999) FPS (min | max | average): 2.519 | 616.6 | 18.12 Memory usage (phys | virt): 403 | 422 MiB Thread count: 13 CPU usage (average): 84%
__________________
Groucho's Avisynth Stuff |
2nd April 2017, 12:23 | #29 | Link |
Professional Code Monkey
Join Date: Jun 2003
Location: Kinnarps Chair
Posts: 2,555
|
You can't compare those. That one is compiled with mingw.
__________________
VapourSynth - proving that scripting languages and video processing isn't dead yet |
2nd April 2017, 12:45 | #30 | Link |
Professional Code Monkey
Join Date: Jun 2003
Location: Kinnarps Chair
Posts: 2,555
|
Are primaries and whitepoint even relevant? Isn't that effectively included in the already exported values?
__________________
VapourSynth - proving that scripting languages and video processing isn't dead yet |
2nd April 2017, 13:04 | #31 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Blu-Ray style HDR is always stored with BT.2020 matrix and BT.2020 primaries. BT.2020 is practically used as a "container". Most UHD Blu-Rays only use a subset of the BT.2020 container. The metadata tells us which primaries the master display was calibrated with. Which is usually DCI. This information can be used to pick a suitable gamut compression curve.
|
2nd April 2017, 14:13 | #32 | Link |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
but it's still work in xp
__________________
See My Avisynth Stuff |
2nd April 2017, 14:55 | #33 | Link |
Retried Guesser
Join Date: Jun 2012
Posts: 1,373
|
2000 still sounds impossibly futuristic. I can't get used to it.
In The Year 2000 Last edited by raffriff42; 18th April 2017 at 22:04. |
2nd April 2017, 17:35 | #34 | Link | |
Professional Code Monkey
Join Date: Jun 2003
Location: Kinnarps Chair
Posts: 2,555
|
Quote:
__________________
VapourSynth - proving that scripting languages and video processing isn't dead yet |
|
3rd April 2017, 07:57 | #36 | Link |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
Why would a user who for example just wants to decode a BD source care what compiler was used? Maybe I'm missing something but isn't this just another source filter for a variety of formats?
__________________
Groucho's Avisynth Stuff |
3rd April 2017, 08:20 | #37 | Link |
Professional Code Monkey
Join Date: Jun 2003
Location: Kinnarps Chair
Posts: 2,555
|
There's a known speed difference between compilers. That's why. I can tell you the result long before you do the test. My test builds are never compiled for speed.
__________________
VapourSynth - proving that scripting languages and video processing isn't dead yet |
3rd April 2017, 16:45 | #38 | Link | ||
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
Quote:
Quote:
That makes more sense.
__________________
Groucho's Avisynth Stuff |
||
3rd April 2017, 16:48 | #39 | Link | |
Professional Code Monkey
Join Date: Jun 2003
Location: Kinnarps Chair
Posts: 2,555
|
Quote:
Release builds are obviously different...
__________________
VapourSynth - proving that scripting languages and video processing isn't dead yet |
|
3rd April 2017, 18:12 | #40 | Link |
Registered User
Join Date: Oct 2001
Location: Germany
Posts: 7,277
|
Feature request: Support .mpls parsing. It's really a pain to always load all the separate files a playlist makes up and later join them together,... (FFmpeg itself can handle playlist files fine when build with libbluray)
|
Thread Tools | Search this Thread |
Display Modes | |
|
|