About the SetFrameRate at Android Camera Input MIO

by ever » Tue, 14 Apr 2009 03:47:39 GMT

Sponsored Links
SetFrameRate at Camera Input MIO does not negotiate with the camera
driver for the preview framerate, it just postpone the Camera Input
MIO to receive video frame from buffer queue when recording is
The preview framerate could be different from what we ask for
recording (encoding), doesnt this condition cause any problem? Ex.
Camera client sends preview frame to buffer for Camera Input MIO at 30
fps, but the app asks recording at 20 fps.

About the SetFrameRate at Android Camera Input MIO

by Han Chao » Tue, 14 Apr 2009 05:03:25 GMT

 Preview FrameRate and Recording are different conception.
Somethimg Recording FrameRate can't reach the setting , it may do as
much as possible.

Camera Input MIO should be the preview FrameRate.

Sponsored Links

About the SetFrameRate at Android Camera Input MIO

by Han Chao » Tue, 14 Apr 2009 05:04:29 GMT

 We have discussed it .
Some setting of preview and recording may be separated.

About the SetFrameRate at Android Camera Input MIO

by ever » Tue, 14 Apr 2009 05:22:48 GMT

 Hi Han Chao,
could you tell me more detail about the framerate between preview,
mio, encoder and composer node.
thanks a lot.


Other Threads

1. Rotation Redux (resolved!)

Thanks to a clever colleague here who suggested this.

Since sub-activities inherit any android:screenOrientation set on 
their launching parent in the manifest, if you lock the parent one 
way but want the user to be able to control the orientation of the 
child, you need an explicit constant for that. Lo! and behold! 
ActivityInfo has one, "user" -- so:


So "portrait," "landscape," "user," and "sensor" give pretty good control

I also see "nosensor" -- which I assume you need if you have 
previously set a parent to "sensor."  ? or?

Finally, there is "behind" -- does anyone know what a "behind 
orientation" would be" ?

-- Ward


Okay, I think I know the answer as to what can cause an activity not to rotate.

Every activity I wanted to rotate was started with 
startActivityForResult() (i.e. it was a sub-activity). It appears 
sub-activities "inherit" the "android:screenOrientation" of their 
parent in the manifest.

In my case, I have portrait main screens, launching landscape 
sub-activities that contain forms for keyboard entry. If I set


on the main screen, the sub-activities will not rotate, unless I 
_explicitly_ add android:screenOrientation="landscape" to them. Which 
is fine, except they start out rotated, which is not necessarily what 
a user expects.

I suppose I could launch my data entry screens as first-class 
activities (using startActivity() instead of 
startActivityForResult()) and pass the results back out-of-band and 
manually restart the parent, but it sure isn't as pretty as using the 
built-in result machinery.

(Or, yes, I could become more "one" with Android and do two sets of 
layouts and put the user in absolute control, but that's a lot of 
work and I am so very lazy...)

-- Ward


Hello All:

I asked this before and did not get an answer, so let me try again, simpler:

On the G1...

What can cause an activity to NOT rotate to landscape when the phone 
is opened? (I want it to rotate.)

No android:screenOrientation is set, and the activity is destroyed 
and recreated, but the new layout is still portrait.


-- Ward


2. Very Large Views

Let's say I use a ScrollView to pan over a very large view. The large
view draws itself dynamically in onDraw().

Is there a practical limit to the size of the view? That is, are view
contents cached or buffer-backed and can I turn that off?

3. How to run more fast on Eclipse

4. ANN: Android Training, Big Nerd Ranch (Atlanta, GA), March 16-20

5. Android Surfaces and Locking Questions.

6. Are you localizing an app? Do you want to be?

7. Problem with FPS using Opengl es on G1