x42/meters.lv2

collection of LV2 plugins for audio-level metering

meters.lv2 - Audio Level Meters

meters.lv2 is a collection of audio-level meters with GUI in LV2 plugin format.

It includes needle style meters (mono and stereo variants)

• IEC 60268-10 Type I / DIN
• IEC 60268-10 Type I / Nordic
• IEC 60268-10 Type IIa / BBC
• IEC 60268-10 Type IIb / EBU
• IEC 60268-17 / VU

Stereo & Mono variants of bar-graph meters:

• 30 Band 1/3 octave spectrum analyzer IEC 61260
• Digital True-Peak Meter (4x Oversampling), Type II rise-time, 13.3dB/s falloff.
• True-Peak (4x Oversampling) + RMS (600ms integration time) combined with numeric readout
• K-12, K-14, K-20 / RMS type K-Meters according to the K-system introduced by Bob Katz
• DR-14 (crest factor / loudness range measurement method)

and the following stereo plugins:

• EBU R128 Meter with Histogram and History
• Stereo Phase Correlation Meter (Needle Display)
• BBC Mid/Side M-6 (Needle Display)
• Goniometer (Stereo Phase Scope)
• Phase/Frequency Wheel
• Stereo/Frequency Monitor

as well as a mono:

• Signal Distribution Histogram
• Bitmeter

Usage

Should be pretty much self-explanatory. A few notes:

• click + drag on the calibration-screw allows to modify the reference level of the needle meters
• shift + click on the calibration-screw resets to default
• ctrl + click on meters with scalable GUI resets the window-size to 100%
• clicking anywhere on the bar-graph meters resets the peak-hold

Install

Compiling these plugin requires the LV2 SDK, gnu-make, a c-compiler, libpango, libcairo and openGL (sometimes called: glu, glx, mesa).

  git clone https://github.com/x42/meters.lv2.git
  cd meters.lv2
  make submodules
  make
  sudo make install PREFIX=/usr

Note to packagers: The Makefile honors PREFIX and DESTDIR variables as well as CFLAGS, LDFLAGS and OPTIMIZATIONS (additions to CFLAGS), also see the first 10 lines of the Makefile. You really want to package the superset of x42-plugins.

Note on build-dependencies

These plugins count on rather recent (Jan 2013) fixes^Wfeatures of some libraries (but may work with older versions too):

In particular multi-threading in cairo, pixman and pango. Versions of those libraries earlier than libcairo < 1.12.10, libpixman < 0.30.2 and libpango < 1.32.6 are not thread-safe. As with all concurrency issues, things may or may not work and if you only open one meter GUI at a time it's usually fine.

Also note that the plugins use the LV2 idle-interface (lv2 >= 1.4.2) The plugin-host (eg. ardour or qtractor) needs to be compiled with this or a later version of the LV2 SDK to support the features.

The plugin-host must also support http://lv2plug.in/ns/ext/resize-port/

Screenshots

meters.lv2's Issues

Disable always-on-top

All meter windows are always-on-top (Arch/XFCE/Carla) and i can't let them run in background without closing all windows manually. Other plugins behave properly (Calf, wolf spectrum..).
Can you make that optional?

Integrated should start reporting after 400ms not 5 seconds

I've been reading though the specifications again and I don't see any reason why integrated cannot start being reported after the first 400ms analysis window (followed by subsequent 100ms updates).

Clang warnings

In file included from src/meters.cc:624:
src/surmeter.c:124:12: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
                if (in_a < 0) in_a = 0;
                    ~~~~ ^ ~
src/surmeter.c:125:12: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
                if (in_b < 0) in_b = 0;
                    ~~~~ ^ ~

spectrum analyzer scale

In the analyzer when setting the gain slider to minimum the scales do not match the level displays anymore. (v0.5.1 - reported by C.L.A.)

GUIs not drawing

After a recent update all my x42 meter plugins stopped to draw their interface. There are either black windows shown or some messed up pixmaps from X11 cache (I guess).

This renders the entire plugin suite unusable.
Does anybody have the same problem?

Dynamic Range Meter According to Pleasurize Music Foundation

