I have to open a VST for it to work - what's going on?

[liquidsound]

This is becoming an amazing entertainent! I hardly encounter people like this. I thougth that most of the world major sickness were eredicated....

First:
From day one I never believd a single problem this guy had was legittimate. Maybe has to do with the fact that he jumped from a VCR to a PC overnight!

Second:
I still think he's here just to give hard time. Why? Either when he born they broke All the Mirrors in town and this shows his bad luck or he just looks for some...

Third:
His "virtual Problems" are so Unique that if he has chosen MuLab (out of the blue?) must be for some of the following reasons: He's totally new to software music and MuLab was the first thing he got to play with (free or low budget) or he got same OR MORE problems with other software and since no Developer would ever give him su much dedication as Jo he had to abandon them and run here.
Too bad he did not experienced XT forum... he would be smashed to pulp in a New York Minute!

Forth:
Being an artistic person (I saw his guitar work and it's quite amazing) this DAW business could be overwhelming if you have no experience to be able to do some Lateral Thinking when issues show up.

Fifth:
He did underestimate the Group Forum Thing. Here we get help not just from Jo but from everyone.

So.... Lower your Ego, open the door, participate and ASK v.s. DEMAND!

[MuTools]

That is simply not my experience of MU.LAB. I break it every day in many ways, it's a pretty fragil application in my opinion.

So what new MU.LAB issues did you encounter yesterday and today?

And I'm perfectly entitled to my opinion. Furthmore, I'm willing to explain why I feel this way to anyone that honestly wants to understand my MU.LAB experience.

I'm listening.

I think you need to get real.

1) I'm sure you will not get any money back from any software company because you discovered a bug in the software. That's why i said "get real". Are you really convinced you can do that? On what ground?

2) I you think i must get real, then wake me up. What am i missing? (i'm sure i'm missing something, but of course i don't know what, that's the essence of 'missing something') Please keep text short and essential. Thanks.

I've used MU.LAB (this time around) about a week and I had how many problems that I've posted about let alone the ones I don't post about because of the difficuilty of doing so and the poor service I get when I do. Not to mention the abuse I have to put up with in the process.

I assume there is a communication style issue between us. That's a pity. Maybe it will improve along the way?

It sounds like you don't respect my words.

I'm not sure what you mean by that. I don't agree with everything you say, that's for sure.

I meant that when i say that i want MU.LAB to be rock solid i.e. usable and stable, then you sounded to minimize/humiliate the integrity of my words. You sounded that you think you know it all and your definitions are far better than mine. Which is not a very inviting communication vibe. Maybe you're not aware of how your words sound. Anyway, as long as you have a respectful heart, then no problem. And in the end your real soul will be reflected, so no prob if you're 'on the good side'. (whatever that may mean, that's philosophy and OT here)

I've been thinking about my VST compatabilty issues with MU.LAB. Maybe I should start a thread entitled somehting like "Plugins that won't work in MU.LAB." List the plugin, describe the issues, etc. etc. That might save some other folks some time and maybe some of the plugin developers will get involved in finding out what's really happeing. Do you think that's a good idea?

The problem is that

1) there are new plugins every week so it's a huge job to check them all.

2) the existing plugins regularly get updated so you have to check them all again after each update.

What i'm certainly interested in is: If you can find overlaps in the VST plugin issues you have in MU.LAB, then let me know. I mean if the same problem is there with plugin X Y and Z, then chance is growing that it might be a MU.LAB issue.

I'LL also add, if MU.LAB behaves in an poor way when dealing with a plugin issue that it could have handled more appropriately then it's understandable that a person wouldn't be too quick to blame to plugin.

FYI: The latest MU.LAB 3.0.38 (the release version) already has an improvement there: If you browse for a plugin from within the popup menu or if you drag and drop a plugin on a rack or modular area, and the plugin cannot be recognized or is invalid, MU.LAB shows an alert. Thanks for focussing that.

[MuTools]

From day one I never believd a single problem this guy had was legittimate. Maybe has to do with the fact that he jumped from a VCR to a PC overnight!

I must counter this.

John was absolutely right focussing the 'bi-directionallity' issue and a MIDI CC issue, cfr this thread http://www.kvraudio.com/forum/viewtopic.php?t=280289

Also the fact that there was no alert when a faulty VST is dropped on a rack was worth mentioning it.

It may be true that he has less experience with music software, but that's no problem. I want MU.LAB to be easy and accessible, within the context of its flexibility. I have a feeling John had experience with analog modular synths (the real patching stuff) and that he tries to apply the same things here. Which is a very ok intention. It should work. And it does work, but as in all software (as in all human products) there are some imperfections here and there. Doing my best to resolve all imperfections. But normally one doesn't reach 100% perfection, not in software, nor in guitars, nor in...
But lets try to.

I still think he's here just to give hard time. Why? Either when he born they broke All the Mirrors in town and this shows his bad luck or he just looks for some...

He has a special communication style, that's clear. That's his right. Lets not judge the vibe of his soul before we really know. In fact, this forum is not meant to make personal judgements. I only ask one thing: Respect for each other. If someone turns out to be really unrespectful, then we'll take action. But the harshness or sweetness of words do not necessarily correlate with respect.

He did underestimate the Group Forum Thing. Here we get help not just from Jo but from everyone. So.... Lower your Ego, open the door, participate and ASK v.s. DEMAND!

+1

[liquidsound]

Thanks to put some brakes...
I just loose it when gratefulness is not in the right priority

I guy in the XT forum said that you are one the few developers he would sit with, and share a cup of coffee any time. I must agree.
Get a table for three

You have no idea how ready we are to pour good stuff on this guy if he could allow it.

Hoping for the best!

[MuTools]

