8/19/2023 0 Comments Plogue bidule recording![]() Bonus: a project can have multiple sync sources, and any module/plugin can sync to any of those sources. On the other hand, it does have a “Sync Transport” module that works like the transport in any other DAW (play, stop, etc.), which includes tempo sync, and can be the sync source for any sync-able module or plugin. This is not intended as a criticism, it just isn’t a standard DAW. Though it includes modules for basic sequencing, as well as recording and/or playing back audio and MIDI, none of this works like it does in a “standard” DAW. The help file includes descriptions of all the included modules, and there are some good examples included with the program to give you an idea of what’s possible. Connectors on the modules themselves show their function/label in the status bar when moused over, which is handy. I have not tested how deep you can go with this pluginception (sorry, had to be done)Įverything connects with virtual cables, which are color-coded according to function (audio, MIDI, etc.). It can also be loaded into other hosts as a VST or VSTi plugin itself, and that plugin can also load plugins. The low level “bidules” (their word for modules) make me kind of imagine it as a sort of digital Radiophonic Workshop with modern conveniences such as VST plugins and instant recall via file management. However, it is also a rather capable DSP environment, almost along the lines of SynthEdit or Reaktor, though not quite as deep– but also not as “high level” as, say, Reason, which is still modular, but doesn’t really let you build stuff in the same way. Basic recording setup, with several inputs from an audio interface being mixed and recorded.Īt the most basic level, Bidule is a modular VST host/DAW. That’s the kind of thing I want to cover in this series of articles, and this seemed like a great place to start, especially since a new version has been released fairly recently (link below). Anyway, for some people, myself among them, I think Bidule is the kind of thing that fits into a particular niche quite well. While there are definite similarities, I don’t really see Bidule as the same kind of thing, but again, more on that later. For some that do, they might prefer something more like Reaktor. It’s not really designed to be a “press record and go” type of DAW, and not everyone has a use for a modular DSP environment. Bidule has been a regular part of my audio life for years, and although it took some getting used to, there’s really nothing else like it.īeside lack of marketing, I think the main reason this program doesn’t get much attention is that it’s not the kind of thing everyone needs, or even wants. I’m not sure how much of that will be addressed, but there’s nothing that ruins it for me, so I don’t really care either. There is also room for improvement in ease-of-use type stuff, which I’ll cover more later. Being a modular, multi-purpose kind of program though, there’s always room for more. I gather there are more planned features, but as it is, it’s more than usable, and has so many features I couldn’t possibly cover them all here. It’s still technically in beta, but I seldom come across a bug or crash (except under certain circumstances, see below). ![]() I tried changing the properties for the LoopBe30 devices, and deselected "Echo MIDI input to output" and "Is MIDI input device", but the problem still happens.Plogue’s Bidule has been around for quite some time, it seems like I first downloaded an alpha version well over 10 years ago. The difference between Maple MIDI Tools and LoopBe30 as I used them was that Maple MIDI Tools created a separate section in Composer's MIDI Device Configuration dialog for each in port and out port, whereas LoopBe30 has a section for each In/Out port (together). Luckily, LoopBe30 automatically then "mutes" the port so as to stop this loop. When I start recording into Composer, as soon as I hit a note, it plays back on the LoopBe30 virtual MIDI cable (as it should), but then Composer detects data coming through the port and switches the default input device to that "cable" and starts an infinite loop. However, I am now running into problems recording. I'm still using the same procedure for keyboard input, however. So, I installed LoopBe30 ( is their site). Now that I have a new computer with Windows 7 RTM 圆4, I had to find an alternative as Maple MIDI Tools doesn't have a 64-bit version out yet. ![]() Recording was done through a MIDI-to-USB module that hooked up my keyboard controller to my PC. I'm having trouble recording into Notation Composer.īefore my old, Windows Vista x86, computer broke, I used Maple MIDI Tools to give me virtual MIDI ports to connect Composer to various VSTs I would start up in Plogue Bidule.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |