Autotheory took over all my MIDI device slots

[ivansc]

Not sure what is going on here, but when I open either a VSTi or any one of three different daws I have, Autotheory has taken over all MIDI device slots apart from the two built in ones on my soundcard.
I tried uninstalling the software, which is apparently all gone now, but my MIDI devices are still only showing the autotheory ones. Cant use either my Emu Xboard or my Roland TD8 kit.
How do I get rid of this?

[Mozaic36]

Go to the Device Manager and uninstall the "SBVmidi virtual midi driver". We are currently working on an update that solves this issue which affects a very small portion of users.

[frragnarsson]

More info on this.

Autotheory doesn't uninstall properly.

I've been living a nightmare where my midi devices stopped working and I got out of memory errors regarding midi in my DAW (Sonar and others).

At last I found out it was connected to wdmaud.drv and registry settings in HKLM\Software\Microsoft\Windows NT\CurrentVersion\Drivers32.

It got fixed when I deleted repeated entries like midi1, midi2, with the value wdmaud.drv, but left the entry named midi.

It seems that for all recent versions of Windows, it should be only one entry for midi, (and wave and mixer), with the value of wdmaud.drv. The need for midi1, midi2 entries are leftovers from ancient Windows versions.

When dealing with this, I uninstalled Autotheory which absolutely refuses to work now after reinstall. No midi out (to DAW) and no midi in (from keyboard controller).
Also, even when uninstalled, when I connect new hardware midi devices, Autotherory software devices pop up, AND new registry entries like midi1,midi2 with value wdmaud.drv are created.

It seems that I need to search manually for leftover Autotheory registry entries and delete them, in hope of getting it to work again.

[frragnarsson]

I've now spent several hours trying to get autotherory to work.
Won't spend more time with it.
Wasted money, far too much time and effort.
It's like diarrhea, how it creates multitudes of "devices" with each effort to uninstall (which is botched) and reinstall.

The only good thing is the midi "out of memory errors" I had have completely stopped.

[Mozaic36]

We do not advise altering the registry of your computer. We don't do anything in the registry directly actually. Windows does it automatically when installing the driver to declare the names of the outputs, etc.

You can remove the driver from the Device Manager and check the option to remove all the files.

Also, you understand that AutoTheory is supposed to have multiple devices? (AutoTheory 1, AutoTheory 2, AutoTheory 3, etc.) Each one acts as a different midi controller to be assigned within your DAW to different instruments.

We are more than happy to help you out in a more direct manner, please email us support@autotheory.net

[frragnarsson]

Thank you for answering.

I have quite an experience with Windows and have been an IT specialist for well over 20 years and work at a software company.
My experience includes among other things, doing changes to the registry, creating scripts that install and change the registry for software distribution, etc.

It may well be an artifact from your software development environment (Borland/Embarcadero?) or the installer (some have codebase going back to the 90s, I know Borland does, had Borland C in 1991 and Delphi before that), that puts this in the registry.

See for example https://www.steinberg.net/nc/en/support ... ivers.html

I am well aware that you are assigning 8 virtual MIDI devices (named AutoTheory, but also others named MIDI) (,but in device manager, you might get 8,16 or 24 devices named Autotheory, which shouldn't happen (unless it is USB hardware on different ports).

[pottering]

That's because controlling multiple instruments is one of their main features,

https://www.youtube.com/watch?v=jb7X2sVS3Lk

there is no way (at least no simple way) of doing with all the possible DAWs in Windows without the multiple virtual MIDI cables.

Also, it did not install other MIDI ports beyond the 8 "AutoTheory#" ones in my 2 systems (Win 7 and Win 10).

[DrDri]

What version of Windows are you on? Is it 32 or 64bit?

It may well be an artifact from your software development environment (Borland/Embarcadero?) or the installer (some have codebase going back to the 90s, I know Borland does, had Borland C in 1991 and Delphi before that), that puts this in the registry.

Windows does the changes in the registry when installing the driver, according to what's in the sbvmidi.inf file (which gets copied to your AutoTheory installation folder as a backup in case you want to have a look) in the "AddReg" section.

According to your link, this looks like some kind of known windows bug where the total number of devices is limited?

[frragnarsson]

I am happy to report that I got it to work.

I downloaded the virtual midi driver from http://www.springbeats.com/sbvmidi/ and rebooted.
That got the midi input to Autotheory to work. Mozaic Beats licenses the driver from them for Autotheory.
The I reinstalled Autotheory and rebooted. Output from Autotheory worked after that.

This was on Windows 10 64 bit.

I learned from previous troubles (before I got Autothery) that here is one other point that can cause problems with midi devices.
Google midi UpperFilters and ksthunk, for a registry entry that is frequently missing.

[frragnarsson]

I'd like to add that the troubles I had and others, are most likely stemming from the driver from springbeats, but not directly from Autotheory product itself.

[ivansc]

Quoting Mozaic earlier: Go to the Device Manager and uninstall the "SBVmidi virtual midi driver". We are currently working on an update that solves this issue which affects a very small portion of users.

OK I did as requested above and I dont actually HAVE the SBVmidi virtual midi dsriver showing. How are you doing on that update, guys? I am very reluctant to reinstall the full program in the hope that it will uninstall the SBV stuff as well this time.

[Mozaic36]

Inside of the Device Manager, did you look in "sound, video and game controllers"?

[Atakmuzik]

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

We do not advise altering the registry of your computer. We don't do anything in the registry directly actually. Windows does it automatically when installing the driver to declare the names of the outputs, etc.

You can remove the driver from the Device Manager and check the option to remove all the files.

Also, you understand that AutoTheory is supposed to have multiple devices? (AutoTheory 1, AutoTheory 2, AutoTheory 3, etc.) Each one acts as a different midi controller to be assigned within your DAW to different instruments.

We are more than happy to help you out in a more direct manner, please email us support@autotheory.net (mailto:support@autotheory.net)

I am having an issue of each device working on all midi channels on my computer daws with my Akai MPC 3000. I Use my MPC as a sequencer for Reason Pro Tools and Cubase and those 3 Daws are the sound modules for music and recording. Once I bring Autotheory into the equation all of the sounds play on every channel and confuses the whole song. Autotheory1 Autotheory 2. Autotheory 3 ect. does not do a good job separting midi thru.
I prefer not to use Reason Auto theory because it seems limited up against the Stand Alone version.

[Mozaic36]

Can you be more specific about your situation? You should be able to assign individual AutoTheory outputs to different instruments within different DAWs. I would imagine that the issue relates to routing within the DAWs. You need to make sure that the instruments are only receiving midi from specified AT devices.