VideoTek (Avisynth and MPV Waveform Monitor)

[FranceBB]

Originally Posted by StainlessS

Should be
"v1.2 Added support for all input color spaces ..."

Modified.

Originally Posted by StainlessS

I will not remove my prev post, as it gives some background to bugrep in devs forum.

Yeah, keep it, it's nice to have a list of changes in the discussion here on Doom9 so that we can always go back to a previous version. You could have left the previous posts as well.

Originally Posted by StainlessS

Nope, no GitHub account just yet, one day maybe.

Oh...

[DTL]

This is great vector-rasterizer but it do not have graticule for unkonwn reason. Especially with IQ axies overlaid that are good enough for control the most important 'euro-standard' skintone with +I axis direction (angle). So it is good addition for this plugin to have option to overlay 'typical' or any hand-designed graticule with degrees markings (at least with 10-degree step) and IQ axies or at least vector-marking to that typical skintone to control.

I though about why magically NTSC skintone vector so good aligned with one of the system axises (and also why IQ axises are rotated to magical angle about 33-deg) - the idea was simple: because NTSC was very buggied with phase-distortions in analog TV so engineers trying to keep at least the most important skintone color make additional rotation of IQ axies so at skintone the I channel is at its maximum amplitude and Q channel close to zero - so any possible cross-distortions between I and Q channels makes minimum real color shift. And also engineers for color tone setting for video cameras got very simple tool for bringing skintone to standard value using vectoroscope screen with overlayed graticule with IQ axies.

Also at typical vectorscope the +I axis is pointed to the upper-left corner so it is good to have option for vertical-flipping of vectorscope image (keeping symbol markings not flipped).

In 2020 I tried to make multi-channel SDI vectorscope for our engeneers for easy setup and in-between cameras aligning of skintone using old Blackmagic Decklink cards as SDI inputs to windows-based computer and directshow multigraphs with ffdshow and this vectorscope rasteriser (with graticule applied as layer via avisynth). Unfortunately due to old card and old drivers the system start to lower update framerate after about 1 hour of running. If anyone interested in this project you can e-mail me.

Also as practice shows it is good to have ROI-selected vectorscope - so some control for setting ROI coordinates at runtime and passing to crop engine or ROI selecting engine inside vectorscope is good. So operator can get cleaner image of the interested part of frame instead of less-informative all-frame colors.

[FranceBB]

New Version Released

- Avisynth users: no need to update, no changes have been made.
- MPV Users: Added support for MPV, check it out here: https://github.com/FranceBB/mpv-scripts

Please note that due to the limitation of LAV Filter Complex, the MPV version is slightly different from the Avisynth Version:

[wonkey_monkey]

Is the oscilloscope thing on the bottom left upside down? Isn't it usually white at the top, black at the bottom?

[FranceBB]

Dammit, it is, I just checked...



Fix in progress, hold on.

[FranceBB]

Fixed, check new version: https://github.com/FranceBB/mpv-scripts/releases

[kedautinh12]

Thanks

[FranceBB]

VideoTek v1.3 Released!

Changelog:
- Introduced support to the new HLG Scope via VideoTek(Mode="HLG") which now shows where the reference white of HLG should be, namely 75% of the Limited TV Range signal, so 0.525 Volts. By default, Mode stays as SDR.

Usage Example with HDR HLG videos:

#Indexing a video
video=LWLibavVideoSource("test_shooting.mxf")
audio=LWLibavAudioSource("test_shooting.mxf")
AudioDub(video, audio)


#Calling VideoTek with HLG Mode
VideoTek(Mode="HLG")

The HLG Mode will enable the 75% Reference White marker at 0.525V.

[frank]

Sorry, the mpv VideoTek.lua doesn't work.
On 'y' player stops at end with black screen.
Next 'y' gets video and next 'y' gets audio.
No return to normal play is possible.

I use mpv\portable_config\scripts
The mpv is version v3.

mpv.conf

vo=gpu
hwdec=auto

[FranceBB]

Originally Posted by frank

Next 'y' gets video and next 'y' gets audio.
No return to normal play is possible.

yeah, 'cause this line was missing:

return "[aid1] asetpts=PTS [ao]; [vid1] setpts=PTS [vo]"

Fixed, new release coming.


MPV Waveform Monitor v1.3 Released

Changelog:
Fixed a bug where audio and video were returned separately instead of together when the function was deactivated

Now cycling through "y" works

