VirtualDub2

[LigH]

OK, I still linked veedub64.exe to my desktop... :o

Regarding the sliding split screen, the key of davidhorman's request was to move the slider "live" with the mouse pointer hovering over the video, like in some image-compression comparing websites before with JavaScript (unfortunately I don't remember which).

[wonkey_monkey]

A sliding split screen ... possibly not as easy for videos as for still pictures. There may be modulo constraints for supported widths of the split panes.


It would be done (I would imagine) as part of the Windows/DirectX painting, by which time everything's already RGB (right?). Instead of painting input on left and output on right, just paint with clipping to the same place.

Regarding the sliding split screen, the key of davidhorman's request was to move the slider "live" with the mouse pointer hovering over the video, like in some image-compression comparing websites before with JavaScript (unfortunately I don't remember which).

Exactly. I tried to make an AviSynth filter like that once, but it always lagged behind because VirtualDub was fetching ahead.

I found the page I was thinking of, maybe the same one:

https://xooyoozoo.github.io/yolo-octo-bugfixes/#swallowtail&jpg=s&bpg=s

[StainlessS]

Why not, done.

Can we also have "VirtualDub2 Script Editor" window title, thanx :)

EDIT: And for the Hex Editor too.
EDIT: And maybe the help.

EDIT: For SawBones AutoIt utility, have now changed to VirtualDub2 as required main window title, need to know what the
script editor will be called otherwise if future name changed then will cease to function properley, awaiting next release to
see if script editor window renamed.

[AKBabel]

I have found some new bugs.^^
If a dpx sequence is loaded via “sequence” VirtualDub only loads 1201 files (actually there are more than 11000) and the image stops while encoding at the 1201 frame. The encoding still runs for 11000 images and the final video stops at frame 1201, showing the full timeline of 11000 frames.
Everything seems fine with “linked segments”.
If I try to batch run a job (source rgba64, used filters: resize, gamma correct, levels) it stops with an error message.
Message:
“Error during script execution at line 27 column 47: error in external Sylia linkages
VirtualDub.video.filters.instance[1].Config(0)<!>;
VirtualDub.video.filters.Add(“levels”);Virtua”

If I try to run same project directly, it works fine.

[shekh]

I have found some new bugs.^^
If a dpx sequence is loaded via “sequence” VirtualDub only loads 1201 files (actually there are more than 11000) and the image stops while encoding at the 1201 frame. The encoding still runs for 11000 images and the final video stops at frame 1201, showing the full timeline of 11000 frames.
Everything seems fine with “linked segments”.


When you click on "Sequence", the number next to it is how much?
After you click "open", what is the timeline length?
If you go to File->File information, what is there? (number of segments, duration etc, screenshot would help too)
Can you navigate through entire sequence?


If I try to batch run a job (source rgba64, used filters: resize, gamma correct, levels) it stops with an error message...


Reproduced.

[AKBabel]

When you click on "Sequence", the number next to it is how much?
After you click "open", what is the timeline length?
If you go to File->File information, what is there? (number of segments, duration etc, screenshot would help too)
Can you navigate through entire sequence?
The number showing next to "sequence" was also 1201.
I guess I found out. There was a file missing (01201.dpx) in the sequence. But it showed up all 11000 pics in the timeline and I was able to navigate through the sequence.

[shekh]

The number showing next to "sequence" was also 1201.
I guess I found out. There was a file missing (01201.dpx) in the sequence. But it showed up all 11000 pics in the timeline and I was able to navigate through the sequence.

It is amazing FFMpeg gem.
As extreme example it can detect sequence containing only binary progression, pretending it has all files.

result: duration is 16 frames

test_000.png
test_001.png
test_002.png
test_004.png
test_008.png
test_016.png


result: duration is 1 frame (stops when fails to see test_001.png)

test_000.png
test_002.png
test_003.png
test_004.png


Absolutely irrational imo. Will think what to do with this.

Btw, GammaCorrect Config bug is old (also present in VD 1.10.4)

