Another linux question

Install xmms-musepack though Synaptic or apt or Adept or whichever interface to the packaging system you use. It really couldn't be easier. Try running basic searches through your program (I know Synaptic can do this) in search of packages--a lot of it is already in repos for you to use without having to build yourself.

Jam it back in, in the dark.

You need to enable the universe repositories.
Do this through Synaptic, or manually edit your /etc/apt/sources.list file and add universe to the end of your "deb ..." lines for general packages. Alternately, you can provide it here and I (or someone else) can show you the changes.

There's nowhere I can't reach.

You being new is why I added the bit at the end about one of us being able to help you with it if you wanted.

Beyond that, though, I don't know anything about gamma correction.

This thing is sticky, and I don't like it. I don't appreciate it.

Getting it to act along with the server startup is simple.

Let us say you decide upon using this (replace the argument values as appropriate):

xgamma -rgamma 1.0 -ggamma 1.0 -bgamma 0.8

You would then stick that command into a file in your home directory named .xinitrc, and append a " &" to the end of the line, like so:

# xinitrc
xgamma -rgamma 1.0 -ggamma 1.0 -bgamma 0.8 &

I am a dolphin, do you want me on your body?

By "home directory", I mean your personal folder, where your profile information, program settings, and personal files are stored (by default). "Home directory" is a fairly common term in the Linux world, and bash (the command-line) helps to accomadate you here. In Bash, you can switch to your home directory quickly by typing simply cd as a command. Also, the character ~ is used to reference your home directory in Bash as well, such that:

~/.xinitrc is translated by Bash into /home/piccolonamek/.xinitrc.

To get the .xinitrc up simply, run this on the terminal to fire up gedit using the proper filename. If a file doesn't exist by that name, gedit will write it for you when you save your work.

gedit ~/.xinitrc

I was speaking idiomatically.

.xinitrc needs to have 0644 permissions (or better). Does it? To check, run "stat ~/.xinitrc" and see what the Access line shows. You can also go and add it to the Sessions in Gnome by using System > Administration > Sessions or something to that effect--add the command with a priority of 20 and it should work fine.

MPC encoder? Do you have a command available on your computer called "mppenc"? That's the musepack encoder. Search your repos for mpc/musepack and see if anything looks helpful?

What kind of toxic man-thing is happening now?

Originally Posted by PiccoloNamek

I have the XMMS plugin for playing MPC files, but there's nothing about an encoder (which I need and frequently use.)

Did you even look for mppenc? But that file you have is a tar, so you will need to unpack it using the tar command.

This should work:

tar -xf FILE

Quote:

Another thing I am going to have to do is figure out how to run Cool Edit 2000 on this system. I don't want to have to boot back into windows just to work on some WAV files. No other audio editor will do. CE2000 is the best of the best for plain old waveform editing, and nothing else even begins to compare.

With that attitude, I can't help you find anything comparable. You don't even want to try anything else, it seems.

How ya doing, buddy?

It doesn't "just work" on Windows, either. You have to install the encoder there. Here, you do the same thing. Unpack that tar, then read the README file enclosed.

Though Merv's commands should build and install it for you. I really don't see what's so hard, here. It worked fine for me on Ubuntu, SUSE, and Gentoo. :\

What, you don't want my bikini-clad body?

That's not "just working", Namek. You still had to do work to get it installed, much less working. You should not expect switching your OS to be an easy feat at first (even from Windows to OSX), or else you will be looking for trouble. About the readme, that's odd. The version I download always had a README file, but it also needs to be compiled, so...

Oh, also. As a random note, you may need to be mindful of your paths when you use mppenc. As an example, if the path to an audio file has Japanese in it anywhere, mppenc bombs on this end. It may not for you, or this might not be relevant to you (English-only filenames), but just a warning.

Be careful about modifying anything in /usr/bin, and make sure you don't nuke or change anything you don't know about in there, since blowing up things like gnome-control-center would be quite inconvenient.

