Mixbus, Mixbus32C: v6.2 now available with VST3 support!

[V.G.]

Big problem for me after this update! None of the projects I worked with in the previous version will start! The download starts and stops at the "Setup Editor" stage. The rainbow wheel spins endlessly. You have to end the program using Force Quiet.
A new empty project opens without problems.
Of course it's crazy to update and not make a backup before that!! But it is(((


P.S. I wrote to the support service twice! No answer.

[arthie]

is this a free update for owner of Version 6??

[Perry Warren]

I'm running Windows 10. I install all VST3 plugins to Documents\VST3 folder.

The VST3 spec mandates that plugins should be in

Code:

    C:\Program Files\Common Files\VST3\

see https://steinbergmedia.github.io/vst3_do...inlocation

It is one of the great assets of VST3 to also mandate this on Windows (previously only Mac had a fixed location for VST plugins). It makes everything more consistent and less likely go wrong.

If you really have to pick another folder, you can configure this in Mixbus Preferences > Plugins > VST > VST3 Path.

I re-installed T-Racks 5 and left all paths to the default and it now works. Kind of weird that I don't have problems with any of the other plugins and i works fine in Reaper. It appears to be something with Mixbus. Some of the other plugins as I recall didn't let me choose my own path so I just copied them to the Documents\VST3 folder and they all worked fine. I did this so I wouldn't have to define too many paths to search for plugins and also for easy backup purposes. All good now though. Thanks.

[V.G.]

is this a free update for owner of Version 6??

Yes.

[thekoala]

I have been getting a lot of waveform redraw errors when zooming - sections go missing, or wrong portions of the waveform being drawn at certain zoom levels, and sometimes when drag and dropping audio files they appear blank until I either move them or expand / contract the track height, or do something else like change zoom level or horizontal position.

Is anybody else getting canvas drawing errors in the editor? This is on Linux. Doesn't happen in previous versions.

For example, the two waveforms in the attachment should be almost identical.

   

   

[Pi_K]

I have been getting a lot of waveform redraw errors when zooming - sections go missing, or wrong portions of the waveform being drawn at certain zoom levels, and sometimes when drag and dropping audio files they appear blank until I either move them or expand / contract the track height, or do something else like change zoom level or horizontal position.

Is anybody else getting canvas drawing errors in the editor? This is on Linux. Doesn't happen in previous versions.

For example, the two waveforms in the attachment should be almost identical.

Hey thekoala!
I have random issues exactly like yours in Eindows, with my first version installed V6 and until today 6.1.22 (im not gonna update to 6.2 until I finished my ongoing projects)
But thanks to report it because I thought was just my computer...

[JiriR]

I have been getting a lot of waveform redraw errors when zooming - sections go missing, or wrong portions of the waveform being drawn at certain zoom levels, and sometimes when drag and dropping audio files they appear blank until I either move them or expand / contract the track height, or do something else like change zoom level or horizontal position.

Is anybody else getting canvas drawing errors in the editor? This is on Linux. Doesn't happen in previous versions.

For example, the two waveforms in the attachment should be almost identical.

I have already pointed out the problem of plotting the curve in the previous version. No response from Harrison.
http://forum.harrisonconsoles.com/thread...l#pid52550

[Jostein]

I have already pointed out the problem of plotting the curve in the previous version. No response from Harrison.
http://forum.harrisonconsoles.com/thread...l#pid52550

The forum is good for discussing bugs but not for reporting them. You should always mail to mixbus@harrisonconsoles.com if you want a response. More info here:

http://forum.harrisonconsoles.com/thread-1629.html

[JiriR]

I have already pointed out the problem of plotting the curve in the previous version. No response from Harrison.
http://forum.harrisonconsoles.com/thread...l#pid52550

The forum is good for discussing bugs but not for reporting them. You should always mail to mixbus@harrisonconsoles.com if you want a response. More info here:

http://forum.harrisonconsoles.com/thread-1629.html

Ben goes to this forum and often responds. After all, he inserted the notification of the new version here himself. When Ben writes to my email, others won't know how to fix the problem.

[Jostein]

Ben goes to this forum and often responds. After all, he inserted the notification of the new version here himself. When Ben writes to my email, others won't know how to fix the problem.

Of course, he writes in the forum when new versions arrive, and often else as well, that has nothing to do with the (official) bug handling.

This has been discussed several times before and the link I gave you earlier provides you with the best way to get a response. I myself wish for a bug reporting system where one can see if something has been reported before, but it's Harrison's choice to do it this way and they write very clearly on a pinned post at the forum in a bold style that Harrison customers should write to support.