[GMJCZP]

Thanks for the program. I ask if this version can coexist with other versions because when I use the "File" menu it opens correctly but when I use the context menu I open VirtualDub 1.10.4, I do not know what I'm doing wrong. I use W7 32b

Of course with this problem this program is not added to the other "Open with"

Edit: I noticed that auxsetup is now apart in a folder called "extras", unlike VirtualDub and VirtualDubMod.

[shekh]

Thanks for the program. I ask if this version can coexist with other versions because when I use the "File" menu it opens correctly but when I use the context menu I open VirtualDub 1.10.4, I do not know what I'm doing wrong. I use W7 32b

Of course with this problem this program is not added to the other "Open with"

Edit: I noticed that auxsetup is now apart in a folder called "extras", unlike VirtualDub and VirtualDubMod.

AFAIK "Open with" is not part of any VirtualDub itself, maybe it is created manually or some 3rd party setup.
You can simply "Open with", "Choose..", and the new entry will coexist with old one.

auxsetup is only useful to install frameserver driver. Which in fact can be done once using any VD version (the drivers are autonomous and nothing has changed in them). I wanted to remove this because there was too many (barely useful) executables in the main folder.

[StainlessS]

You can simply "Open with", "Choose..", and the new entry will coexist with old one.

I not so long ago did a reinstall of XP32, I seem to remember that on "Open With", "Choose...", etc, it did not add new coexisting entry,
I had to do something additional to get it to add the "VirtualDub" option to the list of available options.
Not sure what it was that I did, maybe ticked "Always use the selected program to open this kind of file" box, or maybe saved AVI,
or something else.
If you do tick "Always use the selected ... ", you can always go and change back to original setting. (probably what I did).

[Midzuki]

Changing to easy name: VirtualDub2

But why didn't you change the names of the files themselves? :confused:

I mean:

vdub2.exe
vdub2x64.exe
VirtualDub2.chm
VirtualDub2.exe
VirtualDub2x64.exe
VirtualDub2.vdi
VirtualDub2x64.vdi

[GMJCZP]

Thank you shekh for answering me, but the new entry is not added because VirtualDub 1.10.4 is opened instead of VirtualDub2. Is more or less what TinMan is trying to say.

Edit: in short, I have VirtualDub 1.10.4 and VirtualDubMod 1.5.10.3 both modded by bcn_246.

[shekh]

But why didn't you change the names of the files themselves? :confused:

I mean:

vdub2.exe
vdub2x64.exe
VirtualDub2.chm
VirtualDub2.exe
VirtualDub2x64.exe
VirtualDub2.vdi
VirtualDub2x64.vdi

I see the name "VirtualDub" as a shared/inherited namespace. Steering away from it creates some trouble.
Some people use scripts with "virtualdub.exe" or "vdub.exe" name baked in. It is trivial to modify, but why?
Also the registry key for settings is "virtualdub.org".
Inside the chm the word "VirtualDub" is on all pages. I think it is not very good idea to replace it.

[StainlessS]

Will the script editor title bar name be changed ? (I'm good either way but would be nice to know)

EDIT:
Can we also have "VirtualDub2 Script Editor" window title, thanx :)

EDIT: And for the Hex Editor too.
EDIT: And maybe the help.

EDIT: For SawBones AutoIt utility, have now changed to VirtualDub2 as required main window title, need to know what the
script editor will be called otherwise if future name changed then will cease to function properley, awaiting next release to
see if script editor window renamed.

EDIT: Have now banished 3 versions of VirtualDub from my machine (v1.8MPEG2, v1.9.xx and v1.10.4), am though keeping
VdubMod as I have several templates / scripts that rely upon it and it does not conflict with Vd2 in the same way that VD final does.

EDIT To Below: thanx Shekh, good to know.
Guess I have to mod the VDMod reliant scripts etc to work with VD2, and can then get rid of that one too :)

[shekh]

