Mixbus, Mixbus32C; v6.1.22 Update now available

[Dingo]

Hi,
I think I got the same issue.
Snare sent to a drum bus. When soloing this bus, I could ear snare + guitar whereas the "Spill" button confirmed that only snare was assigned. No "Master" or any send engaged on guitars.
I solved the issue by clicking randomly on "Isolated" or "Soloing" buttons on the monitor section...

@parabellumartstudio and @fmiller it seems as though you have solo isolated a track by mistake.
Have a look at the Solo Isolate section of the manual.

[sunrat]

Hi,
I think I got the same issue.
Snare sent to a drum bus. When soloing this bus, I could ear snare + guitar whereas the "Spill" button confirmed that only snare was assigned. No "Master" or any send engaged on guitars.
I solved the issue by clicking randomly on "Isolated" or "Soloing" buttons on the monitor section...

@parabellumartstudio and @fmiller it seems as though you have solo isolated a track by mistake.
Have a look at the Solo Isolate section of the manual.

I was rather confused by the solo options when first using MB. Couldn't work out why effects/busses would be soloed along with a channel. Turned out that's what SIP (Solo In Place) does. To hear just the channel you need to switch to PFL/AFL. Only applies if you use Monitor section.
I'm as bad as anyone when it comes to reading the manual as a last resort, but the extensive Mixbus manual is well worth consulting first.

[fmiller]

Hi,
I think I got the same issue.
Snare sent to a drum bus. When soloing this bus, I could ear snare + guitar whereas the "Spill" button confirmed that only snare was assigned. No "Master" or any send engaged on guitars.
I solved the issue by clicking randomly on "Isolated" or "Soloing" buttons on the monitor section...

@parabellumartstudio and @fmiller it seems as though you have solo isolated a track by mistake.
Have a look at the Solo Isolate section of the manual.

Yes, I'll have a look at the manual, but I'm pretty sure that during my issue the blue "Isolated" button was not blinking as it does when one of the tracks is Solo isolated.
Anyway, I got the problem only one time. It must be my bad.

[rdesanti]

Got this in the email TODAY. Aug 11/2020
Install works perfectly! No bumps or bruises! LOL

Dingo edited to remove server links

Note: Although Mixbus32C can open prior Mixbus sessions, we highly encourage you to finish old projects using the version of Mixbus that you started them in.


Thanks for your interest in Mixbus32C!

We are committed to providing a great experience for all of our users! You can ask questions about Mixbus at our User Forum, or through our support email address (mixbus@harrisonconsoles.com).

Connect with us online through popular social media networks (Facebook, Twitter, Google+, and YouTube) to stay up-to-date on the latest Mixbus developments."

[JiriR]

I compared the drums to the grid using the Rhythm Ferret function and now I'm trying to combine the regions. After calling the Combine function, the Mixbus falls to the desktop.
   

Edit: So I figured it out. The tracks must be combined one after the other, each separately. A little tedious ...
   

[Pi_K]

JiRir! Yes!
Some months ago I reported that bug myself.
Also, at least in my computer, once I start working on a full song making the separations of about 10 drum tracks, the first section of the song lets say works ok...
But once I move forward with other sections making of course the whole project with a lot of regions I get a reeeeallly slaggy almost unusable system...
Every youtube video tutorial of R. Ferret shows of course how to use it in small sections...
Harrysin replied that the couldnt reproduce the issues in their computers but your post proves my point...
The combine issue is tedious yes and is funnt because at least I see how the system becomes more operational once Im combining the last 3 or 4 tracks. So has to be the code and how handles I dont know, memory, resources, Im not sure...

[JiriR]

And that's not all. After performing Combine, waves draw error curves at different magnifications. It is still the same place in the arrangement. Sound is everything is fine. I deleted the "peak" folder to recreate the waveforms, but the bug still appears in many places.
               

[Pi_K]

But you zoom in and you start to see it correctly?
It happens to me as well.
I started with V6 and it persist apparently.

[JiriR]

But you zoom in and you start to see it correctly?
It happens to me as well.
I started with V6 and it persist apparently.

It's only right in the first picture. All other images show an error when magnified.
And yes, with the track zoomed in vertically, it's correct for a while until the time zoom changes.

---

Next, let's say the peculiarity of v6 - when zooming, the load of all 4 processors (!) Flies up to 90% for a while.
I have i5-6300HQ processors. Am I wrong about something? For example, in Presonus Studio One, nothing like this happens.

[Pi_K]

It has to be the coding...
both things: the Ferret regions beeing combined and this kind of non-working wave graph issue I detected in V6, that is my first one.
Im using Mixbus now with the option "every processor except one" but apparently no mather what PC you have, the bug still persists (see my signature, I have an old computer but we are having the same behaviour)
I really hope Ben or someone from Harrison's can read and make some patch for us...

But (Im not a software engenieer) if this is in the code, as I read were rewriten in Version 6, we're in trouble