freespirit

Last year was started what we hope will become a long running tradition when an Amarok user known as linkmaster03 sent us this picture of his amazing Amarok pumpkin carving.

This year, Jessy Ouellette dropped by our IRC channel with this picture of his pumpkin masterpiece, which absolutely blew our minds!



So happy Halloween to everyone and a big thanks to Jessy for letting us blog this picture!

The upcoming Amarok 2.2.1 release is turning out to be quite an impressive one, especially considering how short of a release cycle we have put ourselves on. The changelog is full of good stuff already!

True to form though, I am going to do a little "2.2.1 is going to be great, but checkout what we have in store for 2.2.2" post!

So here goes:



If you are recoiling in horror at all those random colors, fear not, you will not see them at all. If however you have a ton of moodbar files lying around for your collection and liked this feature in Amarok 1.4.x, you are in luck! Showing the moodbar (if available) in the progress slider is configurable, and moodbars have been added to the playlist layout editor so you can add it to your favorite playlist alyout in any way you choose. Even the 4 different moodbar "styles" (normal, angry, frozen and happy) have been ported over.

The moodbar generator itself seems to work still, even though it could really use some love and a porting to Phonon (or even to qtscript so it could be easily integrated into Amarok and, for instance, run on demand when playing a track or process the entire local collection in one go).

The sun is setting on the development of Amarok 2.2.0. With todays release of Amarok 2.2 rc1, we are preparing to release 2.2.0 very soon and end this significant chapter in the history of Amarok.

This rc contains a number of important bugfixes compared to Beta2 and also adds a few much needed features and improvements to the podcast support. See the release announcement for a full list of changes and please help us by reporting bugs.

As with any sunset, tomorrow is a new day. And once 2.2.0 has been released, we can start over, improving on Amarok 2.2 and slowly start thinking about 2.3 and how to make it even better.

One of the features from Amarok 1 that has so far been missing from Amarok 2, is the ability to edit track metadata directly in the playlist. While it might sound surprising that such a seemingly simple and oft requested feature should take so long to implement, the extremely flexible nature of the Amarok 2 playlist made it quite tricky to get right.

Recently I decided to have a go at it, and after a few false starts, I think I finally finally made it work. So as of today, cliking on an already selected item in the playlist makes it go into "edit mode" where (some of) the visible fields can be edited (subject to a few rules about which pieces of metadata it makes sense to manually edit).

The hard part here was to generate editors that fits whatever layout the playlist is setup to use. Below are screenshots of inline editing with 2 different layouts. The look of the edit boxes could possibly do with a little tweaking, but the functionality is pretty solid.





As the attentive reader will note, this also allows changing track ratings directly in the playlist.

Look for this to arrive in an Amarok 2.2 near you.

Today I want to write a bit about some of the stuff that is made possible by me working on both Magnatune.com and Amarok.

On Magnatune.com, we have recently added a number of features to make the memberships more attractive. One of these features (which has actually been around for a while now) is a personal list of favorite albums for each member. On each album page, there is a small button that adds the album to the list of favorites



Clicking this button adds the album to the favorites page (and in a nifty little trick, the button gives feedback and changes to a link to the favorites page). The favorite page look something like this:



Besides some basic editing (removing albums form the list) it also provides direct download links (for download members) and an option to start a flash player containing all these albums. Based on the data we now have about peoples favorites, I just pushed our latest feature live this morning. This new page provides personal recommendations based on what a member has in their list of favorites, as well as any previous downloads.



As one of the main complaints that I often hear about Magnatune.com is that it is hard to discover new music based on what you already like, hopefully this will help a little. The feature is currently only available for paying members, but that might change in the future.

So, that is the Magnatune.com side of things, and how, you ask does all this relate to Amarok?

If we go back to the release of Amarok 2.1.0, one of the things I had been working on was something called Amarok URLs. These are basically URLs that Amarok triggers on and that can cause Amarok to do any number of different things. While their use in 2.1 was quite limited, one of the main ideas behind them was to make it possible to integrate html pages, possibly generated elsewhere, that can make Amarok perform certain actions.

Using such urls, the Magnatune service in Amarok 2.2 will fully support the membership favorites and recommendations features. I could spend the next few pages describing how exactly this works from a user perspective, but I think I will just throw a video your way!