Will the script editor title bar name be changed ? (I'm good either way but would be nice to know)


Yes, going to change in next hotfix build. Also in other windows titles (status, log, jobs, ...)

[Midzuki]

It is trivial to modify, but why?

Because of *consistency*.

Just as an example, in the beginning MPC-HC used an mplayerc.ini as if it were just a newer version of Media Player Classic. Fortunately the developers realized that MPC-HC was greater than the original MPC and started to act accordingly.

[GMJCZP]

I still do not know why VirtualDub 1.10.4 opens with the context menu instead of VirtualDub2, please help me.

[shekh]

I still do not know why VirtualDub 1.10.4 opens with the context menu instead of VirtualDub2, please help me.

You are right, this association does not work the way I thought. Need to investigate.

[GMJCZP]

You are right, this association does not work the way I thought. Need to investigate.

Thanks.

[shekh]

I still do not know why VirtualDub 1.10.4 opens with the context menu instead of VirtualDub2, please help me.

This .reg template worked for me:


Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\VirtualDub2.media.x86\shell\open\command]
@="\"E:\\vd\\VirtualDub.exe\" \"%1\""

[HKEY_CLASSES_ROOT\VirtualDub2.media.x64\shell\open\command]
@="\"E:\\vd\\VirtualDub64.exe\" \"%1\""

[HKEY_CLASSES_ROOT\.avi\OpenWithProgids]
"VirtualDub2.media.x86"=hex(0):
"VirtualDub2.media.x64"=hex(0):


Looks like the manual method (browse for program) relies on filename.exe, might have worked if I followed Midzuki' suggestion.

[GMJCZP]

I tried saving it in a .reg file and followed without fixing the problem.

[shekh]

I tried saving it in a .reg file and followed without fixing the problem.

You did not reply to PM, so have you replaced "e:\\vd..." with the correct path?
I'd prefer to prepare installer instead of massaging reg files, but it needs time.

[shekh]

New build: bugfix + some renames VirtualDub->VirtualDub2

I have found some new bugs.^^


fixed

there seems to be a slight problem with borderless mode after coming out of fullscreen

After new fixed I tried to push everything: fullscreen on off, maximize on off, layout auto size on off, ...
All works. Let me know if you find something.

[shekh]

Another idea: centered mode. Disable the output frame, just show the input frame (or vice versa), centered in the window with no border, and maybe the possibility to change background colour.

Do you mean to fit (letterbox) image into window? As opposed to current "Fit Outside" method.
The reason I don't offer more common "Fit Inside" is I am still abusing the display system which is quite restricted. It is also impossible to have large zoom :(

[wonkey_monkey]

Looks good so far! Although wouldn't you know it, I have a couple more suggestions, I'm afraid...

Could fullscreen maintain aspect ratio? Could there be scaling options in fullscreen mode?

One minor one: would it be possible when zipping up a version to put everything in a directory? It's a bugbear of mine when you have to create a new folder to drag everything into instead of just dragging out a folder :)

[shekh]

Because of *consistency*.

Just as an example, in the beginning MPC-HC used an mplayerc.ini as if it were just a newer version of Media Player Classic. Fortunately the developers realized that MPC-HC was greater than the original MPC and started to act accordingly.

I thought about this and renaming "VirtualDub.exe" still does not look more appealing. It is 50/50 to me (no go).

In any case, I sorted various occurences of "VirtualDub" which I have to consider. Comments enabled. https://sourceforge.net/p/vdfiltermod/tickets/101/

[shekh]

Could fullscreen maintain aspect ratio? Could there be scaling options in fullscreen mode?

Why not? It has the same right-click menu. Have you tried?


One minor one: would it be possible when zipping up a version to put everything in a directory? It's a bugbear of mine when you have to create a new folder to drag everything into instead of just dragging out a folder :)

Sorry, I prefer it like it is...

[GMJCZP]

You did not reply to PM, so have you replaced "e:\\vd..." with the correct path?
I'd prefer to prepare installer instead of massaging reg files, but it needs time.

