preiswerte Schmerzmittel ohne Rezept HCG-Injektionen Online-Apotheke

(Not at all Monthly) Community Update #3

After being asked if we are re still alive a few times on twitter, we decided that it is time for another one of our nearly monthly community updates.

Git build numbers and other tweaks to the build process

In addition to a lot of tweaks to the building process from djcj, we’ve also got a patch ready to make the build number helpful again. What this means is that we’ll exactly know what version of Nightingale you have when you report bugs or feature requests.

Moving and copying in play queue

queue_movePreviously the play queue would only let you copy tracks. Now, thanks to luisgmarine’s work you can move tracks.  If you press Control (or your OS’s equivalent of a copy key) you can copy and then paste the tracks.

Copying in playlists

playlist_copyPlaylists already showed the cursor for copying tracks when pressing Control on the keyboard, now they actually let you copy tracks in place.

Libnotify settings

Libnotify settings in the playback paneEver since we added libnotify support to Nightingale we wanted to expose preferences to disable it.  Now they are available in the playback section, if your version of Nightingale is able to show libnotify track change notifications.

Lastly, we’re currently discussing moving developer meetings to another day of the week. If you previously couldn’t attend the developer meetings, or if you plan to keep attending them, head over to the poll on the forum.

See you next month!

Got comments? Post them here!

New: Monthly Community Update

Default Nightingale Equalizer Presets

A few months ago we opened a poll asking you how you would like to get the newest news from the project. This post is the first of hopefully many to come. It’s going to be a quite big one, as it covers the last three months instead of just one month. If there won’t be enough content (aka no content) there will be no community update post.

This first edition is based on the last three developer meetings, so it’s a bit longer. Oh and yeah, we have monthly developer meetings on IRC now.

Remember that these are all things we are currently working on. Some of features mentioned bellow can already be tested in our nightly builds.

Nightingale command line helpCommand Line Playback Control

Remember the command line support extension for Nightingale (and Songbird)? Good news, that’s in Nightingale by default now! You can get an exact command set by typing nightingale -help.


Based on an old MPRIS extension for Songbird from loganfsmyth, freaktechnik added support for MPRIS 2. This allows Linux users to get information about Nightingale and control Nightingale via DBus. More information on the MPRIS implementation can be found in this wiki article. On the topic of wiki: we’ve found a way to fend of spam bots and as a result you get edit rights by default again!

Dock Actions on elementary OSMac & Linux Dock Shortcuts

We accidentally removed the Mac OS X dock playback controls in 1.12 when we upgraded XULRunner. Johnmurrayvi re-added dock support and added a mute/unmute item. Our default .desktop file for Linux now also contains the same actions as the Mac OS X dock, thanks to the CLI API.

Mac Extensions

Previously, a couple of issues with the old Apple Media Keys extension had been reported. Notably, there was a problem requiring the media key to be pressed twice in order for it to register. We’re happy to say that the “apple-mediakeys” and “apple-remote” extensions, originally written by whitedragon (Nick Kreeger) for Songbird, have been added into our repository and the reported issues have been resolved.

Default Nightingale Equalizer PresetsEQ Presets

Just recently freaktechnik landed the infrastructure and the UI for equalizer presets. Not only does Nightingale have a set of default presets, it also lets you save your own presets. But that’s just the beginning. It comes with a powerful API for add-on developers to create own preset sets, preset importers or any other equalizer preset related extension you can think of!

Tagging Issues

We’ve noticed a lot of issues popping up recently involving song metadata being read or written incorrectly. In our recent developer meeting during June, we discussed this problem and possible solutions. Since the meeting, new testing builds with a patched TagLib have been posted, as well as dependencies, to the patched-taglib-1.7.2-testing folder on our Sourceforge page. If you have experienced any problems you think may be related, give these builds a try. Please post any problems or comments (positive or negative!) about the builds in our forum, as we need feedback on the issue.

A Teaser for the Future

One of the biggest tasks Nightingale has set out to accomplish is updating the code so that it can utilize newer versions of the core XULRunner platform. Until now, Nightingale has relied on the 1.9 version, and updating any XULRunner application from 1.9 to 2.0 is significant step, requiring many changes, in and of itself. After an extensive amount of work, not only working on the Nightingale code, but also creating updated dependency packages, there are many signs of life from new builds based on XULRunner 9.0.1. The effort over the last year can be seen in the master-xul-9.0.1 branch of the repository, as well as the xul-9.0.1 branch of the dependencies repository. With all of these changes, the updated Nightingale builds on Linux, Mac, and Windows, and the core features are functional. The next task is changing the user interface code to provide the intended experience. For example, as seen below, the media library page has yet to be updated, and is currently inoperable. Still, even without the library page, the builds can play music!