As always, note that this is very new code and there may be obvious bugs shown in the video. The most obvious is that it needs to be simple to get back the the Magnatune service "front page", but I am working on a solution for that one.


direct link if aggregations breaks the embedded vid (or if you prefer to watch in higher quality)

So this is what I have implemented so far. In essence it is pretty basic stuff, but it shows of what is possible when integrating online content into Amarok 2.

Last Friday, trunk was opened for features and changes intended for Amarok 2.2. In the scope of a few hours more than 250 commits had been made as people were frantically committing their local git repos.

Today, less than one week later, I though it was worth posting a little update and a video showing how all of this new stuff fits within Amarok. While most of the stuff that is shown in this video has already been blogged about before its kind of interesting to see it all in Amarok at once after having only been able to run them separately for a while.

The features shown in the video are (roughly in order of appearance)

- New browser navigation interface
- Wikipedia applet mkII.
- Videoclip applet showing matches for current track and playing a youtube video.
- Videoclip applet playing a video podcast.
- Dockable interface elements


Direct link

Since so much stuff in trunk has changed in such a short time, there are plenty of small bugs and visual issues present in the video, but there is plenty of time to work on these before even getting close to a 2.2 release. Considering just how many changes have been made, I am surprised that trunk is currently working as well as it does

Also there are many features currently being worked on that are still not in any state to show of.

In a previous blog post I showed an experimental prototype that aimed to do away with the vertical tab bar along the left edge of Amarok. The many replies to this post was about 50/50 for and against this idea. In the post, I mentioned that I wanted to add some kind of "breadcrumb" navigation bar to make navigation easier and also to always show the user where he "is", something that the tabs, admittedly, quite nicely accomplished, at least for the lowest level (which browser is active).

Since I had some time off last week, I decided to see how I could improve the original idea and add the breadcrumb interface. I quickly realized that the big vertical, kickoff style, back button was not very pretty, so as you will see, the latest version does away with that completely. It also turned out that when you have a nice breadcrumb bar, having each "category" show its own name, as all the services have been doing so far, really does not make much sense, so this is something that I could remove as well. Finally, this new interface finally gave me the chance to display some extended info about each category, before selecting it, something I have been planning to do for a long time for the services and which now makes sense for all categories. The info that is currently shown is just a placeholder until we figure out the real text/image for each item, so don't place too much importance on the actual info just yet!

I guess you think that I have been writing enough and you want to see the video already, so here it is:

Video on youtube

(note that this vid is available in HD)

I think that overall this works much better than the initial version I blogged about (even though I already liked that a lot) and I am confident enough that I can work out the final issues, that I am going to commit this to trunk as soon as 2.2 opens up for development.

Yesterdays blog entry about a prototype QDockWidget based Amarok 2 interface got a nearly overwhelming amount of positive feedback. So let me start out by saying thank you to everyone who commented.

It did make us think about some things though. Since the vast majority of comments would very much like to see this feature included in Amarok, you guys must have some kind of idea what you would actually use this flexibility for, and what kind of layout you want to create. So today we are going to try to do a little experiment based on all this feedback.

What we would greatly appreciate is if you would do a small simple mockup of what kind of layout you think you would create using this feature and post it to imagebin.ca or somewhere similar and then link it in the comments below, if possible with a very short description text. We are not talking about spending hours in the Gimp making a pretty picture, a simple pencil-on-the-back-of-a-napkin type sketch will do just fine. All it should show is how you would, based only on the possibilities show in the video, arrange the main interface elements, which ones would be placed where, hidden completely, or stacked together using tabs. A very important note is that this is not a free form chance to dream up an entirely new interface, but only about what you would change if this new feature became available. To keep things simple, please post each new mockup as a separate top level reply.

We know that the results of this will be quite biased, as what seems like a really good layout in theory might not work when you actually try it out in the real world. So ideally this experiment should really be done after this feature has made it into Amarok, but since there is currently no timeline for that, we are going to do this as best we can anyway!

The really interesting thing to see here is whether everyone has their own personal ideas about what would be a good interface layout, or if many of the suggestions gravitate towards something similar.

