Over the last decade or so, Mixcraft has carved out a niche for itself as one of the best DAWs in the budget sector. The solution could lie with Mixcraft, Acoustica’s Windows-based DAW. The problem is even worse at the more affordable end of the DAW market, which seems particularly unfair why should you be punished for being a newcomer to music production or working with a limited budget? But if it’s so self-evident, then why is it frequently not the case with music software? DAWs in particular often suffer from clunky interfaces and unfriendly layers of menus and sub-menus, whether that’s a result of decades-old interfaces being incrementally updated or new features being added and overwhelming the user with options. “Software should be easy to use.” It’s hard to disagree with California software developer Acoustica’s company slogan. Does the latest version of their affordable DAW still achieve it? If you sent us a log file that shows the freeze in build 310, that might help us solve it for you.Acoustica’s company philosophy strives for user friendliness above all else. Most people are using build 310 with no freezing. I'm really very curious to see why build 310 would be freezing for you. Finally, we added some extra crash proofing for certain rare crashes. We also fixed a crash that involved unplugging a WaveRT USB device. There's also a crash if you mix down to flac with track markers. There's a very ugly crash that occurs in build 301 if you leave the Control Surface preferences dialog open for a while. Musicvains wrote:I'm running b301 and not b310 because b310 crashes when I'm making fast edit or changes or moves it starts with that " not responding" so I reinstalled b301 and did the same movement / edits / changes / ect, And no crashes, none of that "not responding " ,so my question is what was the whole complain of b301 crashing because ive been using it since the update came out and b301 doesn't crash, so can some one tell me about the b301crash and how it happens so I can be aware. Submit an Acoustica Support Request and attach the log file along with a brief description of the problem. Finally, click OK to go to the location of the mixcraft-log.txt file. Click in the Run box and press Ctrl+V to paste in the line from above. Press the Windows Key+R to pop up the Run box in Windows. To find the mixcraft-log file, highlight the following line and press Ctrl+C to copy it: Try installing build 310 again, and if you run into the problem again, quit Mixcraft and send us your mixcraft-log.txt file. If there is some issue that we don't know about, we'd like to find out what's going on. Build 301, on the other hand, has a very serious crash that you wouldn't like if you came across it. Musicvains wrote:So I downloaded the 7.7 b310 from 7.7 b301, and let me tell you that for some reason the latest version was crashing mixcraft, firs I was like maybe is my computer since I haven't updated my drivers since a long time, but then I realize I have 16 ram and my computer is fast with lots gb, so I uninstalled the latest versionb310 and installed reinstalled b301 and my projects started running smooth with no crashes, so I think that the latest version needs fix can you please look in to that or notify me why was b310 the latest version crashing ?Īs far as we know, there are no major problems like that with build 310.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |