Yauap vs. gst123 vs. MPlayer (Command line)

Introduce yourself, create test postings or talk nonsense
User avatar
thenktor
Salix Wizard
Posts: 2426
Joined: 6. Jun 2009, 14:47
Location: Franconia
Contact:

Re: Yauap vs. gst123 vs. MPlayer (Command line)

Post by thenktor »

mimosa wrote:*However*, it doesn't play ape files. Perhaps it would work to convert them to .wav using mac and pipe the result to mplayer ...
Why not convert them to FLAC, which is supported everywhere nowadays?
Image
burnCDDA (burns audio CDs)
geBIERt (German beer blog)
User avatar
mimosa
Salix Warrior
Posts: 3311
Joined: 25. May 2010, 17:02
Contact:

Re: Yauap vs. gst123 vs. MPlayer (Command line)

Post by mimosa »

Ah, does mac do that? I was going by mac -h, which mentions only .wav.
User avatar
gapan
Salix Wizard
Posts: 6349
Joined: 6. Jun 2009, 17:40

Re: Yauap vs. gst123 vs. MPlayer (Command line)

Post by gapan »

No, you'll have to first convert ape to wav and then wav to flac.
Image
Image
User avatar
thenktor
Salix Wizard
Posts: 2426
Joined: 6. Jun 2009, 14:47
Location: Franconia
Contact:

Re: Yauap vs. gst123 vs. MPlayer (Command line)

Post by thenktor »

Search google for ape2flac. I bet there is a script out there that does everything for you: decoding, encoding, tagging.
Image
burnCDDA (burns audio CDs)
geBIERt (German beer blog)
User avatar
gapan
Salix Wizard
Posts: 6349
Joined: 6. Jun 2009, 17:40

Re: Yauap vs. gst123 vs. MPlayer (Command line)

Post by gapan »

Robin wrote:
gapan wrote:
Robin wrote:SalixOS only wants me to run one application at a time. If I open even a terminal window while I have the browser running, the second application simply locks up and won't respond until I close the other.
That doesn't make sense.
You're right, it doesn't make any sense at all. I should be able to open a terminal while I still have the browser open or a document open that I want to copy-and-paste into the terminal from. But the minute I start a second application, it locks up and won't respond.

I ended up writing down the commands I wanted to put in the terminal and closing the Startup Guide document before I could get the terminal to let me input any commands.

It acted as if something was eating up all the processing power and RAM merely by opening the terminal.

So I guess I'm done with SalixOS. No big deal, there was really no way to check hardware compatibility other than to install it and try it out. What's strange is that it ran really well from the LiveCD! Installed, however, it locked up and would run only one application at a time.

Very strange.

Perhaps I messed something up when I installed Xfce and removed LXDE. I will try it again when the 13.37 Xfce LiveCD is ready.
You definitely messed something up when you tried and failed to upgrade to 13.37.
Image
Image
User avatar
Robin
Posts: 28
Joined: 12. Apr 2010, 01:26
Location: Dixie, Occupied CSA
Contact:

Re: Yauap vs. gst123 vs. MPlayer (Command line)

Post by Robin »

I sure did! Well, I always mess up things I'm new at, and this is very different from Xubu. My experience with Xubu has been so easy and trouble free that I gained very little "Linux know-how" from using it. It's like the difference between "two years' experience" and "one week's experience repeated 103 times," lol.

I think that when I removed LXDE and added Xfce, that I also removed some LXDE-dependent component that wasn't replaced by the usual method of adding Xfce to an existing install of the LXDE version. I think it was the Session Manager perhaps. Then the failed upgrade because I put 13.7 instead of 13.37, duh. I was in too much of a hurry, impatient, over-tired, and worried about school starting up the next day. Lessons learned!

I'll start fresh when the new 13.37 Xfce LiveCD final is released, and when I have the time to give it the attention I should.

Thanks for your patience with me, I'll try not to be a pain in the neck when I try again.

Very grateful for your help, and for this nice distro,
Robin
Post Reply