MuTools

T. · Post by T. » Mon Nov 26, 2007 5:27 pm

Bonteburg wrote:More stuff!

Possible bug:

I couldn't choose a midi channel per part (right click on part) playing a multitimbral plugin (RMIV).
That is, I could choose one but it didn't seem to do anything.

Marco

Same here with RMIV, also with ANAMARK.
I thought this is a MU.LAB-free limitation (the "multitimbral" thing)?
greetings
T.

muzycian · Post by **muzycian** » Mon Nov 26, 2007 7:08 pm

Bonteburg wrote:Yo!

muzycian wrote:There has been killed a bug that could cause hanging notes when playing very short notes on your keyboard, depending on the buffer size of the audio device.
maybe it's the buffer size then? Is there a way to access/change it in MU:LAB?

No, the buffer size on OSX is set by the Core Audio device.

Any hanging notes when playing a keyboard on the mac mini?
Yep, same situation. It's puzzling in that it really looks like it's connected to chords and fast notes, so you can't possibly be all wrong.

Is that with the same keyboard or another keyboard?

BTW: which midi keyboard is it that you use on the G4?

Crossfade Loopsynth improvement:

strange, can't remember to have changed anything related to this...
Hah! Maybe the bug was a function of some other bug or something? So you never knew when you did away with it.
Do you have Crossfade Loopsynth? But anyway it's gone now

Yes, lets drop the issue. When it works it's ok

muzycian · Post by **muzycian** » Mon Nov 26, 2007 7:09 pm

Bonteburg wrote:Interestingly enough, it doesn't happen in AU hosts, nor in Renoise (vst host but a tracker)

Indeed an interesting fact.

pljones · Post by **pljones** » Mon Nov 26, 2007 7:21 pm

muzycian wrote:It's when doing "New Session" when the MPA is already open.

Ah yes... I'd imported a MIDI file...

muzycian · Post by **muzycian** » Mon Nov 26, 2007 7:23 pm

Bonteburg wrote:More stuff!
Possible bug:

I couldn't choose a midi channel per part (right click on part) playing a multitimbral plugin (RMIV).
That is, I could choose one but it didn't seem to do anything.

That's a MU.LAB Free limitation: VST synths only receive on channel 1.

Ideas:

-There's a lot of black in the rack area when you make the window bigger so I thought, wouldn't it be cool if you could change to modular view with a right click on the rack view?

You can already use:

-> The main Edit menu
-> F3
-> The TAB key (when the Rack window is active)

That should be sufficient imho.

-On right-clicking to delete a connection (modular view) i think it would come in handy to have a "delete all connections" option, to be able to unhook a whole module really quickly.

OK, available in beta E.

Bonteburg · Post by **Bonteburg** » Tue Nov 27, 2007 5:32 pm

muzycian wrote: Is that with the same keyboard or another keyboard?

BTW: which midi keyboard is it that you use on the G4?

Same keyboard, Evolution MK 249-C

Oxygenee · Post by **Oxygenee** » Thu Nov 29, 2007 2:40 pm

Hi!

I was just trying the latest Beta on OSX on an iMac Intel. I realized that certain vst-plug-ins can't be loaded in Mu-Lab.
I tried Quikquak Rayspace and GlassViper as well as Luxonix LFX 1310, which pop-up a window with "Can't create VST Plug-in!".

Hope you get it working!

muzycian · Post by **muzycian** » Thu Nov 29, 2007 3:32 pm

Will check'em

toxicoh · Post by **toxicoh** » Thu Nov 29, 2007 9:18 pm

Oxygenee wrote:Hi!

I was just trying the latest Beta on OSX on an iMac Intel. I realized that certain vst-plug-ins can't be loaded in Mu-Lab.
I tried Quikquak Rayspace and GlassViper as well as Luxonix LFX 1310, which pop-up a window with "Can't create VST Plug-in!".

Hope you get it working!

Hi,

I've got LFX 1310 working here. Not a bad multi-effect VST.

muzycian · Post by **muzycian** » Fri Nov 30, 2007 10:40 am

Oxygenee wrote:Hi!

I was just trying the latest Beta on OSX on an iMac Intel. I realized that certain vst-plug-ins can't be loaded in Mu-Lab.
I tried Quikquak Rayspace and GlassViper as well as Luxonix LFX 1310, which pop-up a window with "Can't create VST Plug-in!".

Hope you get it working!

I tried GlassViper and LFX-1310, both working OK here on a mini mac intel with OSX 10.4.10.

Strange that it doesn't work on your system

Maybe some shared library is missing?

Anyway, i've added some extra logging code into MU.LAB beta E (coming very soon), so that we might get some more details of what's going on.

So once you got beta E, please do this:

-> Launch MU.LAB
-> Rightclick the background at the left/right of the Transport Panel, and choose "Toggle Log File State" so that you get "Log File Activated".
-> Now goto the VST Plugin Manager -> Add VST Plugins -> choose one of this problematic plugins -> If MU.LAB would ask to rescan, choose yes.
-> OK, at this point you would get "Couldn't create VST plugin"
-> Now quit MU.LAB, and send the Log-yyyymmdd-hhmmss.txt file to me for examination.

All with the coming beta E please, as that one will contain more detailed logging info.

pljones · Post by **pljones** » Sat Dec 01, 2007 3:26 pm

BR:

Load a sampler, such as Kontakt2. Load an instrument or multi.

In MU.LAB change the Audio settings.

The sampler gets kicked and reloads all the samples. Bad

.

Of course, because of the way memory is handled, if the sample set is large, K2 complains it can't allocate enough memory and turns itself off. Worse

.

muzycian · Post by **muzycian** » Sat Dec 01, 2007 3:39 pm

pljones wrote:BR:

Load a sampler, such as Kontakt2. Load an instrument or multi.

In MU.LAB change the Audio settings.

The sampler gets kicked and reloads all the samples. Bad .

It's not a bug, it's intended behaviour.

When the audio settings are changed, it's a very good & safe thing to effectively reset all VST plugins.

Of course, because of the way memory is handled, if the sample set is large, K2 complains it can't allocate enough memory and turns itself off. Worse .

Simple solution:

1. Save the session
2. Do "New Session"
3. Change your audio settings
4. Reload the original session

Changing the audio settings while having a BIG project open is not something frequently occurs, right. And anyway, it's not very recommended neither. You're still dealing with computers, right

pljones · Post by **pljones** » Sun Dec 02, 2007 9:03 am

OY, if it's intended, I'll avoid it.

muzycian · Post by **muzycian** » Sun Dec 02, 2007 1:01 pm

pljones wrote:OY, if it's intended, I'll avoid it.

When the audio settings are changed, all plugins must adapt to the new situation.

Theoretically, this can be done in a neat vst way, and most plugins will handle this procedure properly.

But as you know there are also a lot of more "volatile" plugins.

And i'm sure you agree that it would not be ok that if you have a big project open, then on changing the audio settings, one of the plugs make crash the whole project.

So it's definitely a good thing that the session is saved when doing the Audio Setup.

Now MU.LAB simply reloads that saved session and so all plugins are hard resetted to the new audio setup, making it a 100% sure that all plugs are set for the new situation.

Just a question: are you changing your audio setup that many times?

I think: once my audio hardware is connected and setup, i don't touch the audio setup anymore for a long time.

Do you agree that my proposed solution in the previous post is a good solution, ok enough to cover that (non-frequent) situation?

pljones · Post by **pljones** » Sun Dec 02, 2007 8:33 pm

Yes -- like I say, now I know it's intended, I'll avoid doing what I was doing. It was testing-related, I'll just pick something other than Kontakt2 to have loaded!

MuTools

KVR Audio

MU.LAB beta D