Free DSP codecs!!!

-
Wow.. a blast of new sites for omapzoom..

And then I see this on the new omapzoom google groups!!!
* MPEG4 Video Dec
* H263 Video Dec
* JPEG Dec
* JPEG Enc
* AAC Dec
https://gforge.ti.com/gf/project/openmax/frs/?action=index
And you also now have a wiki for omap

Comments

Unknown said…
It depends on your definition of "free". I have to accept a license agreement that I didn't bother to read but I'm pretty sure it will prevent me from putting these in any kind of rootfs and distribute it for development purposes.
6:50 AM CDT
jayabharath said…
FelipeC & Nishant,

It's not 'free' as in free speech. It's free beer :)

I am not a legal expert - but as far as I see it does not prevent using these codecs in TI manufactured devices for development purposes.

The license itself is liberal the way I see it.

Here is a excerpt from the text" Object Code License.
TI hereby grants to you a limited, non-exclusive license to reproduce and use the Licensed Materials provided to you in object code format (the "Object Code Licensed Materials") and to distribute an unlimited number of object or executable copies of such Object Code Licensed Materials, provided that if the Object Code Licensed Materials are provided to you in object code format only, such Object Code Licensed Materials, and any object or executable copies thereof, are used solely and exclusively on devices manufactured by or for TI."
5:27 PM CDT
Nishanth Menon said…
Jay, thanks for your comments on this. on an related note - would beagleboard and zoom devices fall in this category? where do I look to see if I can actually use these codecs? does this mean that if I use this on overo earth (gumstix), I will get sued?
6:29 AM CDT
Chris Pearson said…
As long as the device uses a TI part, which the Overo Earth of course does, you are protected. We have no issues with distribution in binary form for development purposes. If you want to deploy these codecs in a production environment you should get a production license, which would also grant you support.

Since the codecs are C64x+ code, they are of little use on a non TI part.

Let me know if you have more questions
9:34 AM CDT
Nishanth Menon said…
I get this mostly. but i think this discussion should be shifted out to Open Max dsicussion forum or a new wiki page of it's own(I think the DSP codecs deserve thier own wikis..)
11:08 AM CDT
jayabharath said…
Added summary of these comments to http://omappedia.org/wiki/Talk:OpenMAX_Project

Please feel free to make separate wiki pages on OMAPpedia as you see appropriate.
9:25 AM CDT
Unknown said…
I tried these codecs; they don't work on beagleboard nor N900 with any version of the dsp-bridge. That's a shocker.
3:44 PM CST
Nishanth Menon said…
I'd think this was more inline with Android release... unfortunately..
4:05 PM CST
Post a Comment

Popular posts from this blog

simpler alternative to minicom

-
Tired of setting up and switching ports in minicom and want something simple? welcome to picocom setup a script such as ~/bin/ttyUSB0 picocom -f n -p n -b 115200 -i -r -l /dev/ttyUSB0 and next time, just run ttyUSB0 and viola u have a terminal.. ctrl+a followed by ctrl+q quits..
Read more

Quick and Dirty userspace testing of regulator with virtual consumer

-
Writing a driver for a new regulator is usually fun, until you need to test the darned thing. Many of the users of the regulator is probably not yet ready in an development environment and need to test cant wait. I had recently a similar situation and found CONFIG_REGULATOR_VIRTUAL_CONSUMER You'd probably register and provide and regulator supply, but without a driver using it in a controlled environment (read shell script or so), it is hard to poke holes completely into your driver. Steps are rather simple. Assumption - you already have a regulator registered in the system and you are aware of the regulator name - You can also figure out it's name by the following (an example from 3.9-rc8 on Beagle-XM): # head /sys/class/regulator/*/name ==> /sys/class/regulator/regulator.0/name /sys/class/regulator/regulator.1/name /sys/class/regulator/regulator.2/name /sys/class/regulator/regulator.3/name /sys/class/regulator/regulator.4/name /sys/class/regulator/regulator.5/...
Read more

Setting up Email forwarding System for GIT

-
Image
The post is a derivative of the omapzoom wiki page . Disclaimer: my mastery of the wiki tags are dismal.. apologies... some day i hope to have time to post it here Many new developers have been stumped when they need to use git-send-email in corporate environment – usually, if not as a norm, ms exchange servers form the backbone of such an email server system. This page was written based on one of such requirements. To get started, we shall consider common scenarios: a) Setting up a mail forwarding system with postfix on ubuntu b) Setting up a mail forwarding system on a fedora machine c) Using msmtp for using gmail a. to send a patch using a gmail ID b. to send a patch using your corporate ID but through gmail Postfix on Ubuntu – mail forwarding For setting up postfix, you need: a) A mail relay server which will allow your machine to talk to it -> speak to your IT representatives/ other developers sitting next to you b) Super user privileges on the machine you are working on. Step...
Read more