When you work with GSM/cellular systems, the definite resource are the specifications. They were originally released by ETSI, later by 3GPP. Special notice TSG CT meeting #83 approved in principle the withdrawal of TS from Releases 11, 12 and The rationale will be prepared. (3GPP TS version Release 12) print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
|Language:||English, Spanish, Dutch|
|Distribution:||Free* [*Sign up for free]|
All 3GPP specifications are publicly available on the 3GPP server. This page provides guidance as to how to find the specifications you are seeking. If you are . 3GPP. 3GPP TS V (). Release 9. 2. Keywords. UMTS, GSM, radio, layer 3, stage 3, network,. LTE. 3GPP. Postal address. The present document has been developed within the 3rd Generation Partnership Project (3GPPTM) and may be further elaborated for the purposes of 3GPP.
The last four years have not been easy for our multimedia community - both contributors and users. We should now look to the future, try to find solutions to these issues, and to have reconciliation between the forks, which have split the community for so long.
Unfortunately, much of the disagreement has taken place in inappropriate venues so far, which has made finding common ground and solutions difficult. We aim to discuss this in our communities online over the coming weeks, and in person at the VideoLAN Developer Days in Paris in September: a neutral venue for the entire open source multimedia community.
The FFmpeg project.
After graciously hosting our projects FFmpeg , MPlayer and rtmpdump for 4 years, Arpi our hoster has informed us that we have to secure a new host somewhere else immediately. If you want to host an open source project, please let us know, either on ffmpeg-devel mailing list or irc.
March 16, , FFmpeg 2.
It contains all features and bugfixes of the git master branch from the 6th March. Please see the Release Notes for a list of note-worthy changes.
If you wish to participate as a student see our project ideas page. You can already get in contact with mentors and start working on qualification tasks. Registration at Google for students will open March 16th. Good luck! The event will take place on 21st and 22nd of March.
More information can be found here We demonstrate usage of FFmpeg, answer your questions and listen to your problems and wishes. If you have media files that cannot be processed correctly with FFmpeg, be sure to have a sample with you so we can have a look! You can read the details here. The workshop is targeted at FFmpeg beginners. First the basics of multimedia will be covered. Thereafter you will learn how to use that knowledge and the FFmpeg CLI tools to analyse and process media files.
The workshop is in German language only and prior registration is necessary.
The workshop will be on Saturday starting at 10 o'clock. We are looking forward to meet you again!
December 5, , FFmpeg 2. A big thank-you to Andreas Cadhalpun and all the people that made it possible. It has been anything but simple. Unfortunately that was already the easy part of this news. The bad news is the packages probably won't migrate to Debian testing to be in the upcoming release codenamed jessie. Read the argumentation over at Debian. However things will come out in the end, we hope for your continued remarkable support!
We all know FFmpeg is used by the industry, but even while there are countless products building on our code, it is not at all common for companies to step up and help us out when needed. So a big thank-you to Samsung and the OPW program committee! If you are thinking on participating in OPW as an intern, please take a look at our OPW wiki page for some initial guidelines.
The page is still a work in progress, but there should be enough information there to get you started. If you, on the other hand, are thinking on sponsoring work on FFmpeg through the OPW program, please get in touch with us at opw ffmpeg.
With your help, we might be able to secure some extra intern spots for this round! September 15, , FFmpeg 2. August 20, , FFmpeg 2. Please see the changelog for more details. July 29, , Help us out securing our spot in OPW Following our previous post regarding our participation on this year's OPW Outreach Program for Women , we are now reaching out to our users both individuals and companies to help us gather the needed money to secure our spot in the program.
We need to put together 6K USD as a minimum but securing more funds would help us towards getting more than one intern. If you would like to donate by money transfer or by check, please get in touch by e-mail and we will get back to you with instructions. July 20, , New website The FFmpeg project is proud to announce a brand new version of the website made by db0. While this was initially motivated by the need for a larger menu, the whole website ended up being redesigned, and most pages got reworked to ease navigation.
We hope you'll enjoy browsing it.
July 17, , FFmpeg 2. The OPW aims to "Help women cis and trans and genderqueer to get involved in free and open source software". Part of the process requires securing funds to support at least one internship 6K USD , so if you were holding on your donation to FFmpeg, this is a great chance for you to come forward, get in touch and help both the project and a great initiative!
We have set up an email address you can use to contact us about donations and general inquires regarding our participation in the program. Hope to hear from you soon! June 29, , FFmpeg 2. They fix a security issue in the LZO implementation , as well as several other bugs. See the git log for details. The event will take place from 8th to 10th of May. Please note that this year's LinuxTag is at a different location closer to the city center.
More information about LinuxTag can be found here We are looking forward to see you in Berlin! The OpenSSL software library was updated on 7th of April, shortly after the vulnerability was publicly disclosed.
We have changed the private keys and certificates for all FFmpeg servers. The details were sent to the mailing lists by Alexander Strasser, who is part of the project server team.
Here is a link to the user mailing list archive. We encourage you to read up on "OpenSSL heartbleed". It is possible that login data for the issue tracker was exposed to people exploiting this security hole. You might want to change your password in the tracker and everywhere else you used that same password.
April 11, , FFmpeg 2. It contains bug fixes for Tickets , , , , and as well as several other fixes. March 24, , FFmpeg 2.
The event will take place on 15th and 16th of March. More information can be found here We invite you to visit us at our booth located in the Linux-Live area! There we will demonstrate usage of FFmpeg, answer your questions and listen to your problems and wishes. February 9, , trac. The affected server was taken offline and has been replaced and all software reinstalled. We believe that the original compromise happened to a server, unrelated to FFmpeg and MPlayer, several months ago. That server was used as a source to clone the VM that we recently moved Trac to.
It is not known if anyone used the backdoor that was found. We recommend all users to change their passwords. In due course, it is populated with a specs which have not changed version at this meeting round and b new spec versions arising from this meeting round.
This system remains unchanged. But instead of clearing down the "latest" folder so that it reflects exactly the meeting-related folder, the "latest" folder now retains the contents it had prior to this TSG round.
Then, as new versions of specs become available from MCC, these versions are uploaded to the "latest" folder and any previoius version of the same spec in the same Release is deleted. Thus within a few weeks of the end of the TSG round, the "latest" folder becomes once more aligned exactly with the latest meeting-related folder. This means that no existing spec is ever missing from the "latest" folder, which now contains the latest available version of each spec in each Release.
There are now no gaps representing anticipated new versions of specs. Newly brought under change control i. The target dates are shown in the table below. Where very many CRs have to be implemented, or very many specifications are to be produced, a further week beyond the above deadlines may be required.
These dates are agreed by the TSG Chairmen. Over the Christmas and New Year period, when the winter TSG round finishes shortly before the holiday period, an extra week or so is normally added to the final deadlines.