General discussion

I am playing music over a USB DAC which is my 2nd soundcard, so that all other non-music noice goes to the default onboard card. This works all fine, but the volume indicator bar in moc stays at 0%, even when in alsamixer the PCM volume is clearly up (and music can be heard nicely).

I have the following in ~/.moc/config

ALSADevice = "plughw:1"
ALSAMixer1 = PCM

I can control the volume without a problem with my keyboard using the following key bindings in my i3wm config file:

bindcode 122 exec amixer -c 1 set PCM 3%- unmute
bindcode 123 exec amixer -c 1 set PCM 3%+ unmute
bindcode 121 exec amixer -c 1 set PCM toggle

So, what should I do to also get the correct PCM volume indicated within moc?

Cheers.

Hi Everyone,

I am running MOC on Lubuntu on a bananapi.

Everything is running perfectly fine. But there is a very weird bug!

Whenever I use mocp -f which is the command for next track, the next song does not play, all i hear is crackling and literary no audible noise. mocp -i shows that the track is running ok.

If I pause the track with mocp -P and then unpause with mocp -U. The song goes back to normal and I can here it clearly and perfectly!

I haev used MOC before on many other systems, this is the first time I test on the BPi and do not have a clue what is going on!

Hi to all.

I want to use mocp for a new project and the goal is to keep playing music all the time over a raspberrypi, i already installed and try it and its great.
The problem i have is to make shuffle from different folders, i mean i have to play 3 songs from folder ROCK and after 1 song from JAZZ and later again other different 3 songs from rock and keep this cicle.

Can i do this with mocp? i miss something or could you advice me some way.

Thanks !

Hello,

I have some multi-disk albums. Their track numbers are correct, but if there are two disks, the tracks are displayed like this:

01 Track_on_first_disk
01 Track_on_second_disk
02 Another_track_on_disk_1
02 ...
...

What tag do I need to include (in vorbis files) so that the tracks can be sorted properly? I have tried DISK and DISKNUMBER, but moc doesn't care about these. I'd like the tracks like this:

01 ...
02 ...
03 ...
...
18 ...
01 ...
02 ...

If moc doesn't currently support this, I'd like to request this as a feature please :)

cheers

hello,

not a bug but just a comment/ask.

First, here are the relevant informations :
- Moc 2.5.0-beta2 on Linux 3.15.8-1-Arch x86_64

Just changed from debian stable (7.0 - don't remember which Moc version was installed) to ArchLinux.
When using my former configuration file, mocp starts with the following message :
- Using digits as keys is deprecated as they may be used for specific purposes in releases 2.6.

It's not really an issue, as the message couldn't be clearer and mocp starts normally. I can use my old shorcuts for fast dir. without any error message.

But...

I'm french, using an azerty keyboard. So, logically, qwerty's keys given in config.example ( !@#$%^&*() ) are largely distributed on an azerty keyboard, which is not the most confortable disposition for fast directories.
As digits keys are deprecated - even if it doesn't cause any real problem, seems it will in 2.6 - I want to follow the indications and find an other way to configurate fast dir's keys.

So, I tried with AZERTY special caracters of digit line on keyboard, which are : &é"'(-è_çà

The problem is that some of those caracters are not allowed and cause a FATAL_EROOR when parsing the ~/.moc/keymap file.
As most alphabetical keys are used, it's not possible to have a range a keys next to each others on other lines. And F1...F9 are used for external commands. KP_1...9 or "eacute" are not allowed.

Is there a way to get round with that ? I mean, scattered keys to access fast dir. is not really an easy and "fast" way.
If digits are not allowed in next version, it will be a problem for non-qwerty users. Or maybe I just didn't catch a better way to do it ?

(And I'm curious about the announced use of digits keys ?)

Thanks in advance (and for the great work done here !)