Free thao sys meter software for linux

Jack Meter is a basic console based DPM (Digital Peak Meter) for JACK. I wrote it for quickly checking remote signal levels, without having to run X11 to use a pretty graphical meter such as meterbridge.
Usage
Usage jack_meter [-f freqency] [-r ref-level] [-w width] [-n] [< port >, ...]
where -f is how often to update the meter per second (8)
-r is the reference signal level for 0dB on the meter
-w is how wide to make the meter (79)
-n changes mode to output meter level as number in decibels
< port > the ports to monitor (multiple ports are mixed)
Enhancements:
- uses new JACK API (and hence requires JACK version 0.100.0)
- connects multiple ports on the command line
- informational messages are new sent to STDERR
- added -n option to output level as number in decibels

Analog VUmeter is a visualization plugin for XMMS.

If you like this plugin, then please send me feedback, comments, patches, etc. Also what I need is artwork or skins, so mail me if you would like to help with that.

Idea for this plugin came from similar plugin for winamp called Homeboy analog VU meter, and ideas how to write plugin to xmms from MSA plugin.

At first I only wanted to make something, that would look like the real thing, but as time passed, I have tried to make it also behave like it actually did something useful.

So what you are actually seeing is dBFS value for sound, which means RMS value of soundlevel compared to reference ((2^16-1)/2). Values range from 0 dBFS (highest) to -91 dBFS (lowest).

PulseAudio Volume Meter is a simple GTK volume meter for the polypaudio sound server.

MDKS Vertical Meters is a Super Karamba theme taken from http://www.kde-look.org/content/show.php?content=40009 by kilrae, added 2 more bars and makes some visual changes! MDKS Vertical Meters is a system monitor.

Tnx kilrae for this good idea, I like it!

gnetload network load meter project is a network and ISDN load meter that is similar to xisdnload, but works in a distributed environment.
It includes an agent (devstata) that runs on machines with interfaces to be monitored and periodically sends status information over the network. A display program (gnetload) collects and displays the data.
Both can be run on the same machine, or be used to report on the state of a dedicated router on another machine. Using multicast or broadcast addresses, data can be fed to more than one instance of gnetload. A menu for taking network interfaces up and down is also provided.
Usage: ./gnetload [-I] [-t tickscale] [-g geometry] [-d] [ip]:port
Enhancements:
- The config script was updated to build with GTK2 and GCONF2 where available.
- There are no other code changes.

JACK Meterbridge is a meterbridge for the UNIX based JACK audio system.

It supports a number of different types of meter, rendered using the SDL library and user-editable pixmaps.

Supported meters

PPM - Peak Program level Meters

Approximatly conforming to BS 6840-10. These meters are designed to indicate peak amplitude, as opposed to VU meters which are designed to indicate volume.

The scale is correct according to the standard, 4 equates to 0dB, 1 to -12, 7 to +12, and it is linear with decibels.

Ive never used a real PPM meter, so I dont know if it reacts correctly. Feedback welcome.

VU - Volume Unit meters

Conforming to BS 6840-17:1991. Real meter is larger.

These meters are designed to measure the "volume" of an audio signal, it is not as relevant to digital systems as PPM meters, but is useful if you are interfacing to analogue tape, FM broadcast equipment or want a general idea of the signal volume.

The -r flag (set reference level) is usful with these meters as it will allow you to calibrate to your DA converters. The meter is pre-adjusted so that it should allign correctly calibrated DA converters with analogue systems. If you wish to run with 0dBFS = 0dBu then use "-r 20"

DPM - Digital Peak Meter

Conforming to IEC 268-18:1995 (peak indiciator decay may not be correct).

These are meters as typically seen on digital consoles, HD recorders etc.

There are the most efficient in screen realestate and CPU use but look a bit boring.

JF - "Jellyfish" Meter (aka. Goniometer)

A jellyfish meter is a stereo scope display, it can be used to spot phase and mono compatibility problems.

Some charateristic problems can be seen, eg. a signal with a stronger left channel is seen as a shape sloping to the left [], more right slopes to the right [/], and dead mono is a vertical line [|].

The meter below the scope display indicates the degree of stereo correlation between the channels, a value of +1 means that it is perfectly mono compatible, and -1 and that the channels are in anti-phase (so they will cancel out if mixed).

If someone has better examples, please mail them to me, there are probably tutorials online.

SCO - Scope

A rendering of an oscilloscope display.

It has a basic trigger function, but there is no timebase control. It renders one pixel per sample, so it will probably be next to useless at 96KHz

Sys::Utmp::Utent is a Perl module to represent a single utmp entry.

SYNOPSIS

use Sys::Utmp;

my $utmp = Sys::Utmp->new();

while ( my $utent = $utmp->getutent() )
{
if ( $utent->user_process )
{
print $utent->ut_user,"n";
}
}

$utmp->endutent;

As described in the Sys::Utmp documentation the getutent method returns an object of the type Sys::Utmp::Utent which provides methods for accessing the fields in the utmp record. There are also methods for determining the type of the record.

The access methods relate to the common names for the members of the C struct utent - those provided are the superset from the Gnu implementation and may not be available on all systems: where they are not they will return the empty string.

ut_user

Returns the use this record was created for if this is a record for a user process. Some systems may return other information depending on the record type. If no user was set this will be the empty string. If tainting is switched on with the -T switch to perl then this will be tainted as it is possible that the user name came from an untrusted source.

ut_id

The identifier for this record - it might be the inittab tag or some other system dependent value.

ut_line

For user process records this will be the name of the terminalor line that the user is connected on.

ut_pid

The process ID of the process that created this record.

ut_type

The type of the record this will have a value corresponding to one of the constants (not all of these may be available on all systems and there may well be others which should be described in the getutent manpage or in /usr/include/utmp.h ) :

ACCOUNTING - record was created for system accounting purposes.
BOOT_TIME - the record was created at boot time.
DEAD_PROCESS - The process that created this record has terminated.
EMPTY - record probably contains no other useful information.
INIT_PROCESS - this is a record for process created by init.
LOGIN_PROCESS - this record was created for a login process (e.g. getty).
NEW_TIME - record created when the system time has been set.
OLD_TIME - record recording the old tme when the system time has been set.
RUN_LVL - records the time at which the current run level was started.
USER_PROCESS - record created for a user process (e.g. a login )
for convenience Sys::Utmp::Utent provides methods which are lower case versions of the constant names which return true if the record is of that type.

ut_host

On systems which support this the method will return the hostname of the host for which the process that created the record was started - for example for a telnet login. If taint checking has been turned on (with the -T switch to perl ) then this value will be tainted as it is possible that a remote user will be in control of the DNS for the machine they have logged in from. ( see perlsec for more on tainting )

ut_time

The time in epoch seconds wt which the record was created.