Mixbus quantizing5/5/2023 ![]() ![]() Being able to adjust multiple sources or channels with a single group fader is one of the bigger advantages to having multiple busses at your disposal. A live sequencing workflow in Mixbus still leaves a lot more to be desired. Mix Bus is a term used in the live sound and recording worlds and is commonly associated with output channels/busses as discussed above. Or, if we can recreate the crash here, we can implement a fix inside Mixbus so the crash won't happen in the future. There are plans to add this for a live workflow (quantize for the next iteration when looping) but I don't know about the priority. Once you've recognized the cause of a crash, we can help you consider how to avoid it. If you are a new user to Mixbus, then "all" of your plugins should be considered new. Generally the only way to detect this is to take notice of the performance when you start using a new plugin. A plugin that corrupts the program memory can result in very odd behavior or crashes in Mixbus. This might include:Ī) A sequence of operations that we didn't anticipate: For example, we recently found a crash when you try to use the gain up/down shortcuts, while you are dragging a selected region in the editor.ī) An automatic event such as Mixbus's auto-backup (every 2 minutes), or a virus-checking scan that is somehow triggering an unexpected crash.Ĭ) Plugins: plugins are third-party code that we load into our program. ![]() They usually come shortly after an operation that, over time, you can learn to recognize. Generally speaking, crashes aren't random. We can send a "debug" version of Mixbus that will provide us a more explicit report, but (a) it takes some extra steps on the user's part, and (b) sometimes it still isn't clear how to fix the problem. So it can be hard to determine what is causing the crashes on Windows. Unfortunately, Windows does not provide us the same level of crash-reporting and troubleshooting that Mac does. This will usually (but not always) tell us exactly where the crash occurred, whether it is inside Mixbus itself, a plugin, or the OS. To do that, please click "Generate Report" when Mixbus crashes, then click "Show Details", and then select-all/copy/paste the text of the crash into an email for us. On MacOS, you can generate a "crash report" which can often help us pinpoint the cause of a crash. But we can't guarantee perfect operation on every setup. We've worked very hard to eliminate them. ![]()
0 Comments
Leave a Reply. |