M3 Tests

[MuTools]

The mulab-3-0-16-win.zip file has been updated, now containing the proper .exe.

So we can just drop the new .exe over the old, if we downloaded earlier?

Yes, that will work.

[dwsel]

- While playing with MUX and MuSynth in editor mode I noticed that I can't add new bricks/elements, replace function does not also work. Sometimes it looks that new window flashes and disappears after a millisecond.

While playing live in the editor MU.LAB threw on me:

Code: Select all

Internal thread loop time-out error @ usr_rltm_thrdlck[10]

I haven't check if the same thing happens under Windows too.

Procedure:
- Open demo song in MU.LAB
- I press play
- I put 'Tube Limiter' preset in main rack, I cycle through presets to 'ringmodsynth' preset (this step is not necessary)
- I press TAB to enter editor mode
- I click right and press 'replace' for 'WFT oscillator' (it happens for other blocks too)
- menu does not appear, element disappears although connection lines coming from/into it are staying in place
- playback stops and after a few seconds exception is thrown onto the screen

log:

Code: Select all

00:00:13:049 Started Logging
00:00:14:081 MS Windows XP Professional
00:00:14:081 MU.LAB FREE 3.0.16
00:00:14:081 /Z:/mnt/windows/programy/_music/edit seq/mulab3/mulab/MULAB.exe
00:00:20:509 flclss_wn[89] fn=LibraryFolders.txt, ec=2
00:00:20:534 flclss_wn[89] fn=LibraryFolders.txt, ec=2
00:00:30:434 flclss_wn[89] fn=Process.Png, ec=2
00:00:30:439 flclss_wn[89] fn=LibraryFolders.txt, ec=2
00:00:30:450 flclss_wn[89] fn=ParameterEditor.Xml, ec=2
00:00:30:452 flclss_wn[89] fn=ParameterEditor.Png, ec=2
00:00:30:454 flclss_wn[89] fn=Knob.Png, ec=2
00:00:30:456 flclss_wn[89] fn=ParameterEditor.Xml, ec=2
00:00:30:457 flclss_wn[89] fn=ParameterEditor.Png, ec=2
00:00:30:458 flclss_wn[89] fn=Knob.Png, ec=2
00:00:30:460 flclss_wn[89] fn=ParameterEditor.Xml, ec=2
00:00:30:460 flclss_wn[89] fn=ParameterEditor.Png, ec=2
00:00:30:461 flclss_wn[89] fn=Knob.Png, ec=2
00:00:41:141 flclss_wn[89] fn=Process.Png, ec=2
00:00:41:146 flclss_wn[89] fn=LibraryFolders.txt, ec=2
00:00:41:155 flclss_wn[89] fn=ParameterEditor.Xml, ec=2
00:00:41:156 flclss_wn[89] fn=ParameterEditor.Png, ec=2
00:00:41:156 flclss_wn[89] fn=Knob.Png, ec=2
00:00:44:842 flclss_wn[89] fn=Process.Png, ec=2
00:00:44:846 flclss_wn[89] fn=LibraryFolders.txt, ec=2
00:00:44:855 flclss_wn[89] fn=ParameterEditor.Xml, ec=2
00:00:44:856 flclss_wn[89] fn=ParameterEditor.Png, ec=2
00:00:44:857 flclss_wn[89] fn=Knob.Png, ec=2
00:00:56:035 flclss_wn[89] fn=LibraryFolders.txt, ec=2
00:00:56:058 flclss_wn[89] fn=LibraryFolders.txt, ec=2
00:00:56:067 flclss_wn[89] fn=VoiceOut.Png, ec=2
00:00:56:069 flclss_wn[89] fn=VoiceIn.Png, ec=2
00:00:56:070 flclss_wn[89] fn=TestSineGenerator.Png, ec=2
00:00:56:070 flclss_wn[89] fn=TempoSyncedMonoEcho.Png, ec=2
00:00:56:072 flclss_wn[89] fn=SamplePlayer.Png, ec=2
00:00:56:075 flclss_wn[89] fn=MultiModeFilter.Png, ec=2
00:00:56:076 flclss_wn[89] fn=PatchPoint.Png, ec=2
00:00:56:076 flclss_wn[89] fn=NoteModifier.Png, ec=2
00:00:56:077 flclss_wn[89] fn=NoiseGenerator.Png, ec=2
00:00:56:077 flclss_wn[89] fn=MuSynthCore.Png, ec=2
00:00:56:078 flclss_wn[89] fn=MultiSamplePlayer.Png, ec=2
00:00:56:079 flclss_wn[89] fn=Mod.Png, ec=2
00:00:56:080 flclss_wn[89] fn=LevelCompressor.Png, ec=2
00:00:56:082 flclss_wn[89] fn=EventMonitor.Png, ec=2
00:00:56:083 flclss_wn[89] fn=MIDIChannelSplitter.Png, ec=2
00:00:56:083 flclss_wn[89] fn=MonoEcho(Long).Png, ec=2
00:00:56:084 flclss_wn[89] fn=MonoEcho(Short).Png, ec=2
00:00:56:084 flclss_wn[89] fn=AudioOutput.Png, ec=2
00:00:56:084 flclss_wn[89] fn=MixerStrip.Png, ec=2
00:00:56:085 flclss_wn[89] fn=AudioLimiter.Png, ec=2
00:00:56:085 flclss_wn[89] fn=AudioInput.Png, ec=2
00:00:56:087 flclss_wn[89] fn=Balancer1-2.Png, ec=2
00:00:56:087 flclss_wn[89] fn=Amplifier.Png, ec=2
00:00:56:088 flclss_wn[89] fn=AllpassFilter.Png, ec=2
00:01:00:569 flclss_wn[89] fn=Process.Png, ec=2
00:01:00:573 flclss_wn[89] fn=LibraryFolders.txt, ec=2
00:01:00:618 flclss_wn[89] fn=ParameterEditor.Xml, ec=2
00:01:00:626 flclss_wn[89] fn=ParameterEditor.Png, ec=2
00:01:00:627 flclss_wn[89] fn=Knob.Png, ec=2
00:01:14:511 Internal thread loop time-out error @ usr_rltm_thrdlck[10]
00:01:24:610 Are you sure to quit?Cancel
00:01:29:542 Are you sure to quit? Answer=Quit without Save
00:01:34:550 Internal thread loop time-out error @ usr_rltm_thrdlck[10]
00:01:41:112 Internal thread loop time-out error @ usr_rltm_thrdlck[10]
00:01:47:874 Internal thread loop time-out error @ usr_rltm_thrdlck[10]