I have problems with the energy power and the internet connection, sorry.
You're right, is better prepare a robust solution. In the 41489 version the problem continues, open VD 1.10.4 instead of your program.

[wonkey_monkey]

Why not? It has the same right-click menu. Have you tried?

I did - the zoom options do nothing (the tick doesn't move). The aspect ratio options weren't doing what I had expected, and I hadn't realised what it was doing because of the abstract test video I was using - it seems to be cropping in order to fill the screen completely, instead of adding black bars to show the whole video, which I think would be the most expected and useful behaviour (since there is currently no way to view a full video in the right aspect ratio, unless it happens to match your screen).

Sorry, I prefer it like it is...

Well, okay, but for those who like to copy a single directory it would be useful (VirtualDub2 currently lives in a folder on my desktop); for those who don't, they just have to go down one level and it's the same as before. It is therefore objectively the best way for everybody ;)

[shekh]

I did - the zoom options do nothing (the tick doesn't move). The aspect ratio options weren't doing what I had expected, and I hadn't realised what it was doing because of the abstract test video I was using - it seems to be cropping in order to fill the screen completely, instead of adding black bars to show the whole video, which I think would be the most expected and useful behaviour (since there is currently no way to view a full video in the right aspect ratio, unless it happens to match your screen).


Have you seen post 474 https://forum.doom9.org/showthread.php?p=1836670#post1836670

Zoom and aspect ratio work the same way as in non-fullscreen state.
You cannot zoom less than to fill entire window and it means with small picture you have no options at all. With 1920 picture on 1920 screen you can zoom 100, 150, 200 etc. Not 75.

[Midzuki]

I thought about this and renaming "VirtualDub.exe" still does not look more appealing. It is 50/50 to me (no go).

In any case, I sorted various occurences of "VirtualDub" which I have to consider. Comments enabled. https://sourceforge.net/p/vdfiltermod/tickets/101/

That's fine. I will keep NOT using your mod, even though it is better than the original VirtualDub.

</END_OF_DISCUSSION>

[wonkey_monkey]

You cannot zoom less than to fill entire window and it means with small picture you have no options at all. With 1920 picture on 1920 screen you can zoom 100, 150, 200 etc. Not 75.

Oh... well, that would be a really useful change if it could be possible. Otherwise it's impossible to view all of a video at the right aspect ratio unless it happens to match your screen.

[LigH]

Is this now officially "Quengelware" (pester power item)? :o

[shekh]

Oh... well, that would be a really useful change if it could be possible. Otherwise it's impossible to view all of a video at the right aspect ratio unless it happens to match your screen.

I agree but it is quite difficult to do.

[wonkey_monkey]

I agree but it is quite difficult to do.

Fair enough! Thanks again for your continuing efforts!

[GMJCZP]

I look forward to this program in the near future can coexist with other versions of VDub and VDubMod (adding to contextual menu), but at this rate I think they will go to eternal rest, lol.

I have a proposal, is it possible to add the "Streams" menu, including "Stream list" command, like the one VirtualDubMod has, this is one of the reasons why I still use it, the other one is for the script editor, which already has VDub 2.

[StainlessS]

I look forward to this program in the near future can coexist with other versions of VDub and VDubMod

It never proved much of a problem for me (having just banished about 3 versions of Vdub from my machine), only ever problem
may have been context menu opening, and even that was easily solved with a registry fix.
I had about 4 or 5 versions all avialable via hotkeys. just needed to copy the directory, and uninstall, then make shortcuts and
add hotkeys. Easy peasy, but no longer necessary due to the fantabulous fan-dabby-dozy Vdub2 :)

EDIT: I used to rename VirtualDubFilterMod to VirtualDub_DEEP.exe for use with the reg fix
(just so I knew which option to click in open with menu).

[SeeMoreDigital]

I look forward to this program in the near future can coexist with other versions of VDub and VDubMod...
I'm with StainlessS. Up until this weekend I ran the last version of the original VirtualDub and VirtualDub2 both launched ok from the 'taskbar' and ran without any major issues. Now it's just VirtualDub2 :)

[shekh]

I have a proposal, is it possible to add the "Streams" menu, including "Stream list" command, like the one VirtualDubMod has, this is one of the reasons why I still use it, the other one is for the script editor, which already has VDub 2.

Currently this feature (multiple streams) is very far.

[Revan654]

I would Thank anyone who put work into this and picked up where VDub left off. I was hoping someone would pick it up at some point, Didn't even know VDub2 even existed until I came across this while searching for another encoder.

I do have one question if someone could answer this. I couldn't find any subject on the matter. Is there any kind of support for HDR capturing or planned support? I do have a HDR capture card I was wondering if I could use this program to capture a HDR signal.

- Thanks

[shekh]

I would Thank anyone who put work into this and picked up where VDub left off. I was hoping someone would pick it up at some point, Didn't even know VDub2 even existed until I came across this while searching for another encoder.

I do have one question if someone could answer this. I couldn't find any subject on the matter. Is there any kind of support for HDR capturing or planned support? I do have a HDR capture card I was wondering if I could use this program to capture a HDR signal.

- Thanks

Hi, I am not sure about HDR capture specifics. There is selection for 10 bit and 16 bit input formats (confirmed to work with Magewell and some Decklink drivers). Is this what are you looking for?
Possible formats are v210, P210, P216, P010, P016, v410, Y410, Y416, r210, R10k.
If you need to capture any HDR metadata, this is absent.

[GMJCZP]

StainlesS, here I have what originally shekh sent me via PM, includes the files .avi and .avs:

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\VirtualDub2.media.x86\shell\open\command]
@="\"C:\\Program Files\\GordianKnot\\VirtualDub2_41489\\VirtualDub.exe\" \"%1\""

[HKEY_CLASSES_ROOT\.avi\OpenWithProgids]
"VirtualDub2.media.x86"=hex(0):

[HKEY_CLASSES_ROOT\.avs\OpenWithProgids]
"VirtualDub2.media.x86"=hex(0):

It is only defined for 32b.

I have a script that I have that VD 1.10.4 opens very slowly and VDMod opens it in better way, but VD2 opens it up much better. I think it's time to let VD 1.10.4 die in peace.

[StainlessS]

Good choice mine already gone.

[Yanak]

Done, VersionInfo updated.

I know i'm a bit late but thank you very much for this and all the rest :)
( did not had time to install yet as not on my machine tho )

[Revan654]

Hi, I am not sure about HDR capture specifics. There is selection for 10 bit and 16 bit input formats (confirmed to work with Magewell and some Decklink drivers). Is this what are you looking for?
Possible formats are v210, P210, P216, P010, P016, v410, Y410, Y416, r210, R10k.
If you need to capture any HDR metadata, this is absent.

Yes I would need the metadata(Atlease I think I do, not 100% sure). I know shortly Magewell will be releasing there new SDK that has fully HDR support. Maybe that can be added in?

I don't know how the programming works with SDK or how VDub 2 is programmed in general.

I found this from Magewell Maybe you can make sense of it.

"If you have the ability or the experience on how to preview the HDR signal,you do not need to wait for our SDK.
In our SDK,you will know how to capture the HDR singal ,and we will provide a filter to present the recorded video.

We will provide the HDR preview filter,render,and a series of examples in our SDK. We just provide a way to show/record the HDR video.How to integrate HDR fuction into the third-party software is your job.You just provide the filter and render on Microsoft Directshow based software,such as GraphEdit."

^an EDID file must be uploaded to the card first, Which is the easy task. It figuring out how to capture the HDR signal which has been confusing.

[shekh]

If you have the ability or the experience on how to preview the HDR signal

Sad part it's exactly what I don't have. I loosely follow various hdr-related threads but I still have no clue how HDR10 metadata is stored in video and what it might look like.
The capture in vd2 is (mostly) based on DirectShow (much like GraphEdit), so the talk about preview filters etc. makes sense to me.

