Free mp3 encoder for virtual dj software for linux

AMPLE is short for "A MP3 LEnder". I wrote AMPLE one summer when I was coding for a company and got fed up with having to FTP over all my MP3 files from my home server to the computer at work just to listen to them. And through the other "MP3 servers" I could find didnt fit my needs for one of the following reasons:
Depended on libfoo, libbar, python, perl, php3, Apache, libssl, etc, etc, etc...I just wanted to listen to the files
Had a lot of features for "DJ:ing" etc that I really didnt need. Well....it was fun to write too.
So whats good with AMPLE?
Small, standalone (written in C using no external libraries)
Portable (I think), I often try to compile it on the SourceForge compile farms
Allows you to listen to your own MP3s away from home, nothing more, nothing less
This is beginning to sound like marketing cr*p so Ill just stop right there, check out the links on the left for more info.
Enhancements:
- There are only two fixes in this release. One is a compilation fix for Solaris and the other one is a security fix. Turns out a buffer used for local communication didnt have sufficient checks. User data isnt written without checks though so the worst that can happen is that huge amounts of memory is allocated. The socket was also bound to the loopback device so it should only be locally abuseable.

KmPg2 is a very simple to use MPEG2 encoding wizard that allows the user to create high quality DVD compatible MPEG2 streams, without requiring any technical knowledge.
Creating high quality MPEG2 streams involves a lot more than simply feeding the input video to mpeg2enc/transcode/mencoder/etc.
The input video needs to be carefully prepared by pulling it through a chain of stream processing tools like low-pass filters, color correction filters, static and dynamic chroma and luma noise filters, scalers, and so on.
This processing chain needs to be tuned in such a way that all irrelevant data (like noise) is removed before the video enters the encoder. KmPg2 uses the video processing / encoding tools from the MJPEGTools project to achieve this.
KmPg2 features a profiler that enables the user to interactively create custom pre-processing pipelines that are optimised for a specific type of video material. These preprocessing pipelines (profiles) can be stored and used with the actual encoding wizard.
For example, you could create a profile that is designed especially for restoring a single aging VHS tape, or you could create a profile tuned for your digital camcorder and re-use it for every new recording that needs to be encoded.
At this moment KmPg2 accepts only one format of input video: Raw Sony DV video streams. This is the video format that most people use nowadays for high quality video processing and editing. Support for using AVI files for input is expected in future versions.
Main features:
- Produces DVD compliant MPEG2 streams
- Seperate chroma/luma noise filtering
- Low-Pass filtering support
- Contrast/Brightness/Saturation correction
- White balance correction
- Special black-and-white mode
- Crop image to Widescreen (16:9) or Panavision (2.35:1)
- Output conforms to Rec.601 specifications
- Both constant bitrate and variable bitrate encoding
- Unsharp masking
- Supports progressive and interlaced source material
- Support for removing overscan area
- Provides feedback to user about average/peak bitrates
- Show output on screen while encoding
- Generate encoding shell scripts
- Generate quick preview-encodings of parts of source video

High Level Virtual Machine is a toolkit for developing virtual machines for dynamic languages.
The High Level Virtual Machine is:
- Based on LLVM (Low Level Virtual Machine). LLVM is HLVMs sister project. HLVM gains tremendous capability from LLVM in the areas of code generation, bytecode storage, runtime execution, etc.
- Aimed at supporting dynamic languages such as Ruby, Python, Perl, Jython, Haskell, Prolog, etc.
- A complete compiler developers toolkit for creating new languages easily. To write a new compiler, language designers simply write a plugin that describes the language to HLVM and how to translate the grammar productions into HLVMs comprehensive Abstract Syntax Tree (AST). After that, HLVM handles all aspects of code generation, bytecode storage, XML translation, JIT execution or interpretation, and native compilation.
- A language interoperability framework. Because all front end compilers generate code in the same AST, they can interoperate. Use of the runtime library for common constructs (e.g. "string") allow even complex data types to be shared between languages. Users of HLVM can write complex programs in multiple languages and be assured the result can be executed efficiently.
- A code management system including code revisioning, interface versioning, automated recompilation, separation of workspaces, etc.
- Currently under development. Project started April 20th, 2006. Stay tuned to this web site for future developments.

iPod Video Encoder is a command line tool for convenient encoding of video files for use on iPod video. iPod Video Encoder project uses the ffmpeg tool for the actual encoding.
It features recursive encoding of all files in a directory, and generating a podcast.xml file for convenient use in iTunes.
It can be used in a cron job that periodically checks directories for new files and encodes them without user intervention.
Main features:
- Encoding of single files
- Optional specification of a/v bitrates
- Recursively encode all files in a directory
- Generating a podcast.xml for convenient use in iTunes
Options:
--version show programs version number and exit
-h, --help show this help message and exit
-R, --recursive Process directories recusively
-f, --force Force re-encode existing iPod videos
-t, --test Only encode first 10 seconds, to produce test videos
-e EXTENSIONS, --extensions=EXTENSIONS
Comma separated list of input extensions. Default: avi
-i IPODEXT, --ipodext=IPODEXT
iPod extension. Default: .ipod.mp4
-b VIDEO_RATE, --video-rate=VIDEO_RATE
Video bit rate, in kbps (default: 1024)
-a AUDIO_RATE, --audio-rate=AUDIO_RATE
Audio bit rate, in kbps (128)
-W WIDTH, --width=WIDTH
Video width, in pixels (default: 320)
-H HEIGHT, --height=HEIGHT
Video height, in pixels (default: 240)
-P, --pretend Do not really encode, just print out the ffmpeg
commands which would be executed
-v, --verbose Enable verbose output
Podcast options:
-p, --podcast Generate a podcast.xml file for each directory.
--podcast-documentroot=PODCAST_DOCUMENTROOT
Podcast document root; eg. /var/data/Movies/
--podcast-baseurl=PODCAST_BASEURL
Podcast base URL; eg. http://localhost/
Enhancements:
- Only uses the -e option for processing directories.
- The default ipod extension is now _ipod.mp4 for Windows compatibility.
- The README file has been extended with information on the .ipod-encoder settings file.
- The program no longer crashes when HOME is not set on Windows.
- --width and --height parameters have been added.

