MuTools

muzycian · Post by **muzycian** » Tue Dec 11, 2007 12:42 am

Hi,

A new MU.LAB Public Beta C update is available.

This update especially fixes a nasty bug that sometimes could cause a hang when doing composition edits.

That's why this update is distributed sooner than planned.

Below is a complete list of what's new.

If you already installed MU.LAB Public Beta B (the previous version) then you can simply install the new MU.LAB application patch.

A patch is a newer version of the application file. Just put the new version over the existing version. This way you don't have to do any setting up again.

Everything downloadable from:

http://www.mutools.com/mulab/beta

What's new in Public Beta C

* Tuned: MPA: "Embed Editor" disabled for VST plugs
* Tuned: On doing New Session, the first rack is automatically focussed
* Tuned: In the MuSynth Edit Editor, the meta parameter knobs now have proper default values (on alt+click)

* Fixed: Composer: Some compistion operations (eg splitting audio parts) could cause a hang
* Fixed: Composer: Cut-Copy-Paste didn't properly work
* Fixed: MPA: "Embed Editor" didn't work
* Fixed: Saving a new MuSynth patch in the Edit Editor, then switch to the Play Editor, now the new patch is properly listed in the browser

* And some other little tunings

gemada · Post by **gemada** » Tue Dec 11, 2007 11:42 am

I've tried all MU.LAB plubic beta releases and i have some clicks and pops in my sessions using asio4all latest driver release. With LUNA PR8.4 i can use asio4all without these problems so my experience tells me that the audio engine in LUNA runs a lot smother than in MU.LAB.
I've tried tunning the asio4all settings in MU.LAB but this glitches still occur. With LUNA i have no problems.
Is there anyone else having the same issues?

P.S.: I'm using windows xp sp2 and my setup has more than enough power to deal with audio and midi.

muzycian · Post by **muzycian** » Tue Dec 11, 2007 12:18 pm

gemada wrote:I've tried all MU.LAB plubic beta releases and i have some clicks and pops in my sessions using asio4all latest driver release. With LUNA PR8.4 i can use asio4all without these problems so my experience tells me that the audio engine in LUNA runs a lot smother than in MU.LAB.
I've tried tunning the asio4all settings in MU.LAB but this glitches still occur. With LUNA i have no problems.
Is there anyone else having the same issues?

P.S.: I'm using windows xp sp2 and my setup has more than enough power to deal with audio and midi.

Gemada, did you play with all beta versions of MU.LAB?

Do you have an idea when this changed behaviour popped in?

Last question:

Are these pops/clicks coming when sequencing VSTIs
or when playing audio files?

Or doesn't that make a difference?

gemada · Post by **gemada** » Tue Dec 11, 2007 2:56 pm

Thanks for your reply.
I've tried all MU.LAB beta versions (public ones).
And it happens with vsti's and audio files. It doesn't make a difference.

I have another question (sorry if this sounds noob):
Is it possible to make volume automation in an audio file?

gemada · Post by **gemada** » Tue Dec 11, 2007 3:23 pm

Muzycian:
I've found that if i set the maximum buffer size (2048) in asio4all the clicks and distortions disappear.
But note that if i use reaper or cubase i can set the buffer size way down to 256 samples without glitches.
Sorry for mentioning other software developers but i want to provide you all the details about this subject

Thanks again.

muzycian · Post by **muzycian** » Tue Dec 11, 2007 3:48 pm

gemada wrote:Thanks for your reply.
I've tried all MU.LAB beta versions (public ones).
And it happens with vsti's and audio files. It doesn't make a difference.

And what's the CPU meter saying, i mean: at what CPU load does the clicking start?

FYI: You can click the CPU meter to switch between various mode:

* no value disply
* show current percent
* show number of overloads
* show maximum cpu weight

And does the clicking match with the number of overloads, i mean: when you set the cpu meter in "show number of overloads", does any value increase then match with a click?

And another question: does it also click when you do "New Session", and then simply play 1 audio file thru an empty Rack?

I have another question (sorry if this sounds noob):
Is it possible to make volume automation in an audio file?

Of course: just record the volume slider movement of the target rack.

gemada · Post by **gemada** » Tue Dec 11, 2007 3:57 pm

