LEADTOOLS Support
General
General Questions
Arguments in ReceiveProc equate to one byte per pixel?
This topic and its replies were posted before the current version of LEADTOOLS was released and may no longer be applicable.
#1
Posted
:
Tuesday, September 25, 2007 5:07:57 PM(UTC)
Groups: Registered
Posts: 3
I am using the ReceiveProc method in a callback filter:
Width = 352, Height = 240, Bitcount = 8, Size = 84480 (bytes). If my math is correct (352x240=84480), this equates to one byte per pixel. This is a high color video image, and I would think there would a minimum of one byte per channel, or a size of at least 337920 bytes. The resultant image's colors are quite flattened out. I am using the Microsoft MPEG-4 v2 filter. Could this be causing the size argument to be so small?
#2
Posted
:
Wednesday, September 26, 2007 1:13:59 AM(UTC)
Groups: Guests
Posts: 3,022
Was thanked: 2 time(s) in 2 post(s)
If the Bit Count parameter of
the callback filter's ReceiveProc is 8, this means the image is actually one
byte (8 bits) per pixel.
If you want to see how the
toolkit builds the filter graph internally, and which filters are used exactly,
by adding a call to our EditGraph() function after the filter graph has started
running. This could tell you how and where the image got converted from 24-bit
to 8-bit.
To see the graph, you'll need
the Microsoft DirectShow GraphEdit utility. If you don't have it, you can get
it from the following post on our forum:
http://support.leadtools.com/SupportPortal/cs/forums/3889/ShowPost.aspx#3889
LEADTOOLS Support
General
General Questions
Arguments in ReceiveProc equate to one byte per pixel?
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.