![]() ![]() ![]() Another user with this problem had removed ASIO4ALL and the problem went away, although he had contacted them and received directions on removal." "The only thing that I could think of from here is that there's possibly some remnants left over that are causing the problem. ![]() Well here is the exact e-mail I received from e-mu support(after they asked if I ever used ASIO4ALL): If you've got anything more specific than that, I certainly want to learn about it! Please ask E-MU support what they believe these remnants are, where they are located and how exactly they interfere with their driver - and don't let them get away with weasel words along the lines of: "There is nothing specific we had in mind, you know, but there have been anecdotes of (.) and we just want to make sure that (.)"! This is called "FUD" audio applications WRT ASIO4ALL and you better leave these alone! Have you considered the option that they just might have been making nothing more than an idle guess?Īfter uninstalling ASIO4ALL 2.8, any occurrences of the string "ASIO4ALL" in the registry were not created by it and you should leave them alone! They either belong to some Windows internal caches (shell, etc.), where deleting them likely has no impact - or - they represent settings made by e.g. Well, what did the E-MU support tell you when you asked them that question? Sounds like they know something that I don't! ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |