Do the tests yourself, or at least double check my data.
Reminder, don’t trust dweebs on the internet.
#Mixbus 32c license series#
If you want to see how each DAW stacks up relative to each other, please check the other articles in this series for a relative comparison. Your audio device and system may have different latency numbers. REMEMBER - These numbers only mean something relative to each other on my system. I have added additional testing without the limiter this round. Previous tests were done with Limiter On, because that is the default state of Mixbus when you open a project. Kontakt will no longer run on my machine and I have no interest in debugging it. Hardware is unchanged.įor this round I used MSoundFactory’s Drum Sampler. I’ve heard that Mixbus 7 might have better latency, so let’s start it off with the elephant in the room: Mixbus latency. Report Id: cff0410f-61ec-49f0-b5eb-4bd10540a555įaulting module name:, version: 2.64.1.0, time stamp: 0圆2eb3df7įaulting application start time: 0x01d8c7298838b61eįaulting module path: D:\Program Files\Mixbus8\bin\ 7 is out and I’ll be exploring the new feature(s) in the next 4 posts. Report Id: 3500f31a-e667-42e0-a921-e57e0baf33d0įaulting package-relative application ID:įaulting application name: Mixbus.exe, version: 0.0.0.0, time stamp: 0圆2fdb8e7įaulting module name: KERNELBASE.dll, version: 1.2075, time stamp: 0x923a0837įaulting application start time: 0x01d8d600cca591fdįaulting application path: D:\Program Files\Mixbus8\bin\Mixbus.exeįaulting module path: C:\WINDOWS\System32\KERNELBASE.dll To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.Īpplication Path: D:\Program Files\Mixbus8\bin\Mixbus.exe The program Mixbus.exe version 0.0.0.0 stopped interacting with Windows and was closed. Here are some excerpts from event viewer:
#Mixbus 32c license install#
Install prefix: /home/builder/win-stack-w64Ĭ compiler flags: Ĭ++ compiler flags: System type 64-bit operating system, 圆4-based processor Processor Intel® Core i7-3630QM CPU 2.40GHz 2.40 GHz Now running latest win10 with all updatesĮxperience Windows Feature Experience Pack 120.2212.4180.0
Getting pretty frustrated with this, and I have 8 new projects on the go so cant exactly roll back to version 7 now.īeen running mixbus on this machine just fine from about version 3 or 4
#Mixbus 32c license update#
are there some logfiles I can send to support? Is there an update coming soon? I've had like six crashes a day for the last week.
600MB ram (16 gigs in the machine!), 18-20% CPU 'running" for COUPLE OF MINUTES TILL I KILL THE PROCESS. Not exactly CRASHED, more just hung - CPU running about 18%.Ĭould not get any response from desktop or anything else until I ctrl-shiFt-Esc to bring up task manager ( where i notice the two MB processes running). No virtual instruments, only one (mixbus brand!) reverb effect on one mixbus. Just a few minutes ago, it crashed as I tried to export a stereo file of a 6-track mix. MixBus 7 was working just fine - and nothing else has changed on the machine.įrequently crashes as I drag a clip from one track to another in the editor window.Ĭrash as in BOOM! out go the lights, the process terminates unexpectedly So, I recently pay for this upgrade, and its crashing all the time.
0 kommentar(er)
