EQ4MOC - Equalizer Preset Editor for MOC

Submitted by CanuConde on Wed, 2026-06-03 07:22

Forums:

MOC version: 
2.6

Hello everyone,

I would like to introduce a small project I've been working on called Eq4MOC.

EQ4MOC is a graphical editor and viewer for equalizer presets used by MOC (Music On Console). The goal of the project is to make it easier to create, modify and manage equalizer settings without manually editing configuration files.

Current features:
Create and edit equalizer presets
Visual representation of equalizer bands
Save and load presets
Simple graphical interface
Moc theme support

I originally created it because I use MOC as my primary music player and wanted a more convenient way to work with equalizer configurations.

Source code:
github.com/canuconde/EQ4MOC

Feedback, bug reports and feature suggestions are welcome.

tomaszg

Wed, 2026-06-03 07:34

You seem to be missing some obvious includes in some files. Compilation fails due to lack of ‘#include <iostream>’

src/eqSet.cpp:104:9: error: ‘cerr’ was not declared in this scope

BTW. Is there a reason why you wrote Makefile by hand? That was part of "retro" approach? Seems that these days writing simple meson configuration file makes much more sense and offers better compatibility across distributions.

tomaszg

Wed, 2026-06-03 07:41

One of the problem with hand-written Makefile is that it misses some flags that might be needed on some systems. In my case it needed:

-LDFLAGS = "-lncurses"
+LDFLAGS = -lncurses -ltinfo

(note also the quotes which are not needed)

CanuConde

Wed, 2026-06-03 07:59

Thanks for taking a look.

The missing include was my mistake and has already been fixed.

Regarding the Makefile, there wasn't any particular reason beyond familiarity. I've been using Makefiles for years and for a small project like this it felt like the simplest solution.

That said, I'm interested in learning Meson and may consider migrating in the future if it improves portability and packaging.

tomaszg

Wed, 2026-06-03 08:33

There is usually little reason to use some build configuration tools (autotools, cmake, meson) as long as you build the code on a single machine/distro/platform. However as soon as you I tend for s project to be more publicly available, it is better to automate the process a bit better. Of course, you can do it in your makefile just by invoking pkg-config a bit more, but things like meson automate those things nicely.

I can help you get started and submit a pull request with basic meson config. You can fine tune it from there.