Here are the most popular ideas ever about Amarok .
Amarok 2.0 with GTK+ 2
Written by t4ggs the 14 Jan 09 at 10:43.
New
If Amarok will now work in windows and mac os x, why not to make a GTK version for those of us that use GNOME??
Filter by Lyrics in Amarok 2
Written by ethana2 the 12 Jan 09 at 08:30.
New
This functionality should be available, but disabled by default.
Amarok 2 already uses
http://lyricwiki.org to fetch lyrics for the currently playing track. There should be an option that, when enabled, fetches lyrics for every song in one's media library and stores them in a searchable database, so a person who only remembers one phrase from a song in their vast library can locate the exact song rapidly.
Solution #1:
Encourage alsa developers include alpha driver on alpha and beta karmic
Some fresh news from iwai,please include the test driver on karmic alphas and betas to accelerate development.
From: Takashi Iwai
Subject: Testers wanted: New SB X-Fi driver
Newsgroups: gmane.linux.alsa.devel
Date: 2009-05-14 10:52:17 GMT (2 days, 1 hour and 34 minutes ago)
Hi,
after some communications with Creative, I finally got a mergeable
version of their X-Fi driver. It's not my crappy hack but by genuine
Creative :)
The patch is now merged into sound-unstable GIT tree topic/ctxfi
branch:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-unstable-2.6.git
The corresponding alsa-driver snapshot tarball is:
ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-unstabl e-snapshot.tar.gz
The driver module is named as snd-ctxfi.
I tested only the driver builds with recent kernels, but unfortunately
I have no test hardware now, so it'd be helpful if anyone can test
it with a real hardware.
Note that the ctxfi driver might conflict with the HD-audio driver.
So it'd be nice if you save the output of lspci before loading the
drivers and let me know if any problem happens. Also, at testing,
please check the kernel message. If this conflict really happens, try
to build without hd-audio, that is, run configure with
--with-cards=ctxfi option in addition to others, and test whether it
works with this workaround (better after reboot to reset the board
info by BIOS).
Once after I get positive feedbacks (or fix after negative ones), I'm
going to merge it to the main tree so that it'll be in the next
kernel. So, a quick test report would be greatly appreciated.
thanks,
Takashi
It is good news that you managed to have productive communications
with Creative.
I did have a very good relationship with Creative and EMU until all my
contacts left the company.
It took me years to build up the relationship, but I did not have the
time to start again from scratch.
If you manage to get the open source NDA signed with them, ask them to
contact me, informing me of such, and I can then pass all the
datasheets I have on to you. I do need direct contact from them before
I can do this though.
The datasheets cover almost all Creative and EMU sound cards.
Kind Regards
James
Some fresh news from iwai,please include the test driver on karmic alphas and betas to accelerate development.
From: Takashi Iwai <tiwai <at> suse.de>
Subject: Testers wanted: New SB X-Fi driver
Newsgroups: gmane.linux.alsa.devel
Date: 2009-05-14 10:52:17 GMT (2 days, 1 hour and 34 minutes ago)
Hi,
after some communications with Creative, I finally got a mergeable
version of their X-Fi driver. It's not my crappy hack but by genuine
Creative :)
The patch is now merged into sound-unstable GIT tree topic/ctxfi
branch:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-unstable-2.6.git
The corresponding alsa-driver snapshot tarball is:
ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-unstable-snapshot.tar.gz
The driver module is named as snd-ctxfi.
I tested only the driver builds with recent kernels, but unfortunately
I have no test hardware now, so it'd be helpful if anyone can test
it with a real hardware.
Note that the ctxfi driver might conflict with the HD-audio driver.
So it'd be nice if you save the output of lspci before loading the
drivers and let me know if any problem happens. Also, at testing,
please check the kernel message. If this conflict really happens, try
to build without hd-audio, that is, run configure with
--with-cards=ctxfi option in addition to others, and test whether it
works with this workaround (better after reboot to reset the board
info by BIOS).
Once after I get positive feedbacks (or fix after negative ones), I'm
going to merge it to the main tree so that it'll be in the next
kernel. So, a quick test report would be greatly appreciated.
thanks,
Takashi
It is good news that you managed to have productive communications
with Creative.
I did have a very good relationship with Creative and EMU until all my
contacts left the company.
It took me years to build up the relationship, but I did not have the
time to start again from scratch.
If you manage to get the open source NDA signed with them, ask them to
contact me, informing me of such, and I can then pass all the
datasheets I have on to you. I do need direct contact from them before
I can do this though.
The datasheets cover almost all Creative and EMU sound cards.
Kind Regards
James
Solution #2:
Wait until driver is stable
Written by
stoffel the 16 May 09 at 14:54.
Wait until the driver is stable enough before including it in the mainstream Ubuntu.
In the meantime, the driver can be offered as a *separate* download and a howto can be made.
Reason: if the driver causes (severe) issues, people will attribute these issues to the whole Ubuntu platform, meaning bad for Ubuntu's reputation.
Wait until the driver is stable enough before including it in the mainstream Ubuntu.
In the meantime, the driver can be offered as a *separate* download and a howto can be made.
Reason: if the driver causes (severe) issues, people will attribute these issues to the whole Ubuntu platform, meaning bad for Ubuntu's reputation.
Solution #3:
Add ALSA 1.0.21 TO UBUNTU KARMIC 9.10 X-fi Stable driver is out now
1-09-2009 alsa release 1.0.21
http://www.alsa-project.org/main/index.php/Changes_v1.0.20_v1.0.21
Creative Commons ID3 Tags in Music Files
Written by punong_bisyonaryo the 15 Feb 09 at 06:43.
New
Adding Creative Commons license tags in MP3, Ogg, and other audio files, so that when you run Rhythmbox or your favorite music player, you could easily look up the license e.g. BY-SA etc. for your CC music, while at the same time it could display "Copyright NameOfRecordCompany" for non-CC e.g. copyrighted music.
Through this, if you regularly play music in public or use music in commercial projects, you could easily filter which music you can legally use.
Solution #1:
Standardize the inclusion of CC tags in music files
The first step to the solution, of course, is to have the main sources of CC distribution such as Jamendo to adopt the practice of embedding CC information with each music file. I am not well-versed in the technology behind it, but it shouldn't be that difficult to implement.
With this framework in place, players such as Rhythmbox, Amarok, and others can easily filter music based on a CC criteria chosen by the user.
The first step to the solution, of course, is to have the main sources of CC distribution such as Jamendo to adopt the practice of embedding CC information with each music file. I am not well-versed in the technology behind it, but it shouldn't be that difficult to implement.
With this framework in place, players such as Rhythmbox, Amarok, and others can easily filter music based on a CC criteria chosen by the user.
Solution #2:
Leave As-Is
Leave it As-Is
Leave it As-Is
Implement the Amazon Music store into Amarok 2.x
Written by rouge568 the 17 Nov 08 at 00:19.
New
Amarok 2.0 in just around the corner, and with it comes seamless integration with various online services. (Last.fm, Mangatunes store, etc.). However, Mangatunes is not extensive, and just won't make the cut for an all-purpose stop for DRM music. Thus, we need to integrate the Amazon Store into Amarok. This is not only to compete with iTunes on windows and macs, but also to open up low cost and legal digital music to linux users.
Solution #1:
Auto-generated solution of idea #16533
Written by
iKonaK the 16 Dec 08 at 08:52.
Ubuntu Brainstorm was updated in January 2009. Since the idea #16533 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution. Thanks!
<i>Ubuntu Brainstorm was updated in January 2009. Since the idea #16533 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution.</i><br /> Thanks!
Solution #2:
Improve backward compatibility
Linux has some serious backward compatibility issues. Programs tend to only work for 6 months, and people can't downgrade.
We should improve forward/backward compatibility so that programs are no longer release specific.
Linux has some serious backward compatibility issues. Programs tend to only work for 6 months, and people can't downgrade.
We should improve forward/backward compatibility so that programs are no longer release specific.
Solution #3:
The PPA version is working. Simply move it into mainline.
Many people use the PPA package created by Bogdan Butnaru ("amarok14"). It works perfectly fine in Jaunty. There is no legitimate technical or policy reason not to bring this package into mainline. It works, is documented, and no more or less supported than any number of other packages.
You can easily argue that Amarok 2 should not replace 1 because of its massive usability and functional regressions, but I prefer to think of A2 as simply a different app. Certainly, there is no sign that any of the problems will be addressed any time in the next 12-24 months.
There is no question that having Amarok 1.4 in mainline, and as the default media player in Kubuntu Jaunty, would be a massive improvement. It is already written, packaged, and working. This is purely an administrative decision. Let's make it, and restore some of Kubuntu's credibility.
Many people use the PPA package created by Bogdan Butnaru ("amarok14"). It works perfectly fine in Jaunty. There is no legitimate technical or policy reason not to bring this package into mainline. It works, is documented, and no more or less supported than any number of other packages.
You can easily argue that Amarok 2 should not replace 1 because of its massive usability and functional regressions, but I prefer to think of A2 as simply a different app. Certainly, there is no sign that any of the problems will be addressed any time in the next 12-24 months.
There is no question that having Amarok 1.4 in mainline, and as the default media player in Kubuntu Jaunty, would be a massive improvement. It is already written, packaged, and working. This is purely an administrative decision. Let's make it, and restore some of Kubuntu's credibility.
Don't let amarok 1.4 die
Written by mrjamesbond007 the 3 Apr 09 at 21:53.
New
I really like amarok 1.4 and i'd very much appreciate its further developement - and i know that there is amarok2 but i have the feeling that it's not going to be just as good as the first version. I just think the developers should have stick to the old layout concept. Maybe one day all the missing functions will be integrated into amarok2 but i think a further redevelopement of the existing layout-concept in qt4 would have been better.
HTML Support in Rythmbox/Amarok
Written by beattyml1 the 23 Oct 08 at 16:52.
New
I would suggest that we look into the possibility adding a light web browsing interface to rythmbox/amarok that would allow users to browse music stores such as amazon and possibly integrate the downloading process so that we would have built in music store functionality to compete with iTunes, and I know about Jamendo and Magnatune but they have a very limited selection and would not win over the average user
Solution #1:
Auto-generated solution of idea #14744
Ubuntu Brainstorm was updated in January 2009. Since the idea #14744 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution. Thanks!
<i>Ubuntu Brainstorm was updated in January 2009. Since the idea #14744 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution.</i><br /> Thanks!
Solution #2:
Integrate services into the application rather than using a browser
Written by
Warbo the 15 Jan 09 at 12:28.
It seems ugly to me if a music player contains a Web browser for the sole purpose of accessing music stores. A better approach would be to support the stores, on a plugin basis, within the application itself. Then everything is more integrated.
This is happening a lot now that the infrastructure is in place.
It seems ugly to me if a music player contains a Web browser for the sole purpose of accessing music stores. A better approach would be to support the stores, on a plugin basis, within the application itself. Then everything is more integrated.
This is happening a lot now that the infrastructure is in place.
"stick" certain songs together in random play
Written by nelson.blaha the 10 Sep 08 at 03:59.
New
I use Amarok, you use Rhythmbox, and the other guy uses Banshee, so consider this a suggestion for whatever music player it is that you use. Some songs just go together, and when you're done hearing song A, you know it's supposed to flow into song B. You should be able to tell your music player this, and any time the random play pool contains song A and B, it will play AB (and maybe C etc?)
Include "python-dcop" on default installation.
Written by HermanChess the 11 Sep 08 at 19:05.
New
Everytime I install Amarok I need to download "python-dcop" to be able to show what I'm listening in Emesene (a popular msn messenger app). I'm sure other programs use it, and it's pretty small, it should be included either in Ubuntu's installation, or on Amarok or Emesene packages.