What other settings are you using? With only those the ARM and x86
code produce identical results.
--
- johann koenig
google
libvpx has the notion of "speed" settings. A lower speed setting will
take longer to encode, but give better performance. For realtime
encoding on devices we usually aim for a speed setting of 4 or above.
Did you set this?
Did you use --enable-realtime only for the ARM?
Poor is a subjective term and hard to determine what could be going on
with your setup. You could try setting --cpu-used=n where n is a
number between -1 and -16 while encoding on the pc and see if there is
a matching quality to what you are seeing for the ARM encode.
(Setting a negative number holds the encode to that number throughout
the process. If you set it to a positive number it can adapt to the
cpu load and go higher/lower, which will make your encode not
deterministic).
Are you comparing the Android encode with a vpxenc encode? Is there
the possibility that you missed setting up some of the parameters that
vpxenc sets up? Or is your program cross platform and you are running
the same c code on both?
> --
> You received this message because you are subscribed to the Google Groups "WebM Discussion" group.
> To post to this group, send email to webm-d...@webmproject.org.
> To unsubscribe from this group, send email to webm-discuss...@webmproject.org.
> For more options, visit this group at http://groups.google.com/a/webmproject.org/group/webm-discuss/?hl=en.
>
yes. i have enabled it even on x86 platform too.
On Jan 19, 3:00 pm, Attila Nagy <attilan...@google.com> wrote:
> do you have CONFIG_REALTIME_ONLY as 1 in x86 too?
previously i have tried that too. i have also checked by enabling the
> on armv7 you want also
> #define HAVE_ARMV5TE 1
> #define HAVE_ARMV6 1
>
above macros and didn't get the desired decoded video quality.
To post to this group, send email to webm-d...@webmproject.org.
To unsubscribe from this group, send email to webm-discuss...@webmproject.org.
Are you running on a device or in the emulator?
I don't know what your initialization code does. You can configure
and build the examples, copy vpxenc to the phone and run it from there
with the same parameters as on the pc to check for bit exactness.
Link against that lib in your Android project.
But first, please clone a new libvpx tree in a clean directory and
start over from there. Editing source files because of a mismatched
ABI sounds like a problem with the source tree that needs to be solved
first.