A software that emulates various synthesizers and organs for music production.
Bristol is an emulator that allows you to use a variety of existing synthesisers and organs. Currently, the software has ten synthesisers implemented with a mixer that is currently under development. Bristol Audio software comprises of an audio engine and a photo-realistic graphical user interface known as Brighton.
To reduce audio underruns, you can also chown/chmod bin/bristolengine to suid root which enables it to use low latency scheduling. Additionally, increasing bufsize and preload can also reduce this effect, but this will lead to an increase in latency. If you are using an SB Live! card with ALSA drivers, you may need to configure a bufsize of 2048 (i.e. 512 samples), which can be compensated for by reducing the preload to 2 or 1.
Bristol can currently run 16 voices on a P-II 450, which is the default voice count. You can run any number of simultaneous synths connecting to the same engine, all with the same polyphony since the MIDI voice structures allow for dynamic assignment of sounds to voices.
You can also run the software with split keyboards, layering multiple synths on a single MIDI channel, and more. However, some of the synths may max out on a P-II 450 CPU when there is a lot of MIDI activity, for example, the DX and Explorer at 16 voices.
You can start different synths with different voice counts, allowing you to have a 16 voice hammond, a monophonic minimoog, and a 5 voice prophet running at the same time. The first synth you start will create the voice count, and subsequent synths can have fewer voices than the initial value.
Pressing 'q' in the GUI will send a quit signal and exit the app gracefully. When the last synth quits, the engine will also exit. If you press 'p', libbrighton will dump a screenshot in XPM format to /tmp/.
However, there is a lot of debugging sent to stdout, and you may want to consider adding redirects to /dev/null in the bin/startBristol script to get rid of it. When the final rev-1 is uploaded, most of this debugging information will be taken out.
To reduce audio underruns, you can also chown/chmod bin/bristolengine to suid root which enables it to use low latency scheduling. Additionally, increasing bufsize and preload can also reduce this effect, but this will lead to an increase in latency. If you are using an SB Live! card with ALSA drivers, you may need to configure a bufsize of 2048 (i.e. 512 samples), which can be compensated for by reducing the preload to 2 or 1.
Bristol can currently run 16 voices on a P-II 450, which is the default voice count. You can run any number of simultaneous synths connecting to the same engine, all with the same polyphony since the MIDI voice structures allow for dynamic assignment of sounds to voices.
You can also run the software with split keyboards, layering multiple synths on a single MIDI channel, and more. However, some of the synths may max out on a P-II 450 CPU when there is a lot of MIDI activity, for example, the DX and Explorer at 16 voices.
You can start different synths with different voice counts, allowing you to have a 16 voice hammond, a monophonic minimoog, and a 5 voice prophet running at the same time. The first synth you start will create the voice count, and subsequent synths can have fewer voices than the initial value.
Pressing 'q' in the GUI will send a quit signal and exit the app gracefully. When the last synth quits, the engine will also exit. If you press 'p', libbrighton will dump a screenshot in XPM format to /tmp/.
However, there is a lot of debugging sent to stdout, and you may want to consider adding redirects to /dev/null in the bin/startBristol script to get rid of it. When the final rev-1 is uploaded, most of this debugging information will be taken out.
What's New
Version 0.40.0: N/A