MuTools

Stephan326 · Post by **Stephan326** » Sat Oct 06, 2007 4:05 pm

My Inputs are not showing either....

pljones · Post by **pljones** » Sat Oct 06, 2007 7:38 pm

ApBTranCer wrote: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.

Thanks! (My excuse is I'm feeling under the weather...)

pljones · Post by **pljones** » Sat Oct 06, 2007 7:56 pm

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! And it didn't report any problems! But it only reported 35 plugins found rather than 169. 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).

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.

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?)

fycfung · Post by **fycfung** » Sat Oct 06, 2007 8:07 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.

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.

fycfung · Post by **fycfung** » Sat Oct 06, 2007 8:11 pm

BTW, I repeated the track-not-showing-up-when-recording along with a nasty hang of the last note by using Synth1.

muzycian · Post by **muzycian** » Sat Oct 06, 2007 8:58 pm

aMUSEd wrote:Running the scan again but now it's ignoring Sytrus as it crashed last time. I want to make it try scanning Sytrus again - is there a way to do that without deleting the whole xml file?

Yes

-> Vst Plugin Manager
-> Add Plugins
-> Then browse to and select the file itself!

That way you're adding a single vst plugin instead of a folder

Now if a plugin is already in "quarantaine" so to say, you'll get an alert "X already in database". Scan again?"

Then choose yes.

muzycian · Post by **muzycian** » Sat Oct 06, 2007 8:59 pm

aMUSEd wrote:Oh well - no audio i/o's = no sound anyway!

As messaged earlier: this is because of a stupid new bug that slipped in because of changing the audio setup strategy.

Will be fixed in beta B2, which is in the pipeline, coming "in a minute"

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

D-Fusion wrote:Oh and don't worry muzycian (this is the only picture i am going to upload since it does'nt show anything special from MuLab)
So i hope it is ok

Ok

aMUSEd · Post by **aMUSEd** » Sat Oct 06, 2007 9:02 pm

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.

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

pljones wrote:Mmm... is my email not working or is this a very closed group?

Sorry pljones, will include you in the beta group again.

Because i wanted to refresh the beta testers list, i wiped the list after the beta A email.

In the beta A email was a request to reply on it if you wanted to stay part of the group. Didn't get a reply from you so that's why your beta-flag wasn't raised again. Now it is

You'll get B2 right away.

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

D-Fusion wrote:Just tried with Rob Papen Blue also with a arpeggiator setting and the same happened there (See the Adventus post above for details).

Ok will check.

Bug number 2:
If you delete a synth in the rack the window up in the right corner does still show the synth name (Not refreshed or cleared).

Correct. Will be resolved in beta C (not yet in B2!).

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

muzycian wrote:Because i wanted to refresh the beta testers list, i wiped the list after the beta A email.

No problem... but I did reply and you replied to my reply

. I asked you to switch email addys. Maybe that's what caused the problem?

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

Bonteburg wrote:-I still get the hanging note syndrome

Did you try it on the Mac mini already (with another keyboard)?

How does it go there?

-Mulab crashed again on loading an Crossfade Loopsynth preset without a sample
(used to work in Luna)

Will check.

-I can't seem to "target" (ie play) a VSTi without having a sequence.

Right-click the plugin and choose "Focus".

-VSTi stay "targeted" even when they have been deleted.

Correct. Will be resolved in beta C (not yet beta B2).

-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?

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

pljones wrote: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?)

The good news is that deleting all the plugs in VstPlugins.xml after the crasher and then rerunning the scan worked perfectly. Nothing else caused a problem. (In Beta A, the same plugin crashed MU.LAB; LUNA PR8.4 managed to scan the plugin okay, though. However, when I closed LUNA, I did get the "memory cannot be accessed" error... weird.) The plugin in question is the Rapture Demo.

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

fycfung wrote:Minor suggestion for beta b: when you ask for a new session and you're already playing, then it still keeps playing. I think it would be better to stop playing when a new session is created.

OK