I don't know if this is the best place to suggest this but it would be great to have a DR meter that mimic TT Dynamic Range Meter (different to LU dynamic range in EBU r128 meter) available in this awesome collection. I found this two projects that may help:
https://github.com/adiblol/dr_meter
https://github.com/simon-r/dr14_t.meter
Please don't doubt to delete this if is the wrong place or wrong request.
Thank you Robin for all your work.

Multi channel Support

Hi x42,

This looks fantastic!

I'm wondering if you have thought of supporting 4 channel audio goniometer? There a a number of quad/multi-channel enthusiasts that are moving to PC based listening that would love to see their music in a goniometer as in the 'old days' they could buy vector scopes for quad (see example below):

https://www.youtube.com/watch?v=fZxvrwlFjaU

If you are not interested I'd be willing to have a hack but to be quite honest I've got no background in technical audio or mathematics so I'd need advice or your thoughts on how to even implement the theory. But you code would be a good start.

THX
Garry

Font size on inline display

Is it possible to increase the font slightly of the inline displays for the values? The scale of the VU meter for instance is barely noticeable when used on a UHD screen.

Prerequisite Installation Documentation

Problem:

Prerequisites are vague in the documentation, some prerequisites are not even listed such as fftw3.

Solution:

Prerequisites should be defined and installation instructions provided within the documentation.

Frequency/Phase wheel segfaults Ardour5 when run via ssh-X

When I run Ardour5.4 via ssh -X, as soon as I open the gui of the Frequency/Phase wheel, Ardour segfaults.
Oddly enough ssh -Y is fine.

ebur128 crashes ardour

(just to keep it alive somewhere)
debian jessie + ardour 4.1 "Here Come the Warm Jets" (debian sid) + x42-plugins 20150712 (debian sid)