Joeq is a virtual machine and compiler infrastructure designed to facilitate research in virtual machine technologies such as Just-In-Time and Ahead-Of-Time compilation, advanced garbage collection techniques, distributed computation, sophisticated scheduling algorithms, and advanced run time techniques.
Joeq is entirely implemented in Java, leading to reliability, portability, maintainability, and efficiency. It is also language-independent, so code from any supported language can be seamlessly compiled, linked, and executed -- all dynamically.
Each component of the virtual machine is written to be independent with a general but well-defined interface, making it easy to experiment with new ideas.
Joeq is released as open source software, and is being used as a framework by researchers on five continents on topics ranging from automatic distributed virtual machines to whole-program pointer analysis.
Joeq is a virtual machine and compiler infrastructure designed to be a platform for research in compilation and virtual machine technologies. We had three main goals in designing the system. First and foremost, we wanted the system to be flexible. We are interested in a variety of compiler and virtual machine research topics, and we wanted a system that would not be specific to researching a particular area.
For example, we have interest in both static and dynamic compilation techniques, and in both type-safe and unsafe languages. We wanted a system that would be as open and general as possible, without sacrificing usability or performance.
Second, we wanted the system to be easy to experiment with. As its primary focus is research, it should be straightforward to prototype new ideas in the framework. With this in mind, we tried to make the system as modular as possible, so that each component is easily replaceable. Learning from our experience with Jalapeno, another virtual machine written in Java, we decided to implement the entire system in Java.
This makes it easy to quickly implement and prototype new ideas, and features like garbage collection and exception tracebacks ease debugging and improve productivity. Java, being a dynamic language, is also a good consumer for many of our dynamic compilation techniques; the fact that our dynamic compiler can compile the code of the virtual machine itself means that it can dynamically optimize the virtual machine code with respect to the application that is running on it. Javas object-oriented nature also facilitates modularity of the design and implementation.
Third, we wanted the system to be useful to a wide audience. The fact that the system is written in Java means that much of the system can be used on any platform that has an implementation of a Java virtual machine. The fact that Joeq supports popular input languages like Java, C, C++, Fortran, and even x86 binary code increases the scope of input programs. We released the system on the SourceForge web site as open source under the Library GNU Public License.
It has been picked up by researchers on five continents for various purposes, among them: automatic extraction of component interfaces, static whole-program pointer analysis, context-sensitive call graph construction, automatic distributed computation, versioned type systems for operating systems, sophisticated profiling of applications, advanced dynamic compilation techniques, system checkpointing, anomaly detection, secure execution platforms and autonomous systems. In addition, Joeq is now used as the basis of the Advanced Compilation Techniques class taught at Stanford University.
Joeq supports two modes of operation: native execution and hosted execution. In native execution, the Joeq code runs directly on the hardware. It uses its own run-time routines, thread package, garbage collector, etc. In hosted execution, the Joeq code runs on top of another virtual machine. Operations to access objects are translated into calls into the reflection library of the host virtual machine.
The user code that executes is identical, and only a small amount of functionality involving unsafe operations is not available when running in hosted execution mode. Hosted execution is useful for debugging purposes and when the underlying machine architecture is not yet directly supported by Joeq. We also use hosted execution mode to bootstrap the system and perform checkpointing, a technique for optimizing application startup times.
Joeq system consists of seven major parts:
- Front-end: Handles the loading and parsing of input files, such as Java class files, SUIF files, and binary object files.
- Compiler: A framework for performing analyses and optimizations on code. This includes the intermediate representation (IR) of our compiler.
- Back-end: Converts the compilers intermediate representation into native, executable code. This code can be output to an object file or written into memory to be executed. In addition, it generates metadata about the generated code, such as garbage collection maps and exception handling information.
- Interpreter: Directly interprets the various forms of compiler intermediate representations.
- Memory Manager: Organizes and manages memory. Joeq supports both explicitly-managed and garbage-collected memory.
- Dynamic: Provides profile data to the code analysis and optimization component, makes compilation policy decisions, and drives the dynamic compiler.
- Run-time Support: Provides runtime support for introspection, thread scheduling, synchronization, exception handling, interfacing to external code, and language-specific features such as dynamic type checking.

The Linux Virtual Server is a highly scalable and highly available server built on a cluster of real servers, with the load balancer running on the Linux operating system.

The architecture of the server cluster is fully transparent to end users, and the users interact as if it were a single high-performance virtual server.

The basic goal of the Linux Virtual Server Project is to:
- Build a high-performance and highly available server for Linux using clustering technology, which provides good scalability, reliability and serviceability.

This is a project to create 64-bit virtual CPU, create a 64 bit assembler for the CPU and then port C to it, and then create scripts to port GNU/Linux to it.
The aim is to run 64-bit Linux on common 8/16/32 bit CPUs in applications where speed is not an issue.
Enhancements:
- Added C code intended tor a PIC Preliminary documentation More updates to Gambas program