Keep the status of the auto-save option across restarts, otherwise auto-save will only be enabled for the current session
On : Windows always stay on top of the patchbay Off: Windows only appear on top of the patchbay when double-clicking on a bidule
Enable/disable use of your operating system's regional settings which include language, units settings (floating points are separated by comma or radix), etc. Bidule ships with some pre-defined languages, if you would like to help us in adding a translation to your language, please advise us so! WARNING if some VST/AU plugins cease working, please try without this option checked, if it makes any difference, please advise the plugin authors that they do not support C locales properly.
On : Each time MIDI Learn is used, there will be a dialog asking for CC Types (i.e. 7/14 bit, relative). Off: 7bit MIDI CCs will always be used.
On : The video card will use its power to render the patchbay, potentially antialiasing lines. Off: A default "Microsoft" software OpenGL renderer will be used. If the graphics slows down, or you get audio glitching when moving things around, you may want to try both settings to see what your system prefers.
Set the path where Bidule can find your VST plugins, this only exist for the Windows version as Bidule will automatically look to the standard locations in OS X (/Library/Audio/Plug-Ins/VST and $HOME/Library/Audio/Plug-Ins/VST)
On : sorts the VST plugins by company names Off: sorts the VST plugins with the folder names in your VST plug-ins folder
Enable the ReWire Mixer (i.e. being able to use ReWire devices) feature of Bidule.
Enable/disable Bidule ReWire slave outputs to show up as stereo in the ReWire master application
Select the number of ports you want to use in the Bidule ReWire device, a port represent 16 MIDI channels, some software limit the number of available MIDI outputs (ReWire, virtual instruments, software and physical outputs) and will show each channel of each port as a possible MIDI output so you might want to set this to something lower than 4. These will usually show up as Plogue Bidule Device Bus:x Chn:y in a ReWire mixer.
Preferences for streaming file from and to disk, don't touch if you're not sure what you're doing...
WAVEFORMATEXTENSIBLE is the new Microsoft standard header created to support multichannel WAVE files and non standard bit depths. as it is new, not all editors understand what those files are at all, while others expect all multichannel, or 24bit files to be in that format. Hence why you have the choice of the following behaviours:
The sampling rate to use for the audio interface. Be aware that some interfaces don't support all possible sampling rates. You will get an error message if you select a sampling rate not supported by your audio interface when you try to use it.
This is the size of the buffer used internally in Bidule, not the one for your audio driver. The lower this quantity the lesser the latency but the higher the CPU requirements.
Size of the FFT window, all FFT settings have no effect on CPU usage if you do not use the spectral features of Bidule.
Enable this option if you wish Bidule to bypass your ASIO driver's control panel latency setting and try set it closer to its own buffer size. ONLY use this setting if you know what you're doing. (under some configuration it may just as well add more crackling).
Since some ASIO control panels (like Creative ASIO) do not allow you to set power of two buffers (32,64,128,256,512), this is often the only way to get low latency and low MIDI I/O jitter using Bidule with your driver. In any case look at the "Current Latency Details" text displayed in the GUI of your Audio Device in Bidule for more details If you get both input/output buffer size "->match", then you know you have the best settings. if you get "-> adapting", then it probably means that it can be tweaked a bit more.
When reducing the number of bits in audio samples, its better to dither. If your audio card only has a 16 bit DAC, you should think of putting this on (for a slight CPU increase)
The number of virtual MIDI ports (named Bidule 1 to x) created when Bidule launches.
When this is enabled, Bidule will add a little latency to incoming MIDI events in order to keep the timing between events as accurate as possible. This is usually useful when either using a larger (i.e. greater than 10ms) latency or using another application to send MIDI to Bidule (compared to live playing).
On : Use the names of MIDI devices as specified in Audio MIDI Setup. Off: Build the names of MIDI devices using manufacturer, model and port.
When this is enabled, Bidule will never attempts to replace one audio/MIDI device by another if the wanted one is not currently available, instead if will show only a red bidule.