As said on IRC: opening the EBU128 GUI in Ardour 4.1 is crashing ardour :
ardour-4.1.0: ./gui/ebur.c:702: void render_radar(EBUrUI*): Assertion ui->radar_pos_cur == ui->fastradar' failed.
Abandon`

Note that:

• the plugin loads fine in the mixer strip, the crash happen only when trying to open the GUI
• ebur128 is opening properly as standalone.

Realtime Spectrogram

Hi Robin, there are no realtime spectrogram that I know of as an lv2 plugin. Would a plugin like that fit in this collection? It would be really useful for people working in post production. Thanks again for your wonderful work!

lv2lint fails on surround8 meters plugin

When packaging x42-plugins 20200714 for Arch Linux I ran lv2lint 0.6.0 against them.

It seems that the surround8 variant of the meters plugin does not validate:

$ lv2lint -Mpack "http://gareus.org/oss/lv2/meters#surround8"                                                                                                                                                                                                  [1]
lv2lint 0.6.0
Copyright (c) 2016-2020 Hanspeter Portner ([email protected])
Released under Artistic License 2.0 by Open Music Kontrollers
<http://gareus.org/oss/lv2/meters#surround8>
  {24 : peak4}
    [FAIL]  Symbol
              lv2:symbol not unique
              seeAlso: <http://lv2plug.in/ns/lv2core#symbol>
  {28 : peak4}
    [FAIL]  Symbol
              lv2:symbol not unique
              seeAlso: <http://lv2plug.in/ns/lv2core#symbol>
  <http://gareus.org/oss/lv2/meters#surmeterui_gl>
    [WARN]  Toolkit
              usage of unofficial external UI is discouraged
              seeAlso: <http://kxstudio.sf.net/ns/lv2ext/external-ui#Widget>

The above output is from the system installed version contained in x42-plugins 20200411.

The below is from the build environment (fox x42-plugins 20200714):

lv2lint 0.6.0
Copyright (c) 2016-2020 Hanspeter Portner ([email protected])
Released under Artistic License 2.0 by Open Music Kontrollers
<http://gareus.org/oss/lv2/meters#surround8>
  {24 : peak4}
    [FAIL]  Symbol
              lv2:symbol not unique
              seeAlso: <http://lv2plug.in/ns/lv2core#symbol>
  {28 : peak4}
    [FAIL]  Symbol
              lv2:symbol not unique
              seeAlso: <http://lv2plug.in/ns/lv2core#symbol>
  <http://gareus.org/oss/lv2/meters#surmeterui_gl>
    [WARN]  Toolkit
              usage of unofficial external UI is discouraged
              seeAlso: <http://kxstudio.sf.net/ns/lv2ext/external-ui#Widget>

spectrum analiser has 20k 'noise'

There is a slow build up of the 20k band.
After a day or 2 it was at -30 dB.

This is in Ardour 4.7, in stop mode, on a track with no inputs and with the other plugins bypassed.

plugin built from x42-plugins-20150702.tar.xz

Simple Scope: no controls mode?

The Stereo Phase Scope has an options panel that is hidden by default and can be shown if needed.

I think it might be useful to hide the Simple Scopes settings and extra information below (marked red) at will:

This could allow to save some screen space when the user doesn't need so much info and tweaking the settings at the moment.

SSE compiler flags only valid for x86

meters.lv2/Makefile

Line 13 in 13750c7

OPTIMIZATIONS ?= -msse -msse2 -mfpmath=sse -fomit-frame-pointer -O3 -fno-finite-math-only -DNDEBUG

Stereo Phase Scope vectorscope refreshing problems

The Stereo Phase Scope seems to not draw the vectorscope. It displays the "Visual buffer overflow" warning message in the bottow right corner, and doesn't draw the yellow dots, or draws them once and keeps that "snapshot" for a few minutes. Sometimes the stuck vectorscope shows randomly on it's own, but it shows every time I enable CRT persistency. The display doesn't react immediately to point size change or other settings though, they seems to take effect with next refresh of the vectorscope (for example after 2 minutes).

Here's a stuck snapchot that shows only when CRT persistency is enabled, it dissapears when I turn it off:

Here we can see two point sizes overlaping becasue if the CRT persistency. It took a few minutes to draw the big dots on top of the small ones:

A-weigthed RMS - WHO ITU H.870 support metrics

I see some meters has peak/TOP RMS.

Do we have something integrating to measure RMS avg or RMS A-weigthed?

Floating GUI behaviour with Reaper's new LV2 support

Hi! As you may or may not know, the Reaper devs are finally adding LV2 support. This is included in their current Release Candidate build, so it likely should be in the next stable release. I've been using the dev builds, and while I haven't been testing the LV2 support very thoroughly, a decent number of plugins I've tried have appeared to work without issues, including some of the x42 plugins. Now, with the Meter plugins specifically, I've encountered a mildly annoying issue with floating GUIs. I've brought this behaviour up in Reaper's forums, and it seems they're unable to easily fix this on Reaper's end. One of the devs told me: "Those plug-ins have UIs that only exist as floating widgets (that are not embeddable in the chain window)".

While I don't understand much about what's happening here under the hood, I'll try to describe what's going on from a user's point of view. Reaper can basically open plugin windows in two ways, either as an independent floating window, or embedded inside what they call the FX chain window, where you can easily switch between the plugins of a track. And each plugin can naturally also be displayed either with a generic UI or with the plugin's own GUI. Now this is where it gets weird with the Meter plugins. When I open one of them in the FX chain window, it displays the generic UI in the chain window, and simultaneously opens a separate floating GUI window, making me close two windows every time I'm done using the plugin GUI. This floating window is also a little different from usual, lacking typical controls on the DAW's side (I believe this was a fix made by the devs to mitigate some of the issues with these floating widgets—at an earlier stage it would always open two windows, even when attempting to only open the floating window).

I've only ever seen this behaviour with the x42 Meter plugins. All others I use open without issues, with their own GUI, inside the FX chain window. It's more an annoyance than a real issue (it's possible to just open the floating GUI directly, without the chain window), but still... I don't know if there's any way to easily fix this, if it's related to the fundamentals of how GUIs are displayed by these plugins. But any ideas would be appreciated. There aren't a whole lot of good native Linux audio monitoring plugins around that I know of, so I would like to keep using these, without any extra annoyances. :)

build fails on Big Sur

had to
export RW=robtk/
after make submodules ( documentation issue ?) to find robtk
finally failed with

c++ -I/usr/local/opt/zlib/include -I/usr/local/opt/sqlite/include -I/usr/local/opt/readline/include -I/usr/local/opt/[email protected]/include -Wall -Wno-unused-function -g -msse -msse2 -mfpmath=sse -fomit-frame-pointer -O3 -fno-finite-math-only -DNDEBUG -DXTERNAL_UI -DHAVE_LV2_1_8 -fPIC -fvisibility=hidden pkg-config --cflags lv2 -DVERSION=""0.9.18-2"" -I. -DHAVE_IDLE_IFACE pkg-config --cflags cairo pango -DUSE_GUI_THREAD -pthread
-o build/meters_glui.dylib gui/meters.c
obj/pugl.o obj/needleUI_gl.o obj/eburUI_gl.o obj/goniometerUI_gl.o obj/dpmUI_gl.o obj/kmeterUI_gl.o obj/phasewheelUI_gl.o obj/stereoscopeUI_gl.o obj/dr14meterUI_gl.o obj/sdhmeterUI_gl.o obj/bitmeterUI_gl.o obj/surmeterUI_gl.o
pkg-config --cflags --libs fftw3f -lm zita-resampler/resampler.cc zita-resampler/resampler-table.cc
-shared -dynamiclib -L/usr/local/opt/bzip2/lib -L/usr/local/opt/zlib/lib -L/usr/local/opt/sqlite/lib -L/usr/local/opt/readline/lib -L/usr/local/opt/[email protected]/lib -framework Cocoa -framework OpenGL pkg-config --libs cairo pangocairo pango
clang: warning: treating 'c' input as 'c++' when in C++ mode, this behavior is deprecated [-Wdeprecated]
clang: error: no such file or directory: 'obj/pugl.o'
clang: error: no such file or directory: 'obj/needleUI_gl.o'
clang: error: no such file or directory: 'obj/eburUI_gl.o'
clang: error: no such file or directory: 'obj/goniometerUI_gl.o'
clang: error: no such file or directory: 'obj/dpmUI_gl.o'
clang: error: no such file or directory: 'obj/kmeterUI_gl.o'
clang: error: no such file or directory: 'obj/phasewheelUI_gl.o'
clang: error: no such file or directory: 'obj/stereoscopeUI_gl.o'
clang: error: no such file or directory: 'obj/dr14meterUI_gl.o'
clang: error: no such file or directory: 'obj/sdhmeterUI_gl.o'
clang: error: no such file or directory: 'obj/bitmeterUI_gl.o'
clang: error: no such file or directory: 'obj/surmeterUI_gl.o'
make: *** [build/meters_glui.dylib] Error 1

Did I miss something?

Multi-Channel Versions of PPM Meters?

Is it possible that a similar approach for multi-channel support could be added, as with the Meterbridge in Mixbus and Ardour?
The use case is for when Carla (or other app) might be used instead.

In addition, the ability to assign channel names, perhaps, even from a file?

documentation for the 4 new Surround plugin

Hi Robin,
is there any user documentation somewhere for the 4 new surround plugins (level 3, 4, 5 and 8)?
Thanks.

Line Weight of Meter Needle

Is it possible that a setting could be added that would the setting of the line weight of the meter needle -- as with the VU Meter -- so when you are using a smaller meter size, the needle can still be made to look "hefty" enough?

Antialiasing for the Simple Scope?

I wonder if it could be possible to use anti-aliased line drawing for Simple Scope to make the display even higher quality?

missing gobject-2.0 LDFLAGS

I get the following error when building just using make

g++  -I. -Wall -Wno-unused-function -g -msse -msse2 -mfpmath=sse -fomit-frame-pointer -O3 -fno-finite-math-only -DNDEBUG -DXTERNAL_UI -DHAVE_LV2_1_8 -fPIC -fvisibility=hidden `pkg-config --cflags lv2` -DVERSION="\"0.4.027-12\"" -DVERSION="\"0.4.027-12\"" `pkg-config --cflags cairo pangocairo pango` -Irobtk/ -DDISPLAY_INTERFACE -I.  `pkg-config --cflags jack lv2 pango pangocairo ` -pthread -DDEFAULT_NOT_ONTOP \
  -DXTERNAL_UI -DHAVE_IDLE_IFACE \
  -DJACK_DESCRIPT="\"lv2ttl/plugins.h\"" \
  -DAPPNAME="\"meter\"" \
  -o x42/x42-meter-collection \
  robtk/jackwrap.c robtk/pugl/pugl_x11.c   \
  -DX42_MULTIPLUGIN src/meters.cc jmeters/vumeterdsp.cc jmeters/iec1ppmdsp.cc jmeters/iec2ppmdsp.cc jmeters/stcorrdsp.cc jmeters/msppmdsp.cc ebumeter/ebu_r128_proc.cc jmeters/truepeakdsp.cc jmeters/kmeterdsp.cc zita-resampler/resampler.cc zita-resampler/resampler-table.cc x42/x42-ebur128.o x42/x42-phase-correlation.o x42/x42-dr14.o x42/x42-k20rms.o x42/x42-goniometer.o x42/x42-phasewheel.o x42/x42-histogram.o x42/x42-bitmeter.o x42/x42-surmeter.o x42/x42-spectrum30.o x42/x42-stereoscope.o x42/x42-truepeakrms.o `pkg-config --cflags --libs fftw3f` -lm \
   -lm -lX11 `pkg-config --libs  cairo pangocairo pango glu gl`  `pkg-config  --libs jack`
robtk/jackwrap.c:271:84: warning: ‘LV2_URI_Map_Callback_Data’ is deprecated [-Wdeprecated-declarations]
 static uint32_t uri_to_id (LV2_URI_Map_Callback_Data callback_data, const char* uri);
                                                                                    ^
robtk/jackwrap.c:821:68: warning: ‘LV2_URI_Map_Callback_Data’ is deprecated [-Wdeprecated-declarations]
 uri_to_id (LV2_URI_Map_Callback_Data callback_data, const char* uri)
                                                                    ^
robtk/jackwrap.c: In function ‘int main(int, char**)’:
robtk/jackwrap.c:1440:17: warning: variable ‘osc_port’ set but not used [-Wunused-but-set-variable]
  int            osc_port         = 0;
                 ^~~~~~~~
/usr/sbin/ld: /tmp/ccbGEONX.o: undefined reference to symbol 'g_object_unref'
/usr/sbin/ld: /usr/lib/libgobject-2.0.so.0: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
make: *** [robtk/robtk.mk:124: x42/x42-meter-collection] Error 1

fixed by using

LDFLAGS+=`pkg-config --libs gobject-2.0` make

resize window to 100%

add a possibility to resize the needle meters to the original size.

issue with bbc meter, din meter, 1/3 octave spectrum display ... AND Carla TROUGH X11VNC

all this lv2 plugins fail when they are used through x11vnc : carla ends with segmentation fault, jalv don't show anything ...

Thanks

add lv2:optionalFeature idisp:queue_draw and lv2:extensionData idisp:interface to *.ttl where appropriate

Title says it. Hosts supporting the inlinedisplay extension but relying on proper advertising of its support plugin-wise won't be able to show any fancy graphs

Frequency/Phase wheel not drawing the points

The grid and GUI is drawn all fine as well as the phase correlation meter, but the scope points are not drawn.

Possibly related to #8

x42-meter freeze my machines with nvidia driver

Hello,
x42meter plugins crash fairly quickly on my two machines having in common the nvidia drivers. Everything goes well when I test these plugins on "non-nvidia" machines.

Distribution: debian stretch, kernel 4.9.0.3 rt, nvidia-legacy-304-xx driver, modules tested : the whole series of x42-meters, in standalone or in plugin with ardour. version 0.9.3 ( debian stretch ) or the latest 0.9.14 demo , same results.

The plugin tested is alone. Playing with the plugin window quickly leads to a blocking of the whole machine, mandatory reboot.

Thanks for all your work on linux and ardour, and for your help

EBUrLV2 error: Host does not support urid:map

ebulv2 and goniometerlv2 needs LV2_URID__map, but didn't announce that in the ttl file as requested feature. That leads to a crash in guitarix, because guitarix didn't support LV2_URID__map. Please use
lv2:requiredFeature urid:map
in the respective ttl file.

regards
hermann

Crash with multiple meters (in Carla host)

When i have two 'UV meters' open in custom gui they run for some seconds and then crash/freeze Carla (no screen/window updates, sound continues properly). This also happens when i add/remove/add another x42 plugin. It doesn't happen if i 'replace' the plugin. It works properly if i just add one plugin and keep it. Other plugins (non-x42) work fine with multiple instances/plugins.

The bug itself seems xorg or nouveau related. Sometimes just the Carla window freezes, sometimes the whole graphic backend/keyboard (x11?) is frozen. I can always SSH into the machine and kill Carla though and get the system back.

Here is a log fragment.

Any idea what could be wrong?

Linux 5.2.0-arch2-1-ARCH SMP PREEMPT Mon Jul 8 18:18:54 UTC 2019 x86_64 GNU/Linux
jack2-dbus 1.9.12
x42-plugins 20190714
carla 2.0.0
cadence 0.9.0
nouveau kms + glamor (GTX770/NVE0)
xorg-server 1.20.5
mesa 19.1.2

Build fails with LTO

I tried to build with the following *FLAGS to optimize the build: -flto=4 -Werror=odr -Werror=lto-type-mismatch -Werror=strict-aliasing

Note the -Werror=* flags are used to help detect cases where the compiler tries to optimize by assuming UB cannot exist in the source code -- if it does exist, ordinarily the code would be miscompiled, and this says to make the miscompilation a fatal error.

I got this error:

make[1]: Entering directory '/var/tmp/portage/media-plugins/x42-plugins-20220714/work/x42-plugins-20220714/meters.lv2'
x86_64-pc-linux-gnu-g++  -I. -march=native -fstack-protector-all -O2 -pipe -fdiagnostics-color=always -frecord-gcc-switches -flto=4 -Werror=odr -Werror=lto-type-mismatch -Werror=strict-aliasing  -Wformat -Werror=format-security -Werror=implicit-function-declaration -Werror=implicit-int -Werror=int-conversion -Werror=incompatible-pointer-types -g -msse -msse2 -mfpmath=sse -fomit-frame-pointer -O3 -fno-finite-math-only -DNDEBUG -DXTERNAL_UI -DHAVE_LV2_1_8 -fPIC -fvisibility=hidden `pkg-config --cflags lv2` -DVERSION="\"0.9.22\"" -march=native -fstack-protector-all -O2 -pipe -fdiagnostics-color=always -frecord-gcc-switches -flto=4 -Werror=odr -Werror=lto-type-mismatch -Werror=strict-aliasing  -Wformat -Werror=format-security -DVERSION="\"0.9.22\"" `pkg-config --cflags cairo pangocairo pango` -I../robtk/ -DDISPLAY_INTERFACE -I.  `pkg-config --cflags jack lv2 pango pangocairo ` `pkg-config  --cflags liblo` -DHAVE_LIBLO -pthread -DDEFAULT_NOT_ONTOP \
  -DXTERNAL_UI -DHAVE_IDLE_IFACE \
  -DJACK_DESCRIPT="\"lv2ttl/plugins.h\"" \
  -DAPPNAME="\"meter\"" \
  -o x42/x42-meter-collection \
  ../robtk/jackwrap.c ../robtk/pugl/pugl_x11.c   \
  -DX42_MULTIPLUGIN src/meters.cc jmeters/vumeterdsp.cc jmeters/iec1ppmdsp.cc jmeters/iec2ppmdsp.cc jmeters/stcorrdsp.cc jmeters/msppmdsp.cc ebumeter/ebu_r128_proc.cc jmeters/truepeakdsp.cc jmeters/kmeterdsp.cc zita-resampler/resampler.cc zita-resampler/resampler-table.cc x42/x42-ebur128.o x42/x42-phase-correlation.o x42/x42-dr14.o x42/x42-k20rms.o x42/x42-goniometer.o x42/x42-phasewheel.o x42/x42-histogram.o x42/x42-bitmeter.o x42/x42-surmeter.o x42/x42-spectrum30.o x42/x42-stereoscope.o x42/x42-truepeakrms.o `pkg-config --cflags --libs fftw3f` -lm \
  -Wl,-O1 -Wl,--as-needed -flto=4 -Werror=odr -Werror=lto-type-mismatch -Werror=strict-aliasing -Wl,--defsym=__gentoo_check_ldflags__=0 -lm -lX11 `pkg-config --libs  cairo pangocairo pango glu gl`  `pkg-config  --libs jack` `pkg-config  --libs liblo`
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-int’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=int-conversion’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=incompatible-pointer-types’ is not valid for C++
../robtk/jackwrap.c: In function ‘int main(int, char**)’:
../robtk/jackwrap.c:1671:30: warning: ignoring return value of ‘int system(const char*)’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
 1671 |                 (void)system ("xmessage -button ok -center \"Cannot connect to JACK.\nPlease start the JACK Server first.\" &");
      |                       ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-int’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=int-conversion’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=incompatible-pointer-types’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-int’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=int-conversion’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=incompatible-pointer-types’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-int’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=int-conversion’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=incompatible-pointer-types’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-int’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=int-conversion’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=incompatible-pointer-types’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-int’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=int-conversion’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=incompatible-pointer-types’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-int’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=int-conversion’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=incompatible-pointer-types’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-int’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=int-conversion’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=incompatible-pointer-types’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-int’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=int-conversion’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=incompatible-pointer-types’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-int’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=int-conversion’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=incompatible-pointer-types’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-int’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=int-conversion’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=incompatible-pointer-types’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-int’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=int-conversion’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=incompatible-pointer-types’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-int’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=int-conversion’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=incompatible-pointer-types’ is not valid for C++
src/goniometer.h:168:3: error: type ‘struct LV2gm’ violates the C++ One Definition Rule [-Werror=odr]
  168 | } LV2gm;
      |   ^
./gui/../src/goniometer.h:168:3: note: a different type is defined in another translation unit
  168 | } LV2gm;
      |   ^
src/goniometer.h:151:20: note: the first difference of corresponding definitions is field ‘cor’
  151 |         Stcorrdsp *cor;
      |                    ^
./gui/../src/goniometer.h:151:20: note: a field of same name but different type is defined in another translation unit
  151 |         Stcorrdsp *cor;
      |                    ^
src/../jmeters/stcorrdsp.h:27:7: note: type ‘struct Stcorrdsp’ should match type ‘Stcorrdsp’
   27 | class Stcorrdsp
      |       ^
src/meters.cc:68:6: error: type ‘MtrType’ violates the C++ One Definition Rule [-Werror=odr]
   68 | enum MtrType {
      |      ^
./gui/needle.c:34:6: note: an enum with different value name is defined in another translation unit
   34 | enum MtrType {
      |      ^
src/meters.cc:69:9: note: name ‘MT_NONE’ differs from name ‘MT_BBC’ defined in another translation unit
   69 |         MT_NONE = 0,
      |         ^
./gui/needle.c:35:9: note: mismatching definition
   35 |         MT_BBC = 1,
      |         ^
lto1: some warnings being treated as errors
lto-wrapper: fatal error: x86_64-pc-linux-gnu-g++ returned 1 exit status
compilation terminated.
/usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../../x86_64-pc-linux-gnu/bin/ld: error: lto-wrapper failed
collect2: error: ld returned 1 exit status
make[1]: *** [../robtk/robtk.mk:125: x42/x42-meter-collection] Error 1
make[1]: Leaving directory '/var/tmp/portage/media-plugins/x42-plugins-20220714/work/x42-plugins-20220714/meters.lv2'
make: *** [Makefile:40: meters.lv2] Error 2
 * ERROR: media-plugins/x42-plugins-20220714::gentoo failed (compile phase):

Note this is built via the x42-plugins repo, but I checked this repo and the code pattern is still there.

Originally reported downstream: https://bugs.gentoo.org/860402
Full build log: build.log

How to compile for windows ?

Hi
Can i compile it for windows in linux ?

X42 Meter Questions

Just bought x42 Meters to use with Mixbus 32C v9. Got some questions:

1. Is it possible to have a meter automatically display at a specific size?
2. Is it possible to have a meter appear in the same location on next launch?
3. Is it possible to have a meter reappear at all on next launch?
4. Is it possible to have a meter open with a specific trim value? (Say -9db vs 0db)

I am already using the Mixbus Meterbridge, which does reappear on next launch, and I use Moom on OSX to force it to a specific location/screen.

I was hoping to use the x42 VU meter as a way to add bus VU meters, to create the effect of an actual console “meterbridge”.

thoughts?

fix makefile

I got an error
Makefile:150: *** recipe commences before first target. Stop.
which is because line 150 should start with two spaces instead of a tab.