[Revan654]

Sad part it's exactly what I don't have. I loosely follow various hdr-related threads but I still have no clue how HDR10 metadata is stored in video and what it might look like.
The capture in vd2 is (mostly) based on DirectShow (much like GraphEdit), so the talk about preview filters etc. makes sense to me.

I think filter can be built for HDR, I'm just not sure how.

I been searching on the subject matter. It gets very confusing at times.

This is what the HDR section of metadatalooks like:

Mastering display color primaries : R: x=0.680000 y=0.320000, G: x=0.265000 y=0.690000, B: x=0.150000 y=0.060000, White point: x=0.312700 y=0.329000
Mastering display luminance : min: 0.0200 cd/m2, max: 1200.0000 cd/m2

Entire Video Metadata

Video
ID : 256 (0x100)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info? : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
Codec ID : 36
Duration : 2 s 83 ms
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Writing library : ATEME Titan KFE 3.7.0 (4.7.0.2002)
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : SMPTE ST 2084
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : R: x=0.680000 y=0.320000, G: x=0.265000 y=0.690000, B: x=0.150000 y=0.060000, White point: x=0.312700 y=0.329000
Mastering display luminance : min: 0.0200 cd/m2, max: 1200.0000 cd/m2

More Here: https://trac.ffmpeg.org/ticket/5831

HDR used by Youtube with MKV looks like this:

+ EBML head
|+ EBML version: 1
|+ EBML read version: 1
|+ EBML maximum ID length: 4
|+ EBML maximum size length: 8
|+ Doc type: webm
|+ Doc type version: 4
|+ Doc type read version: 2
+ Segment, size 29548815
|+ Seek head (subentries will be skipped)
|+ EbmlVoid (size: 45)
|+ Segment information
| + Timecode scale: 1000000
| + Duration: 154.538s (00:02:34.538)
| + Multiplexing application: google
| + Writing application: google
|+ Segment tracks
| + A track
| + Track number: 1 (track ID for mkvmerge & mkvextract: 0)
| + Track UID: 11717489602804838
| + Track type: video
| + Default duration: 16.683ms (59.940 frames/fields per second for a video track)
| + Codec ID: V_VP9
| + Video track
| + Pixel width: 1280
| + Pixel height: 720
| + Video colour information
| + Colour matrix: 9
| + Colour range: 1
| + Colour transfer: 16
| + Colour primaries: 9
| + Video colour mastering metadata
| + Max luminance: 1000
| + Min luminance: 0.001
| + Red colour coordinate x: 0.68
| + Red colour coordinate y: 0.31996
| + Green colour coordinate x: 0.26494
| + Green colour coordinate y: 0.68996
| + Blue colour coordinate x: 0.15
| + Blue colour coordinate y: 0.05998
| + White colour coordinate x: 0.3127
| + White colour coordinate y: 0.32896
|+ Cues (subentries will be skipped)
|+ Cluster

[shekh]

I examined the Exodus_UHD_HDR_Exodus_draft.mp4 with ffprobe. Now I see "side_data_type=Mastering display metadata" attached to each frame, but the parameters are the same through entire demo. Boring example.

[kolak]

They will be the same as HDR10 uses static matadata for whole stream. It should be repeated every GOP for seeking needs.

HDR10+ uses dynamic metadata but I don't think that you can find any samples yet.
DolbyVision is also dynamic metadata, but it's proprietary, so even if you can extract it, you won't know what to do with it.

[shekh]

They will be the same as HDR10 uses static matadata for whole stream. It should be repeated every GOP for seeking needs.

HDR10+ uses dynamic metadata but I don't think that you can find any samples yet.
DolbyVision is also dynamic metadata, but it's proprietary, so even if you can extract it, you won't know what to do with it.

Thanks. Following Revan654 question I was thinking what can be done with metadata capture. Because it can be a sequence of unrelated clips it must be possible to preserve variable metadata (per scene) despite its static nature. The fact that it is included per GOP helps this idea.