Yeah, that would be nice, having a big chat with many of us on music soft and music in a nice pub with good beer and nice women (although the latter would not catalyze the music soft topic ). When, where?

[liquidsound]

Well.. Italy or Us don't have the right Pub, for the "W" company Italy would do well .

Get your business going and I am sure we will have a real celebration in a huge Headquarters Conference room and then a PUB!

[2busdriver]

I can't seem to load the following Vst's. Have these been discussed already?

Amplitude 3
Kontakt 4
Xils synth
Ultra Analog synth

There's quite a few more vst effects plugins, can someone direct me to the correct thread for solutiuons? Thank you

[MuTools]

I downloaded and installed the first in the list, Amplitude, and it works fine here.

I remember Kontakt was going fine too.

I also remember that someone reported an issue with Xils synth some time ago, but i forgot what it was about. Can you please do a search.

Tip: If you have done a 'bulk scan' i.e. scanning folder(s) full of VST plugs, and there are some plugs that result to be disabled, then also try quiting MU.LAB, restart MU.LAB, and try to 'Add' these plugins individually. I'm not sure whether this will make a difference but i remember that someone once reported how the scanning of one plugin could influence the scanning of the following plugins So can you try doing some 'fresh' rescans and let me know whther that makes a difference.

[TheGuysanIdiot]

Hi All,

In my opinion Jo has created a fantastic DAW. The DAW has been created so that we can create music and hopefully spread some joy to the people of the world.

Human nature is a complex thing. Sometimes we are happy, sometimes we are sad, sometimes we get angry and sometimes we show compassion.

We all come from different parts of the world and that is great. We only have words to communicate our views. Watching this forum over the past year I have been amazed how well people use the English language especially people from other countries.

I think it would be a good idea that everyone at least puts their country on the “Location” part of their profile (mine is United Kingdom). I think this will help us all when communicating with each other.

I said earlier that everyone has a right to their own opinion, while this is absolutely true we must all use respect at all times.

If indeed we all want this great DAW to grow. We must all support it and work together.

So when we all gather round this table to discuss issues relating to MU.LAB we all leave our swords and shields outside.

If we cannot all work together on such a wonderful tool such as MU.LAB. What chance does humanity have in general.

I offer my hand in friendship to anyone that is truly interested in helping Jo with MU.LAB. But I will make it quite clear. I will only offer my hand once.

Help me help Jo.

OZ

[2busdriver]

I downloaded and installed the first in the list, Amplitude, and it works fine here.

snip

Man, really good news! I will re-try. Thnaks!

[vinpizza]

I use Kontakt Player 4 and it work fine here.

[pljones]

Yeah, Kontakt 4 demo (PC) loads up fine here, too.

[2busdriver]

I see it now, thanks folks. The warnings about 8 plugs available on the free edition are true! I didn't realize that I had 8 plugs already in the database, but when I found the "add manually" (thanks Mutools!) it became clear about how many I had already scanned\loaded. Now I'm going to the Mu.Lab Store to upgrade to XT or UL. Full speed ahead baby!!!!

[johnjaypl]

Jo I think I'll save us both a lot of time by not responding to most of the comments. I don't think there's much to be gained there anyway.

I'm still thinking about the VST compatability thread. It wouldn't have to be perfect. Just a place to say I tried version X of such and such a plugin and this was my experience. My only hesitation is that once I get working what I want working I won't be spending enough time here to update it and if there's no other interest in that kind of thing here then it would quickly die. Of course if MUTOOLs participated in such a thing that would be a different story. Maybe with such a thread you'll be able to spot the recuring symptoms that you mentioned. I still think MU.LAB would profit from tracking down some of the VST issues.

Of all the speculations about me that I read on the forum I enjoyed this one the most.

I have a feeling John had experience with analog modular synths (the real patching stuff) and that he tries to apply the same things here. Which is a very ok intention. It should work.

I wish it was true. Although it is true that I try to apply what I imagine to be the "real patching suff" to your product. And I can't, and honestly don't really want to think about it any other way.

I don't remember saying anything worse about your product than "It's not rock solid." I assure you, there are worse descriptions to give a product.

I wish you the best, I hope you get the kinks out.

Peace,

John

[MuTools]

Jo I think I'll save us both a lot of time by not responding to most of the comments. I don't think there's much to be gained there anyway.

As you whish.

I'm still thinking about the VST compatability thread. It wouldn't have to be perfect. Just a place to say I tried version X of such and such a plugin and this was my experience. My only hesitation is that once I get working what I want working I won't be spending enough time here to update it and if there's no other interest in that kind of thing here then it would quickly die. Of course if MUTOOLs participated in such a thing that would be a different story. Maybe with such a thread you'll be able to spot the recuring symptoms that you mentioned. I still think MU.LAB would profit from tracking down some of the VST issues.

If there are VST issues, please report them here. I only ask that if one is reporting a VST issue, please try to narrow down the issue as much as possible so only the VST that is necessary to repeat the problem is kept in the session. Then also try to repeat the same issue with other VSTs. If that's positive, then please do report it, as then chance is reasonable it's a MU.LAB issue. I'll keep on supporting and helping in narrowing down issues where i can. And of course will fix MU.LAB where there is something wrong.

Of all the speculations about me that I read on the forum I enjoyed this one the most.

I have a feeling John had experience with analog modular synths (the real patching stuff) and that he tries to apply the same things here. Which is a very ok intention. It should work.

I wish it was true. Although it is true that I try to apply what I imagine to be the "real patching suff" to your product. And I can't, and honestly don't really want to think about it any other way.

Please continue using M3 as you like!

Feel free to experiment with it.

And if something is not behaving as you expect, lets talk about it here, and lets analyse what's going on.

As you did with your new topic