Minitaur Editor - again

[Eanna]

Hi,

So, I found what is causing the bug...

The file in the installation zip called config.lua initially contains:

Code: Select all

_midiInName = "Moog Minitaur 2"
_midiOutName = "Moog Minitaur"

When I launch the editor, the content of this file is changed to:

Code: Select all

_midiInName = "Off"
_midiOutName = "Moog Minitaur"

Next time I launch the editor, the editor fails to launch. I then dismiss the "Minitaur Editor.exe has stopped working" dialog, and the file content is changed again, to:

Code: Select all

_midiInName = "Off"
_midiOutName = "Off"

The name of my Minitaur device in the Windows Control Panel is "Moog Minitaur".

So, I re-expanded the zip, and this time, made the config.lua file Read Only. The application doesn't appear to have a problem with this file being read-only. I now can reliably launch the editor.
In order to match my system setup, I changed the config file to read "Moog Minitaur" for both Input and Output ports.
Problem solved!

I do notice that the editor doesn't appear to use Midi In at all? If I move the dials on the hardware, the on-screen controls do not change. And when I change presets on the hardware, again the on-screen knobs do not move. Is that expected behaviour??

I am happy to post this answer in my original post from earlier. I've emailed myself the text of this post...

[misterpete]

No. The onscreen dials should definitely respond and move when the hardware ones do.
Patch selection and transfer is instantaneous too.
Make sure you Select IN and OUT correctly~ Minitaur USB eg as well as correct MIDI in /out channels
see excellent demo here: http://www.youtube.com/watch?v=wdK1zcwuyyU

Is that expected behaviour??

[Stuka]

Might find some helpful info here:

http://forum.moogmusic.com/viewtopic.php?f=11&t=14726