Free 1.00 cm is equal to how many meters software for linux

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

cm Compilation Manager is a new tool for build automation and compilation management. cm Compilation Manager addresses a number of shortcomings I see in make.
Main features:
- A clean syntax based on a context-free language description
- Whitespace insensitivity
- Distinct macros and variables
- Separate procedure and production namespaces
- Many native programming constructs such as foreach loops for easy iteration, and more powerful tools such as anonymous functions with static scoping.
- Built-in support for recursive directory handling without additional invocations of cm.
- An intelligent, automatic configuration file generator
- Pre-generated functions for handling common build tasks in a platform-independent manner
- Support for multiple build configurations and multi-pass builds over complicated directory hierarchies
Installation instructions:
Download cm, classib, and gc.
Install the garbage collector per the included instructions. (Basically ./configure; make; sudo make install.) When running configure, you will need to pass it the parameters: --prefix=/usr/lib --with-threads=posix.
Unzip classlib (tar vzxf classlib.tar.gz).
Configure classlibs Makefile with any paths you need to modify.
Build and install classlib with make && sudo make install.
Unzip cm (tar vzxf cm.tar.gz).
Build and install cm with make && sudo make install.
Configure cm by executing: cd /usr/local/etc && sudo cminit
To verify your cm installation, you can rebuild it with the included Cmrules files by typing cm @clean && cm -m opt in the same directory you built cm in with make.
Enhancements:
- The license was changed to the GPL.
- This release includes a dynamic module/plugin system and two initial plugin modules.
- It supports non-root installation, additional command line options, and caches parsed files for quick retrieval during multi-pass builds.
- Several bugfixes are also included.

Class::Meta::Express is a Perl module for concise, expressive creation of Class::Meta classes.

Synopsis

package My::Contact;
use Class::Meta::Express;

class {
meta contact => ( default_type => string );
has name;
has contact => ( required => 1 );
}

This module provides an interface to concisely yet expressively create classes with Class::Meta. Although I am of course fond of Class::Meta, Ive never been overly thrilled with its interface for creating classes:

package My::Thingy;
use Class::Meta;

BEGIN {
# Create a Class::Meta object for this class.
my $cm = Class::Meta->new( key => thingy );

# Add a constructor.
$cm->add_constructor( name => new );

# Add a couple of attributes with generated accessors.
$cm->add_attribute(
name => id,
is => integer,
required => 1,
);

$cm->add_attribute(
name => name,
is => string,
required => 1,
);

$cm->add_attribute(
name => age,
is => integer,
);

# Add a custom method.
$cm->add_method(
name => chk_pass,
code => sub { return code },
);
$cm->build;
}

This example is relatively simple; it can get a lot more verbose. But even still, all of the method calls were annoying. I mean, whoever thought of using an object oriented interface for declaring a class? (Oh yeah: I did.) I wasnt alone in wanting a more declarative interface; Curtis Poe, with my blessing, created Class::Meta::Declare, which would use this syntax to create the same class:

package My::Thingy;
use Class::Meta::Declare :all;

Class::Meta::Declare->new(
# Create a Class::Meta object for this class.
meta => [
key => thingy,
],
# Add a constructor.
constructors => [
new => { }
],
# Add a couple of attributes with generated accessors.
attributes => [
id => {
type => $TYPE_INTEGER,
required => 1,
},
name => {
required => 1,
type => $TYPE_STRING,
},
age => { type => $TYPE_INTEGER, },
],
# Add a custom method.
methods => [
chk_pass => {
code => sub { return code },
}
]
);

This approach has the advantage of being a bit more concise, and it is declarative, but I find all of the indentation levels annoying; its hard for me to figure out where I am, especially if I have to define a lot of attributes. And finally, everything is a string with this syntax, except for those ugly read-only scalars such as $TYPE_INTEGER. So I cant easily tell where one attribute ends and the next one starts. Bleh.

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

conntrack is a userspace command line program targeted at system administrators. conntrack program enables them to view and manage the in-kernel connection tracking state table.
Main features:
- listing the contents of the conntrack table
- searching for individual entries in the conntrack table
- adding new entries to the conntrack table
- listing entries in the expect table
- adding new entries to the expect table

Equalize plug-in does a histogram equalization of the image.

That is, it modifies the images histogram so that it is approximately horizontal, so that all intensity values cover about the same number of pixels in the image (i.e. the histogram is well-balanced).

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