Troubleshooting: ---------------- 1) Segmentation faults and file not found errors: A likely cause of the program not running is not following the proper format in one of the input files. Remember the tracks.txt file uses spaces between parameters and the faders.txt and prefs.txt files use tabs. In the tracks.txt file, double check that a line starts with a number, then a space, then a track name, then space, then a either a minus sign, plus sign, or double plus sign, then end the line with enter. And be sure to type "end" on the bottom line (on Windows and some Mac systems) and please hit the enter key! An additional space can throw everything off such that the program will not see the correct track name to read and stop when it tries to open a track that does not exist. You will be warned when a certain audio file cannot be found and the mixer will exit. If you misspell one of the wavefile track names, the same error will occur and program will exit. A common mistake I have made is putting a space after "end" and before enter. This is easy to do because you may hit spacebar to stop audio playback in another program, but the wrong screen is in focus so you add a space somewhere in your textfile accidentally. 2) Channel errors: In your faders.txt file, do not enter commands for channels that do not exist such that may happen when reusing fader files from other projects. In other words, if you have only 3 tracks in your tracks.txt list and you put a volume entry in for channel 4, the program may return an error. Carefully make sure you have entered all the parameters for a certain operation. For example, the time entry needs three numbers: minutes, seconds, and milliseconds. If you are only entering a value for seconds you still need to enter zeros for minutes and milliseconds. It is easy to forget a parameter such as the Q value for an equalizer. Or you may mix up the order. Using the fader generator program should help you to fill in all fields. 3) File order problems If you remove a track from the tracks.txt file, your mixer channels and automation will get assigned to different files! The tracks after the deletion will be affected because the wave file sources get assigned to channels based solely on their order in the track file list. Instead of removing a track from the list, simply mute it with the minus sign after the space after the track name. Or, put a dummy file (that actually exists) in its place and mute it. 4) Not hearing changes It is easy to forget to hit "save" after you change parameters. Some text editors such as Gedit show the buffer with a * to indicate changes have been made, but not saved. Again, check that you have the correct channel assigned to the effect you are trying to manipulate. 5) Distortion in the mix If you are getting distortion in your mix file, you most likely have exceeded the 0 dB full scale limit somewhere in the mixer. If not running Mixer4 in the terminal, check your stats.txt file to see what your peak output level is. It should be below 0. Also check the level of the channel peaks and reduce the volume level of anything close to 0 dB. Check the overall output level before you get too far into a mix and keep it below -6 dB to have some headroom. See the trimming section to easily reduce overall levels if you have a lot of volume changes made already and want to easily bring down the level. 6) Text file header issues Please use only plain text files. New in version 1.091 is the ability to start a text file with "begin". Anything before "begin" will be ignored. This is helpful if a text editor is mysteriously adding some header information before your real data. 7) Cross-platform problems There may be issues when porting a text file made in Linux/Mac to Mixer4 running in Windows or vice versa. This is due to the different ways the operating systems read cues for the end of a line of text. I believe there are some utilities available to make a smooth conversion. But, it is on the list of future features to correct such issues directly with Mixer4. Therefore, I do not recommend at this time to switch platforms mid-stream on a project.