I've got playback OK, but how about encoding?

I can find virtually nothing on this. Playback is a must, but encoding is not critical to me, since I can encode on my Mac under OS X. But it would be nice to be able to get it working.

There's a (fairly round-about) way to get encoding working on Ubuntu described here:

https://help.ubuntu.com/community/CDRipping



But nothing on that page relates to encoding into the format using the KDE desktop. And anything else I can find by googling sounds mostly irrelevant--and much like pulling teeth, anyway.

I use Kubuntu mostly because the "fit-and-finish" is to a higher standard than with the GNOME desktop, which leaves a bad taste of Windows 95 in the mouth. But I guess KDE is something of an afterthought for Canonical, and there are annoyances with KDE that reveal themselves over time, as well, so maybe I should have used straight Ubuntu.

Still and all, if has anyone managed to get AAC encoding working on Kubuntu and can offer advice I'd be grateful.

I only use standard Ubuntu myself but you could try this:

http://wiki.hydrogenaudio.org/index.php?ti...c_kaudiocreator

Basically the same as the Ubuntu instructions, though you need to install faac encoder and then call it from the kaudiocreator program.

Thanks -- don't know how I missed that. All I found in the Knowledgebase myself was some method using WINE.

Unfortunately, it looks like that's out-of-date. There's no Kaudiocreator: encoding seems to have been rolled into K3B, which seems to be the burning program. And the menus are quite different in that, and don't appear to offer anything similar (though it's not clear what some of them do at all).

I think I'm going to have switch to the GNOME desktop. As it is, there don't seem to be full equivalents to Open Office and the GIMP on the KDE side, and there's other useful stuff that's GNOME, some of which doesn't seem to run right if you install it under KDE. The other thing is whenever I try to Google any problem I always get tons of hits back for Ubuntu even if the fix isn't relevant to Kubuntu. It looks nice and works well (most of the time) but being the minority version of a minority OS doesn't set you up well for solving problems.

Wine and foobar2000. Always worked for me. It was a win-win because you could use the .exe codecs instead of the linux runaround of installing codecs. Plus foobar2000 is one hell of piece of audio conversion software that can handle single image files with embedded cuesheets.

For playback its a give or take but for conversion foobar2000 all the way, everyday.

Kaudiocreator is available via the packet manager. It's even included in the 'kdemultimedia' package as part of the official KDE multimedia release. This console command should help:




I'm not quite sure whether I correctly understand you here, neither Open Office (which is a generic application for a lot of different systems/environments anyway) nor The GIMP require the GNOME desktop environment to be installed. KDE runs them both as well, hence there's no need for any equivalents. GNOME's own applications often work on KDE as soon as the aptitude manager downloads and installs the desktop-specific libraries, which it does by itself while resolving dependencies. This is also valid the other way round, I remember having successfully tested KDE's Amarok audio player on my first Linux installation, which was set up around 6 weeks ago - openSUSE with GNOME.


All Ubuntu guides and fixes I've relied on/needed so far have also worked for Kubuntu, most of them instruct you to use console commands anyway. Don't give up too quickly if the described way how to resolve an issue isn't identically reproducable on KDE.

Of course, no one forces you to keep running KDE, but switching the entire environment just because of minor problems might cause things to become even more complicated, mainly due to you being forced to learn using the desktop-specific applications once more.

Well, thank you. But I'm not going on any more Kubuntu wild-goose chases right now, so I'll give it a miss.



I didn't say they did. (Neither did I say that oo.org was a GNOME application.) I said there didn't seem to be full equivalents for these and other applications specifically for KDE. (This is one reason why, for example, Canonical is still defaulting to supplying Kubuntu with oo.org not Koffice, I suppose.)



You are correct. However, this doesn't always work very well ... which I why I specifically made that point.



Yes, that's right. I've installed KDE apps on several Linux systems that used GNOME as a default. Again, it doesn't always work very well -- or not without some fiddling around.



I've used Ubuntu quite a bit over several years and I wouldn't agree that the default applications for Ubuntu are any harder to use than those for Kubuntu. If they are for you, then I suggest you avoid it. I shan't.

As I said, it's becoming plain to me that choosing what is more an after-thought to Canonical, on which there are fewer developers working, on which there's less information, for which I can't always find what I want, and for what is essentially a minority version of a minority OS is not a good idea. But others will make other choices, I'm sure.

Are we a little pissed today?

aac (faad/faac) has been available on *NIX for years.

what is the issue?

oo.org is not a gnome apps, neither a KDE one. Even Gimp, inkscape, or Ardour are not well integrated in the DE.

I don't understand why some people have the necessity to use "kde" or "qt" application on KDE and gtk apps on GNOME. On windows nobody cares which graphic toolkit an app uses.