Ok, lets get started with setting things up. You will need to start up your virtual midi application before you start up Live and Bidule, and create at least 2 virtual in/out's. On windows you will need a utility like "midi yoke" that will create virtual midi i/o in Live and Bidule. When you start up Bidule on osx, it creates 4 virtual midi in/out's. You can download the latest version at This tutorial is made with screenshots out of osx. Plogue Bidule is a modular environment that allows you to do some things Live 4 can't do (yet) We will set up a 16 step sequencer in bidule, that outputs to Live.īut first things first. In this tutorial, we are going to do something simple. You will always find something inspiring in Bidule and Live 4 working as one. And for those people it is pretty much the same experience as for me. It became clear that not many people where too enthusiastic about the idea of running a second application. Both lists must have the same number of items in them.After answering a lot of posts where i ended up suggesting Plogue Bidule as a solution. If you decide to edit the pedal controller numbers list **you must edit the lastdata list also**. (How much I don't know - I haven't benchmarked anything here). Also, if you have only 1, 2 or 3 pedals, you need only put 1, 2 or 3 numbers in that list - it will also make the script a little faster. If you prefer to use different MIDI controller numbers, use can substitute them in the bracketed list. Second, the script hard-codes the standard MIDI controller numbers for pedals. You can change this to suit - operate the pedals and observe in Pianoteq's MIDI monitor window what values precede the rogue 127's. The identifier 'bounce' in the script sets this as an upper limit. It turns out that rogue 127's can be preceded by numbers other than 0 - for my combination of keyboard/pedals that can be as high as 15. The first thing to note is that it is worse than we thought (!). If (lastdata > bounce) then - but probably ok if outside bounce limitĮlse - in bounce range -> assume pedal is up unfortunately 127 may be emitted when the previous value is > 0 and 0) then - it's one of our pedals method: check data stream for the successive values of 0, 127 (ie 'impossible' operator input) specious 127 controller data values generated when pedal comes up to rest position fix Roland RPU-3 pedals to suppress rogue output ![]() Despite the version number, this script seems stable. VSTLua scripting can be done in any plain text editor, and loaded into the client as described in the link above. VSTLua is loaded into an instance of the Cantabile Lite VST host, and Pianoteq is loaded into the host's rack immediately following, so that Pianoteq gets the MIDI stream via VSTLua. The script is loaded into the VSTLua client (available here - ). The solution below uses a script in LUA to do that. In fact, rather than reject it, I retransmit it as a zero value (just to make sure!). ![]() We can then check if a 127 is likely genuine (previous value large) or unlikely (previous value small), so we can reject a 127 after a 0 as 'impossible' operator input. The problem is that we need to distinguish 127's that are genuine data from those that aren't, which means knowing what the previous values were. Unfortunately it doesn't address the problem, is messy, and in different set-ups could be a hidden gotch-ya. This is fine for Pianoteq, as you can have it listen on a different MIDI channel, so the 127's are ignored. It's rather confusing, and I succeeded only in converting the MIDI channel number of the pedal controller data value of 127 to another MIDI channel. One solution I devised uses virtual MIDI cables to route the MIDI data into the MIDIox utility (Windows). ![]() Not only is it a great treat in Pianoteq (with sostenuto, Satie sounds wonderful), but it has potential as a versatile MIDI controller for other instruments (such as Sample Modeling's tasty Ms. The RPU-3 is a nice unit, capable of transmitting the full range of values. So if the pedal is controlling a piano sustain, suddenly the sound goes to max sustain just when you lift your foot off. What happens is that when the pedal is lifted off and the MIDI data values approach the limit (0 or 127), inexplicably a rogue value of the other limit (127 or 0) is sent. I have a couple of other solutions to this issue, probably due to the electronics in the VMK188plus not de-bouncing the pedal properly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |