Free rename multiple files software for linux

IO::Multiplex is a Perl module that can manage IO on many file handles.

SYNOPSIS

use IO::Multiplex;

my $mux = new IO::Multiplex;
$mux->add($fh1);
$mux->add(*FH2);
$mux->set_callback_object(...);
$mux->listen($server_socket);
$mux->loop;

sub mux_input {
...
}
IO::Multiplex is designed to take the effort out of managing multiple file handles. It is essentially a really fancy front end to the select system call. In addition to maintaining the select loop, it buffers all input and output to/from the file handles. It can also accept incoming connections on one or more listen sockets.

It is object oriented in design, and will notify you of significant events by calling methods on an object that you supply. If you are not using objects, you can simply supply __PACKAGE__ instead of an object reference.

You may have one callback object registered for each file handle, or one global one. Possibly both -- the per-file handle callback object will be used instead of the global one.

Each file handle may also have a timer associated with it. A callback function is called when the timer expires.

ConfigReader::Simple is a simple configuration file parser.

SYNOPSIS

use ConfigReader::Simple;

# parse one file
$config = ConfigReader::Simple->new("configrc", [qw(Foo Bar Baz Quux)]);

# parse multiple files, in order
$config = ConfigReader::Simple->new_multiple(
Files => [ "global", "configrc" ],
Keys => [qw(Foo Bar Baz Quux)]
);

my @directives = $config->directives;

$config->get( "Foo" );

if( $config->exists( "Bar" ) )
{
print "Bar was in the config filen";
}

# copy an object to play with it separately
my $clone = $config->clone;

# only affects clone
$clone->set( "Foo", "Buster" );

# save the config to a single file
$clone->save( "configrc" )

# save the config to a single file, but only with
# certain directives
$clone->save( "configrc" => [qw(Foo Bar)] )

# save to multiple configuration files
$clone->save(
"configrc" => [qw(Foo Bar)],
"global" => [qw(Baz Quux)],
);

ConfigReader::Simple reads and parses simple configuration files. It is designed to be smaller and simpler than the ConfigReader module and is more suited to simple configuration files.

AVI TV Episode File Resizer script is not for multiple MOVIE files (only TV) however it can do SINGLE MOVIE files quite nicely. The project was designed to help me fit (resize the file) multiple Xvid TV episodes (entire season) on a single DVD. Most of the time a TV series is almost exactly the same hours, mins, secs.

That enables this script to set the video bitrate the same for every file (episode) being processed to get the desired file size. The calculation is based on the hours, mins, seconds and the desired file size you want. If you correctly enter the time you will end up with a file size VERY close to the value you entered. The episodes will likley vary about 10 secs or so. Try to average that out when you select the episode time

The new files will have the EXACT same name as the old files so the input and output cannot be in the same DIRECTORY.

The "input files" selector can select multiple files so you can encode one or many files.

If you select an entire season (about 25 episodes) of files it could take quite a few hours to complete. The progress bar updates AFTER the completion of the first file and after every file there after. The current file being processed is displayed in the bottom status bar.

Transcode single pass is used to REencode the files.

Each file will be REencoded with MP3 audio bitrate of 96 kbps. The video is REencoded with the Xvid4 codec.

I used this script to go from 230MB to 175MB with good results. That saved me almost 1.4G for the season (25 episodes) and let me get it on a single DVD to play on my stand alone player.

You should try it with a single file first to check the quality and then do a batch job.

There are other tools to do this but this one can be setup and going in less than 1 min.

It takes almost 10 hours to do an entire season (25 episodes) at an episode time of 25 min 30 sec with a target file size of 171MB (ends up being about 174.8MB)

Tie::FieldVals is an array tie for a file of enhanced Field:Value data.

SYNOPSIS

use Tie::FieldVals;
use Tie::FieldVals::Row;

# tie the array
my @records;
my $recs_obj = tie @records, Tie::FieldVals, datafile=>$datafile;

# object methods
my @field_names = $recs_obj->field_names();

This is a Tie object to map the records in an enhanced Field:Value data file into an array. Each file has multiple records, each record has its values defined by a Field:Value pair, with the enhancements that (a) the Value part can extend over more than one line (because the Field names are predefined) and (b) Fields can have multiple values by repeating the Field:Value part for a given field.

Because of its use of the Tie::File module, access to each record is reasonably fast. The Tie::File module also ensures that (a) the whole file doesnt have to be read into memory (b) record changes are written to the file straight away (c) record changes dont require the whole file to be rewritten, just the part of the file after the change.

The advantage of this setup is that one can have useful data files which are plain text, human readable, human editable, and at the same time able to be accessed faster than using XML (I know, I wrote a version of my reporting software using XML data, and even the fastest XML parsers werent as fast as this setup, once there were a reasonable number of records). This also has advantages over a simpler setup where values are given one per line with no indication of what value belongs to what field; the problems with that is that it is harder to fix corrupted data by hand, and it is harder to add new fields, and one cant have multi-line data.

It is likewise better than a CSV (Comma-Separated Values) file, because again, with a CSV file, the data is positional and therefore harder to fix and harder to change, and again one cant have multi-line data.