If demo is not played MU.LAB crashes without leaving trace in log.

I wonder if this also exists on Windows.

[edit]
At MU.LAB 2.x replacing and adding was not working too, but at least it wasn't crashing MU.LAB.

[MuTools]

- While playing with MUX and MuSynth in editor mode I noticed that I can't add new bricks/elements, replace function does not also work. Sometimes it looks that new window flashes and disappears after a millisecond.

While playing live in the editor MU.LAB threw on me:
"Internal thread loop time-out error @ usr_rltm_thrdlck[10]"
I haven't check if the same thing happens under Windows too.

Procedure:
- Open demo song in MU.LAB
- I press play
- I put 'Tube Limiter' preset in main rack, I cycle through presets to 'ringmodsynth' preset (this step is not necessary)
- I press TAB to enter editor mode
- I click right and press 'replace' for 'WFT oscillator' (it happens for other blocks too)
- menu does not appear, element disappears although connection lines coming from/into it are staying in place
- playback stops and after a few seconds exception is thrown onto the screen

I wonder if this also exists on Windows.

<edit>
At MU.LAB 2.x replacing and adding was not working too, but at least it wasn't crashing MU.LAB.

That's on LINUX, right?

Just for to avoid confusion to other users/readers, note that MU.LAB is not supported on Linux.

I think it's best to post messages about Wine/Linux in the Linux topic/thread, otherwise it may become confusing.

FYI: I tried what you described with MU.LAB on OSX (as you wrote "I wonder if this also exists on Windows" i thought i was about OSX) and no problem on OSX.

To be complete, i also tried on Windows, no problem either.

[dwsel]

Ok... I'll keep it in mind. Feel free to move/delete my post if you have mod rights. If not I may delete it myself.

[MuTools]

It's ok to post your feedback abount M3 on Wine, thanks for that!

But i just want to make sure it doesn't cause any confusion about the OSX and Windows versions.

So i think it's best to post these Wine/Linux messages in this topic:

http://www.kvraudio.com/forum/viewtopic.php?t=268483

Thanks!

[Bonteburg]

MU.LAB 3.0.16 crashed on completing a mixdown:

crashlog

The mixdown itself is flawless!

[MuTools]

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.

[MuTools]

MU.LAB 3.0.16 crashed on completing a mixdown:

crashlog

The mixdown itself is flawless!

I can't repeat this

2 questions:

1) Was it a mixdown to file or to a sample?

2) Whas it using VST plugins?

[MuTools]

MU.LAB test 3.0.17 is available in http://www.mutools.com/mulab/azalea

What's changed: http://www.mutools.com/mulab/azalea/mul ... hanges.txt

If you've already installed MU.LAB 3.0.16, then you can simply install the latest patch.

Else please install the full 3.0.17 package. Then if you want to keep your current MU.LAB settings, then copy everything in your current Mulab/Settings folder to the new Mulab/Settings folder before using the new MU.LAB.

Cheers,

Jo

[MuTools]

There is a problem with scanning/using VST plugins in 3.0.17.

I'll check that asap, but it will be tomorrow as i have to go somewhere now.

I've temporarily removed the MU.LAB 3.0.17 for OSX packages from the webfolder.

Talk soon

[liquidsound]

v3.0.16 = Draw new sequence part -> default loop is part length

It's nice but the freedom of changing the length of a Part while working without the additional step of going in the Key editor and repositioning the internal loop marker is also very nice...
How about using a modifier key while stretching a Part to re-implement that feature belonging to the previous betas? (Also very nice indeed)
OR in the context menu a choice of "Remove Loop" from selected par(s)
One Move Two Birds...

BTW is there a feature in the Skin SDK that controls the Parts Pitcture?

[Bonteburg]

MU.LAB 3.0.16 crashed on completing a mixdown:

crashlog

The mixdown itself is flawless!

I can't repeat this

2 questions:

1) Was it a mixdown to file or to a sample?

2) Whas it using VST plugins?

Mixdown to file, and yeah I was using vst plugs, but none of them were trouble before. That said, it happened between a few failed attempts to run a ninjam plugin on other hosts and my computer might have been a little stressed out.

Maybe I was clicking on the wrong spot of the wrong interface at the wrong time.

I created a mixdown of the same project just now and it was all O.K.

[MuTools]

is there a feature in the Skin SDK that controls the Parts Pitcture?

No. (it's on the whishlist)

[MuTools]

MU.LAB test 3.0.18 is available in http://www.mutools.com/mulab/azalea

What's changed: http://www.mutools.com/mulab/azalea/mul ... hanges.txt

If you've not yet installed MU.LAB 3.0.16, then best the full new package. Then if you want to keep your current MU.LAB settings, then copy everything in your current Mulab/Settings folder to the new Mulab/Settings folder before using the new MU.LAB.

If you have already installed 3.0.16, then you can simply apply the newest application patch.

[dwsel]

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?