Themselve.
Amos said that they intended to delegate the work to a third party company, but not sure if they finally did it. Until I know is a develop of Moog Inc.
As i’ve said in the other thread:
after more than 2 years I can’t believe that we are so many users having troubles with the Minitaur editor/driver and they didn’t solved it yet.
But don’t worry they continue launching new products and more and more.
You should write to Gil at moogmusic dot com and ask him for an invitation to the beta forum. We are working really hard these days to finish the new firmware and editor for the Minitaur which fixes almost everything and adds a lot of new features!
As soon as we are finished, the next one will be the Sub Phatty, for which there is already a new beta firmware and hopefully next Sub 37
You should write to Gil at moogmusic dot com and ask him for an invitation to the beta forum. We are working really hard these days to finish the new firmware and editor for the Minitaur which fixes almost everything and adds a lot of new features!
As soon as we are finished, the next one will be the Sub Phatty, for which there is already a new beta firmware and hopefully next Sub 37 >
I don’t own the Minitaur presently but I think it is in my immediate future. Is Windows 7 64bit supported?
I am doing my tests on exactly that platform, the editor and plugin work fine within Ableton Live, haven’t tested thoroughly in Renoise and Bidule, the other DAWs I have installed, though.
Mind you, my use is limited to playing and sending messages from the hardware to the software and vice versa, as well as making short clips, but I don’t use the presets much.
The old hardware disconnected bug hasn’t showed up for ages already
i really hope so. Minitaur is a great sounding product (pitch range limitation notwithstanding) - but on the software side of things…tremendous promise, but the implementation, not quite a home run…
All I can tell is that the firmware and editor for the Minitaur is almost done, and that the next stop is the Sub Phatty.
Regarding the Taurus III, I have firmware 2.0.4 and it works for me, though I give it a specific use. I could try to replicate your issues and try to help you resolve them
OK… I just receive my Minitaur and I have follow all the installation prodecure (firmware update 2.1.1) BUT after installing the driver 2.23, Windows (10 64bit) does not recognize the Minitaur!!! And the editor too… In my devices manager, I have the yellow exclamation point on the Minitaur… Because the driver is NOT correctly installed… But it is!!! SO what is the problem???
Waiting for quick help!!!
You might have a red message on the Editor settings at the right. If you click on the MIDI Input and MIDI Output menus there, you can select another Minitaur port. Can you?
I have no red message… It is just that your driver is NOT working.
I really hope like other users that you will finally release a WORKING driver soon!!!
OK the new beta firmware and drivers are just… PER-FECT!!!
They will be available very soon!!! And now I can have SO MUCH pleasure with my Minitaur with Live!!!
VST on Ableton doesnt works as it says “Minitaur firmware version disconnected” : (on the settings of Live i tried all the combination with Track , Sync , Remote) and it works just if them all are disabled (this mean that i can’t use External Instruments and then the Editor works but i can’t hear the Minitaur sounds)
Actually i’m using USB + MIDI cable on the ext.audio interface :
On Ableton Track Sync Remote all disabled. (works only in this way)
Standalone still works ( i don’t use it)
VST works BUT : i can’t do automation directly using knobs from Minitaur , i must map the “FilterCutoff” on a different MIDI controller and then recording the automation , that’s not really confortable.
Editor works fine but i have that problem for the automation.
ALL THIS WORKS ONLY WITH WINDOWS DRIVERS (Moog Drivers aren’t recognized from windows error code 10)
So..i really hope the new firmware/editor will work perfectly with the only USB hooked.
OK the new driver/firmware/editor are working great now on Windows in Ableton. God job guys!!!
BUT… Now you really have to find a way to add the changing of the preset name and knobs position when doing a pgrm change in the DAW… Because it is finally the most important thing with the VST editor… Without that, what is finally the real interest of the editor VST…???
The big advantage to have the preset name and most important, the knobs POSITION, is that you really know “where” is your sound… I’m sure you are understanding me, right? And I know you can do it for sure too!!!
It is a really most important feature…
Without that, I sincerely don’t feel a real interest to use the VST editor… I can do prgm changes and automations directly in Ableton…