search

google-code-export / webm

Automatically exported from code.google.com/p/webm
1 stars 0 forks source link

Attempted to divide by zero error then I'm trying to connect VP8 Encoder input pin #187

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Created DirectShow Editing Services graph, with AvgTimePerFrame = 0 (I don't 
know why it's happen, DES-thing) and real frame rate is 25 fps.
2. Connected our filter to get YUY2 output.
3. Trying to connect VP8 filter input pin and got the following exception - 
"Attempted to divide by zero.".

What is the expected output? What do you see instead?

No output, pin no connected, app crash.

What version are you using? On what Windows version?

Latest version from webmproject.org, Windows 7 x64.

Please provide any additional information below.

This problem never happen in DirectShow graph from webcam and correct 
AvgTimePerFrame value, so, I think it's connected only with AvgTimePerFrame = 
0. 

I'm tried WMV and AVI output (MJPEG Compressor for video) in the same DES graph 
with AvgTimePerFrame = 0, all was ok. Time stamps is correct.

Thank you!

Original issue reported on code.google.com by roman.minyaylov@gmail.com on 24 Sep 2010 at 8:36

GoogleCodeExporter commented 9 years ago

Original comment by matthewj...@google.com on 4 Dec 2010 at 12:23

GoogleCodeExporter commented 9 years ago 
Matt I think this might be a duplicate of 
http://code.google.com/p/webm/issues/detail?id=238.

Original comment by fgalli...@google.com on 6 Dec 2010 at 2:30

GoogleCodeExporter commented 9 years ago 
We do have a check for 0 when the upstream filter attempts to connect to the 
encoder's input pin, so I'm not sure yet where the exception is coming from.  
(To the OP: was there any assertion information attached to the output you 
observed, such as an assertion message and/or line number?)

Original comment by matthewj...@google.com on 6 Dec 2010 at 6:05

GoogleCodeExporter commented 9 years ago 
Sorry, just exception "Divide by zero". But, as I told, if input frame rate 
(AvgTimePerFrame) is ok - no problems, encoding is correct. Only if 
AvgTimePerFrame is 0 this exception happen.

Original comment by roman.minyaylov@gmail.com on 6 Dec 2010 at 7:32

GoogleCodeExporter commented 9 years ago 
We need to duplicate the exception.  One way is to build a graph, but using 
ConnectDirect and specify an explicit media type, with AvgTimePerFrame as 0.  
QueryAccept should reject the connection, so I don't know why a 0 value there 
would cause the app to crash.

Original comment by matthewj...@google.com on 3 Feb 2012 at 10:39

GoogleCodeExporter commented 9 years ago

Original comment by albe...@google.com on 8 Mar 2012 at 12:08