Mixbus, Mixbus32C v8.2.170 update now available!

[undertryps]

I actually have to downgrade to 8.2.66 once again, due to vst3 issues.
It seems like the same vst3s that weren't working for me in the previous build (basically u-he plugins) now change parameters after a session is closed and then reopened.
This means that every time I open a project I've been working on, my compressor settings are wrong (changed from what they were the last time) and my synths sound crazy.
It happens in both old and new projects.

Is anyone else experiencing this?

Just tested u-he Triple Cheese VST3 on Intel build (8.2.170) and am not finding this behaviour, settings are accurately saving and re-opening for me.

Hi,

I also tested on win 10 u-he Triple Cheese VST3 (rev 3898) mixbus 32c (8.2.170) and I have no sound that comes out of the synth, better when I change parameter values they are not kept. I do not understand that it works with you.

[Dingo]

@ undertryps I downloaded Triple Cheese latest version, installed, did a plugin update scan, made sure I was monitoring input and tested using the Virtual Keyboard (just to reduce external variables).

I get sounds outputting and all my settings accurately save and recall.

On macOS Intel I am running VST3 version 1.3.0 rev 12092  x64 using MB32C v 8.2.170.

[undertryps]

@Dingo yes indeed after Triple cheese update, all works. But why this bug on the rev 3898 version with Mixbus when it works with another daw? So you always have to update all the plugins with Mixbus?

[krans]

Does this mean that the vst3s behave as they should in v8.2.170 if you/I just do a new plugin scan?

[undertryps]

Hi, 

For me it worked. 
Update plugins + scan or not (I did not scan after the triple cheese update)  because I already had it I guess, and it works. 
But other plugins require a scan maybe. 

In any case must try!

[Dingo]

If you update an existing plugin or add a new one you should do a 'Discover New/Updated' - if you are having issues with plugins missing 'Re-scan All' is a useful option.

[krans]

Does this mean that the vst3s behave as they should in v8.2.170 if you/I just do a new plugin scan?

For me (on Linux) this doesn't change anything.
Even with TripleCheese, which has been mentioned here as a testing synth.

I can make a MIDI sequence, simply open a preset in TripleCheese, close the project, reopen and it sounds completely different!
Crazy different! Like there's no doubt something happened along the way.

So I'm switching back to 8.2.66 even one more time.

[Dingo]

@krans, thanks you are correct - Triple Cheese is not recalling 100% correctly.
Mea culpa - I fooled myself whilst testing.. whilst the majority of the controls appear to be correct the Envelope and LFO controls are not per the presets I have recalled. Too much cheese...
However other VST3 instruments that I have do recall 100% ... so not sure where the issue may lie ?

[undertryps]

hi,

Same on my side on win 10 with triple cheese, I had not tested the recording part sequence midi, closing project and reopening. Other plugins have the same problem, example vst Rhodes, arturia...

[Patrik]

one other issue that bugs is that text is not as sharp as before, I sent Harrison support screenshots. its like less clear and sharp. ia have a hi res display so I did notice right away and 8.1 looks more crisp

I have the same problem with less sharp text when upgrading to 8.2.170 from 8.2.66 . Im on Mac OSX 10.13 and 10.14.