MuTools

MuTools · Post by **MuTools** » Thu Sep 22, 2016 3:42 pm

antoniaz wrote:Thanks, I will be able to check tonight about the precise message but if I remember well I got something like "VST plugin X not found".

Ah ok, then re-add it to MuLab's VST plugin database before opening the project, or browse for the plugin file upon opening the project. Nothing new wrt M7.0, right?

Anyway, new VST projects directly created with 7.1.8 do not show issues.
The issue is in reopening an older 7.1.7 project (I have just one of them).

So if i understand you well you say that a M7.1.7 project that uses a VST does not open in M7.1.8?
Well i tried that here and it just works fine.
If you would want to test it further, i have re-uploaded the M7.1.7 patch into the galaxa webfolder so please narrow it down to a step by step so i can repeat the issue.

antoniaz · Post by **antoniaz** » Thu Sep 22, 2016 4:58 pm

mutools wrote:
antoniaz wrote:Thanks, I will be able to check tonight about the precise message but if I remember well I got something like "VST plugin X not found".
Ah ok, then re-add it to MuLab's VST plugin database before opening the project, or browse for the plugin file upon opening the project. Nothing new wrt M7.0, right?

Anyway, new VST projects directly created with 7.1.8 do not show issues.
The issue is in reopening an older 7.1.7 project (I have just one of them).
So if i understand you well you say that a M7.1.7 project that uses a VST does not open in M7.1.8?
Well i tried that here and it just works fine.
If you would want to test it further, i have re-uploaded the M7.1.7 patch into the galaxa webfolder so please narrow it down to a step by step so i can repeat the issue.

I tried again with new 7.1.7 patch on galaxa. No way, it is impossible to reload properly the old project also in this case.

So I have installed 7.1.8, reinserted the VSTs in the plugin manager, exported old tracks as MIDI files and rebuilt the song in 7.1.8 with new racks and VSTs.
Apparently it was working, the project plays and can be reopened properly.
Then I tried to create another different song. Again, for some time it worked fine.
After one hour I reopened the song and I got the same kind of issue !!!
MIDI tracks are preserved but racks and effects are lost.

I really don't know what happens.
Typical messages in the log are:
00:08:39:128 Couldn't create some module(s) => OK
00:08:39:128 MpuStp[1050] couldn't load plug rack

Thanks and regards

MuTools · Post by **MuTools** » Thu Sep 22, 2016 10:12 pm

There is a new MuLab 7.1.9 for Mac 64 bit: http://www.mutools.com/galaxa/mulab-7-1-9-osx64.zip
How to install: Replace the current MuLab 7.1.8 .app file with this new version.

This new version fixes a new bug in MuLab 7.1 OSX MIDI input engine, which was also partially rewritten during the recent Mac works.
This new version should also be more solid wrt its GUI display output, and less dependent on which OSX version it is running on.

Please let me know whether there are any remaining issues.

antoniaz · Post by **antoniaz** » Fri Sep 23, 2016 6:27 am

With 7.1.9 I still cannot load projects from previous versions 7.1.7 and 7.1.8.
With 7.1.9 I created new test projects with various VSTs and for the time being they can be reloaded properly. However, I still get a single error in the log every time:

00:52:08:676 Error VstPlgnMngr[1322]

MuTools · Post by **MuTools** » Fri Sep 23, 2016 6:56 am

antoniaz wrote:With 7.1.9 I still cannot load projects from previous versions 7.1.7 and 7.1.8.

I already double-checked this and it works fine here. Maybe something on your system? I really don't know what you mean or how to repeat this. If you can give me an exact step-by-step starting from a new project how to repeat this issue, let me know and i'll retry to repeat it. If there is anyone else that encounters a similar issue, pls let me know.

With 7.1.9 I created new test projects with various VSTs and for the time being they can be reloaded properly. However, I still get a single error in the log every time:
00:52:08:676 Error VstPlgnMngr[1322]

This is another error cause by some VST plugin doing invalid threading ie calling user thread functions from a non-user thread. You should avoid such VSTs. The next version will also show the name of the VST with that error.

toxicoh · Post by **toxicoh** » Fri Sep 23, 2016 7:09 am

It's working pretty well for me. Some old VSTs didn't make the change. That's ok.

Now I'm busy making new MUX patches for old VST instruments I liked. I love how MUX works.

MuTools · Post by **MuTools** » Fri Sep 23, 2016 7:14 am

antoniaz, pls make a simple little project with M7.1.7 or M7.1.8 using a single freeware (so i can use it too) VST and open that project in M7.1.9. If that doesn't work, post that zipped project here. Thx.

antoniaz · Post by **antoniaz** » Fri Sep 23, 2016 7:08 pm

mutools wrote:antoniaz, pls make a simple little project with M7.1.7 or M7.1.8 using a single freeware (so i can use it too) VST and open that project in M7.1.9. If that doesn't work, post that zipped project here. Thx.

