The rest of this article is focused on only multiple global alignments of homologous proteins. Bidule is a commercial software application for the creation of interactive computer music and multimedia produced by the Canadian company Plogue Arts and Technology.The first two are a natural consequence of most representations of alignments and their annotation being human-unreadable and best portrayed in the familiar sequence row and alignment column format, of which examples are widespread in the literature. It runs on both Windows and Mac computers. īidule uses a modular structure based on a patch cord metaphor much like AudioMulch, Reaktor, Pure Data, and Max/MSP. Individual modules are called bidules (the Plogue web site states that the word "Bidule" is French for "thingy" or "gadget"). A set of bidules and connections is called a layout, and sub-patches called groups can be built within layouts and saved for use elsewhere. The program features real time audio, MIDI, Open Sound Control (OSC), and spectral processing. With other audio DAW software ReWire, Bidule can run as a ReWire mixer or device. Bidule can run standalone or as a VST, VSTi or AU plugin, and can host the same. ASIO/CoreAudio is supported for low latency audio. Parameters can be linked to MIDI or OSC input or to other module parameters.īidule can use multithread processing, and there is a beta build for discrete processing. Over one hundred modules and groups come with the software, including modules that can perform high-level math on signals.You can see Audiomulch promotes vertical signal flow (inputs up outputs down) as opposed to Reaktor’s horizontal (left-right). A clever thing in AM is that the modules are on a macro level - you don’t need to mess about with their innards. In that sense it’s not a pure visual patching environment. Having a library at the right macro level is hard. In Reaktor you’d find 3 (and lately 4) types/levels of objects - 1 the core objects (primitives e.g. Automation is left to your DAW’s timeline.Ī + block), 2 macros that don’t make whole usable instruments, 3 ensembles = instruments and effects, sometimes skinned in their own custom UI (4). The overall UI is different but the same functionality is achievable (though not as integrated as in AudioMulch). There is however a giant user-contributed library. In Max/MSP (and Bidule), in addition to the spartan interface, building blocks’ parameters are specified directly inside the blocks themselves (e.g. range 0.1 to 300).Īt the opposite end of the spectrum, e.g. Buzz (and SunVox on iOS) exposes high level instruments, and UI much like AudioMulch but with tracker sequencing.Īudulus is nice but for me has the same “danger of obsolescence” problem as AudioMulch - except if with AM you could roll out an old OS on a newer device, or emulate an AM-compatible environment in a VM, to do the same on iOS is much much harder. I’d argue there’s sufficient parallel between these and modular, so maybe it’s worth examining VCV Rack (keeping in mind the associated risks : ) with the same caveat that Automation is “outsourced” to other tools. at that point design dept starts asking why not code, and questioning having a large enough audience to justify developing such a specific product. I think an overall problem with patching environments is that they are essentially programming environments, e.g.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |