Welcome Guest ( Log In | Register )


Important

The forums will be closing permanently the weekend of March 15th. Please see the notice in the announcements forum for details.

 
Fcchandler-plugins + Intel Hd 4000 Grafics
« Next Oldest | Next Newest » Track this topic | Email this topic | Print this topic
Gubel
Posted: Jan 22 2013, 02:37 AM


Member


Group: Members
Posts: 14
Member No.: 35995
Joined: 22-January 13



Hello!

My first Post here! smile.gif But don't worry, I'm using VD for years now, for every video- and capture-addicted stuff...great program!

I'm having a little problem since I upgraded my PC-system to a new Intel i3-3225 + Z68-board with Intel HD 4000 IGP-grafics: I've installed ALL fcchandler-suff (MPEG2, FLV, QT), including newest versions of his AAC- and AC3-AAC-Plugins. (Thanks to fcchandler at this point - good work!!). I also have ffdshow installed, all decoders activated. Whenever I open a video-file that is not AVI (MPEG2, FLV, MP4 (with H.264 or sth. else), ...), the left preview-window stays green or freezes the first frame shown and doesn't show any video-content. The video is properly loaded, the right windows and the output are just fine! But without the preview it's hard to do some A/B-comparison, I can just see the output.
I've noticed this error only since I changed to the new Intel HD-graphics...any help?

If it does matter: I'm using Windows XP SP3 32-bits

Thank you!

Best regards
Alex

PS.: Sorry for my "so lala"-english, im from Germany biggrin.gif
 
     Top
dloneranger
Posted: Jan 22 2013, 05:43 AM


Moderator


Group: Moderators
Posts: 2366
Member No.: 22158
Joined: 26-September 07



Try playing with the display options in the preferences


--------------------
MultiAdjust JoinWav WavNormalize FFMPeg Input Plugin v1827 UnSharpMask
Windows7/8 Codec Chooser
All FccHandlers Stuff inc. Installers for acm codecs AAC, AC3, LameMp3
 
    Top
Abrazo
Posted: Jan 22 2013, 09:25 PM


Advanced Member


Group: Members
Posts: 775
Member No.: 28995
Joined: 5-November 10



A few ideas:

1) Installed most recent version of VirtualDub : v1.10.13 ?

2) Video > Color depth : choose 16-bit / 24-bit / ... instead of Automatic ?

Minor chances (because it is the Input pane that has a problem):

3) Having applied a Video > Filter ? Same problem without (activated) filters ?

4) What about de-activating "Enable 3D video filter acceleration (VDXA)"-checkbox in the VirtualDub menu Options > Preferences ?
 
     Top
Gubel
Posted: Jan 25 2013, 03:50 AM


Member


Group: Members
Posts: 14
Member No.: 35995
Joined: 22-January 13



Thank you for the first time!

1) I tried the new "experimental" release of VirtualDub 1.10.13. This didn't affect this problem. I noticed no difference at all. So I'm now staying with the last "stable" release 1.9.11, until a new main release.

2) That's it! I normaly have "autoselect" enabled to load the native colorspace the decoder delivers. Most Videos (MPEG2, MPEG4, H.264, VC-1) are YV12 (4:2:0-YUV). Exactliy (and only) this setting causes the decribed problem, even if I select YV12 manually. RGB is not an option of course, but I can load the videos as YUY2 (4:2:2). Then the preview is OK and and I have no loss in color-resolution when the source is YV12 natively.

3) The output-pane always displays correcly even if no filter is applied and the input-colorspace is set to YV12.

=> So, I simply use YUY2 instead of autoselect (which mostly is YV12) and everything is alright! Every output-codec also accepts 4:2:2 as input. Only if I temporarily save to an uncompressed AVI, the file would get a bit bigger, because the 2 color-channels of the source-4:2:0 is resized ("blown up") to 4:2:2. But in this case, after filtering-work is done I can switch back to YV12 anyway, when I don't need the preview anymore...

OK, Thanks again!

Best regards
Alex
 
     Top
phaeron
Posted: Jan 26 2013, 08:35 PM


Virtualdub Developer


Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02



In Options > Preferences > Display, uncheck Use DirectX Overlay Surfaces and check Use Direct3D. It sounds like your video drivers have broken overlay support.
 
    Top
Gubel
Posted: Jan 27 2013, 01:59 AM


Member


Group: Members
Posts: 14
Member No.: 35995
Joined: 22-January 13



First of all: I succeeded!
The "color depth"-setting is now set to autoselect again, so I'll load native YV12.

OK, one thing I forgot:
QUOTE
What about de-activating "Enable 3D video filter acceleration (VDXA)"-checkbox in the VirtualDub menu Options > Preferences ?

By default it was disabled - now I have it activated. I didn't notice that it affected anything...

Now to the Preferences -> Display settings:
user posted image