Unfortunately, it's not so easy to find a single freeware VST that works in a 7.1.7 project and shows issues in 7.1.9.
So far I got problems only when I reload a project using some commercial (64-bit) VSTs.
For instance, I have just created another 7.1.9 song with a commercial VST and it can not be reloaded in 7.1.9
after first saving.

But I have noticed a new thing: the issue is not occurring if I close the project (even with commercial VST) by replacing it with a new empty one and then I reopen the first VST project without quitting MuLab...

I'm starting to think that is not an issue related to incremental MuLab versions.
It seems that the quit project action is missing something so that the project is not properly saved.
Just a guess of course...

MuTools · Post by **MuTools** » Fri Sep 23, 2016 7:16 pm

When i did the test on my side i used U-he Diva + TDR Vos Slick EQ and that project reloaded fine, no issues at all. Which VST are you talking about? If the issue is only occurring with a specific VST then chance grows that it's an issue of that VST, not MuLab.

antoniaz · Post by **antoniaz** » Fri Sep 23, 2016 7:54 pm

mutools wrote:When i did the test on my side i used U-he Diva + TDR Vos Slick EQ and that project reloaded fine, no issues at all. Which VST are you talking about? If the issue is only occurring with a specific VST then chance grows that it's an issue of that VST, not MuLab.

Last failure I got was with ValhallaRoom and Ubermod, for instance.
Unfortunately, it's difficult to have a clear use case with a specific VST always showing the issue.
Please consider also my previous hint of checking the difference between closing a VST project by replacing with a new one vs. closing it by quitting MuLab. For sure I have noticed a different behavior
in terms of handling plugin information.

MuTools · Post by **MuTools** » Fri Sep 23, 2016 8:05 pm

Just tried Valhalla Room demo, all working fine here, tried all scenarios, no save/load issues at all. Anyone else having issues with Valhalla Room in MuLab 7.1?

syntonica · Post by **syntonica** » Sat Sep 24, 2016 6:38 am

Whew. Lots of things going on in the trenches. My kernel blew up again, so seeing as I just made a backup before monkeying with 64-bitness, I installed Sierra over the top of my main drive. So far, so good--all my plugins still work! (... and so does my beloved Textpander!!)

Only had one issue. Thread secd was going ape, using 20% of my CPU. I had to log into iCloud and then log back out before it shut down.

Using the CPU usage percentage on Activity Monitor to monitor a loop using 8 instances of Waves Element2 (brutal!):

32 bit: 200%
7.1.7: 240%
7.1.8: 230%
7.1.9: 220%
(all are averages as the percentages will vary by a couple of percent over time.)

So, things are getting better, but the 64-bit versions still crackle a bit when they start up. I'm not seeing the slow GUI issue I was seeing in Mavericks, so that is gone. Hooray!

I killed off JBridgeM as I suspect that may be what killed the Kernel. Will try 32 Lives to see how it acts.

I made a test with the Valhalla Room demo (I actually had it installed as I was comparing with VVV to see which I want.) and settings are being saved fine--just have to remember to save!

. I also had no issues opening the same project with all the current 64-bit versions.

If anyone knows of a 64-bit VST that can replace the brilliantly simple Luxonix LFX-1310, please let me know. Everything else I have seen is to ridiculously complicated, or not the nice wide variety of effects.

Michael L · Post by **Michael L** » Sat Sep 24, 2016 7:14 am

syntonica wrote:If anyone knows of a 64-bit VST that can replace the brilliantly simple Luxonix LFX-1310, please let me know.

Well its only right to replace a KVRDC plug from '05 with Guitar Gadgets from '14. (Its more "advanced" because it replaces Wah-Wah with Miao-Miao

).
Or the free Guitar Rig Player.

syntonica · Post by **syntonica** » Sat Sep 24, 2016 8:06 am

Okay, I just realized Activity Monitor is giving relative percentages... How utterly useless.

However, the differences in CPU usage I reported above still exist.

syntonica · Post by **syntonica** » Sat Sep 24, 2016 8:14 am

Michael L wrote:
syntonica wrote:If anyone knows of a 64-bit VST that can replace the brilliantly simple Luxonix LFX-1310, please let me know.
Well its only right to replace a KVRDC plug from '05 with Guitar Gadgets from '14. (Its more "advanced" because it replaces Wah-Wah with Miao-Miao ).
Or the free Guitar Rig Player.

Thanks! Unfortunately, Guitar Gadgets is missing the variety I want. Same with Guitar Rig Player. Looks like Pro is what I want. Since I am saving my pennies for Komplete, someday it will be mine! Someday...

Edit: I just discovered that my Predator can be used as an effects unit and has three slots and nigh 30 different effects that cover the gamut. W00t! Sorry, Lux, but you've been replaced...

Now if only the GUI could be shrunk to must the fx section.

MuTools

KVR Audio

MuLab 7.1.30