MuTools

pljones · Post by **pljones** » Sat Oct 06, 2007 9:25 pm

muzycian wrote:Would you liek to have the single-click back?
What do others think here?

Click on an empty rack-slot should prompt to add, as it does. Click on a filled in rack-slot should at least focus, if not open, the plugin (it doesn't focus it at the moment - just doesn't popup the plugin list). Right-click could offer "insert plugin", maybe, if the rack-slot is empty and "replace plugin" if it's filled.

muzycian · Post by **muzycian** » Sat Oct 06, 2007 9:31 pm

Fuzzbeard wrote:Hi

I'm using a Windows XP machine, with an Audigy 2ZS soundcard.

On the first run of MU-LAB (I had completely trashed the Beta A installation) I got to the ASIO config screen.
Samplerate was set to 48000Hz in the window.
Could not select inputs or outputs (got the same screen as D-Fusion)
Set Midi I/O Ok, then I get a message
"Couldn't set preferred ASIO samplerate 44100Hz => Current Samplerate = 48000Hz"
Click on OK and MU-LAB comes up with the Sequence and Racks screen, then crashes.

(MULAB.exe has encounteres a problem and needs to close....)

On subsequent runs, MU-LAB will always come up with the samplerate error, then crash.

Hmm... Just noticed that while it had crashed, it had not terminated completely.
I ran the app several times, now looking at the Task Manager, I have multiple instances of MULAB.EXE and DrWtsn32.exe in the processes list. Trying to end the processes does not remove them from the process list. *must* reboot

Just rebooted, then started MU-LAB. Got the same behaviour, and still could not remove MULAB.exe from the process list.
Another reboot required.

Ah well, back to Beta A

Sorry bout that mate.

I just did a check on the "Couldn't set preferred ASIO samplerate" situation: forced a wrong samplerate in my AudioSetup.txt, and launched mulab. No problem, got the message, but then it worked fine.

I assume that the heavy reboot stuff is related to an asio driver issue.

Note that the message itself is correct. The Audigy 2ZS indeed works on 48 kHz.

To avoid the message, go to Edit -> Audio Setup and choose the right samplerate.
Oh, but you got a crash before that point, right?
So then edit AudioSetup.txt in your mulab/settings folder and set the samplerate manually to 48000

Does this work?

Strange that the samplerate issue pops up now, and not on beta a

pljones · Post by **pljones** » Sat Oct 06, 2007 9:31 pm

Hey, neat! I just found that "Load MuSynth file" with the sequencer running previews the patch!

muzycian · Post by **muzycian** » Sat Oct 06, 2007 9:34 pm

> DiGiT < wrote:i was able to open the program this version, had no problems at all. btw, my plugin folder was empty last time. this time too.

however, once i stopped the the demo project, i couldnt start it again. i could do everything but start the sequencer once it was stopped.

And was the rest of the GUI responsive?

Could you access the mulab menus etc...?

muzycian · Post by **muzycian** » Sat Oct 06, 2007 9:35 pm

fycfung wrote:Hi Jo,
Here's something I encountered...

I'll go deeper into this report after B2.

muzycian · Post by **muzycian** » Sat Oct 06, 2007 9:38 pm

Newbie Brad wrote:I did a clean install of Mu.Lab beta B. I didn't test it very hard, but I got good audio. I noticed when using ASIO4All audio driver I couldn't get the control panel button in the audio setup window to function.

Maybe Asio4All doesn't have a control panel?

Any A4A experts here?

FreeAmp 2 loads but if a few notes are played it seems to crash Mu.Lab beta B's audio, just like it did in beta A. As with beta A, beta B couldn't read keFIR v.1, Loopitch, WaveThresh, Synchro, Eclipse, PanGloss, AlienArtifact, or ReValver 2.

Will check (some of) these plugs.

muzycian · Post by **muzycian** » Sat Oct 06, 2007 9:41 pm

ApBTranCer wrote:
pljones wrote:Mmm... is my email not working or is this a very closed group?
i was wondering the same thing, until i noticed that beta b was posted to the same URL that was given in the beta a Email. I hope we're all still in, cuz im bustin my balls lookin for bugs and havin fun doin it lol

As mentioned in the Beta A email, i've reset the beta testers list so to get it fresh and up to date.

If you didn't get a Beta B email, please *email* me about beta testing.

Anyway, indeed the same web folder will stay steady during this beta stage.

muzycian · Post by **muzycian** » Sat Oct 06, 2007 9:45 pm

jens wrote:I don't know if this really is a bug but I can say for sure that it really bugs me:

if the pencil tool is in use, switching from the compossr to the midi-editor or from the midi-editor to the composer, automatically switches to the selection tool.

Each editor memorizes its tool

jens · Post by **jens** » Sat Oct 06, 2007 9:55 pm

muzycian wrote:
jens wrote:I don't know if this really is a bug but I can say for sure that it really bugs me:

if the pencil tool is in use, switching from the compossr to the midi-editor or from the midi-editor to the composer, automatically switches to the selection tool.
Each editor memorizes its tool

nope, it doesn't - hence my post - so it's a bug then...

muzycian · Post by **muzycian** » Sat Oct 06, 2007 10:03 pm

pljones wrote:Okay, now for a bug report .

I gave MU.LAB Beta B a fresh folder all of its own. As with others, no ASIO in or out found. Never mind.

