VST2, 32-bit: Resizing doesn't work properly in Mixbus

[macay]

When I load the plug-in in Harrison Mixbus, the resizing doesn't work properly. This happens on initial loading as well as on loading configurations (window is too small).

Please let me know if you need more info.

Windows 7, 64-bit Harrison Mixbus 2.5.1 (32-bit) ScopeSync 0.2.2

[bcsharc]

We've noticed some issues with the window sizing in Cubase which have been fixed in the latest commit. Any chance of a screenshot to confirm if this is a similar problem?

[wellis]

Unfortunately, it looks like Harrison have stopped offering a demo of Mixbus, which means we're not going to be able to debug for now. Hopefully the latest update that sharc mentioned will have helped, but I know you were going to try that in Studio One anyway.

[macay]

Here you go. The screenshots are in same the order it appeared on the screen.

This is how it looked like after initial loading:

Slider demo:

BCF2000:

[wellis]

That's quite weird, that it shows some of the window! If you get time, it would be great if you could experiment with editing the .layout files to change the main component width to see what happens. For example, in the BCF2000.layout file, you'll see the following lines:

<!--Main Component--> <component backgroundcolour="ff2d3035" lfid="default"> <bounds x="0" y="0" width="674" height="732" />

If you open the file in Notepad, change the width value, to "1000", for example, save the file and then hit the reload configuration button (which you can just see the edge of, next to the load configuration button), what happens?

[wellis]

P.S. How did you manage to load the Slider demo with the load configuration button being hidden?

[macay]

Mixbus lets me resize the plug-in window manually, so that I can make the buttons visible. That's why this issue is not a biggie actually. Just annoying :) AFAIK the VST support in the Windows version of Mixbus is still young, so it might be something on their end?

Setting the width parameter in the BCF layout to 1000 and hitting the reload button afterwards, resizes the window so that everything is displayed.

[wellis]

That's very strange, Mixbus must be applying the wrong size to the window then, as the other DAWs are sizing to fit correctly. Maybe we can report it to them after we've got to a public release.

[macay]

Yes, I can do that.

[wellis]

I just managed to test this using Mixbus running on Windows 7 64bit and had no sizing issues with the latest version from Github (https://github.com/bcmodular/scopesync/raw/7b884acf323b9e70bd0b4223be9cb16f25926793/VST%20Plugin/ScopeSyncVST.dll). Could you check that you've tried with that version?

[macay]

Well, it worked, but only once... So let me elaborate.

I had to replace the previous version of the plug-in while Mixbus was running to get it recognised (without any loaded instance to to able to exchange the dll file). Then, when I loaded a new instance and opened the plug-in window, all was looking fine.

After restarting Mixbus, the plug-in wasn't showing up in the plug-in list anymore, though. Resetting the black list and rescanning gave me an error: [INFO]: detecting VST plugins along C:\Program Files (x86)\VST [WARNING]: Cannot get VST information from C:\Program Files (x86)\VST\ScopeSyncVST.dll [INFO]: located 1 VST plugin files and loaded 0

On loading a previous session with an instance of scopesync I got this: [ERROR]: Found a reference to a plugin ("1935897465") that is unknown. Perhaps it was removed or moved since it was last used. [WARNING]: insert could not be created. Ignored.

When I put back the previous plug-in version, all is fine again. Weird.

[wellis]

Well, I'm about to do some testing of a new version that's plenty different again, so let's see how I get on with that.

[wellis]

Interestingly, I get the same problem when switching back and forth with the version I linked above. However, I don't have the same problem with the version I uploaded last night. I'll keep an eye on this as it gets closer to the next release.

I wouldn't recommend trying the latest Github version just yet, as it's not compatible with the old configuration files and will need a full release to use.

[wellis]

@macay Was this still an issue for you with the most recent release?