707
I Use This!
Moderate Activity

News

Analyzed about 4 hours ago. based on code collected about 15 hours ago.
Posted almost 11 years ago
Hola, this is a third weekly report describing my work on my Google Summer of Code project to rewrite MTP (Android) support in Amarok from scratch. This week I've finished implementing reading the track list from MTP devices. What I've done this ... [More] week:Finished the background job to read MTP tracks and their metadata. Includes a nice progress bar (everyone loves progress bars) and is abort-able too.Implemented central MtpTrack class and associated MtpAlbum, MtpArtist, MtpComposer, MtpGenre and MtpYear classes that are used to represent the collection entities in the Collection Browser.Thanks to the above, Collection Browser now shows the entity tree of your MTP device (first screen-shot), which is nice.Problems I've faced: First little bugs/API omissions with libmtp are showing up (inability to flush libmtp's object cache). Fortunately the upstream is very helpful, so I'm looking forward to discuss it with them.What's next: Given that I've basically done work of both week 3 & week 4 from my timeline, I'll do a bit of polishing and testing. I'll also look at week 5 schedule which contains playability of MTP tracks directly in Amarok.You can view and test my code by checking out gsoc branch of my personal Amarok clone repository.On a related note, we've released Amarok 2.8 Beta! Yay! It contains a galore of improvements and corrections that are slated to end up in Amarok 2.8 (final). I definitely think you can give it some testing, can you? :-) [Less]
Posted almost 11 years ago
Hola, this is a third weekly report describing my work on my Google Summer of Code project to rewrite MTP (Android) support in Amarok from scratch. This week I've finished implementing reading the track list from MTP devices. What I've done this ... [More] week:Finished the background job to read MTP tracks and their metadata. Includes a nice progress bar (everyone loves progress bars) and is abort-able too.Implemented central MtpTrack class and associated MtpAlbum, MtpArtist, MtpComposer, MtpGenre and MtpYear classes that are used to represent the collection entities in the Collection Browser.Thanks to the above, Collection Browser now shows the entity tree of your MTP device (first screen-shot), which is nice.Problems I've faced: First little bugs/API omissions with libmtp are showing up (inability to flush libmtp's object cache). Fortunately the upstream is very helpful, so I'm looking forward to discuss it with them.What's next: Given that I've basically done work of both week 3 & week 4 from my timeline, I'll do a bit of polishing and testing. I'll also look at week 5 schedule which contains playability of MTP tracks directly in Amarok.You can view and test my code by checking out gsoc branch of my personal Amarok clone repository.On a related note, we've released Amarok 2.8 Beta! Yay! It contains a galore of improvements and corrections that are slated to end up in Amarok 2.8 (final). I definitely think you can give it some testing, can you? :-) [Less]
Posted almost 11 years ago
Hola, this is a third weekly report describing my work on my Google Summer of Code project to rewrite MTP (Android) support in Amarok from scratch. This week I've finished implementing reading the track list from MTP devices. What I've done this ... [More] week:Finished the background job to read MTP tracks and their metadata. Includes a nice progress bar (everyone loves progress bars) and is abort-able too.Implemented central MtpTrack class and associated MtpAlbum, MtpArtist, MtpComposer, MtpGenre and MtpYear classes that are used to represent the collection entities in the Collection Browser.Thanks to the above, Collection Browser now shows the entity tree of your MTP device (first screen-shot), which is nice.Problems I've faced: First little bugs/API omissions with libmtp are showing up (inability to flush libmtp's object cache). Fortunately the upstream is very helpful, so I'm looking forward to discuss it with them.What's next: Given that I've basically done work of both week 3 & week 4 from my timeline, I'll do a bit of polishing and testing. I'll also look at week 5 schedule which contains playability of MTP tracks directly in Amarok.You can view and test my code by checking out gsoc branch of my personal Amarok clone repository.On a related note, we've released Amarok 2.8 Beta! Yay! It contains a galore of improvements and corrections that are slated to end up in Amarok 2.8 (final). I definitely think you can give it some testing, can you? :-) [Less]
Posted almost 11 years ago
Hola, this is a third weekly report describing my work on my Google Summer of Code project to rewrite MTP (Android) support in Amarok from scratch. This week I've finished implementing reading the track list from MTP devices. What I've done this ... [More] week:Finished the background job to read MTP tracks and their metadata. Includes a nice progress bar (everyone loves progress bars) and is abort-able too.Implemented central MtpTrack class and associated MtpAlbum, MtpArtist, MtpComposer, MtpGenre and MtpYear classes that are used to represent the collection entities in the Collection Browser.Thanks to the above, Collection Browser now shows the entity tree of your MTP device (first screen-shot), which is nice.Problems I've faced: First little bugs/API omissions with libmtp are showing up (inability to flush libmtp's object cache). Fortunately the upstream is very helpful, so I'm looking forward to discuss it with them.What's next: Given that I've basically done work of both week 3 & week 4 from my timeline, I'll do a bit of polishing and testing. I'll also look at week 5 schedule which contains playability of MTP tracks directly in Amarok.You can view and test my code by checking out gsoc branch of my personal Amarok clone repository.On a related note, we've released Amarok 2.8 Beta! Yay! It contains a galore of improvements and corrections that are slated to end up in Amarok 2.8 (final). I definitely think you can give it some testing, can you? :-) [Less]
Posted almost 11 years ago by The Amarok Team
The Amarok team is proud to announce the immediate availability of the result of 5 months of hard work, the beta release of Amarok 2.8. This release is marked by improvements, corrections and polishing of nearly all Amarok features with over 460 ... [More] commits since Amarok 2.7. Everybody is encouraged to test this beta release thoroughly so that we can release rock-solid Amarok 2.8 final. Some of the reworked areas that that you should try out: The MusicBrainz tagger was significantly improved. Amarok is now power-management aware with a pair of new options in the configuration. The Audio analyzer visualisation is back: the widget is configurable by right click on it and it sits prominently under the Current Track widget. The GUI layout can now be reset to default, so no more shuffling elements around if you want to go back to the original view. Local Collection and Collection Browser were fixed to update correctly when tracks are changed or removed. The Nepomuk Collection was improved to query the Nepomuk database dynamically. Other new features: Opus codec support (with transcoding, needs recent TagLib), more keyboard shortcuts, ASX playlist support, improved file browser, better feedback for unplayable tracks, Last.fm integration improvements and much more. The number of bugfixes is equally impressive: we closed over 400 reports of which more than 80 are bug fixes. Also 22 wishes were granted, some of which are to be found as new features. A couple of other changes have been done, for example behavior when (double-)clicking on tracks in various places has been tweaked slightly, splash screen has been removed and Album Artist level replaces Track Artist one by default in the Collection Browser. Many of these changes were only possible with the help of students who were applying for Google Summer of Code and showed us their coding skills by fixing bugs. The final release notes will feature their names more prominently. We're also happy to announce the return of Amarok's founder Mark Kretschmann who got back to Amarok coding after a two year hiatus. Many of the polishes in the GUI are his doing, we are happy to have him back. :) With all those changes we count on you, dear users, to help us polishing the final release and test the new features and changes. Full ChangeLog will be published in the final release or is available in the source code. See full article for download options. More of them can be added later. Weiterlesen [Less]
Posted almost 11 years ago by The Amarok Team
The Amarok team is proud to announce the immediate availability of the result of 5 months of hard work, the beta release of Amarok 2.8. This release is marked by improvements, corrections and polishing of nearly all Amarok features with over 460 ... [More] commits since Amarok 2.7. Everybody is encouraged to test this beta release thoroughly so that we can release rock-solid Amarok 2.8 final. Some of the reworked areas that that you should try out: The MusicBrainz tagger was significantly improved. Amarok is now power-management aware with a pair of new options in the configuration. The Audio analyzer visualisation is back: the widget is configurable by right click on it and it sits prominently under the Current Track widget. The GUI layout can now be reset to default, so no more shuffling elements around if you want to go back to the original view. Local Collection and Collection Browser were fixed to update correctly when tracks are changed or removed. The Nepomuk Collection was improved to query the Nepomuk database dynamically. Other new features: Opus codec support (with transcoding, needs recent TagLib), more keyboard shortcuts, ASX playlist support, improved file browser, better feedback for unplayable tracks, Last.fm integration improvements and much more. The number of bugfixes is equally impressive: we closed over 400 reports of which more than 80 are bug fixes. Also 22 wishes were granted, some of which are to be found as new features. A couple of other changes have been done, for example behavior when (double-)clicking on tracks in various places has been tweaked slightly, splash screen has been removed and Album Artist level replaces Track Artist one by default in the Collection Browser. Many of these changes were only possible with the help of students who were applying for Google Summer of Code and showed us their coding skills by fixing bugs. The final release notes will feature their names more prominently. We're also happy to announce the return of Amarok's founder Mark Kretschmann who got back to Amarok coding after a two year hiatus. Many of the polishes in the GUI are his doing, we are happy to have him back. :) With all those changes we count on you, dear users, to help us polishing the final release and test the new features and changes. Full ChangeLog will be published in the final release or is available in the source code. See full article for download options. More of them can be added later. Source Tarball Instructions for Linux Distributions Sprache Undefined [Less]
Posted almost 11 years ago by The Amarok Team
The Amarok team is proud to announce the immediate availability of the result of 5 months of hard work, the beta release of Amarok 2.8. This release is marked by improvements, corrections and polishing of nearly all Amarok features with over 460 ... [More] commits since Amarok 2.7. Everybody is encouraged to test this beta release thoroughly so that we can release rock-solid Amarok 2.8 final. Some of the reworked areas that that you should try out: The MusicBrainz tagger was significantly improved. Amarok is now power-management aware with a pair of new options in the configuration. The Audio analyzer visualisation is back: the widget is configurable by right click on it and it sits prominently under the Current Track widget. The GUI layout can now be reset to default, so no more shuffling elements around if you want to go back to the original view. Local Collection and Collection Browser were fixed to update correctly when tracks are changed or removed. The Nepomuk Collection was improved to query the Nepomuk database dynamically. Other new features: Opus codec support (with transcoding, needs recent TagLib), more keyboard shortcuts, ASX playlist support, improved file browser, better feedback for unplayable tracks, Last.fm integration improvements and much more. The number of bugfixes is equally impressive: we closed over 400 reports of which more than 80 are bug fixes. Also 22 wishes were granted, some of which are to be found as new features. A couple of other changes have been done, for example behavior when (double-)clicking on tracks in various places has been tweaked slightly, splash screen has been removed and Album Artist level replaces Track Artist one by default in the Collection Browser. Many of these changes were only possible with the help of students who were applying for Google Summer of Code and showed us their coding skills by fixing bugs. The final release notes will feature their names more prominently. We're also happy to announce the return of Amarok's founder Mark Kretschmann who got back to Amarok coding after a two year hiatus. Many of the polishes in the GUI are his doing, we are happy to have him back. :) With all those changes we count on you, dear users, to help us polishing the final release and test the new features and changes. Full ChangeLog will be published in the final release or is available in the source code. See full article for download options. More of them can be added later. Weiterlesen [Less]
Posted almost 11 years ago by The Amarok Team
The Amarok team is proud to announce the immediate availability of the result of 5 months of hard work, the beta release of Amarok 2.8. This release is marked by improvements, corrections and polishing of nearly all Amarok features with over 460 ... [More] commits since Amarok 2.7. Everybody is encouraged to test this beta release thoroughly so that we can release rock-solid Amarok 2.8 final. Some of the reworked areas that that you should try out: The MusicBrainz tagger was significantly improved. Amarok is now power-management aware with a pair of new options in the configuration. The Audio analyzer visualisation is back: the widget is configurable by right click on it and it sits prominently under the Current Track widget. The GUI layout can now be reset to default, so no more shuffling elements around if you want to go back to the original view. Local Collection and Collection Browser were fixed to update correctly when tracks are changed or removed. The Nepomuk Collection was improved to query the Nepomuk database dynamically. Other new features: Opus codec support (with transcoding, needs recent TagLib), more keyboard shortcuts, ASX playlist support, improved file browser, better feedback for unplayable tracks, Last.fm integration improvements and much more. The number of bugfixes is equally impressive: we closed over 400 reports of which more than 80 are bug fixes. Also 22 wishes were granted, some of which are to be found as new features. A couple of other changes have been done, for example behavior when (double-)clicking on tracks in various places has been tweaked slightly, splash screen has been removed and Album Artist level replaces Track Artist one by default in the Collection Browser. Many of these changes were only possible with the help of students who were applying for Google Summer of Code and showed us their coding skills by fixing bugs. The final release notes will feature their names more prominently. We're also happy to announce the return of Amarok's founder Mark Kretschmann who got back to Amarok coding after a two year hiatus. Many of the polishes in the GUI are his doing, we are happy to have him back. :) With all those changes we count on you, dear users, to help us polishing the final release and test the new features and changes. Full ChangeLog will be published in the final release or is available in the source code. See full article for download options. More of them can be added later. Source Tarball Instructions for Linux Distributions Sprache Undefined [Less]
Posted almost 11 years ago by The Amarok Team
The Amarok team is proud to announce the immediate availability of the result of 5 months of hard work, the beta release of Amarok 2.8. This release is marked by improvements, corrections and polishing of nearly all Amarok features with over 460 ... [More] commits since Amarok 2.7. Everybody is encouraged to test this beta release thoroughly so that we can release rock-solid Amarok 2.8 final. Some of the reworked areas that that you should try out: The MusicBrainz tagger was significantly improved. Amarok is now power-management aware with a pair of new options in the configuration. The Audio analyzer visualisation is back: the widget is configurable by right click on it and it sits prominently under the Current Track widget. The GUI layout can now be reset to default, so no more shuffling elements around if you want to go back to the original view. Local Collection and Collection Browser were fixed to update correctly when tracks are changed or removed. The Nepomuk Collection was improved to query the Nepomuk database dynamically. Other new features: Opus codec support (with transcoding, needs recent TagLib), more keyboard shortcuts, ASX playlist support, improved file browser, better feedback for unplayable tracks, Last.fm integration improvements and much more. The number of bugfixes is equally impressive: we closed over 400 reports of which more than 80 are bug fixes. Also 22 wishes were granted, some of which are to be found as new features. A couple of other changes have been done, for example behavior when (double-)clicking on tracks in various places has been tweaked slightly, splash screen has been removed and Album Artist level replaces Track Artist one by default in the Collection Browser. Many of these changes were only possible with the help of students who were applying for Google Summer of Code and showed us their coding skills by fixing bugs. The final release notes will feature their names more prominently. We're also happy to announce the return of Amarok's founder Mark Kretschmann who got back to Amarok coding after a two year hiatus. Many of the polishes in the GUI are his doing, we are happy to have him back. :) With all those changes we count on you, dear users, to help us polishing the final release and test the new features and changes. Full ChangeLog will be published in the final release or is available in the source code. See full article for download options. More of them can be added later. Source Tarball Instructions for Linux Distributions Sprache Undefined [Less]
Posted almost 11 years ago by The Amarok Team
The Amarok team is proud to announce the immediate availability of the result of 5 months of hard work, the beta release of Amarok 2.8. This release is marked by improvements, corrections and polishing of nearly all Amarok features with over 460 ... [More] commits since Amarok 2.7. Everybody is encouraged to test this beta release thoroughly so that we can release rock-solid Amarok 2.8 final. Some of the reworked areas that that you should try out: The MusicBrainz tagger was significantly improved. Amarok is now power-management aware with a pair of new options in the configuration. The Audio analyzer visualisation is back: the widget is configurable by right click on it and it sits prominently under the Current Track widget. The GUI layout can now be reset to default, so no more shuffling elements around if you want to go back to the original view. Local Collection and Collection Browser were fixed to update correctly when tracks are changed or removed. The Nepomuk Collection was improved to query the Nepomuk database dynamically. Other new features: Opus codec support (with transcoding, needs recent TagLib), more keyboard shortcuts, ASX playlist support, improved file browser, better feedback for unplayable tracks, Last.fm integration improvements and much more. The number of bugfixes is equally impressive: we closed over 400 reports of which more than 80 are bug fixes. Also 22 wishes were granted, some of which are to be found as new features. A couple of other changes have been done, for example behavior when (double-)clicking on tracks in various places has been tweaked slightly, splash screen has been removed and Album Artist level replaces Track Artist one by default in the Collection Browser. Many of these changes were only possible with the help of students who were applying for Google Summer of Code and showed us their coding skills by fixing bugs. The final release notes will feature their names more prominently. We're also happy to announce the return of Amarok's founder Mark Kretschmann who got back to Amarok coding after a two year hiatus. Many of the polishes in the GUI are his doing, we are happy to have him back. :) With all those changes we count on you, dear users, to help us polishing the final release and test the new features and changes. Full ChangeLog will be published in the final release or is available in the source code. See full article for download options. More of them can be added later. Source Tarball Instructions for Linux Distributions Sprache Undefined [Less]