It set off scanning my VST folder. And it didn't crash!

Yes, an extra layer of crash protection enabled on windows.

And it didn't report any problems!

-edit-

It's implicitly reported because "Scanning X" is not followed by "Added X".

-/edit-

But it only reported 35 plugins found rather than 169.

Strange, others also report quite some unrecognized vst plugs.

I'll have a deeper look in this.

Can you please also email me your VstPlugins.txt. Thanks.

Clicking OK gave me a "Memory cannot be read" error (but that could have been because I ran Beta A to check the number of plugins).

Yes, that's indeed the beta A - B together problem.

Starting from beta B, you can have 2 MUTOOLS apps open at the same time.

So a Beta B (or later) + Beta B (or later) should be ok.

(besides any asio driver issues of course, but that's out of mulab's control)

Looking back through the log, it got as far as a crasher and then ignored everything after it, rather than just that one. Restarting MU.LAB Beta B and running the scan again gave the "(ignored plugin)" on everything after that point.

Mmm, strange.

Maybe the crash did influence all following scans?

Just did a test. I know CM Vocoder now crashes here because of a missing system file.

So i scanned that folder. And indeed: "Scanning CM Vocoder" but no "Added CM Vocoder"

But the following plugins were scanned properly.

So at the moment i don't have a clue what could be the issue...

Deleting VstPlugins.xml and rerunning the scan had the same result. I got the "Memory cannot be read" error when closing MU.LAB. (It might have been the popup from the crashing plugin, previously hidden behind MU.LAB?)

Note that not all vst plugin crashes are intercepted by the extra crash protection layer. -edit- It depends on the kind of crash -/edit-

Note to OSX users: this extra crash protection layer is only available on windows.
Don't complain to me, but to apple please. Tell them to improve XCode.

muzycian · Post by **muzycian** » Sat Oct 06, 2007 10:08 pm

fycfung wrote:
jens wrote:I don't know if this really is a bug but I can say for sure that it really bugs me:

if the pencil tool is in use, switching from the compossr to the midi-editor or from the midi-editor to the composer, automatically switches to the selection tool.
Yeah...if there has to be a default, I think it should be the pencil tool, so the user isn't confronted by default with a situation where he can't do anything.

As well in the Composer as in the Sequence Editor, when no parts/events are there, the editor defaults to the pencil

muzycian · Post by **muzycian** » Sat Oct 06, 2007 10:14 pm

aMUSEd wrote:Neat - all hosts should have this feature.

Incidentally can it scan plugins from shortcuts? - I find that is absolutely the best way to manage plugins - another thing all hosts should do.

No.

(not yet)

muzycian · Post by **muzycian** » Sat Oct 06, 2007 10:19 pm

pljones wrote:Click on a filled in rack-slot should at least focus, if not open, the plugin (it doesn't focus it at the moment - just doesn't popup the plugin list).

When filled, single click does what? doubleclick does what?

I would say, to maintain comformity thru out the app, only a doubleclick opens the editor.

A single click could popup the list, as in earlier versions, but that was sometimes annoying, i found. Agreed?

Maybe when filled a single click could focus?

muzycian · Post by **muzycian** » Sat Oct 06, 2007 10:24 pm

jens wrote:
muzycian wrote:
jens wrote:I don't know if this really is a bug but I can say for sure that it really bugs me:

if the pencil tool is in use, switching from the compossr to the midi-editor or from the midi-editor to the composer, automatically switches to the selection tool.
Each editor memorizes its tool

nope, it doesn't - hence my post - so it's a bug then...

it indeed doesn't.

not that that is a big problem.

i just remembered it wrong.

what's the ideal behaviour here?

Calum · Post by **Calum** » Sat Oct 06, 2007 11:29 pm

muzycian wrote:
Bonteburg wrote:-I still get the hanging note syndrome

-Being able to replace a VST for another one in the racks without having to delete it before would speed up things greatly
Would you liek to have the single-click back?

What do others think here?

To be honest, although Luna is now a pale shadow of what Mulab has become, there are still elemnts of Luna PR7b's functionality that I miss. It is hard to put my finger on what just felt right about using Luna PR7b, and it just may be that this was the version where everything fell into place for me and I gained a better understanding of how to operate Luna. But there is something about introducing double-clicking to replace the edit button that just seems to slow the whole process down (one more option to think about). I also miss the fact that recorded automation of a rack's volume and pan no longer flags up the name of the corresponding rack in the Property Panel (Just the words "mixer strip"). Perhaps something like pljones's suggestion may be the answer:

pljones wrote:
muzycian wrote:Would you liek to have the single-click back?
What do others think here?
Click on an empty rack-slot should prompt to add, as it does. Click on a filled in rack-slot should at least focus, if not open, the plugin (it doesn't focus it at the moment - just doesn't popup the plugin list). Right-click could offer "insert plugin", maybe, if the rack-slot is empty and "replace plugin" if it's filled.

I know that some compromises were necessary to make the Modular Plugin Area work in conjunction with the Racks. I would never want to see Mulab take a step backwards, but every now and then it may be worth revisiting the earlier incarnations of Mulab to make sure that nothing important has been lost.

I realise i'm not providing any sort of solution here, just observations. Perhaps I just want the edit button back cause it looked pretty on my skin!