|
|
| Agamemnon |
| Posted: Apr 21 2008, 01:21 PM |
 |
|
Newbie
Group: Members
Posts: 5
Member No.: 23459
Joined: 21-April 08
|
I upgraded to VirtualDub 1.7.8 from 1.6.19 since the latter kept crashing when I tried to use ffdshow with H.264 but the edit display in the Input and Output video panes becomes garbled with vertical parallel lines whenever I switch to an aspect ratio other than 1:1. On top of that the colours in the images look over exposed. If I click on the Desktop the displayed image returns to normal but if I click again on VirtualDub 1.7.8 the image becomes garbled again. VirtualDub 1.8.0 suffers from exactly the same problem.
Here is an example of the problem and what the image should look like. Please see attached images.
http://www.enthymia.co.uk/VirtualDub1.7.8.jpg
http://www.enthymia.co.uk/VirtualDub1.6.19.jpg
I am using an MSI NVIDIA FX5700 256MB VIVO graphics card with version 77.77 of the drivers (the highest driver version which will work with VIVO so don't ask me to upgrade) running on Windows XP SP2.
|
|
| phaeron |
| Posted: Apr 21 2008, 07:21 PM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
There's something going wrong with DirectX display acceleration. Go to Options > Preferences > Display and enable Direct3D mode to work around it.
|
|
| Agamemnon |
| Posted: Apr 22 2008, 01:41 AM |
|
|
Newbie
Group: Members
Posts: 5
Member No.: 23459
Joined: 21-April 08
|
Direct3D was already enabled by default. I've tried every possible combination of Direct X options including deactivating it and the image is still garbled. |
|
| phaeron |
| Posted: Apr 22 2008, 03:14 AM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
Turning off the DirectX option entirely is equivalent to when VirtualDub loses focus, so there's something weird here. Note that you have to select another app and go back to VirtualDub before the display settings in Preferences take effect.
|
|
| Agamemnon |
| Posted: Apr 22 2008, 04:11 AM |
|
|
Newbie
Group: Members
Posts: 5
Member No.: 23459
Joined: 21-April 08
|
Oh, I didn't know I had to reload the AVI file.
Ok. I've now got it to display a clean image by using Direct X and leaving the "Use Direct3D" option unchecked and the "Use DirectX overlay surfaces" checked which uses hardware overlay when playing the file. Thanks.
The only problem that I have now got with version 1.7.8 is that in Capture AVI mode it uses double the CPU resources that 1.6.15 needs to capture live video (PAL 720x576) in real time using the Xvid realtime profile, 90% compare to 45% on a 3.2 GHz P4. Version 1.6.17 is just as hungry. |
|
| phaeron |
| Posted: Apr 23 2008, 04:12 AM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
Try turning off the display panes -- the only difference I can find between 1.6.15 and 1.6.17 is that I had roll back a change in renderer selection that was causing ATI cards to break. 1.6.15 uses a rendering path that usually activates the DirectShow Video Mixing Renderer (VMR); 1.6.17 uses a path that usually activates the standard Video Renderer in DirectShow.
|
|
| Agamemnon |
| Posted: Apr 23 2008, 05:01 AM |
|
|
Newbie
Group: Members
Posts: 5
Member No.: 23459
Joined: 21-April 08
|
I've tried it with panes deactivated. VirtualDub 1.6.17 still uses 90% of CPU power compared to 45% with version 1.6.15, which is the Avery Lee VirtualDub-MPEG2 build so it might have been optimised. Even VirtualDub-MPEG2 1.6.19 uses 90% of CPU power compared to half that with the 1.6.15 build. |
|
