MuTools

D-Fusion · Post by **D-Fusion** » Thu Oct 04, 2007 2:55 pm

muzycian wrote:
D-Fusion wrote:That sounds like a good idea
And maybe a load save Preset/Bank button on the gui editor also.
Oops, which idea?

Maybe best to include the quotes.

Is it about the click-on-rack-slot strategy?

Ooops

Yes it was about the double click on rack idea

I was a bit in a hurry and thought that i did quote it. he-he

Fuzzbeard · Post by **Fuzzbeard** » Thu Oct 04, 2007 3:29 pm

muzycian wrote: What about this idea:

When a single (or double) click on a rack slot:
Then when that slot is empty -> choose plugin
When that slot is not empty -> edit the plugin

And do you think it would be better if there is a "Edit" also in the context menu of the plugins?
Maybe it should be there, logically, but don't want to overload the menus if not necessary.

Hi Jo

I like your first idea.

I don't think that you'll need to include it in the context menu, especially if single clicking will edit the plugin.

Cheers...

muzycian · Post by **muzycian** » Thu Oct 04, 2007 5:27 pm

I just focussed on CM Vocoder.

It doesn't want to load here in MU.LAB.

But it neither wants to load in Live 6, neither in Audition 1.5.

Strange as it loaded on my earlier system.

So i used Dependency Walker (google) and it told me that there were missing files for CM Vocoder.

Can everyone where CM Vocoder crashed in mulab beta a please check wether it loads in other hosts.

Thanks.

pljones · Post by **pljones** » Thu Oct 04, 2007 6:05 pm

muzycian wrote:So i used Dependency Walker (google) and it told me that there were missing files for CM Vocoder.

Mmm... DWMAPI.DLL missing as a dependency of IEFRAME.DLL (->ShDocVw.DLL->Shell.DLL). CM Vocoder is fairly old (mine is datestamped 02/June/2004, ties in with (C) date). I guess bit rot has set in... From a thread here:
http://episteme.arstechnica.com/eve/for ... 4009191831
Oh, and here:
http://forums.microsoft.com/MSDN/ShowPo ... 6&SiteID=1
it sounds like IE7 is the culprit.

DaveL60 · Post by **DaveL60** » Thu Oct 04, 2007 7:22 pm

jens wrote:
muzycian wrote:it's not "fun".
Wrong!

(depending on what kind of a person you are... )

While I'm not beta testing mu.lab, I'll definitely agree with Jens on this one: you get the new toys first and opportunity to really influence where something goes. It can definitely have it's exasperating moments, but it's also fun.

DaveL

Bonteburg · Post by **Bonteburg** » Thu Oct 04, 2007 7:47 pm

Mulab was behaving weirdly just now - being unresponsive, (couldn't press the play button) and slowing down Opera until it almost ground to a halt. Managed to shut down Mulab "the nice way" and zap! Opera springs into life again.

VSTI chosen: Expert Sleepers Crossfade looper.

Marco

Bonteburg · Post by **Bonteburg** » Thu Oct 04, 2007 7:57 pm

oops!
Managed to crash it now - same VSTi, tried to load my "empty" preset (it's a sampler). It kind of works in Luna, albeit with an error message.

log

toxicoh · Post by **toxicoh** » Thu Oct 04, 2007 8:38 pm

2) Not all of my VSTs are being detected.I use a small set of 7 synths and 6 effects. Many people here would use the CM VST packages from the DVD. Ohmygod101_vst2carbon isn't being detected, even after renaming it adding .vst extension. It's in the same folder as the others that are all detected. Trying to add it manually from the VST Manager didn't work either.I just checked, Luna is the same.
Did it open in LUNA?

No, Ohmygod isn't seen in Luna either. Also not in Live 5. It does date from early 2003. Interestingly it doesn't have a vst icon in OSX. Maybe it's just too "old"?

muzycian · Post by **muzycian** » Thu Oct 04, 2007 9:28 pm

Bonteburg wrote:Mulab was behaving weirdly just now - being unresponsive, (couldn't press the play button) and slowing down Opera until it almost ground to a halt. Managed to shut down Mulab "the nice way" and zap! Opera springs into life again.

VSTI chosen: Expert Sleepers Crossfade looper.
Marco

Marco, did you try mulab on your mac mini?

How did it run there?

The 400 Mhz system might be too weak for this...

muzycian · Post by **muzycian** » Thu Oct 04, 2007 9:35 pm

toxicoh wrote:

2) Not all of my VSTs are being detected.I use a small set of 7 synths and 6 effects. Many people here would use the CM VST packages from the DVD. Ohmygod101_vst2carbon isn't being detected, even after renaming it adding .vst extension. It's in the same folder as the others that are all detected. Trying to add it manually from the VST Manager didn't work either.I just checked, Luna is the same.
Did it open in LUNA?
No, Ohmygod isn't seen in Luna either. Also not in Live 5. It does date from early 2003. Interestingly it doesn't have a vst icon in OSX. Maybe it's just too "old"?

Yes, i was thinking maybe it's still a PPC plugin that you want to use on a mac intel machine?

Don't forget that osx has suffered from a lot of updates the last years:

OS9 -> OSX (including codefragments -> mach-o)
Within the OSX versions, several compatibility breaks!
PPC -> Intel

So there are a lot of vst plugins on mac that are broken by these reasons.

And not to forget that the vst 2.3 -> 2.4 transition wasn't very sweet neither on osx.

Generally, if a plugin is not working/recognized in the mulab beta, please also check wether it works or not in other hosts, as a common reference.

So we know it's mulab specific or not.

muzycian · Post by **muzycian** » Thu Oct 04, 2007 10:17 pm

Oops, sorry, forgot to include this text file in the package:

http://www.mutools.com/mulab/beta/luna- ... bility.txt

It tells about LUNA <-> MU.LAB musession file compatibility.

deleted · Post by **deleted** » Thu Oct 04, 2007 10:32 pm

DELETED

pljones · Post by **pljones** » Fri Oct 05, 2007 8:06 am

Okay, weird one.

I had opened MU.LAB. Following from your note about compatibility, I thought: "Oh, I know, I'll import a MuSession from LUNA." Knowing that the one I had in mind was a pre 8.4 session, I immediately launched the last LUNA to save it out again.

MU.LAB crashed:
http://www.drealm.info/mu.lab/drwtsn32-200710050901.log

(I'd put a small amount of money on it being ASIO related.)

pljones · Post by **pljones** » Fri Oct 05, 2007 8:20 am

So the next thing to try is not running both together

.

I loaded LUNA, loaded a .MuSession, saved it (same name), closed LUNA, loaded MU.LAB and told it to open the .MuSession. It refused.

So I closed MU.LAB, loaded LUNA, loaded the same .MuSession and saved it with a new name, just to be sure, closed LUNA, loaded MU.LAB and told it to open the new .MuSession. It still wasn't happy.

http://www.drealm.info/mu.lab/forMuLab.MuSession

Mmmm... That's not exactly a tricky MuSession. But here's an even simpler one that doesn't load (yes, I resaved from PR8.4):
http://www.drealm.info/mu.lab/0.MuSession

toxicoh · Post by **toxicoh** » Fri Oct 05, 2007 8:48 am

Yes, I'm having the same problems loading Luna Sessions. There's an error box asking about trying S.O,S. mode, but that doesn't work either. These are all simple midi or audio projects with no automation.

[Edit: I wasn't expecting compatibility with Luna 8.4, but it would be nice. I've been exporting the midi from those projects to test with MuLab. That works ok.]

MuTools

KVR Audio

MU.LAB beta A