Howdy folks
the process for creating blueprints / work items and specifications is
simple and you can follow the instructions in
[HOWTO for Blueprints]
https://wiki.linaro.org/Resources/HowTo/BlueprintSpecFAQ
to guide you. We can do a session of creating a sample blueprint and its
engineering blueprints + specifications on Thursday's meeting if Kurt
also agrees.
The specifications for Multimedia group can live under:
[Multimedia blueprint specs]
https://wiki.linaro.org/WorkingGroups/Middleware/Multimedia/Specs/1111/
Now, if you go in that area there is nothing, but the point is to use
that wiki area so that all our specs are created under the same roof.
All you need to do when writing your blueprint specification is to type
your URL in your browser, indicating also the name of the spec you are
writing. For example (using a hypothetical name for a specification)
https://wiki.linaro.org/WorkingGroups/Middleware/Multimedia/Specs/1111/engr…
Then you can create your specification in that empty wiki page following
the template given here:
[Specification template] https://wiki.linaro.org/Process/SpecTemplate
For example here is a real specification written in the Graphics WG:
https://wiki.linaro.org/WorkingGroups/Middleware/Graphics/Specs/1111/engr-b…
The naming convention chosen for the Graphics group's engineering
blueprints was "engr-"+"area of interest"+"some acronym to indicate the
functionality". To simplify life Graphics team chose to name their
specifications (in the wiki) and their engineering blueprints (in
Launchpad) with the same names.
Once you have created specifications they can be used to set the URL of
the Launchpad blueprints as per the HowTo instructions (see URL above).
I hope this all makes sense. Please do not hesitate to ask any questions
you may have.
Many thanks,
--
Ilias Biris,
Aallonkohina 2D 19, 02320 Espoo, Finland
Tel: +358 50 4839608 (mobile)
Email: ilias dot biris at linaro dot org
Skype: ilias_biris
Hello folks
with the mini summit now done, this is just a friendly reminder: we
should all be making arrangements for the Cambridge sprint the first
week of August (1st - 5th). There are a few things involved, most of
which should be obvious and details of which can be found here:
https://wiki.linaro.org/Events/2011-08-LDS
In short, we all need to be looking into:
- Event Registration
- Travel/airline tickets
- Hotel (see info on the package deal for Linaro)
And some may need to look into (I cannot directly help with whether or
not this affects you personally):
- VISA
This takes 2-3 months for some, so get on it NOW. At least let Arwen
Donaghey (arwen.donaghey(a)linaro.org) know that you need help (letters
of introduction/justification/whatever) acquiring a Visa so we can
track what needs to happen.
Also, some of the member companies are asking for justification for
why their assignees need to go the event. As done for other work
groups this can be turned around and the answer should be: "if you
don't think you need to go, then you need to justify why it isn't
important for you to go". I think that judging by the way the mini
summit went we are all vital to the success of the activities in
Multimedia and we should all take every opportunity we can to do
plenty with all of the face to face access we get with each other as
well as other teams in Linaro and the community (we will be inviting
some folks to join us for the event).
I can start by confirming that I have registered, have airline
tickets, a booking at the Belfry and require no Visa to travel to the
UK. All I need is my train ticket (which I will buy at Kings-X when I
arrive). I will need to leave a bit earlier from the event on Friday
the 05th, as I have to be in Helsinki on the 06th, and my flight
leaves from LHR at 18:30 on Friday evening.
BR,
*************************************
Ilias Biris,
Aallonkohina 2D 19, 02320 Espoo, Finland
Tel: +358 50 4839608 (mobile)
Email: ilias dot biris at linaro dot org
Skype: ilias_biris
*************************************
Hello!
I have started collecting the actions from the mini summit into our
technical requirement (TR) blueprints in Launchpad. I created 4
already check the links below:
https://blueprints.launchpad.net/linaro-multimedia-wg/+spec/tr-linaro-multi…https://blueprints.launchpad.net/linaro-multimedia-wg/+spec/tr-linaro-multi…https://blueprints.launchpad.net/linaro-multimedia-wg/+spec/tr-linaro-multi…https://blueprints.launchpad.net/linaro-multimedia-wg/+spec/tr-linaro-multi…
To ease any immediate worries - relax folks! These are not yet
connected anywhere, so they do not show up in any status reports for
the cycle. However they should be used as handles to register any work
involved, including postponing or deferrals and track requirements and
dependencies. So they are really placeholders for now - whiteboards
for the work to come. This means also that the assignees will probably
be reconfigured once we plan the work properly.
More will come based on the work to be done still in the mini summit.
I will be posting the new blueprints as soon as they are ready.
Kurt one question: the parsers work as indicated in
http://pad.ubuntu.com/g40gcIob12 - does that merit a separate
blueprint or can the work be tracked in the vendor survey associated
with the openmax blueprint?
BR,
*************************************
Ilias Biris,
Aallonkohina 2D 19, 02320 Espoo, Finland
Tel: +358 50 4839608 (mobile)
Email: ilias dot biris at linaro dot org
Skype: ilias_biris
*************************************
Please check the status report in th wiki
https://wiki.linaro.org/WorkingGroups/Middleware/Multimedia/WeeklyReport
for more information and links.
== Team Highlights ==
11.05 release: libjpeg-turbo and smartt released. Smartt not a tarball
yet but we may get some help to get this released via a launchpad
project for this work. Need to get the individual patches from the
team sent out, in order to get feedback. Sending to patches(a)linaro.org
in order to get our patches counted to the Linaro metrics (this is
important for libjpeg-turbo as there is no libjpeg-turbo wide
community for now - we need to investigate about the upstreaming of
jpeg-turbo). Patches are right now being added to git.linaro.org.
Getting ready for the mini-summit, team has been asked to look through
the summit topics and give feedback.
Those who will not be able to attend in person, should try to get on
the conference line, and check the recorded meeting to review what was
discussed.
Suggestions for topics not covered in the agenda for the mini summit
- obviously OMX vs not-OMX vs something else
- gstreamer (0.11 or 1.0) in order to address some of the
challenges that we and other vendors have seen. Parsers
- Android work related to OMX work and the consolidation work that
the group is targeting could also be another point for the mini-summit
discussion - Kurt to discuss with Zach also on the Android pain points
and what Android folks would need to have fixed.
- Related to the Memory Management activities - 0-copy is the area
of interest in Multimedia. We will review the list of work items in
the mini-summit. As for the impact of the work to other components -
eg EGL API for video related images/surfaces may affect userspace
gstreamer APIs (or other multimedia framework) - to what extent
remains to be seen
Validation tasks (Mandeep) - looking at some new techniques for
analyzing code during optimization.
Worked on the gst-openmax with video raw format mapping
Putting together some documentation notes for the interface issues with OMX.
Uploaded the multimedia test content for 5 codecs (as indicated in
meeting minutes from 31.05.2011) - is the list of video codecs
sufficient or do we need more?
BR,
*************************************
Ilias Biris,
Aallonkohina 2D 19, 02320 Espoo, Finland
Tel: +358 50 4839608 (mobile)
Email: ilias dot biris at linaro dot org
Skype: ilias_biris
*************************************
Hi everyone,
I’m Home Software Enabling engineer of ARM Shanghai and working on multimedia. I have paid attention to Linaro multimedia projects from wiki and mail list for several months.
I found that Linaro 1105 released and didn't include multimedia projects. Is the schedule of multimedia project changed?
Best Regards,
Fang Bao
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
All,
In context of a vc1 parser, I've posted the Annex L section from the
vc-1 spec. This describes the format that is used by TI vc-1 decoder
for simple and main profile.
https://docs.google.com/a/linaro.org/viewer?a=v&pid=explorer&chrome=true&sr…
Advanced profile is something different... just a start code. I'm not
entirely sure offhand the name for the format used for
advanced-profile, but it is different from simple/main profile.
Also, here is the relevant code from the GStreamer plugin for TI VC-1 decoder:
https://github.com/robclark/gst-ducati/blob/master/src/gstducativc1dec.c#L1…
We need to somehow:
a) identify if there are any other possible formats that decoders expect
b) choose caps field name(s) and values to uniquely identify the
different formats, so a vc1parser element could do the necessary
conversion
BR,
-R
hi all,
There're several issues in amr decoder of bellagio components, I list
below. And the patch codes can be found at
http://git.linaro.org/gitweb?p=people/weifeng/bellagio_components.git;a=sho…
1. components name issues -- patched
In bellagio components, amr decoder is named as
OMX.st.audio_decoder.amr for both narrow band and wide band, while in
gstomx, seperate OMX.st.audio_decoder.amrnb and OMX.st.audio_decoder.amrwb
is used.
2. amrwbdec not implemented correctly -- patched
In fact, there's no way to actually call ffmpeg for amrwb decoder in
original code.
3. input buffer more than a frame is not handled correctly -- patched
After qtdemux, the input buffer for decode maybe contain several
frames, but original codes only decode first frame and drop the remainder.
4. sound discontinous -- not resolved
Although all frames are decoded correctly, the sound played is still
not continuous.
Regards,
Wei.Feng
