Side note:
The usage of pacpl is straight forward.
It seems to be able to convert .rm, files, but i am not used to them (So am not 100% and can't test it).
One example of usage is:
which, in my eyes, is easy to remember.

I tried that with my file named 040516dg-a.rm

I took a screen shot of the results. (I added a couple of line breaks between my command and the results)

Any ideas what ffmpeg wants different on the command line?

Attached Thumbnails

 

Is that line of code supposed to be complete? I don't understand it. are the dashes supposed to represent something. The file I am trying to convert is designated 050416dg-a.rm and I am trying to create the mp3 version in the same directory.

Yeah, it means that it doesn't support rm input.

You'll have to compile it with rm support.

I don't exactly know how, but the codec is non-free. I compiled my ffmpeg with non-free and it can convert them.

The dashes show that it is an argument or option to a command, like in
ls is a command, -l is an argument or option to that command.
While for a single-character argument one (often) uses one hyphen, for a full word one (often) uses two hyphen.


So, the full command does:
pacpl # is the command called pacpl
--outdir . # --outdir is the argument which tells pacpl where to put the result, the dot . is the current directory
--to mp3 # --to is the argument which tells pacpl to which codec to convert, in this case to mp3
*flac # means to convert all files (*) which end with "flac" in the current directory.

As i said i don't know rm-files. The man page and page of pacpl says it would support rm files, but i can't test it.
A similar command would be
which does this:
use the command pacpl to convert all files which end with rm to mp3 and put the resulting files in the current/working directory.
but without being able to test it, it's a shot in the dark.
For a single file you need to replace "*rm" with the exact name of the file.
(i guess that others adviced to use ffmpeg for a reason).