![]() ![]() However, my problem now (on my Win 7 desktop) is not MIDI but audio. I haven't looked for the audiodg.exe but will do so if I have issues with AE. I've pretty much followed steps 1-4, but I sometimes (after 3-5 minutes) just hard boot. Install USB drivers - follow instructions.make sure you have the latest OS patches and drivers installed.UN-INSTALL everything FAS - including removing the directory structures.My fall back: - if all the above fails, and you can't get it working. It works VERY WELL for me and I have not experienced the issues you are posting about here. I understand the frustration some of you are going thru, but there's often a simple solution. True, this has all been on a Win7 圆4 Ultimate OS, but it works. This process has worked for me quite well.įWIW - I have also installed the 1.29 and 1.50 USB drivers on XP SP3 PC also on XP SP3 and Hackintosh inside a Virtual Machine (VM under Oracles Virtual Box) and been able to connect thru the VM interface - over USB - to the Axe-II and load/save presets. If it still hangs there may be something corrupt in your Workspace, so delete the Settings file again and select a different workspace and see if that fixes it.Audiodg will restart itself later anyway. I have seen it cause issues with an AE start up. Note that the last folder name will be the same as where AE installed itself. On win7 that's under “:\Users\\AppData\Roaming\Fractal Audio\Axe-Edit 1.0 “ You can also delete the ttings file, but that will make you to set them up again, including workspace and MIdi In/Out settings.If it hangs again (when trying to select Midi In/Out in AE) then the MIDI interface is still locked, so go back to 3 above.During this time, the settings file can become corrupted as AE tries to write last settings used to this file. If it doesn't die, I have seen it take up to 7 mins to go away. If it is, right-click on it and kill the process! It will likely not die immediately as it's trying to release the Midi device. Start Task Mangler and see if you can see AxeEdit.exe (*32 on 64-bit systems) running.WIndows will not release the MIDI device handle for some time. IOW - you can't have TWO different software packages using it at the same midi "device handle" at the same time (even it that is two instances of AE). MIDI (on windows) by nature of the beast requires an "exclusive" device use when in use.When you install the USB drivers, there are 2 parts to it.let me try to explain how to avoid reboot's one more time: It shouldn't make any difference, but at this point none of this does.Ĭlick to expand.Ok all. I'll try uninstalling and reinstalling everything again and may even download the driver again since the one I successfully loaded on the netbook was a fresh download. Tonight I am going back in with the desktop. I read where one of the fixes in 3.03 is for intermittend USB hangs, so I'm hoping that's what that was and it is now fixed. Don't know if that was the answer, but it worked. Had to do another hard boot and this time I also rebooted the Axe. So, I installed the driver on my wifes netbook (XP 3) as well as AE and that seems to be working OK, although I had a hang yesterday in AE where I had to do a hard reboot after which AE hung when I tried to set the MIDI settings. The system was hanging when I referenced anything related to the sound/audio device set up dialogs. ![]() This time around I had problems with the audio driver. I installed a new hard drive since I wanted to upgrade that as well so it was a fresh install. I was running XP 3 on a desktop and decided to upgrade to Win 7. I had intermittent problems with Axe Edit hangs and AE not seeing the driver in/out ports. I've responed on several to weigh in with my story. There are numerious threads about USB related issues.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |