• readable filetypes: .ogg .mp3 .wav .laoe
• writable filetypes: .wav .laoe
• custom file format .laoe stores the separate layers, editing states and documentation
• multi-channel support (mono, stereo, 3 and more), number of channels limited by hardware and sound-system only
• multi-layer support (tracks containing multiple channels), number of layers limited by hardware only
• floating point sample processing
• one volume-mask per channel
• several standard editing functions like copy, paste, cut, move, duplicate, crop...
• unlimited undo-history with absolute view
• extended select functions with variable intensity curve to define smooth selections, and several selection manipulation functions
• layer-stack and channel-stack to manipulate these objects
• zoomable sample-curve view
• zoomable and configurable spectrogram-view
• analysis tools like spectrum view, measure tools, statistics, calculator...
• diverse waveform generators like signal-generator (rectangle, triangle, sinus...), harmonics generator, pitch generator, freehand generator with diverse interpolation features...
• divers amplitude functions like balance, divers fades, compress expand, distortion, autovolume...
• diverse sample-functions like constant and variable resampling , diverse math functions, convolution, forward and inverse fast fourier transform (yes, you can edit the frequency domain!)...
• some filters like parameter-filter, equalizer, multi-notch filter, FFT filter...
• a great spectrogram-filter, which allows to edit in spectrogram-domain, using a brush or rectangle tool to select shapes
• many audio-effects like multiple reverbs, delay-echo, chorus-flange, multipitch, disharmony, pitch shift, time stretch etc...
• a disharmony-plugin to completely disharmonize a sound in several ways
• some plugins (effects and functions) accept a function curve as parameter, to perform variations in time of a parameter of that effect or function
• uniform clip concept allows to perform all these effects and function on usual time-domain audiosamples, frequency-domain spectrums (magnitude, phase) or any parameter curve
• graphic objects may be drawn onto the clip, for documentation purpose
• extensible plugin architecture

• Minimum JRE: 1.6.0_27 (1.6.0ga5)
• A fast harddrive, high rpm, fast read performance
• A Pentium 4 or better processor, a single core will have its "hands full" with certain setups.

@echo off
set BEGINLIBPATH=[drive:java]\JAVA160ga5\bin
set path=[drive:java]\JAVA160ga5\bin
[drive:laoe]
cd [drive:laoe]\laoe
java -Duser.home=[drive:laoe]\laoe -Xms256M -Xmx256M -jar laoe.jar %* 2>laoe-bugs.txt

• [drive: java] = drive with Java
• [drive: laoe] = drive with LAoE

• The specification "-Duser.home=[drive: laoe]\laoe" ensures that LAoE will save all necessary files in own directory instead of saving them in the home directory.
• The specification "-Xms256M" specify the initial size of the memory allocation pool. It comes from the manual "first steps". You can go down or up with the memory size, depending from what you are going to do. Be aware that it has to be the same as the "-Xmx???M" specification.
• The specification "-Xmx256M" is the same amount as used with "-Xms???M" specification. In the file "Laoe.bat" is a size of "512M" used. With the present specification I could do what is visible in the picture including starting PMView Pro for taking the picture without any problems.
• the specification "%*" comes from the file "Laoe.bat".
• The addition "2>laoe-bugs.txt" ensures that errors are saved in the file "laoe-bugs.txt". The 2 in "2>" is not a typo! You can omit this part If you don't want bug reports.

• The first time I started this program was way back in 2011 with the available version of OpenJDK. It wasn't rock solid. Some years have passed and I did try the program again with our latest version Open JDK1.6.0ga5. Also there are some comments about the first Open JDK 1.6.0 versions. So you have to use the latest version.
• Another thing is to think about where you are going to safe/reside the program. At the moment its on my system among all the other user programs, so not the OS/2 drive. But even then you need enough room and the drive must be fast. If you load a big soundfile you can end up with hunderds of megabytes for left and right channels. Its cleaned nicely when you stop, but you need enough room. If you want an other drive for the samples then try the specification "-Duser.home=[drive:laoe]\laoe" with a different drive. Best way to do this is first to setup on [drive:laoe]\laoe with the program. After first run you will find the directory "[drive:laoe]\laoe\.laoe". Now go to the drive of your choice for the samples. Make the directory(folder) "[drive:samples laoe]\laoe". Now MOVE the subdirectory ".laoe" from "[drive:laoe]\laoe" to "[drive:samples laoe]\laoe". After that change the "-Duser.home=[drive:laoe]\laoe" to "-Duser.home=[drive:samples laoe]\laoe" in the commandfile. I have done it in this way, no errors in LAoE.
• If errors occur then the file "laoe.properties" in the directory(folder) "[drive:laoe]\laoe\.laoe" (mind the dot!) might be poluted for setting up the program at start. You end up with a very small empty frame, probably in the upper left corner of the screen. End the program and delete the file "laoe.properties". With startup you get the question for installing the program. Answer this with YES. What's happening is that a new properties is made.
• At start you are presented with 3 frames, one with lots of icons for starting parts of the program, one with play/loop/rec options and one with zoom options. If you open more frames like in the picture above and you close LAoE in the correct way, then they will open again on the same place with next run.
• The frame with the clip starts too small. Therefore the menu and the bottom line with info is not presented in the right way. You can overcome this by dragging the frame a little bigger, see the picture, the frame in the centre with the blue waveforms.
• For some reason a WAV-file loads reasonably fast, with a MP3-file this is much slower, so be patient. Don't know if this is just a problem of not optimised code, differences between available JAVA versions (Sun, Oracle...) or our version of Open JDK. I just tried to open and play files, did open a few frames and open and closed files, did a loop and that all worked. But be aware that more advanced features might not do so well, didn't tried it yet. Said that, this is the only package which works for us, al other systems with similar capabilities do worse or not at all on our system.