Gnac 0.2.2 is out!

The Gnac Team is proud to announce the release of Gnac 0.2.2!

This version contains many bug fixes and improvements including:

* New file chooser specially designed to ease the use of file filters,
* Display track peak, track gain and VBR bitrate,
* Better handling of GStreamer’s missing plugins installation,
* Libunique support: allow only one instance of Gnac,
* Improved debugging feedback and verbose output.

Gnac is now completely translated in nine languages thanks to the incredible work performed by the translators, whom we sincerely thank.

The translations available are:
* Brazilian Portuguese (pt_BR)
* Czech (cs)
* Danish (da)
* French (fr)
* Galician (gl)
* German (de)
* Italian (it)
* Slovenian (sl)
* Spanish (es)

In addition, five partial translations are available:

* Chinese (China) (zh_CN)
* Hebrew (he)
* Norvegian Bokmål (nb)
* Romanian (ro)
* Swedish (sv)

If the translation for your language is missing or incomplete, do not hesitate to get involved by getting in touch with your language team. More information on how to contribute translations can be found at

As user experience and satisfaction is our first priority, a skeleton of documentation for Gnac has been created using Mallard, driven by its task oriented structure. We believe the relevance and quality of the documentation could be maximised if users were to write on topic that they feel would benefit from some help. This process is good for several reasons. First of all, the documentation, being user-driven would certainly be of relevance for most of the users who often experience the same difficulties. In addition, it is a great way to get involved in the Open Source community! Should you be interested in contributed to the documentation in any way, please do get in touch with us. If you want even more involvment, you could even be appointed as Gnac’s official documentation maintainer.

This version represents a new beginning in the way we are working. Indeed, so far we have been focused on developing a stable core, in order for future versions to provide a transition as smooth as possible. The next releases will aim at the consolidation, improvement and testing coverage of our code, leading to the improvement of our code’s stability and to the reduction of bugs carried over from version to version. This stage is crucial, as it will allow faster development of new features without having to delve deep into the core’s code. We would also like to release Gnac versions more often. This means next releases will see less changes and should provide you with an easier transition between the different versions. In addition, this approach permits us to be more dynamical, and to react quickly on user requests, bugs reports and feedback.

We have already many ideas on how to improve Gnac. So be assured that Gnac has a bright future ahead. Some of our ideas can be found at and Please, bear in mind that we are writing Gnac to help you! This means we really do care about your experience using Gnac. So please, do come along with ideas, (constructive!) criticisms and feedback.

Thank you for using Gnac.

We are looking forward to hearing from you.

Your Gnac Team

Comments are closed.