MPEG-4 vendor plugin data buffers

by HV » Wed, 16 Jun 2010 19:37:20 GMT

Sponsored Links
 Hi Folks,

 I have completed the plugin part and calling my decoder library using
the incoming buffers, but I have run into a strange issue. The 1st
buffer starts off OK with the VOL start code and the associated start
code. But after the VOL data ends, I was expecting the VOP start code/
data to start, but I see some junk (I've compared against the actual
bit-stream). Any idea why this is so?

 However, my decoder is able to decipher the VOL data correctly and
then I start reading the next buffer which indeed starts off with the
VOP header but the data does NOT point to the 1st I-Frame at all. It's
way off somewhere (again compared against the input file). I'm
guessing this problem will go away if I can fix the 1st issue (no VOP
start code following the VOL data).

 Also, I see that all the buffers (I get 3 calls into EmptyThisBuffer)
are of the same size (80 bytes). Would appreciate any feedback

Best regards


MPEG-4 vendor plugin data buffers

by HV » Wed, 16 Jun 2010 22:11:30 GMT

 My bad on the size, I was using nSize instead of nFilledLen and hence
was always getting 80. With that change, I see that to being with i
get 32 bytes and then there is a huge chunk coming in which is indeed
the VOP data, but it is still not associated with the 1st I-frame!!

Next I took out my .cfg file and let the PV software based decoder
take over & printed the 1st few bytes of the input data. To my
surprise, I see the same data there as well. Is the MPEG-4 demux is
manipulating data here??



Sponsored Links

MPEG-4 vendor plugin data buffers

by HV » Thu, 17 Jun 2010 16:06:43 GMT

 I checked with multiple clips and see the same behavior (the PV s/w
decoder does NOT get the 1st I-Frame). That said, what I'm confused
about is, how is it able to display the 1st I-Frame in the thumbnail
(within gallery)??



Other Threads

1. Best practice for changing min SDK

I have a sizable install base already on some apps with Android 1.5
set as the minimum version.  I want to update the apps to take
advantage of some of the newer features offered in Android 2.0 and
greater. What is the best way forward so I don't break things for my
current 1.5 and 1.6 users?

If I simply update the application with a new min SDK version, will
1.5 and 1.6 users be prompted to uninstall? Or will they just not see
the update?

What about future development that I want to apply for everyone, say a
bugfix. Will I have painted myself into a corner?

Another solution would be to fork and create a new app for 2.0 users,
but that is undesirable for several reasons.

This must be a somewhat common problem. Have you seen any good ways to
handle it?



2. How to create a view?

I was wonder if somebody knows where to find source code of the radio
button? i basically want to create a radiobutton class with like one
extra variable a long so i figure i have to make a class that derives
off of radiobutton but i kinda want to see example of that done by
finding a source code fo the class radiobutton or any links to
something doing this deriving there own class base on original views
in the library


3. DNS records

4. Pindah mp3

5. Beli Game dari Web Gameloft

6. galaxy 2

7. Rooting htc hero