Help for the questions on adding avi parser node to opencore framework in Android OS

by Jing Deng » Mon, 21 Sep 2009 01:12:54 GMT


Sponsored Links
 Hey everyone:

It's very embarrassed and so sorry to disturb you all for some
problems on Android developping.

I am working on adding avi parser node to opencore framework using avi
parser under the following dir (/fileformats/avi/parser) in Android-
cup-cake.
The problems that beyond my solutions are as followed :


1. In avi parser node(which is my code) I need retrieve codec specific
data from avi parser through calling GetCodecSpecificData()function
(which is under /fileformats/avi/parser in Android-cup-cake).But all
the codec specific data is stored in STRD chunk which is an optional
chunk in avi file. So now the question is the player engine(opencore/
engines/player) need to codec specific data (will be used in dec
node),but maybe the avi file don't have the data.Can I use other
information instead of codec specific data.Would you like give me some
suggestion.And in mp4 files it return the VOL header,what is the
format of it ,and can i generate the structure by myself.

Thanks in any advance.  Best regards .

Qiao

--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Other Threads

1. What is the recommended resolution/aspect ratio for android graphics

Hi All, I'm trying to write an application that will work well on all
screen sizes, for that I have my graphic designer produce images that
are in the requested dpis for each directory (Low density (120), ldpi,
Medium density (160), mdpi, High density (240), hdpi, Extra high
density (320), xhdpi) however, they want to know at which resolution
and aspect ratio each image should be, after looking around the
android documenation, namely: 1)http://developer.android.com/guide/
topics/resources/providing-resources.html#AlternativeResources
2)http://developer.android.com/guide/practices/screens_support.html I
came up with the following information: It is not exact that android
supports 3 screen sizes, android is an OS that can run virtually on
any screen size but there are some screen sizes that are more common
than others, these are demonstrated in the table below (taken from
http://developer.android.com/guide/practices/screens_support.html)

Table 1. Screen sizes and densities of emulator skins included in the
Android SDK. Low density (120), ldpi Medium density (160), mdpi High
density (240), hdpi Extra high density (320), xhdpi Small screen QVGA
(240x320)
Normal screen WQVGA400 (240x400) WQVGA432 (240x432) HVGA (320x480)
WVGA800 (480x800) WVGA854 (480x854)
Large screen WVGA800* (480x800) WVGA854* (480x854)
Extra Large screen

It worth noting here that even though it seems that there is no
correlation between these screen sizes, there is a 3:4:6 scaling ratio
between the three densities, so a 9x9 bitmap in ldpi is 12x12 in mdpi
and 18x18 in hdpi (see
http://developer.android.com/guide/topics/resources/providing-resources.html#AlternativeResources).

We can see some more information on what the screen sizes mean here:

Screen size small: Screens based on the space available on a low-
density QVGA screen. Considering a portrait HVGA display, this has the
same available width but less heightt is 3:4 vs. HVGA's 2:3 aspect
ratio. Examples are QVGA low density and VGA high density. normal:
Screens based on the traditional medium-density HVGA screen. A screen
is considered to be normal if it is at least this size (independent of
density) and not larger. Examples of such screens a WQVGA low density,
HVGA medium density, WVGA high density. large: Screens based on the
space available on a medium-density VGA screen. Such a screen has
significantly more available space in both width and height than an
HVGA display. Examples are VGA and WVGA medium density screens. xlarge: Screens that are considerably larger than the traditional
medium-density HVGA screen. In most cases, devices with extra large
screens would be too large to carry in a pocket and would most likely
be tablet-style devices. Added in API Level 9.

We can also support specific aspect ratios, as defined here:

Screen aspect long: Long screens, such as WQVGA, WVGA, FWVGA notlong: Not long screens, such as QVGA, HVGA, and VGA

-- All of this however, is not enough to answer the simple question of
what the resolution should be on those images - can they all be cut
from the same high res image or should they be re-done for each dpi
since the aspect ratio is different?
 Thanks!
P.s. To clarify, I'm talking about images that should take up the
entire screen - images such as backgrounds etc, and not just regular
images

-- 

2. Populate Spinner from database

How to populate spinner from database?

Following code is not working in my case.

This method shows database entries in spinner


private void fillData() {
     spin_pro= (Spinner)findViewById(R.id.spin_profile);
        Cursor profilesCursor = mDbHelper.retrieveAllProfiles();
        startManagingCursor(profilesCursor);


        String[] from = new String[]{DBAdapter.KEY_PRONAME};

        int[] to = new int[]{R.id.tvDBViewRow};

        SimpleCursorAdapter profile =
            new SimpleCursorAdapter(this, R.layout.profile_list,
profilesCursor, from, to);

        spin_pro.setAdapter(profile);
    }


And this is database class to retrieve data

    public Cursor retrieveAllProfiles()
    {

        return mDb.query(DATABASE_TABLE1, new String[] {KEY_PROID,
                    KEY_PRONAME, KEY_PASSWORD}, null, null, null, null,
null);
    }

-- 

3. Canvas vs OpenGl drawline speeds

4. Thickness strikethrough

5. How to setImageViewUri in Widget using getFileStreamPath()?

6. Receiving phone calls regarding Android Market billing issues?

7. Canceled orders and credit cards