This module is both better and worse than file-oriented databases like DB_File and its variants and extensions (such as MLDBM). This module does not require that each record have a unique key, and the fact that a DBM file is binary makes it not only less correctable, but also less portable. On the downside, this module isnt as fast.

Naturally, if ones data needs are more complex, it is probably better to use a fully-fledged database; this is oriented towards those who dont wish to have the overhead of setting up and maintaining a relational database server, and wish to use something more straightforward.

This comes bundled with other support modules, such as the Tie::FieldVals::Row module. The Tie::FieldVals::Select module is for selecting and sorting a sub-set from a Tie::FieldVals array, and the Tie::FieldVals::Join is a very simple method of joining two files on a common field.

This distribution includes the fv2xml script, which converts a Tie::FieldVals data file into an XML file, and xml2fv which converts an XML file into a Tie::FieldVals data file.

mp3cue cuts an input MP3 file according to the information stored in a .cue file (for example multiple tracks of DJ mix), and writes the output to multiple MP3 files.

poc is a mp3 and ogg streamer supporting following protocols:

HTTP (mp3 and ogg)
RTP (RFC 2250) (mp3 only)
RTP (RFC 3119) (mp3 only)
homegrown FEC protocol (mp3 only)

It should work under any POSIX platform, and does not require any additional library. You need a C99 compiler though.

poc is still beta software, ipv6 and ogg support was not tested extensively.

poc includes mp3cue, a mp3 CUE cutter, and mp3cut, a mp3 command-line editing tool.

The goal of the Parallel Virtual File System (PVFS) Project is to explore the design, implementation, and uses of parallel I/O. PVFS serves as both a platform for parallel I/O research as well as a production file system for the cluster computing community. PVFS is currently targeted at clusters of workstations, or Beowulfs.
The PVFS project is conducted jointly between The Parallel Architecture Research Laboratory at Clemson University and The Mathematics and Computer Science Division at Argonne National Laboratory.
Additional funding for the PVFS project comes from NASA Goddard Space Flight Center Code 930 and The National Computational Science Alliance through the National Science Foundations Partnerships for Advanced Computational Infrastructure.
Main features:
- Compatibility with existing binaries
- Ease of installation
- User-controlled striping of files across nodes
- Multiple interfaces, including a MPI-IO interface via ROMIO
- Utilizes commodity network and storage hardware
PVFS supports the UNIX I/O interface and allows existing UNIX I/O programs to use PVFS files without recompiling. The familiar UNIX file tools (ls, cp, rm, etc.) will all operate on PVFS files and directories as well. This is accomplished via a Linux kernel module which is provided as a separate package.
PVFS is easy to install. The Quick Start page describes how to set up a simple installation. Scripts and test applications are included to help with configuration, testing for correct operation, and performance evaluation.
PVFS stripes file data across multiple disks in different nodes in a cluster. By spreading out file data in this manner, larger files can be created, potential bandwidth is increased, and network bottlenecks are minimized. A 64-bit interface is implemented as well, allowing large (more than 2GB) files to be created and accessed.
Enhancements:
- fixes to build under redhat 2.4.20-20.9 kernel
- checks for missing headers on ancient 2.4 kernels
- removal of unused fields from metadata and control messages
- updated pvfsd rc file
- handle various combinations of redhat kernel patches
- fixes to kpvfsd that had previously been fixed in user space
- fix for sftp directory reading problems
- fix to avoid oopses on clients when bad errno values returned
- adjustments to deal wiht gcc 3.4.0 issues
- fixes to work with redhat 9
- fixes to compile kernel code for xx86_64
- updated logging intrastructure
- fixes to error reporting
- update of makefile in pvfs core
- fix to bug in pvfs_open.c where pcount < 0 caused errors
- removed duplicated code in mgr
- fix for problem with bvrecv() optimization
- more unused code removal
- adjustments to keep portland group compiler happy
- removed sd_path from metadata
- new iod.rc and mgr.rc files
- fixes to chmod
- fixes to get correct fs_ino back to clients
- multiple mtime fixes
- streamlined pvfs file detection
- shared library building
- fixed closing socket bug in iod
- reordered messaging in mgr to iods to improve concurrency
- rename fix
- improved metadata file checking
- do_access permission fixes
- fix for "iod out of space" client hang
- cleaner dead socket handling, including special handling of case where mgr would close fds that clients were using
- noninteractive mkmgrconf

Thunar Media Tags Plugin (thunar-media-tags-plugin) adds special features for media files to the Thunar File Manager.
Main features:
- a so-called bulk renamer, which allows users to rename multiple audio files at once, based on their tags (e.g. ID3 or OGG/Vorbis),
- a special media file page for the file properties dialog, which displays detailed information about quality, length etc.,
- and finally, an audio tag editor which is reachable from both, renamer and the properties page.

GerbMerge is a software that can print circuit boards for electronics. It allows you to combine Gerber (RS274-X) and Excellon files from multiple jobs into a single panel.
Jobs may be replicated and rotated.
Enhancements:
- A new ScoringFile option was added to support the creation of a Gerber file containing scoring (i.e., V-groove) data in between individual jobs.