By default the main checkbox "Use DirectX for display panes" plus the sub-checkbox "Use DirectX overlay surfaces" were activated.
I get a proper preview-display under the following conditions:
- main checkbox "Use DirectX for display panes" completely DEactivated
- main checkbox "Use DirectX for display panes" activated and every other sub-checkbox disabled
- "Use DirectX overlay surfaced" + "Use Direct3D" activated
- only "Use Direct 3D" activated

There are more than one combinations that work. Which settings should I choose now?

No Idea about the Intel HD 4000, it just does pretty good overall grafics performance - even with some Games. I've installed the latest drivers available for Windows XP. (I know, there is only 1 year and 3 months left to work with this pretty good, ever lasting OS - RIP!)

 
     Top
Abrazo
Posted: Jan 28 2013, 07:57 PM


Advanced Member


Group: Members
Posts: 775
Member No.: 28995
Joined: 5-November 10



In VirtualDub > Help > Contents > Dialogs > Preferences > Display tab, most of the settings are explained a little bit more.

An important notice at Display tab is "none of these options affect file output".
So these settings have only an influence on preview quality and display performance.

What I am still curious about is: What setting made you finally succeed into getting a correct display ?
May I suppose that it had nothing to do with "Enable 3D video filter acceleration (VDXA)" ?
 
     Top
Gubel
Posted: Jan 29 2013, 01:55 AM


Member


Group: Members
Posts: 14
Member No.: 35995
Joined: 22-January 13



QUOTE
An important notice at Display tab is "none of these options affect file output".

That's clear - blessedly!
QUOTE
What I am still curious about is: What setting made you finally succeed into getting a correct display ?

ONLY "Use DirectX overly surface" had to be disabled! See my descriptions down below...
QUOTE
May I suppose that it had nothing to do with "Enable 3D video filter acceleration (VDXA)" ?

YES! Has nothing to do with it!

OK, I looked at the help file - now I'm a bit cleverer! A bit, because the one and only option that made it was not described in this (probably older) help-file...

Now I found out/did the following:

- if DirectX is disabled completely, VD uses the simple Windows GDI to display, which is not a good choice in the matter of quality and performance. Also the DirectX picture is interpolated pretty good when zooming the panes...
=> left it on (standard), DX is best...

- "Use DirectX overlay surface" is not described, activated by default. No idea what it does.
=> THIS WAS THE CLUE - I had to disable it.

- Then EITHER "Direct3D" OR "OpenGL" is selectable. None of them is enabled by default. If I activate one of them, I can choose between point-/bilinear-/bicubic-resamling (the differences are clear to me) for preview. No idea what else are the advantages.
=> I left it off (default). The picture is also interpolated very well without Direct3D or OpenGL (even if I don't know by which method).

- I enabled "avoid tearing" (disabled by default) - I don't thing it makes anything worse wink.gif
- The rest is irrelevant for me (16-bit display, 2nd monitor, Terminal Services), I don't intend to use VD under this conditions...

I still don't know, what "Enable 3D video filter acceleration (VDXA)" means - it was off by default, now I have it on biggrin.gif . It didn't affect anything till now...

==> The "display"-settings are now set exactly like on the screenshot above.

Nearly all other settings were clear to me, except a few points in the "options"-menu:

user posted image

- What does "sync to audio", "Drop frames when behind" and "Allow video overlay" mean here? I *hope* it only has to do with preview playback, when VD acts as a player...is it right?

- I figured out, that the "Preview field mode"-setting affects only the output-pane while playing back video in realtime (not scrolling). Clearly "Progressive" simply "does nothing" (simply leaves the interlace-frame as it is) and "Bob" is a very simple bob-filter for preview (BFF/TFF is clear). But what is "Weave" and "Non-Interlace"? Shouldn't "Weave" be the same as "Progressive"? Very confusing...
 
     Top
Abrazo
Posted: Jan 29 2013, 07:49 PM


Advanced Member


Group: Members
Posts: 775
Member No.: 28995
Joined: 5-November 10



Thanks for the feedback.

It seems that not all (recent) options are explained in VirtualDub's Help, but some are:
> 'Drop video frames when behind' + 'Sync to audio' in Processing > Video filters > Rendering/saving
> 'Preview field mode' in Processing > Video filters > Display panes

You can always use the Search-tab in 'VirtualDub help' to try to find more information.
(and there is always 'Google')

So, for VDXA it was possible to find some more info on the VirtualDub.org blog (from the author himself):
> http://www.virtualdub.org/blog/archives/ar...ve_2010-m04.php

VDXA is not a typo
"The "VDXA" in the "Enable 3D video filter acceleration (VDXA)" option in VirtualDub's Preferences dialog is not a typo. It stands for VirtualDub eXternal Acceleration and is an additional API I added in 1.9.3 to allow video filters to use Direct3D 9. However, for some reason everyone keeps confusing it with DirectX Video Acceleration (DXVA), which is an entirely different API for video decoding acceleration in Windows, which is completely separate and which VirtualDub doesn't use."


Regards.
 
     Top
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
8 replies since Jan 22 2013, 02:37 AM Track this topic | Email this topic | Print this topic

<< Back to Testing / Bug Reports