Monthly Archives: January 2015

Samples selection and chopping workflow

  1. Download the naive-chopper script. LINK
  2. Add the path to the folder storing the script to the PATH
  3. Go to directory with WAV files to be chopped.
  4. For segments of length 30 run:
    1. $ for file in *.wav; do $file ../<output-dir>/; done
  5. For 60 seconds long segments run:
    1. $ DURATION=60;
    2. $ for file in *.wav; do $file ../<output-dir>/ $DURATION $STARTPOINT $ENDPOINT; done
    1. For 20 seconds long segments between 2:00 and 3:00 minute:
      1. $ DURATION=20;  STARTPOINT=120; ENDPOINT=180;
      2. $ for file in *.wav; do $file ../<output-dir>/ $DURATION $STARTPOINT $ENDPOINT; done

Using external VST plugins inside the Maschine


To insert plugins go directly to plug-in section of the sound/group and select “+” at first empty slot.

I decided to post this hint, because one might intuitively look for the VST plug-ins in the User Library, without realizing that the browser by default shows only presets, not plugins. So it might seems that user VST plugins were not correctly detected.

Preparing Audio CD master image for CD replication on Windows

Requirements  from the CD pressing company:

  1. In order to be sure that recording parameters like silences between tracks, normalization, cd-texts are correctly set, the audio material has to be provided as DDP.
  2. Correct CD-TEXT should be compliant with the ISO 8859-1 encoding standard.

DDP Image recipe:

  1. Download DDP mastering tools
  2. Add directory storing cue2ddp software to Windows PATH
  3. Copy master WAV file and corresponding cue file with information about individual tracks.
  4. Prepare CUE file according to following rules:
    1. All titles, artist names need to be inside double quotation sings e.g. “Artist Name”
    2. Time format should follow standard: MM:SS:ss:ff
      1. MM – minutes
      2. SS -seconds
      3. ss – milliseconds
      4. ff – frames, from range 1-25
  5. In the folder where both files are strored run cue2ddp.exe <cue_file> <folder_with_DDP_image_data>
  6. Test the correctness of image following the steps describedi in 1.
    1. ddpinfo.exe <folder_with_DDP_image_data>

For less restrictive purposes e.g. private storage the alternative is to use Cue/Bin Image.

Here’s the recipe how to do prepare Cue/Bin Image with Sox.

  1. Run your linux enviroment for audio processing tasks. (do not have linux? Just download the audio processing VM here, run it in the VM environment like Oracle VMbox or VMWare Player and you’re ready to go).
  2. Check is sox installed: sox –version
  3. Download script from github
  4. In the scripts set your own values of varilables like “PERFORMER” and “ALBUM_TITLE” etc (see sections SPECIFIED_BY_USER)
  5. Prepare WAV files. Check 44.1 kHz/16 bits format and rename all files match the pattern <track_index_with_single_leading_zero>-<track_title>.wav eg. 01-This is the song title.wav, 02-This is the song title2.wav, etc.
  6. Run the script with two arguments: Directory with mastered audio files in 16bits/44.1 kHz WAV format and output dir ./ <input_dir> <output_dir>
  7. Check correctness of generated BIN/CUE pair by creating new AudioCD project in CDBurnerXP.
    1. File->Import CUE/BIN

Continue reading Preparing Audio CD master image for CD replication on Windows

How to automatically process collection of sounds on Windows.


  1. Download and install sox.
  2. Run windows command line. “Start->Run Program-> type “cmd” and press enter.
  3. Enter directory storing files you want to process. (cd  command)
  4. Create directory for output files mkdir processed
  5. Run command:
    1. forfiles /m *.wav  /c “sox @path <sox-flags> <output_dir>\\@file”
      1. Variables starting with @ are CMD shell built-in varilables
      2. Variables in angle brackets should be specified by the user
  6. Voila. Results are available in the “processed” directory

Usage examples:

  1. Reduce bit depth to 16 bits
    1. for files /m *.wav  /c “sox @path -b 16 processed\\@file”
  2. FLAC files info
    1. for files /m *.flac /c “sox @path -n stats”



[2] Great explnatation by Hydrogen forum members about why one should always use dither when reducing bit rate.