[frank]

Many thx

But, doesn't work with hw decoding (Intel)
Searching is very slow.

So I stay on Avisynth plugin.

[FranceBB]

Originally Posted by frank

Many thx

But, doesn't work with hw decoding (Intel)
Searching is very slow.

So I stay on Avisynth plugin.

Yeah, hardware decoding won't work.
This is probably 'cause I suck at LUA and I still don't know much about MPV.
The original intent was to play files in real time without having to index them in Avisynth, which... worked... for SD files only. :|
I made it open source hoping that people would actually help me and improve it, but no one seemed interest...

Just FYI, I use the Avisynth plugin regularly, but I don't use the MPV one myself 'cause real time playback is impossible (unless you use SD) and at that point it's just better to do stuff in Avisynth...

[FranceBB]

VideoTek v1.4 Released!

Changelog:
- v1.4 Added frame properties support

[FranceBB]

VideoTek v1.5 Released!

Changelog:
- Improved small monitor image conversion
- Fixed a bug that would sometimes report invalid info at the bottom on the left

[FranceBB]

VideoTek v1.6 Released!

Changelog:

- Added Fractional Framerates Support

Non common, fractional Framerates like 24.5, 24.9, 25.2fps etc are now supported and won't error out as there's a try-catch before ShowSMPTE(). In other words, when non common / non standard framerates are detected, ShowTime() is gonna be used instead.

Normal 24fps (first image)
Fractional 24.5fps (second image)





Bear in mind that in this latter case there will be 3 digits at the end instead of two in the "timecode" as the last portion ain't gonna be frames but rather ms.

[DTL]

Heh - where is our professional 'european reference skintone' colour hue mark at the vectoroscope ? Maybe in the version of 2.0 will be available ?

With some DirectShow input plugin (maybe even current DirectShowSource() is working already too) it is possible to run real pro hardware quality monitor realtime with SDI (or some modern IP-based or optical) input for realtime studio camera engineering setup. So checking/adjusting of the Main Important colour tone of (european) human skin hue is very important. Also for quick alignment of 2 and more physical video cams maybe useful to display several sources vectoroscope render at the same place/window to simplify alignment of the skintone vectoroscope render to the reference mark and between several sources.

Also it is good to have Zoom/Scale (Saturation) control from 1.0 and higher for Vectoroscope window separately to see natural low-saturated data with better precision. It sometime may required about 2x or even 3x zoom/scale to put typical natural scene vectoroscope render to fit window better.

As you show at this example


for real natural scene complete vectoroscope render takes only about 10% or less from full window but it is 100% real and important data to control and adjust if required.

Maybe even in AVS+ scripting (via Eval ?) it is possible to change saturation amplitude display from linear scale to some non-linear (log ? or powered ?) so low saturated natural colours will be more visible in the window area. So it is good to have also switch to scale display of Vectoroscope window (Zoom and saturation transfer function Linear/Log/...).

[FranceBB]

VideoTek v1.7 Released!

Changelog:

- Implemented the new VideoTek(Mode="PQ") with the new 0.406V 58% Reference White marker

I know that Tormento has been asking for this for a long time, so he'll definitely be happy. Big thanks to fzold for cross-checking the 58% reference white at 0.406V.

Usage Example (HDR PQ)

#Indexing a video
video=LWLibavVideoSource("test_shooting_PQ.mxf")
audio=LWLibavAudioSource("test_shooting_PQ.mxf")
AudioDub(video, audio)

#Calling VideoTek with PQ Mode
VideoTek(Mode="PQ")

The PQ Mode will enable the 58% Reference White marker at 0.406V.

[tormento]

Originally Posted by FranceBB

I know that Tormento has been asking for this for a long time

[FranceBB]

VideoTek v1.8 Released!

Changelog:

- Implemented new "Type" parameter to allow nits display instead of volts if explicitly set via VideoTek(Mode="HLG", Type="nits"), but by default it's Type="volts".

As always a big thanks to fzold for cross-checking the values.

Usage Example (HDR HLG Type nits)

#Indexing a video
video=LWLibavVideoSource("test_shooting.mxf")
audio=LWLibavAudioSource("test_shooting.mxf")
AudioDub(video, audio)

#Calling VideoTek with HLG Mode and Type nits
VideoTek(Mode="HLG", Type="nits")

The nits reference in HLG mode will enable the 0, 100, 200, 400, 600 and 1000 nits markers.