If we get enough feedback on this, we will follow up later with another blog post about the result and any lessons learned.

If any of you needs to revisit the video, here is the direct link.

Seeing how Leo refuses to give up in our little "battle of the blogs", blogging cool new feature after cool new feature, its time for me to fire the next salvo

Disclaimer 1: What I am going to show you here is a personal prototype, made to facilitate discussions. It is currently not planned for inclusion in any version of Amarok. In fact there is no guarantee it ever will appear in a released version as it is quite a controversial topic among the Developers.

Disclaimer 2: The observant among you will notice many small bugs and glitches in the video, such as album covers in the playlist doing weird things, double borders around some elements and likely many others. This is par for the course when creating a quick prototype like this...

That being said, I would really like to hear the opinions of the wider community on this one, so let me know what you think: Want? Don't Want? Wonderful? Horrible? ... Or should I just try to get some more sleep instead of hacking up all this crazy stuff?

Now for the actual video. Due to its rather large size, this one is hosted on youtube to avoid killing our server:



And here is a direct link (which also gives you the video in better quality) in case syndications kills the embedded video.

I thought my last post about the upcoming audio cd collection was pretty cool, but since Leo and I are having a bit of a contest about who has the greater number of cool features ready for 2.2 and he just had to outdo me with his post about the amazingly cool last.fm based dynamic playlist biases I thought it was time to strike back!

A while back, Seb added some cool new headers to the collections in the collection browser. This code was based on the elements in the service browser. Since Seb's versions actually looked much nicer than the ones in the service browser, I decided to "backport" the changes, and make the elements in the service browser look consistent with the collection headers.

Having done this made everything a bit more consistent, but it also highlighted some other huge inconsistencies in the way the browsers look and work. Currently there are basically 3 different navigations methods in place. For selecting the browser we have the oft criticized vertical tab bar, for selecting a service there is the service browser which is a type of dig-down interface, and for selecting playlist categories, we use a stacked toolbox approach. Obviously this is not good for usability, and it does not look good either.

So, in an attempt to standardize the navigation across these different browsers and the navigation between browsers themselves, we started discussing the options at the recent developer sprint in Berlin. We concluded that the interface currently used in the service browser was by far the most flexible and that it might be worth using this for all the browser navigation.

So skipping a few days of extracting, generalizing and putting this code to new use, we now have this:



And since a still image really does not really explaint he concept very well, here is a small vid to show the new interface in action.

This is in a pretty early state of development, and there are many cases where the interface of the different browsers/categories need to be made more consistent. Also, the current plan is to add a kind of "breadcrumb" bar as known from Dolphin to the top of the browsers, making navigation simpler and making it more clear what "page" you are actually on at any given time.

All in all, this cuts down our 3 competing ways of navigating through the browsers down to one, and finally gets rid of the vertical tabs completely.

I think it is safe to say that I don't cope too well with feature freezes. In order to stay motivated I have to have a few forward looking projects. These usually take the form of interesting git branches on my laptop that I hack on while way from civilization (Much of my most interesting code has been written in my parents small cabin in the woods where my wife and I often go to get away from it all a bit. While she reads I hack

In any case, back when we were getting ready to release Amarok 2.0.0, I ran a small series of blogs about some of the stuff I was working on for later releases. I decided that now was the time to continue with this.

Quite a few users have expressed that they would like the ability to play audio CD's back in Amarok 2. The reason that it was not initially ported was that none of the core developers use CD's much and also because CD playback in Amarok 1.4.x was sort of a hack, both with regards to the actual code, but also the way it was integrated into the user interface. recently, while discussing a possible Google Summer of Code project, which was unfortunately not accepted, I started thinking about the "right" way to do CD playback. And as I had a little time on my hands, I could not help myself but create a prototype. So here is what is currently possible on my laptop:

First off we start off Amarok. Notice the cool new collection headers that Seb have created:



Inserting a CD into the drive, Amarok automatically detects it and uses the audiocd:/ KIO slave to get info if possible. These tracks can then be added to the Playlist like any other tracks (as the attentive reader will note there are a few issues with the track information still):



It is possible to mix these tracks and tracks from any other collection freely:




