|
|
| MikeGuy |
| Posted: Jun 25 2012, 02:21 AM |
 |
|
Advanced Member
Group: Members
Posts: 31
Member No.: 22300
Joined: 23-October 07
|
I updated from 1.9.11 to 1.10.2. I am not sure why, but when I step through the file in VD with the arrow keys, or time line button, sometime I get pixilation. I do not get any in the output, just when I am in the editor. I did not get this back with 1.9. I am wondering if I have a display setting wrong.
Here is a sample screen shot:
http://i48.tinypic.com/2h81caf.jpg
I am wondering if I am viewing the difference from the previous frame ... rather than the whole frame .... or this some other business. Tkx
|
|
| MikeGuy |
| Posted: Jun 25 2012, 05:32 PM |
|
|
Advanced Member
Group: Members
Posts: 31
Member No.: 22300
Joined: 23-October 07
|
I went back to 1.9.11 and the problem went away. This is definitely a 1.10.2 bug.
Problem shows when I am stepping through the clip in VD, not in the saved output. If I go away from the problem, and come back to the problematic frame(s), problem goes away (sometime ... usually).
The way I see it is:
1. Got a coding bug, dude.
2. Maybe I have a View setting wrong in 1.10.2 .
3. Maybe you made some choices ...... say regarding the internal filters .... such that when I bring in DivX chit in 1.10.2 this problem shows up.
Just thought more verbiage may jiggle somebody's brain. |
|
| phaeron |
| Posted: Jul 1 2012, 09:16 PM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
What is the file type (extension) of the video you are working with?
|
|
| MikeGuy |
| Posted: Jul 3 2012, 03:35 PM |
|
|
Advanced Member
Group: Members
Posts: 31
Member No.: 22300
Joined: 23-October 07
|
Thanks for looking into it. Sorry I am late with the answer, but I had internet connectivity issues.
OK, so it happens with every file I open .... if I step around within it with the slider long enough.
It happens both from files that came off the old Sony camcorder (MPEG2/AC-3 ) and AVI/DivX/MP3.
No problem whatsoever with 1.9.11. Problem must be off 1.10.1 or 1.10.2 (I know for sure it shows up in your latest release, maybe even in next to last too).
Now that I fell back to 1.9.11 it's all cool, no longer running in panic mode .... hopefully I told you enough to generate a memory dump resulting in a solution. |
|
| dloneranger |
| Posted: Jul 3 2012, 04:09 PM |
|
|
Moderator
Group: Moderators
Posts: 2366
Member No.: 22158
Joined: 26-September 07
|
Screen shot of the file information dialog would be useful, to see what's actually decoding the video
(for both versions of virtualdub)
There was a recently introduced option in the prefs 'use video stream fccHandler in codec search', you could try changing that
--------------------
MultiAdjust JoinWav WavNormalize FFMPeg Input Plugin v1827 UnSharpMask
Windows7/8 Codec Chooser
All FccHandlers Stuff inc. Installers for acm codecs AAC, AC3, LameMp3 |
|
| MikeGuy |
| Posted: Aug 3 2012, 03:24 PM |
|
|
Advanced Member
Group: Members
Posts: 31
Member No.: 22300
Joined: 23-October 07
|
Here is a sample DivX clip shot around Rockfeller Center in NYC. It is off the cam, converted to DivX/MP3 opened in 2 VD versions. VD1.9.10 chooses to pull in DivX 6.9.2 Codec, and VD 1.10.2 chooses to pull in ffsshow DX50. This is the same file, and VD makes its choices on its own, doing fine in 1.9 and messing in 1.10:
1.9.10 link http://i50.tinypic.com/23vib2h.jpg
1.10.2 link http://i50.tinypic.com/dfbxxy.jpg |
|
| dloneranger |
| Posted: Aug 3 2012, 05:47 PM |
|
|
Moderator
Group: Moderators
Posts: 2366
Member No.: 22158
Joined: 26-September 07
|
Well, you could turn off divx in FFDShow's vfw options to stop the error in it's tracks
- I've never seen ffdshow fail to decode like that though, maybe updating it could help?
Or,
In V1.10+ there's an option in the preferences to use video stream fcchandler in codec search
You could tick/untick that and see if that helps
--------------------
MultiAdjust JoinWav WavNormalize FFMPeg Input Plugin v1827 UnSharpMask
Windows7/8 Codec Chooser
All FccHandlers Stuff inc. Installers for acm codecs AAC, AC3, LameMp3 |
|
| Abrazo |
| Posted: Aug 3 2012, 06:06 PM |
|
|
Advanced Member
Group: Members
Posts: 775
Member No.: 28995
Joined: 5-November 10
|
Could it be that MikeGuy installed the 64-bit version of VirtualDub 1.10.2 ?
That could explain why VirtualDub does not use the (32-bit) DivX-codec and uses ffdshow instead.
If that would be, then it would be good to control the Video decoder configuration of ffdshow and/or try with the most recent version:
http://sourceforge.net/projects/ffdshow-tr...0by%20XhmikosR/
Or,
Install the 32-bit version of VirtualDub 1.10.2 which would normally use the 32-bit DivX-codec for decoding.
|
|
| MikeGuy |
| Posted: Aug 3 2012, 06:37 PM |
|
|
Advanced Member
Group: Members
Posts: 31
Member No.: 22300
Joined: 23-October 07
|
I've downloaded the proper 32 bit version from here:
http://sourceforge.net/projects/virtualdub....2.zip/download
Whatever fault there is, if any, in the old ffdshow has no effect VD 1.9.10. I would rather have VD 1.10.2 get fixed than me unnecessarily reconfigure my settings and screw my machine. |
|
| dloneranger |
| Posted: Aug 3 2012, 07:31 PM |
|
|
Moderator
Group: Moderators
Posts: 2366
Member No.: 22158
Joined: 26-September 07
|
It's not a 'needs fixing' thing, it's a choice
Just untick/tick that option in virtualdubs preferences to restore it's old behaviour
The codec needed is stored in the avi in 2 parts - the codec that created it's fourcc, and the fourcc type
The codecs used for creating the file can often write many different formats
eg a divx type file (dx50) can be written by xvid, divx and ffdshow
When the files written, the codec puts it's own fourcc in, and the kind of fourcc it's writing in
eg
xvid writes xvid/dx50
divx writes divx/dx50
ffdshow writes ffds/dx50
When you come to decode the video there is a choice to be made
Which codec to pick to decode with?
If virtualdub asks for a dx50 decoder then it'll use the last one installed that decodes dx50
Or it can ask for the other codec type instead xvid/divx/ffds
Previously, virtualdub didn't let you choose which decoder you wanted - it just picked the dx50 part
Now, you can choose via the preferences option for it to use either the first part or the second
There isn't a 'right' choice, as it'll depend on what codecs (and versions thereof) are installed on an individual pc
--------------------
MultiAdjust JoinWav WavNormalize FFMPeg Input Plugin v1827 UnSharpMask
Windows7/8 Codec Chooser
All FccHandlers Stuff inc. Installers for acm codecs AAC, AC3, LameMp3 |
|
| Abrazo |
| Posted: Aug 3 2012, 08:44 PM |
|
|
Advanced Member
Group: Members
Posts: 775
Member No.: 28995
Joined: 5-November 10
|
@dloneranger:
Many thanks for this very valuable information. "Untick that option" must normally be the answer and solution for MikeGuy.
I just did a test with activating "Use video stream fccHandler in codec search" (+ Save and OK) in VirtualDub 1.10.2, Options > Preferences > AVI,
and after that, changed the "FourCC Description code" of a DivX encoded AVI from "DX50" to "ffds" with INMATRIX "AVI FourCC Code Changer".
( http://www.inmatrix.com/files/avic_download.shtml )
Indeed, when I opened that changed AVI in VirtualDub 1.10.2, and looked at File > Information..., it showed 'ffdshow video codec" as the Decompressor.
|
|
| dloneranger |
| Posted: Aug 3 2012, 09:05 PM |
|
|
Moderator
Group: Moderators
Posts: 2366
Member No.: 22158
Joined: 26-September 07
|
Yeah - it's a trade off
Do you want your preferred decoder (which may be better) or the one that created it (which may be most compatible) to decode
There's not really a right choice :-)
btw if it can't find the exact decoder that matches, it'll fall back to using the system default one
(Depending on what decoders you have installed on your pc)
--------------------
MultiAdjust JoinWav WavNormalize FFMPeg Input Plugin v1827 UnSharpMask
Windows7/8 Codec Chooser
All FccHandlers Stuff inc. Installers for acm codecs AAC, AC3, LameMp3 |
|
| MikeGuy |
| Posted: Aug 3 2012, 09:07 PM |
|
|
Advanced Member
Group: Members
Posts: 31
Member No.: 22300
Joined: 23-October 07
|
Thanks for the help. Now with checked "Options.Preferences.Avi.Use video stream fccHandler in codec search" 1.10.2 works as good as 1.9.10
With the check on, I get what I am expecting under File Information: DivX 6.9.2 Codec (8 Logical... (DX50)
I single stepped through the file back and forth (about 1000 frames), and the decoding was perfect with the check on. |
|
| Abrazo |
| Posted: Aug 4 2012, 09:49 AM |
|
|
Advanced Member
Group: Members
Posts: 775
Member No.: 28995
Joined: 5-November 10
|
Just a short reaction because I did expect just the opposite (untick).
MikeGuy's VirtualDub 1.9.11 uses the preferred codec to decode the DivX-encoded file and the result is good, so I would say the preferred one is "DivX".
In his VirtualDub 1.10.2 it uses the 'wrong' one, thus it must be the ffdshow-decoder (confirmed by the "print screen").
If the known parameter is unticked that would mean that in this case the "ffdshow" is the preferred one ?
Now MikeGuy has ticked the parameter and the result is good, because now it uses the DivX-codec for decoding.
This should mean and confirm that "DX50" is the description code in his AVI-files.
So, I don't understand ... or it must be that for VirtualDub 1.10.2 and 1.9.11 the preferred codecs can be different ?
|
|
| dloneranger |
| Posted: Aug 4 2012, 10:26 AM |
|
|
Moderator
Group: Moderators
Posts: 2366
Member No.: 22158
Joined: 26-September 07
|
Well, I'm kind of paraphrasing in all of this for simplicity
DX50 is the generic fourcc, and divx, ffds, xvid would be the writing codecs fourcc
so ffds/DIVX would be a divx 5.0 type video stream, encoded using ffdshow
In vfw, the last one installed that understands the fourcc is the default (well, most of the time, kinda, sorta)
But you can ask the others if they understand it as well
So, in v1.9 vdub asked 'hey who decodes dx50' and the OS would say 'this guy here does'
In 1.10 it can do the same or, can say 'hey is ffds around to decode this?'
Then the pc can go 'nope, nothing installed with that name' and vdub will go 'ok, then who understands dx50?'
The 'default' all depends on what you installed, and in what order
Your default could be different to mine
The way to force a 'specific' decoder is from the extended options in the open video dialog
In this instance, I've never seen ffdshow fail to decode a divx like that before, and would suspect that it's a version that has a bug or is damaged in some way
Updating ffdshow might fix it
But on the other hand, if it's a damaged avi file, then each decoder can behave differently as a result of hitting bad data
Then, switching from one decoder to the another can help
--------------------
MultiAdjust JoinWav WavNormalize FFMPeg Input Plugin v1827 UnSharpMask
Windows7/8 Codec Chooser
All FccHandlers Stuff inc. Installers for acm codecs AAC, AC3, LameMp3 |
|
