I wanted to use X-WoF III with Receptor, but of course, it needs something to send transport commands so it can respond.
I installed the VST version of energyXT so it can act as a wrapper.
Open energyXT with the mixer, then set eXT to control/send whatever, and that's it, it works !
This opens a lot of possibilities to do things on Receptor. For exemple, you could use energyXT to play a MIDI file which data is then sent to one or several VSTi.
Fabulous stuff.
Fabulous news, energyXT is working fine in Receptor
-
- KVRian
- 571 posts since 14 Oct, 2004 from UK
-
- KVRian
- Topic Starter
- 571 posts since 14 Oct, 2004 from UK
No, you're right, if you click on setup or mix and go back to edit, the gui is screwed. I've emailed JOrgen about this but it's probably something Muse would have to sort out.
However, there is a way to bypass the problem. If you set eXT to do what you need it to do, you can save the setting in Receptor format. So when you go back to mix, just remove eXT and put it back. Then carry on adding and editing the other channels. Not elegant but it works, and perfect if you need to have the Receptor read a MIDI file without firing your external sequencer first.
Of course, it Muse or Jorgen could fix the problem, it would be perfect.
However, there is a way to bypass the problem. If you set eXT to do what you need it to do, you can save the setting in Receptor format. So when you go back to mix, just remove eXT and put it back. Then carry on adding and editing the other channels. Not elegant but it works, and perfect if you need to have the Receptor read a MIDI file without firing your external sequencer first.
Of course, it Muse or Jorgen could fix the problem, it would be perfect.
-
- KVRist
- 69 posts since 9 Jan, 2006
I found another "solution" to using energyXT. If you use energyXT inside Phrazor, it works allright. Since Phrazor sort of have a built in window manager the problem with screwed up windows doesn't appear.
This leads me to think that it's the Receptors host applications fault that energyXT doesn't work as it should in the first place, since it doesn't handle new windows created by plugins correctly (or at all should I say?). I'm just guessin here since I have no idea how Muse's host application is written. (I do know that it is its own window manager so to speak).
--
Olle Gustafsson
This leads me to think that it's the Receptors host applications fault that energyXT doesn't work as it should in the first place, since it doesn't handle new windows created by plugins correctly (or at all should I say?). I'm just guessin here since I have no idea how Muse's host application is written. (I do know that it is its own window manager so to speak).
--
Olle Gustafsson
-
- KVRian
- 1116 posts since 22 Apr, 2005 from Nashville, TN USA
Olle, I can't get Phrazor's GUI to show up at all on Receptor. latest version shows a nearly black screen and it useless. Is there a trick to installing it?oGG wrote:I found another "solution" to using energyXT. If you use energyXT inside Phrazor, it works allright.
EDIT: never mind. Figured it out, thanks. Got to keep that directory structure intakt, relatively speaking!
