General discussion

I have been setting up my MOC player to submit the songs I play to last.fm, and have then started to use the OnSongChange and OnStop config options.

I have noticed that if I manually select and start a new song while MOC is playing, this triggers an OnStop event as well as an OnSongChange event (and the order my scripts are executed is not guaranteed). If I just play next song in MOC, I only get an OnSongChange event. I don't see the reason for this behaviour, but I can deal with it.

What's more confounding is that if I start the same song already playing again, I only get an OnStop event but no OnSongChange event, and my script will incorrectly think I've stopped playing music. This is a bummer.

I don't know who or if anyone's still taking care of MOC, but the forum seems to be a bit a live at least so I'll try posting. Thanks for reading!

Everytime I start mocp it's like I'm starting it for a first time! It even says welcome to moc 2.5.0-alpha-4! If i change theme it's ok until I exit moc and go to it again. Theme change is lost and I get welcome message again!
Please help me so I can listen to the music again!

The MOC client is split into two, theres the filesystem and playlist view. How can I just view the filesystem view as I never use playlists?

Hi,

thanks for creating moc. It is really great piece of software.

Unlucky with the newest development version it stopped working as it
used to(it was very convenient way).

mocp2.4.4 runned as follows:

mocp -p

started server and starts playing in background. All 2.5 versions
ends with:

FATAL_ERROR: The server is not running

The error occurs due to changes in main.c lines 624-627 in current
code. Changes in code and values set in params instead of running
function start_moc, runs server_command.

Is it bug or feature?

Regards

Hi guys,

due to the lack of working Python bindings for music on console I have written my own ones.

They support every feature `mocp --foobar` supports, like enqueuing, play/pause/stop/toggle, start/kill the server and information about the currently played track.

Additionally I have written a tiny event system based on that binding that makes it possible to you to listen for events like "song changed" or "moc started" or "song paused" and so on.

You can find documentation on this binding at http://moc.lophus.org. The source can be found on http://github.com/jonashaag/python-moc.

I'm glad about any kind of feedback. And now go and write funny things with it! :-)

Jonas

Good day.
I have been playing around with MOC. It's a player that I use on a daily basis, several hours per day. I find it awesome, and great to use on my low-profile laptop. With the default compilation options for my distro, I saw that it wasn't possible to play M4A files without using the --without-aac flags when configuring moc, so that it would resort to FFMPEG and play the files fine.
Faad2 decodes the M4A files MOC won't. Is there any way to use MOC without FFMPEG for playing M4A files? Unfortunately, half of my media library is in this format, so I wouldn't transcode.
Thanks in advance,

Additional info:
Distro: Arch Linux PPC
MOC version: svn commit #2245
Faad: v2.7
Current ./configure flags:
./configure --prefix=/usr --disable-debug \
--disable-libFLACtest --disable-ltdl-install --without-rcc \
--without-musepack --without-aac \
--without-vorbis --without-flac --without-speex \
--without-timidity --without-curl --without-oss --without-jack \
--without-wavepack --without-samplerate --without-display2

I'm using Debian Squeeze and 2.5.0-alpha4. I'm trying to play .wma files but i can't. Is it unsupported? Please help

Right, so I have no bloody idea how to skip to the next song in the MoC client. Stupid, I know, right? I do know that it's none of the obvious choices: Right, Up, Shift + either of the preceding, Ctrl + either of the preceding or Alt + either of the preceding. It is also not Shift + N or Ctrl + N. It is N, which was the ninth or so thing I tried. I'm okay with that. I wouldn't have guessed it at first, though. I can imagine someone not immediately guessing it. Right? I can imagine someone getting frustrated, too.

But, I mean, it's not in the man page. It's not in the online README under Documentation, either. It's not even in the -info- page, which I resort to only when I'm desperate. So I'm curious:

Without guessing, and without bothering someone on IRC, what rational sequence of actions would a user take to find out what key goes to the next song? Looking in the man page won't work, looking in the online documentation (all of it, even!) won't work, so... what's a rational person to do? I mean, assuming someone will be able to guess your keybindings is not often considered a great approach to user interfaces.

Other than that, nice job, devs, it works great.