Yes it happens when i do "New Session", and then simply play 1 audio file thru an empty Rack.
Cpu percent: 1%
Cpu overloads: 0

Stephan326 · Post by **Stephan326** » Tue Dec 11, 2007 4:02 pm

Hey Jo I have not had any response to a request for a reg code. I was a registered LUNA user

muzycian · Post by **muzycian** » Tue Dec 11, 2007 4:17 pm

Stephan326 wrote:Hey Jo I have not had any response to a request for a reg code. I was a registered LUNA user

Can you please PM me about this, also giving your email address.

I got some errors returned from mail servers, and so i couldn't reach everyone.

muzycian · Post by **muzycian** » Tue Dec 11, 2007 4:30 pm

gemada wrote:Yes it happens when i do "New Session", and then simply play 1 audio file thru an empty Rack.
Cpu percent: 1%
Cpu overloads: 0

Here is a temporary link to an older version of MU.LAB:

http://www.mutools.com/mulab/beta/temp/ ... bd-win.zip

Can you please install this older version and see whether playing a single audio file also causes clicks.

You can install this on the same system, no problem.

Just make sure that, for the accuracy of this test, no 2 mulabs are running at the same time.

Secondly, can you also try this musession in the latest Public Beta C:

http://www.mutools.com/mulab/beta/temp/test.musession

Does this musession, which plays a simple riff to a single MuSynth, also generate clicks?

Do the clicks come when you open/close/move windows around, or also when just letting the riff play?

gemada · Post by **gemada** » Tue Dec 11, 2007 7:04 pm

I've tried just like you said and there are a lot of clicks and pops just letting the audio track play.
I've found out that the problem occurs if the samplerate is set to 48khz and you play a 48khz audio file (i've tried with and without "Always resample 44.1 to 48khz" option ticked in asio4all panel). With a sample rate of 44.1khz playing 44.1khz audio files there are no problems. Strange, because my audio onboard is 48khz capable.

The link you send me for the test session isn't working.

muzycian · Post by **muzycian** » Tue Dec 11, 2007 8:02 pm

gemada wrote:I've tried just like you said and there are a lot of clicks and pops just letting the audio track play.
I've found out that the problem occurs if the samplerate is set to 48khz and you play a 48khz audio file (i've tried with and without "Always resample 44.1 to 48khz" option ticked in asio4all panel). With a sample rate of 44.1khz playing 44.1khz audio files there are no problems. Strange, because my audio onboard is 48khz capable.

And so when you use the exact same setup in reaper and cubase, are you then getting the same clicks there?

The link you send me for the test session isn't working.

Oops, sorry, forgot that the internet is case-sensitive.

Now the link is working:

http://www.mutools.com/mulab/beta/temp/test.musession

Best to right-click and save as "test.musession"

Then please open it in Public Beta C and check wether it also generates clicks under the various conditions you noticed.

Thanks.

gemada · Post by **gemada** » Tue Dec 11, 2007 8:06 pm

In reaper and cubase there are no problems under the same conditions...it only happens with mulab.

Ok, i'm gonna try with that test session and reply as soon as i can.
Thanks again for your support

DaveL60 · Post by **DaveL60** » Tue Dec 11, 2007 8:19 pm

Out of curiosity, in any of these programs, are you testing with a mixture of 44.1k and 48k audio samples? And you said the problem exists with both VSTi and audio parts, but does that specifically include a mixture of both? It kind of sounds like the other hosts might be detecting the frequency rate of the cards and adapting, whereas maybe MU.LAB isn't?

DaveL

Bonteburg · Post by **Bonteburg** » Wed Dec 12, 2007 12:53 am

-hanging notes on short chords are still there, though it seems to perform better with monosynths now.

-Handling and GUI is getting more streamlined and fast with every release! Very tight.

-'Replace synth' , excellent!

-Is multitmbral supposed to work in the unlimited Beta? [edit: user error]

-Not so sure about Auto-Play on startup.

It still seems to say "Don't play your keyboard" to me but everything else is turning out very very cool. I even messed with the RMIV audio settings and could still save the session file which, if you're familiar with RMIV amounts to a small miracle.

Marco