VirtualDub2

[shekh]

This is strange. The changes between these versions are minimal and not related to capture or display.
Try moving 42711 to another folder, I saw somewhere that it has effect (maybe drivers keep some crappy settings per exacutable path).
The quoted DirectDraw bug fix is not yet published but you can avoid it: enable dx9 display, or disable vsync

[Morku]

You are right, moving folder seems to affect this. VirtualDub is normal on my D: drive and for testing, I had the previous version on C:. Rebooting PC also seems to help.
So it's not version related. Ignore the post

[wonkey_monkey]

Previous versions of VirtualDub would automatically open a whole image sequence if you dragged the first image onto it, but it doesn't seem to do this any more. Is there a preference I can't see, or has this functionality been removed?

[shekh]

Originally Posted by davidhorman

Previous versions of VirtualDub would automatically open a whole image sequence if you dragged the first image onto it, but it doesn't seem to do this any more. Is there a preference I can't see, or has this functionality been removed?

My bad. I repeatedly find this annoying but keep thinking this is legacy behavior. Will fix.

[SeeMoreDigital]

Originally Posted by shekh

My bad. I repeatedly find this annoying but keep thinking this is legacy behavior. Will fix.

Thanks

[shekh]

Originally Posted by davidhorman

Previous versions of VirtualDub would automatically open a whole image sequence if you dragged the first image onto it, but it doesn't seem to do this any more. Is there a preference I can't see, or has this functionality been removed?

fixed

Originally Posted by lansing

Reporting a few bugs.

In capture mode, the video levels window can be opened infinite instance instead of just one.

And when I changed the exposure value in the levels setting and start capturing, the exposure value was reset back to the previous value from the "capture filter" instead.

Also, when capture is running, clicking "file->exit capture mode" did not work.

Added fixes for menus. Actually, the whole menu does not reflect "capturing" state, most commands are simply ignored. Now "exit capture" works, and also "device disconnect".
For the exposure I have no idea. Maybe there is bug in driver.

[shekh]

Some new/recent stuff: Audio display was significantly polished and got some new controls: https://sourceforge.net/p/vdfiltermo.../AudioDisplay/
I like the possibility to scroll it left-right. Before it felt barely useful because of continuous glitches. Now I even enabled it to sync with preview (however, this is only possible with caching input driver now because of multithreading problems).
If anyone has ideas what to tweak in audio display it is good time

[wonkey_monkey]

Very nice!

[wonkey_monkey]

I just updated and now I find that VirtualDub2 remembers zoom levels from when I last closed it. This, I think, is different to the previous behaviour, where files were always first opened at 100%.

Is there an option to control this?

[shekh]

There is no option. Previously it was not always consistent, was able to remember "auto-size" until you touch anything.
The option would be "remember auto-size and zoom", not big deal to add.

[wonkey_monkey]

I would suggest such an option should be off by default - if you open VirtualDub2 after weeks or months, you would expect it (by default) to show a view of the file unaffected by what you may have been working on last time. Principle of least surprise rules here

[StainlessS]

Originally Posted by davidhorman

I would suggest such an option should be off by default - if you open VirtualDub2 after weeks or months, you would expect it (by default) to show a view of the file unaffected by what you may have been working on last time. Principle of least surprise rules here

+1 on that.

[wonkey_monkey]

Might there one day be support for AviSynth+'s Planar RGB colourspaces?

[kolak]

Is Vdub width restriction to be mod 16 for Cineform due to codec or Vdub limitations? I thought Cineform can be any frame size.

[shekh]

Originally Posted by davidhorman

Might there one day be support for AviSynth+'s Planar RGB colourspaces?

Planar rgb is internally supported, so the question is how to bridge it with avisynth. I'm not sure if vfw output from avisynth already handles them, probably not.

[shekh]

Originally Posted by kolak

Is Vdub width restriction to be mod 16 for Cineform due to codec or Vdub limitations? I thought Cineform can be any frame size.

It is Cineform limitation. I enforced it after discovering a crash with wrong size (in my early builds the limit was not checked).

[kolak]

Is it hard limitation in codec design which can't be overwritten?

[shekh]

Can't tell exactly, it didn't look simple.
Better to ask on https://github.com/gopro/cineform-sdk
There may be possibility to use metadata-based cropping in the codec (not supported by vd2)

[pinterf]

Originally Posted by shekh

Planar rgb is internally supported, so the question is how to bridge it with avisynth. I'm not sure if vfw output from avisynth already handles them, probably not.

It's supported but I couldn't test it, search for
OPT_Enable_PlanarToPackedRGB on avisynth.nl

[shekh]

Originally Posted by pinterf

It's supported but I couldn't test it, search for
OPT_Enable_PlanarToPackedRGB on avisynth.nl

Looks like I can add G3/G4 fourcc's, btw where is vfw export in the source code?