Mixbus 3.0-1970 "Interim Release"

[vanwinkle52]

GETTING BETTER ALL THE TIME (YES , I'M SCREAMING).

FYI.......BY CHANGING THE SECURITY SETTIINGS ON THE VST FOLDERS IN WIN 7 I AM NOW ABLE TO LOAD EVERY PLUGIN I HAVE.
I TOOK TOTAL CONTROL OF THE FOLDERS HAVING ANYTHING TO DO WITH PLUGINS (OWNERSHIP, AUDITING AND ALL PERMISSIONS).
AND YES, THE WAVES PLUGINS WORK BEAUTIFULLY.

GOOD LUCK TO ALL.............................CURLEY

[Tassy]

What is the SECURITY SETTINGS ON THE VST FOLDERS in win7?
Thanks
Tassy

[joegiampaoli]

Beautiful update!
Everything working as expected. Always thankful for your hard work!

[x42]

GETTING BETTER ALL THE TIME (YES , I'M SCREAMING).

I hope because of joy

FYI.......BY CHANGING THE SECURITY SETTIINGS ON THE VST FOLDERS IN WIN 7 I AM NOW ABLE TO LOAD EVERY PLUGIN I HAVE.
I TOOK TOTAL CONTROL OF THE FOLDERS HAVING ANYTHING TO DO WITH PLUGINS (OWNERSHIP, AUDITING AND ALL PERMISSIONS).

Would you mind elaborating? What settings were there before?

By default Mixbus runs as normal user (not administrator) and it needs to be able to read and execute plugins. Write permissions and ownership are not required.

It sounds like some other DAWs on your system run with administrator privileges and hence did not have this problem. Or maybe some Antivirus software got in the way somehow... preventing Mixbus from accessing them.

AND YES, THE WAVES PLUGINS WORK BEAUTIFULLY.

Cool. I'm glad you figured this out. It might help someone else down the road.

If it's just the files (.dll), Mixbus could print a warning ("lacking permissions to open ..") to prevent such cases in the future, but if it's the complete Folder things are murky. There is potential for false positives of "Access Denied" which may confuse more users than it'll help. It's very unusual to have restrictive settings for plugins.

[Ivanoff]

Try the 3.0.1970 "interim release" .
One thing I notice is Mixbus crash sometimes when I shut it down.

[x42]

Try the 3.0.1970 "interim release" .
One thing I notice is Mixbus crash sometimes when I shut it down.

1. Menu > Session > Import (show the dialog, close it again)
   
2. Select a Track in the Editor
   
3. Close the session (or quit) -> Crash
   

If so, you can work around this by de-selecting all tracks before close/quit.
This is already fixed and will be in the next interim.

The cause is the "Import to selected Track(s)" option in the Import Dialog.

[tunca]

Still not working midi import option.

[x42]

Still not working midi import option.

Could you be more specific? Which Operating System? How does it fail?

Menu > Session > Import .. select a .mid file .. works just fine.
Also drag/drop midi from a file-browser to the timelime works here (GNU/Linux and OSX).

[benny van de locht]

The current interim release works very nice on my system!
No more plugin weirdness so far, the d.a.w. reacts snappy.
Thank you for solving this!

[tunca]

Still not working midi import option.

Could you be more specific? Which Operating System? How does it fail?

Menu > Session > Import .. select a .mid file .. works just fine.
Also drag/drop midi from a file-browser to the timelime works here (GNU/Linux and OSX).

Win 10 x64.I'm trying to import Groove Monkey midi files or my own midi files but it doesn't import.And not working drag&drop.