MU.LAB Public Beta C

[muzycian]

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

I'm thinking of adding a diagnostic function into mu.lab, kind of midi monitor, so that we can know whether the problem lays before or after the midi data comes into mu.lab.

Not so sure about Auto-Play on startup.

MU.LAB doesn't auto play on startup anymore!

If it still auto starts up, i assume you have been copying an earlier setting file into the new version.

In that case:

-> quit mu.lab
-> mulab folder/settings/ and open mulab.txt
-> set AutoPlay=0


Thanks for your feedback Bonte!

[gemada]

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

Thanks.

So i've tried test.musession and the result is the same as before:

(Asio4all with 512 buffer size)
44.1khz » No clicks and pops
48khz » Clicks and pops

And i've previously set the same asio4all settings in reaper and cubase to prevent possible sample rate conflits. In those prgrams i can go as low as 256 buffer size in projects with several audio tracks and vsti instruments.

I really don't understand why this happens in mulab.
Thanks again.

[gemada]

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?

DaveL

Thanks for your reply. In those programs i use files with the same sample rate (or convert them inside cubase if needed). And the problem exists with both VSTi and audio parts, isolated or together in the same session.

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

Maybe that's the issue but how can that be solved?
Thanks

[muzycian]

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

Thanks.

So i've tried test.musession and the result is the same as before:

(Asio4all with 512 buffer size)
44.1khz » No clicks and pops
48khz » Clicks and pops

And i've previously set the same asio4all settings in reaper and cubase to prevent possible sample rate conflits. In those prgrams i can go as low as 256 buffer size in projects with several audio tracks and vsti instruments.

I really don't understand why this happens in mulab.
Thanks again.

Just to make sure: did you try to set the samplerate to 48 kHz in reaper and cubase? (while asio4all is set to 44.1 kHz)

If so, did they play fine them, without clicks?

I mean:

Maybe the issue is with asio4all in the situation where the host asio samplerate is not the same as what's setup in asio4all?

I'm not sure, i'm not an asio4all specialist.

And it's difficult for me to properly understand what's going on as i should do some test on your machine...

From all the info i got now, for me it sounds like an asio4all issue.

I can't think of anything else at the moment.

[muzycian]

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

Maybe that's the issue but how can that be solved?

MU.LAB just asks the asio system what samplerates are possible for that audio device driver (in this case: asio4all), and then gives you these choices in the setup dialog.

You pick a samplerate, and then MU.LAB instructs the asio driver to use that samplerate. If the asio driver would give an error, MU.LAB is also forwarding this error to you.

So if you set, in the Audio Setup, the samplerate to 48 kHz, and you don't get an error (on closing the audio setup dialog because it's then that the audio engine is restarted), then we can only assume everything is OK.

Anyway, IF it would turn out that asio4all is not working good at 48 kHz, then just set the MU.LAB samplerate setting to 44.1 kHz, and the problem is solved. Right? And if i interprete all your info correctly, you should also be able to set the buffersize to 256 samples. Right?

Maybe i'm missing a point; as said: it's difficult for me to see the full picture as i can't diagnose the machine myself.

[gemada]

When i choose a sample rate project in reaper, i guess asio4all automatically detects it so there are no conflits with the driver itself and the application running.
I guess the solution is to stick with 44.1khz in mulab.
Muzycian thanks a lot for your support once again

P.S.:I'll keep on trying mulab with asio4all to see if i find where's the issue.

[muzycian]

When i choose a sample rate project in reaper, i guess asio4all automatically detects it so there are no conflits with the driver itself and the application running.

But don't you have an "audio setup" in reaper where you can choose the samplerate, just like in mu.lab?

I guess the solution is to stick with 44.1khz in mulab.

Yes, this will give you the space to make music

Muzycian thanks a lot for your support once again

P.S.:I'll keep on trying mulab with asio4all to see if i find where's the issue.

Great!

If you find any more pieces of the puzzle, please put them on this table!

[Bonteburg]

small bug:
when importing an audio file, the status window doesn't show the progress. (OSX)


possible fine tuning:
Mixdown to audio file - it would be very comfortable to have a dialogue ask you whether you want to import it automatically. The way it is, you tend think 'where's my audio file?'.

[Bonteburg]

rather a specialised bug: Free Alpha (Lin Plug) doesn't make a sound in MU:LAB, osx 10.4 intel.

Not sure if I even should bring tihs up here?

Marco

[jpumphandle]

Public Beta C

In the List Editor for MIDI:
When inserting a Program Change instead a Note is inserted.

[muzycian]

small bug:
when importing an audio file, the status window doesn't show the progress. (OSX)

Had that also once, on win xp, but couldn't repeat it

Will check again on osx.

possible fine tuning:
Mixdown to audio file - it would be very comfortable to have a dialogue ask you whether you want to import it automatically. The way it is, you tend think 'where's my audio file?'.

You have to choose a destination audio file so i'm confident the user knows where he has put it.

Besides this reasoning, it's a nice idea: an (optional) auto import. Added on the whishlist.

[muzycian]

rather a specialised bug: Free Alpha (Lin Plug) doesn't make a sound in MU:LAB, osx 10.4 intel.

Not sure if I even should bring this up here?
Marco

Sure! It never hurts to feedback!

If other users notice the same, this issue can grow in importance, whether for MUTOOLS whether for LinPlug. We devs should get things working for 100%, so that creating music gets even more fun

[muzycian]

Public Beta C

In the List Editor for MIDI:
When inserting a Program Change instead a Note is inserted.

Yes, a bug

Will be fixed in MU.LAB PreRelease, coming later today

[Bonteburg]

possible fine tuning:
Mixdown to audio file - it would be very comfortable to have a dialogue ask you whether you want to import it automatically. The way it is, you tend think 'where's my audio file?'.

You have to choose a destination audio file so i'm confident the user knows where he has put it.

Slight misunderstanding - I meant to say that it could confuse some people to find that an audiofile does not get imported automatically and they would go 'hey, where's my file in the arranger window'.
I agree though, optional would be the best of both worlds.

[hivkorn]

bug with the tritone plug in ! and when i work on multiscreen it don't keep the right place of the screen...AND WHAOOOOOOO , i'm very happy to have buy this software.