[Ssc-dev] EXIF support WAS: Tomorrow's Meeting - Cancelled?

[Andrew Senior]

There might be something reasonable now. I really didn't like exiflib
(clunky C) and started writing my own C++ code after a while. I don't think
it was very complete but it is an option.
I didn't see any android SDK support for low-level JPEG, so I think we might
also need a JPEG library.

Andrew

On Tue, Jan 11, 2011 at 12:04 PM, Hans-Christoph Steiner <hans at at.or.at>wrote:

>
> Since we are already going to be including some NDK libraries, it shouldn't
> be too hard to also include an EXIF library if there is a better one that
> you know of.
>
> .hc
>
> On Jan 10, 2011, at 9:53 PM, Andrew Senior wrote:
>
> I also just looked into the Exif support:
> http://developer.android.com/reference/android/media/ExifInterface.html
> It seems pretty limited. but might be enough to remove the sensitive
> metadata that most phones put in: GPS, date_time, make and model. I guess
> we can't rule out some phone adding a "This photo was written by phone IMEI
> xxxx" in a comment without building the Exif data ourselves. I actually
> wanted to make an Exif metadata editing app, to tag photos, (comment /
> location/ etc.) but it looks like that would require dedicated code.
>
> Andrew
>
> On Mon, Jan 10, 2011 at 9:27 PM, Andrew Senior <aws at andrewsenior.com>wrote:
>
>> Sorry to hear that. Hope you can get it fixed.
>>
>> Here's my update:
>>
>> I got OpenCV for Android working (via windows), - just the cvcamera sample
>> app. (After setting various environment variables and installing JDK & ant,
>> updating eclipse, android SDK, renewing my debug key and editing the build
>> file:
>> http://code.google.com/p/android/issues/detail?id=13024 )
>>
>> I got Google clearance to contribute to the project.
>>
>> I was wondering what using the NDK+OpenCV would do to code portability- is
>> it easy to cover all architectures? And still distribute via the market? A
>> first attempt didn't install on my Evo, even though I read it has the
>> Snapdragon like the Nexus One.
>>
>> http://developer.android.com/sdk/ndk/overview.html says the following,
>> but I'm not sure what coverage that implies:
>>
>> The latest release of the NDK supports these ARM instruction sets:
>>
>>    - ARMv5TE (including Thumb-1 instructions)
>>    - ARMv7-A (including Thumb-2 and VFPv3-D16 instructions, with optional
>>    support for NEON/VFPv3-D32 instructions)
>>
>> Future releases of the NDK will also support:
>>
>>    - x86 instructions (see CPU-ARCH-ABIS.HTML for more information)
>>
>> ARMv5TE machine code will run on all ARM-based Android devices. ARMv7-A
>> will run only on devices such as the Verizon Droid or Google Nexus One that
>> have a compatible CPU. The main difference between the two instruction sets
>> is that ARMv7-A supports hardware FPU, Thumb-2, and NEON instructions. You
>> can target either or both of the instruction sets — ARMv5TE is the default,
>> but switching to ARMv7-A is as easy as adding a single line to the
>> application's Application.mk file, without needing to change anything
>> else in the file. You can also build for both architectures at the same time
>> and have everything stored in the final .apk. Complete information is
>> provided in the CPU-ARCH-ABIS.HTML in the NDK package.
>>
>> Andrew
>>
>>
>> On Mon, Jan 10, 2011 at 8:18 PM, Shawn Van Every <
>> vanevery at walking-productions.com> wrote:
>>
>>> Hi Folks,
>>>
>>> Unfortunately, due to a dental emergency (ouch!!!!) it looks like I won't
>>> be able to meet with you all tomorrow.  Since Nathan is gone as well this
>>> week, it probably makes sense to cancel it.
>>>
>>> I'll try to send out an update at some point tomorrow, perhaps we can all
>>> converse a bit virtually.
>>>
>>> Hope all is well.
>>>
>>> Best,
>>> shawn
>>>
>>> _______________________________________________
>>> Ssc-dev mailing list
>>>
>>> Post: Ssc-dev at lists.mayfirst.org
>>> List info: https://lists.mayfirst.org/mailman/listinfo/ssc-dev
>>>
>>> To Unsubscribe
>>>        Send email to:  Ssc-dev-unsubscribe at lists.mayfirst.org
>>>        Or visit:
>>> https://lists.mayfirst.org/mailman/options/ssc-dev/aws%40andrewsenior.com
>>>
>>> You are subscribed as: aws at andrewsenior.com
>>>
>>
>>
> _______________________________________________
> Ssc-dev mailing list
>
> Post: Ssc-dev at lists.mayfirst.org
> List info: https://lists.mayfirst.org/mailman/listinfo/ssc-dev
>
> To Unsubscribe
>        Send email to:  Ssc-dev-unsubscribe at lists.mayfirst.org
>        Or visit:
> https://lists.mayfirst.org/mailman/options/ssc-dev/hans%40at.or.at
>
> You are subscribed as: hans at at.or.at
>
>
>
>
>
> ----------------------------------------------------------------------------
>
> "Making boring techno music is really easy with modern tools, but with live
> coding, boring techno is much harder." - Chris McCormick
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mayfirst.org/mailman/private/ssc-dev/attachments/20110111/35490653/attachment.htm>