We can't take responsibility for anything, because we don't know what's happening yet. I appreciate your prompt reply,but can we move onto a more realistic solution(such as having someone from the development team,work on an actual bug fix)? You now have two Mixcraft users with the same problem.so what is the next course of action(aside from beating a dead horse)? That said,can Acoustica now start taking responsibility for this mess(rather than trying to assign the cause to M-Audio).please? Yes.the configuration in my M7 is exactly how you described it should be and perhaps I was not clear enough,but I did mention previously,that I had the latest driver installed(meaning that I downloaded the latest driver from M-Audio's website.) I wish it were that simple,in that I just overlooked a simple step.but I am afraid not.Like I had said,everything was working fine when I set everything up initially(but after I closed that instance of my project & opened it up later).everything went haywire. Why? Because audio hardware often ships with outdated drivers, and sometimes Windows itself installs outdated plug and play drivers. In ASIO mode, look at the ASIO device setting and make sure that you've got the M-Track's ASIO driver selected.Īlso, make sure you've got the latest audio drivers for your M-Track Plus installed: M-Audio Drivers & Updates Search. Go into Mixcraft's sound device preferences (File Menu > Preferences > Sound Device) and make sure you're using ASIO mode. I'm sorry to hear that you're having problems with your M-Audio M-Track Plus! Let's see if we can get this working properly. I just dropped a total of $380 on a midi controller keyboard & an audio interface and I just can't afford to buy another DAW right now(and honestly,I really don't want to resort to considering another DAW).because I love everything about version 7.but these bugs of yours are getting out of hand. I'm serious.charge whatever you want for the next update to fix this issue and I'll pay it(just fix the damn bug before I completely lose my sh*t.) Is there a funding problem?Do you guys need more money for research and development?If that's the case,then I will gladly fork over another $89(if that's what it takes to get this issue ironed out).believe me. Please explain to me what is going on here.will you?You guys have been around for over a decade.so why is this crap still going on? I don't understand Acoustica at all.I mean.you spent 2 years developing version 7 and you managed to fix the 3rd party VST-related instability issues.but then you create new havoc in the Sound Device area? I made one fatal mistake though.as I ran the trial version b-e-f-o-r-e I bought an audio interface for it(but then,how could I have anticipated this mess)? I wasted $74 on Mixcraft 6(because the incessant crashes were impossible to fix) and I did not even get the satisfaction of getting a discount on version 7(because apparently,my account info is lost in the abyss).but once I discovered the development of version 7,I was impressed and I decided to give Mixcraft another chance and when I ran the demo of M7,I was convinced that Acoustica had turned a corner. In other words,I can't play anything back and in fact,I can't do a-n-y-t-h-i-n-g in Mixcraft,without those error messages constantly popping up. Mixcraft will not run at all,as it's gone completely haywire! While I do realize that any DAW,will have some minor bugs upon it's initial release.well,this is no minor bug by any means and it's so severe.that it has rendered Mixcraft completely useless! I then closed the application and opened it up yet again and now,I have the info on these settings,but Buffer settings is locked on 256. I then went into the preferences area and there's no information on the Sample Rate & Buffer settings(as it was blank). I just received my M-Audio M-Track Plus(with the latest driver installed) and actually.upon the initial installation,everything was fine.but after I closed my project and opened it again later,disaster struck and I mean UTTER disaster!Īll of a sudden,I received 2 error windows,which are "Unable to open playback device" and "A hardware change has been detected" I wonder if M-Audio or Avid will ever update those drivers? Wow.you know.I have been wondering why music retailers haven't been carrying Mixcraft 7 and now I think I know why.as it seems that Mixcraft is just a cleverly disguised computer virus! No doubt it will arise again when someone else complains about it though. It's not as though I need to keep constantly accessing it anyway. Ianpb wrote:If that's the only way it will work, then so be it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |