![]() NOTE: Please don’t hijack this thread with a discussion about the VST Host.Īnyway – Organteq has 2 foot controllers: an expression pedal (which maps nicely to the Wersi’s own expression pedal) and a Crescendo pedal – which clearly doesn’t have an equivalent. NOTE: I did it to external computer because I find the Wersi internal VST host very problematical and very inflexible (and actually I really don’t like it!). SO – I was using external midi from the Wersi OAX to a separate computer to run the OrganTeq VST (same people who wrote Pianoteq. ![]() I discovered something very odd with the modulation wheel under v2.7 and noticed it was still present under V2.8 (I mentiontioned it to Wersi and they said it was deliberate). the Yamaha PSR SX 700 or the GSI DMC 122 the masterkeyboard version of the crumar mojo even expanders are doing it this way).īut as far as I know Uli Wildhack is working on a smart solution… On one hand the original Wersi pedal can not be connected to the MIDI in 1 or 2 of the OAX System on the other hand a standard MIDI pedsal can not be connected to the internal MIDI bus!Īny other keyboard that I know does it the same way (e.g. This is the one that controls the lower manual and the pedal as well (usually they have Sub-D connectors). the if you are using an original Wersi pedal you have to connect it to the internal MIDI bus. If you don´t like the selected sound you could either change the sound (PRG change) via the organ interface or via your controller (e.g. The only thing you need to control the bass (in this example) is to use the correct MIDI in Channel (usually 3) and you are able to control the default setting. I understand the idea of Uli Wildshack but in my opninion there is no reason to send this sequence: If you start up OAX there is a default setting loaded. a midi pedal send a volume (control 7) and a PRG change? I got the same response like you from Uli Wildhack.īut there is one thing you should be aware of. Was not sure how to start a new forum for this ? Was wondering if anybody else had this problem, maybe Wersi have changed the design slightly as the Top part is a lot older than the bottom or even maybe the speakers have been replaced with bigger ones? I’ve solved this by installing 4 rubber feet to lift it up. Which when put on top of the lower keyboard just touch the back of the lower keyboard jamming the keys. But the OAX1 comes with internal speakers which are fitted underneath the top keyboard and stick out about 1/4 of an inch. One small problem I do have is Allens have given me a lower keyboard module which you stand the OAX1 on giving 2 keyboards which work fine. I have installed the separate swell pedal on the top of pedal board which I find is better than it sliding all over the place. Not sure if its worth the trouble for 4 extra notes? So far I’ve only used my Genos to play the Wersi pedal sounds to see if possible, as I was thinking of building a 2 octave pedalboard.īut Allens Music have provided me with a used 17 note pedalboard instead of the small 13 note. ![]() MIDI IN 2 -> plays on the style or sequence channels. And if you play a MIDI file from an external sequencer, the data such as PRG change and volume and expression pedal, etc. But 16 MIDI channels with piano would rarely match customer requirements. How should the channel know which sound to play. Note: the tracks only play if a PRG change command and controller 7 have also been sent. MIDI IN 1 -> 16 channels -> in the extensive data list you can see the PRG change commands and the assignment of the drums, which these days often no longer correspond to the GM standard! How are you sending data to OAX? Are you using a DAW or another keyboard? Either way works – just which you prefer or find easier? In my earlier post I mentioned loading a sequence first (which would also send controller 7’s and program change. The simple answer is you need to send control 7 (volume) and a program change to “load” the internal MIDI channel. Derek – Here’s the response from Wersi to my question.
0 Comments
Leave a Reply. |