Re: OK, let's get something straight....
I can understand you being apathetic but we shouldn't let Samsung of the hook so easily. I don't think anyone here is under any illusion that Samsung developers are going to drop what there doing and start fixing, recompiling and bug hunting their previous firmwares. We're just highlighting the problem hopefully making enough of a noise and maybe, just maybe they'll fix it. Ultimately the ball is in their court and if they choose to ignore it they may end up losing loyal or potential customers. Lets not forget they have aspirations to be in the pro market so forging a good relationship with their customers is important.
Now to the problem itself, as I commented on Paul's blog regarding gstreamer / openmax I believe after reading enough and checking the changes in the sourcecode (commits) and comparing it with the Tizen version that it won't be an easy fix. The 0.10 (libgstomx) versions of the libraries had problems with changing the profile level and setting the target-bitrate and control-rate, this version of the library is what we have and most probably why we are stuck with baseline. Of course this has been fixed in the newer versions, but the API has changed and that may mean Samsung rewriting part of their closed source apps, upgrading other libraries they are linked against and then testing and bug hunting. For cameras that they now conisder obselete it's simply not worth their time and effort.
I of course hope that I'm wrong and it can be easily fixed... we can but hope
P.S you are correct the NX2000/300/30 were the first Tizen cameras. They haven't released the source of the NX3000 yet but I would say it has a newer version of the OS.