M3 Tests

[Nielzie]

I also get crashes on both of my systems when switching through presets while playing a sequence in Vember Audio SURGE

Something I didn't have in any other DAW I tried (Orion 7, EnergyXT2, REAPER 3)

Yes i also get that crash

It's crashing within Surge, i have no idea why.

I'll email Vember Audio about this.

Emailed them. Curious if they'll respond.

Received an answer from VemberAudio (thanks Claes!) on this:

It's caused by a threading issue in Surge, which will be fixed in a future version of Surge.

Also MU.LAB will be fortified against this situation as in fact the very reason of this problem is an ambiguous aspect (another one) of the VST SDK.

Will be finetuned in the next version.

Ok, thanks!

[MuTools]

MU.LAB 3.0.17
-------------
Tuned: Extra protection against a dubious threading aspect of VST plugins


Does have anything in common with fixing well known bug with VSTs built with old SytnhEdit having problems with multithreading?

The dubious VST threading aspect had to do with the "audioMasterUpdateDisplay" call.

MU.LAB assumed it was called from the GUI thread, which is a logical assumption. But it turned out that e.g. Surge was calling this from another thread, which could cause problems in MU.LAB. The VST SDK is not clear on this aspect and so MU.LAB doesn't make the GUI thread assumption anymore.

[MuTools]

Nielzie, can you confirm the problem with Surge has gone?

And do you sometimes still get crashes on Quit? Or is this problem fixed too?

[theorize]

the latest version of Rhino is now friends with MuLab

[Nielzie]

Nielzie, can you confirm the problem with Surge has gone?

And do you sometimes still get crashes on Quit? Or is this problem fixed too?

Surge seems to work fine now and recently I haven't had any crashes on exit with other plugins in the latest beta. You did a very good job there to fix this!

Another big step forward to rock-stability and world domination..

Thanks!

[Nielzie]

I have a little problem with the KarmaFX Modular Synth in M3 on my laptop. My laptop has a 1280 x 800 resolution screen and the KarmaFX UI Windows is quite large so the whole windows doesn't fit on the screen. That's not M3's fault of course. But when I open the synth then the top of the both the mulab window as the KarmaFX window disappears outside of the monitor boundaries like this:



Click here for an outside link to the print-screen. It's a full screen grab, nothing is cut.

I can't drag the plugin window of KarmaFX because of this, so I can't use the synth normally.

[bpblog]

yeah, good point Nielzie. i use mulab on my netbook, where the resolution height is only 600 pixels. the vsts i use have to be real short.

of course, mulab can't do anything to make our screens larger, but it would perhaps be nice if it could check the height of the plugin on while loading. then, if the plugin gui can't fit on the screen, load so that it isn't in the middle of the screen, but rather that it's titlebar is aligned to the top of the screen. in this way, at least the plugin menu buttons would be accessible.

[MuTools]

Immediate solution: You can right-click the VST window border -> "Move To Top-Left".

Future solution: The default position could indeed be better when the plugin window is larger than the screen => added to the whishlist.

[dwsel]

I'd suggest to make window smaller than screen resolution and add scrollbars like in SAVIhost. I find it very helpfull...

[sorohanro]

I wonder, how the M3 deal with multiple audio inputs ?
I'm trying to figure it out but I'm a bit lost... Is it possible to record from different inputs on different tracks at the same time ?

[MuTools]

No, it's not yet possible <-> 1 mono/stereo recording per take.

But it's one of the top priorities for the next big update (M35 or M4)!

[bpblog]

not the best place to ask this, but i can't think of a better place either.

anyway, i tried to setup a few vocoder plugins in m3, mda Talkbox and TAL-Vocoder, but their inputs don't show properly. there was some talk about using plugins with multiple inputs before, in the days of m2, and the issue seemed to be fixed. i also tried following these instructions:

http://www.kvraudio.com/forum/viewtopic ... 05#3517505

but it won't work. so i just figured i should report. is there another way to fix this?

[MuTools]

I don't think you have to do something special regarding the inputs. It works fine here out of the box using TAL Vocoder in MU.LAB 3:

MP3: http://www.mutools.com/mulab/examples/V ... 100209.mp3

Zipped MuSession: http://www.mutools.com/mulab/examples/V ... 100209.zip

The session needs "TAL-Vocoder.dll".

Tip: When using the internal synth of TAL Vocoder, make sure you have a note playing to it to trigger the synth.

[MuTools]

Question:

When pasting parts or events, the paste position is defined by the snapped mouse position in the editor.

But a popup dialog appears where you can still edit that paste position.

I would like to remove this popup dialog so that pasting immediately occurs at the snapped mouse position.

Then pasting would work exact the same way as e.g. splitting parts, which works fine now.

By removing the popup dialog, we get a more streamlined workflow, i think.

Do you agree?

[robenestobenz]

Question:

When pasting parts or events, the paste position is defined by the snapped mouse position in the editor.

But a popup dialog appears where you can still edit that paste position.

I would like to remove this popup dialog so that pasting immediately occurs at the snapped mouse position.

Then pasting would work exact the same way as e.g. splitting parts, which works fine now.

By removing the popup dialog, we get a more streamlined workflow, i think.

Do you agree?

Yes.... it was a workflow step that I tolerated but never really saw the point of in Mulab. It might just be my way of working, but I rarely had a numerical timeline position in mind when it came to pasting, and by the time I'd looked it up I could have positioned the mouse there anyway.