Jam it back in, in the dark.

Originally Posted by Cyrus XIII

But you have to admit that this is entirely possible on most distros these days. If an Ubuntu or Debian user doesen't want to hack "apt-get install [program]" into the terminal there is always Synaptic.

Synaptic requires just as much information and skill as using Aptitude, or even apt for that matter. Many people I know can type faster than they can click to things, and just for reference most of them are in their thirties. Not using that to say anything negative about you, but I just don't really like GUIs.

Quote:

Plus graphical user interfaces have more advantages over a text-only interface than "stuff you can click on". Tool tips come to mind, intuitively organized menus, stuff like that.

Back to our old friend Synaptic/Aptitude. Go fire up Aptitude and try to tell me that again. Besides, what if X breaks? If the person is completely reliant on gedit for editing, they'll be pretty much screwed without vi, nano, emacs, or friends (since it's really easy to break things in vim). Alternately, what if they need to get something reinstalled, but are inconfident in their skills with apt? Aptitude is much more familiar, and usable.

Quote:

The console is for people who preferably know what they want and how to do it. That's not exatly newbie friendly and it never will be.

How is it not newbie friendly? You can do everything a GUI can much faster on the terminal. I will admit to you here that I used to be a "GUI or Bust" type, but then I found the wonders of man. Namek seems to know what he's doing with Windows, just that the transition from being a "Windows Power User" to "Linux WTF" type person will confuse anyone. As an example, I have a friend's parents (in their seventies) on Linux and they can use it fine, since they're not looking for all this eclectic stuff you are (much less, they're on Gentoo).

It's all choice, though. Want it to "just work" when you were raised on the OS? Go Windows.

How ya doing, buddy?

It's actually gparted for the Gnome version, qtparted for the KDE-ish version.

In your case, Namek, get gparted as Ubuntu uses a Gnome base. The interface is not that dissimilar to that which PartitionMagic uses, if you are familiar with the latter program.

This thing is sticky, and I don't like it. I don't appreciate it.

You cannot edit partitions on a drive which is active (mounted) in any way.

Unmount all active partitions on the volume, and try again. A Knoppix LiveCD could be of use for you.

I am a dolphin, do you want me on your body?

Let me guess, you're trying to work on /dev/[h|s]da, right? That'd probably be the same drive where Linux is installed. You cannot unmount the drive if Linux pulls files from it while you are within the OS. Use fdisk -l to get a list of partitions, and cat the /proc/mounts file to see what is where.

First, ABC's experimental on Linux, as far as I recall. Second, rtorrent is far superior, so grab that instead if you want.

Also, about compiling, Merv pretty well explained the process. Change into the source directory, ./configure --help, then ./configure with appropriate options, make, and sudo make install. Google would have even told you this, if you search for "Linux compile process".

I was speaking idiomatically.

No need for that.
What's the error? And, again, ABC on Linux is experimental. Go read their FAQ, and if the bolded experimental doesn't give it away, his warning on that page should explain why I'm against you trying to use it anyways.

What kind of toxic man-thing is happening now?

I was thinking earlier you wanted to try Linux, but now I see this isn't entirely true.

Not every single bit of hardware will work properly on Linux because it's generally developed for Windows and Windows only. We have scripts to make tasks easier in lieu of a total remedy for this. Scripts can also be used to automate other tasks, as their name and usage implies.

Did you look if it was a bug within ALSA or the driver? If within ALSA, report it so they can actually fix it; same for the drivers, but less can be done on this end. If you feel that you "shouldn't have to" do something to get your system working, I frankly think you shouldn't use Linux, as you're in the totally wrong mindset for it.

You might think that I'm just spouting "Linux is easy!" here, but I'm really not. I know Linux takes a great deal of adaptation to get used to, but going "IT SHOULD WORK LIKE WINDOWS!" is quite naive, sir.

FELIPE NO