That is pretty cool I think. But wait, there is more. Since the audiocd:/ KIO slave is all about "ripping" CD's, why not add this feature to Amarok as well. But instead of using the "ripping" metaphor, lets just integrate it with the existing "copy to collection" framework. This not only avoids having a seperate gui and menu entries for this task, but also allows you to "rip" directly to media devices or other writable collections and not just the local collection:



After selecting a collection that the track should be copied to, its time to select a format ( advanced options for this can be set in the KIO slaves kcm module which is brought up by clicking on the "advanced" button:



And finally we use the target collections organize dialog to figure out where the tracks should actually go:



While this is all still at the prototype state ( It will not be in Amarok 2.1.0 ) it already works quite well. There are a few issues left with the implementation itself and some deeper issues with the audiocd:/ slave that affects this, such as audiocd:/ not always detecting when the cd has changed and keeping the CDDB data from the last CD around. Aslo, making this work required some pretty invasive changes to some core parts of Amarok, so its is something that will need a lot of testing as it can potentially break Amarok in interesting ways that are not directly related to CD playback itself. So far it does not seem that I have messed anything up too badly though

For anyone really eager to break their Amarok, and not afraid to compile it from source, you can grab a patch that should apply against current trunk here. While feedback is greatly appreciated, I will not offer support for any issues you will have with this patch, so use at your own risk!

Some people might think that we have had more than enough "OMG WORLD OF GOO IS GREAT AND RUNS NATIVELY ON LINUX!!!" posts... Well, they are wrong! So here is another one!

I just bough the game, and the post-demo levels are just as crazy, inventive and plain fun as the levels in the demo. So go buy the game already. Lets prove that there is a viable marked for high quality games on Linux: http://2dboy.com/

And while you are at it, grab the free soundtrack as well: http://kylegabler.com/WorldOfGooSoundtrack/

Now back to playing Wo... uhm.... Working! yeah, Working, thats it..

Woho! I finally have a new toy in Amarok worth blogging about!

Today I want to introduce the first draft of the Playlist Layout Editor for Amarok 2.1. In an earlier post, I discussed the new customizable playlist rendering engine and the underlying configuration system. I also hinted that there would be a simple and easy way of customizing your playlist layout. This is exactly what I have been working on for a little while now. And while the results are still mainly at the prototype stage, I think it is far enough along that it is worth giving a sneak peak at.

So lets get some screenshots on the table!



Building on the "Token Dragging" code crated by our GSoC student Teo Mrnjavac we now have an easy to use editor where the layout of a playlist item can be created and modified using drag and drop and a simple config menu. Currently saving these layouts back to xml (loading from xml into the editor works fine ) is not implemented yet, but it is possible to apply a modified layout to the playlist by pressing the "preview" button.





As can be seen, a playlist layout basically consists of 3 configs, one for each major element in the playlist. Album Heads, Album Body, and Single Tracks. The editor has a tab for each of these, but the way they are edited and created are exactly the same. In the last screenshot can be seen how an illusion of ungrouped tracks can be obtained by making the Album Head item have 0 rows and making the Album Body and Single Track items have the same layout.

Enough for now, I had better get back to playing with... uhm... working on this thing!

Back in part 1 I showed a few of the things that will make it into Amarok 2 at some point ( likely for 2.1.0 ).

Today I want to show you another thing that I only recently started working on. Its another somewhat controversial part of Amarok 2, namely the playlist.

Since we first started showing screenshots of where Amarok 2 development was heading, some people have been unhappy with our idea of a new and improved playlist ( and have been extremely vocal about their displeasure ). We have tried reassuring them that the playlist would, in time, come to encompass many of the things from Amarok 2 that they were missing as well as a whole lot more, but it is always hard to communicate such ideas with no screenshots to back them up.

So, since I just today got something running that finally demonstrates some of these ideas, I rush to blog it! Please note that this code is still at a very early state and that there are a few rendering inconsistencies visible that will get sorted out before this ever makes it into trunk.

What this new code does, is basically make the way each item in the playlist is rendered completely configurable. how any rows there should be, what elements ( title, album, artist, score, ... ) should be shown in each row, how much space each element should be given and so on is all fully configurable. (Configurable from a code point of view, the ui for actually configuring it does not exist yet... ). So for instance, configured to mimic the current playlist layout, it might look like this:



That looks a lot like the current playlist, only slightly uglier because of some of the rendering issues I mentioned earlier. Messing a bit with the ( for now, hard coded ) config for the playlist and adding a few elements to some playlist item types we can create something like this:



Here we have added the score to all body item ( tracks in an album group ) and given the title its own line for single track items. Finally, as the grand finale, for people who prefer the Amarok 1 playlist, it is possible to do something like this by making all items have just one line ( and the album header none, thus making it invisible ) and use the same config for body and single track items:



For dramatic effect I have also hidden the context view! Add to this some decent sorting controls, and basically all the functionality from the 1.4.x playlist can be brought back. And yes, some of the items are "jumping a bit", this is one of the rendering issues I mentioned.

I think this playlist will end up being much more configurable and powefull than the 1.4.x one ever was, even if this was not immediately visible in the Amarok 2.0.0 release. But as we have said many times, Amarok 2.0.0 was just the beginning. Now comes the hard part, creating a sane ui for letting the user configure the playlist layout. Luckily, Dan has the concept of how this will work well under control.

First of all, just to get the terminology straight. In this post, I define a filter as something that limits what you actually see in a view, and a search as something that selects items in the view without affecting other elements.

Amarok 1 style playlist filtering.

Since Amarok 2.0.0 was released, one of the frequently mentioned Most Missed Features (MMF) is the Amarok 1.4.x style playlist filtering.

The filtering in Amarok 1.4.x is indeed very powerful, but it also suffers from a number of usability problems and is actually sort of a weirdly placed feature as the collection is where advanced filtering is meant to take place as it will always haver more powerful mechanisms for advanced filtering.

That said, we are very aware that there needs to be a simple way of locating content in large playlists and perhaps even limit the playback of tracks to a subset of what is in the playlist in a non destructive way. Inspired by the progressive searching in apps like Firefox (and indeed many of the KDE 4 applications) we decided to try this out instead. So, hidden away in a small cabin in the very dark woods, far away from streetlights and traffic, I decided to have a go at this.

Amarok 2 style playlist searching.

This morning I committed the initial version of a rather advanced playlist search feature. At its very core, it is just a progressive, as you type, search. This means that as you type, the first track that match the current search term will be selected (and the playlist scrolls to it). Next and previous buttons then allows you to jump around in the tracks matching the search (These really need to get some keyboard shortcuts... Working on that one). The search edit gives immediate feedback on whether there are any matches or not, in the same way that, for instance, the KDE 4 version of Konsole does. By turning the search edit a different color and disabling the next and previous buttons. Now by itself, this is useful, but not super powerful, but this playlist search has a few additional tricks up its sleeve. It is possible to specify which fields should be matched against when typing a query. This is changed by clicking off the fields in a small drop down menu.

Currently it is possible to search any combination of track name, album name, artist name, genre name, composer name or year, and I have a few more ideas for properties to search that i am going to add. It is also possible to "lock" the track progression to only play tracks that matches the current search term. This is toggled using the same small drop down menu. It provides a very convenient way of just playing a particular artist from your all time favorites playlist or any number of similar use cases. Currently this only works when using "standard" or "random track" playback modes however, and I am still pondering whether it actually makes sense for any of the other progressions modes, such as "random album". All the options from this drop down menu are of course stored in the config so the options are persistent across sessions.

We are aware that some people will still miss the old style filtering and that this is not the same thing. We do believe however that a search makes more sense in the playlist than a filter, and that this satisfies many, although not all, of the use cases that the old filter did. Going forward, it might also be possible to add other features to the search, such as selecting all matching tracks, or exporting matches to a new playlist, if there are use cases that support these additions.

One thing I am still pondering is if the filter bar should be visible at all times, making the feature very easily discoverable, or if it should only appear when the search keyboard shortcut is activated....

As mentioned, I committed this code this morning, and baring any major issues turning up, it will be appearing in Amarok 2.0.1 which should be released shortly after new year if all goes well. If you cannot wait that long, it should be appearing in the nightly builds shortly, and failing that, there is always building straight from svn!