win-xr9XULRunner 9 Build on Mac OS XXULRunner 9 Build on Ubuntu

In addition to using a newer version of XULRunner, the other dependencies are using their current stable versions as well. This includes Flac, libogg, libvorbis, libtheora, TagLib, and, most notably, GStreamer and the GStreamer plugins. The code for Nightingale’s mediacore has been updated to utilize the new GStreamer as part of the newer XULRunner builds. screenshotDocumentation

We’ve finally been able to get documentation out of our code again, thanks to thebecwar. You can admire the doxygen based documentation on or build it yourself from our source, exact instructions can be found on the wiki. We’ve also started importing articles from the songbird wiki, so if you’re creating an extension, take a look at the recipebook.

An additional set of documentation has been add to the wiki as well, although it is still a work in progress. While the page on building Nightingale from source has existed for sometime, there has not been any information on building the dependency packages. This page has been created to help document the process, which can prove to be somewhat complex. The first section is intended for building the updated dependencies used in the master-xul-9.0.1 branch, while the latter section is for the current sb-trunk-oldxul branch. The dependencies currently used have proven to be a challenge, as they’re fairly dated, but they’re building on all platforms now, so the latter section will be updated with Linux and Mac instructions in addition to a finalized Windows page.

Finally, another key page has been created, involving in-line tasks from comments, such as “FIXME”, “TODO”, and “XXX”. This page lists the current task markers in the Nightingale code as of 2014/05/14.

Website Translation

While at RMLL freaktechnik and GeekShadow opened translations for the current firstrun, launch and dashboard pages plus the upcoming new main website. When writing this post there already is a French, Portuguese (Brasil), Spanish (Mexico) and a German translation. Those are nearly complete, however with each new Nightingale release we will add new strings for the changelogs, so you’ll never run out of strings to translate. To start translating, head over to the localization page on Babelzilla.

There are 5 comments in our discussion thread.

Nightingale at RMLL 2014 in Montpellier


The next RMLL (that’s Roncontre Mondiale des Logicial Libre or Libre Software Meeting in english) is coming up soon. It feels like Brussels was yesterday, however freaktechnik and GeekShadow will be at this year’s RMLL in Montpellier for Nightingale.

Compared to last year we won’t have a talk. We discussed possible topics and came to the conclusion that we don’t really have anything new to share worthy of a talk.

We will still have a booth for Nightingale, so if you’re from the area, please come and visit us! If you don’t have Nightingale stickers yet it’s the perfect opportunity to get some. We’ll also show off some things we are currently working on, if you’re interested. Or we can talk about music, listen to music and broaden each other’s musical horizon. If you always wanted to get into add-on development this is the perfect opportunity to get an introduction tailored to you. In other words we’ll sit down with any of you and talk about nearly whatever you want!

Got comments? Post them here!

Help testing 1.12.1

Yesterday I landed a new feature in the trunk for 1.12.1. What it does is simply welcoming new users with a firstrun page with helpful information and users who updated with the changelog. This seems like a feature that doesn’t need testing. But it does, because it also serves as a way to measure the amount of installs and upgrades. Currently the stats are running on a test server and you can see them here. All data captured until release will be deleted.

Another reason why it needs testing, is because I had to mess with the session restore component of Nightingale. The same file, could cause a blank page on startup sometimes, but that should be fixed (or not?) . To be sure, that I messed nothing up I need other people than me to use Nightingale with this change, as I have my particular habits, and issues might only occur when you use Nightingale in a different way than I do.

Of course you can also disable the upgrade page, which shows you the changes after an upgrade. To do so just set the preference “nightingale.update.url” to “”. This is one possible reason, why our statistics for upgrades won’t be exact, while we can count on the install statistics (unless for modified builds of Nightingale, of course). Another reason are anti-tracking add-ons or disabled JavaScript.

All other changes Nightingale 1.12.1 currently contains are listed under the release notes. You will see the full release of it before January the 14th, as after this date our integrated updating system will be broken.

You can download a build of Nightingale including the changes from SourceForge or, if your system uses apt, install it from ppa:nightingaleteam/nightingale-nightly. Please report any issues you encounter on GitHub, but please make sure the issue hasn’t been reported yet. Also bear in mind that this is not a release version and might destroy your profile, so only use your existing profile if you don’t care about it, or create a new one by launching Nightingale with the -p argument.

There are 14 comments in our discussion thread.