MU.LAB Beta E

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Hi,

MU.LAB beta E has been released to the beta testers.

What's New since beta D
  • New: Modular Area: You can now delete all in or out connections of a plug at once
    New: When you focus a plug, all parts targetting that plug are selected
    New: Event Value 2 editor: The Pencil tool now also supports selection operations just like in the composer and note editor
    New: Event Value 2 editor: Cut, Copy, Paste and Delete keys are supported
    New: Event Value 2 editor: Now also Aftertouch is supported
    New: Event List Editor: Alt+click = monitor event (cfr Note Editor)
  • Tuned: MuSynth Patch Editor: Now you can also switch between Play and Edit mode via the Options menu (besides using the TAB key)
    Tuned: Improved the Randomize WaveForm function
    Tuned: Event Value 2 editor: selected bars are drawn in front of non-selected bars
    Tuned: Event List Editor: Cut/Copy/Paste is supported
    Tuned: Cut/Copy/Paste explicitly in context menus
    Tuned: Improved playback behaviour when editing a sequence: the non affected parts keep on playing much more smoothly
    Tuned: Improved the automatic name indexing system (used when e.g. 2 sequences have equal names)
    Tuned: When listing all inputs for a Rack, when you choose a plugin from that list, that plugin is focussed
    Tuned: You can now select a Target from the Part Property Panel even while no part is selected
    Tuned: Leftclicking the background of a Rack focusses that Rack
    Tuned: When adding an audio part to the composition, the part defaults to target the focussed target (instead of simply the main out)
    Tuned: Increased the minimum thumb size for scrollbars for more user friendly scrollbars
    Tuned: Finetuned the MuSynth patch library
    Tuned: You can also delete patches from the library via the browser in the patch editor
    Tuned: Various improvements wrt mapping the meta parameters for MuSynth and MUX
  • Fixed: When no voices were playing, the MuSynth was not processing incoming parameter changes
    Fixed: Event List Editor open while New/Open/Revert Session => crash
    Fixed: MPA: Rack -> Embed -> Delete = crash
    Fixed: Selecting a plug in the MPA now properly focusses that plug
    Fixed: Doing "New Session" while MPA is open could lead to faulty behaviour
    Fixed: Loading a Sequence file from within the sequence editor didn't refresh the display
One of the days MU.LAB 1.0 will also be released as a public beta.

Post

Found an issue. Also happens in Beta D.

1. Open Demo.MuSession
2. Mixdown to Audiofile (TestMe.wav)
3. New Session
4. Add Audio Part (TestMe.wav)
5. Double-click on audio part
6. Highlight a region
7. Right-click, DSP Functions, Gain of 1 db
8. Edit, Undo Gain
9. Edit, Undo Insert Part
10. Right-click, DSP Funtions, Gain of 1 db
11. Error: AppName: mulab.exe AppVer: 0.0.0.0 ModName: unknown
ModVer: 0.0.0.0 Offset: 006d756d

Happens every time. Seems to be a problem with undo, I think. Running on Windows XP SP2, Athlon 64 X2

Garry

Post

gathda wrote:Found an issue. Also happens in Beta D.

1. Open Demo.MuSession
2. Mixdown to Audiofile (TestMe.wav)
3. New Session
4. Add Audio Part (TestMe.wav)
5. Double-click on audio part
6. Highlight a region
7. Right-click, DSP Functions, Gain of 1 db
8. Edit, Undo Gain
9. Edit, Undo Insert Part
10. Right-click, DSP Funtions, Gain of 1 db
11. Error: AppName: mulab.exe AppVer: 0.0.0.0 ModName: unknown
ModVer: 0.0.0.0 Offset: 006d756d

Happens every time. Seems to be a problem with undo, I think. Running on Windows XP SP2, Athlon 64 X2

Garry
True. Will be fixed asap.

Thanks a lot for this detailed bug report!

Post

Remember Rapture causing problems on the VST scan - subsequent plugins ignored? Well, Beta E has made matters slightly worse: after ending the scan and displaying the error message, MU.LAB exits. :shrug: Unless this is indicative of a real problem, best ignore it: remember I'm only keeping Rapture to test error handling :).

Post

pljones wrote:Remember Rapture causing problems on the VST scan - subsequent plugins ignored? Well, Beta E has made matters slightly worse: after ending the scan and displaying the error message, MU.LAB exits. :shrug: Unless this is indicative of a real problem, best ignore it: remember I'm only keeping Rapture to test error handling :).
And does Rapture load fine in other hosts on the same machine?

(sorry if i already asked this)

Post

No, it's guaranteed crasher. I'm just highlighting that Beta D and Beta E behaviour is different (although maybe I should recheck D).

Post

pljones wrote:No, it's guaranteed crasher. I'm just highlighting that Beta D and Beta E behaviour is different (although maybe I should recheck D).
Nothing has changed in the vst engine from D -> E.

I think this is some "weird system incompatibility" issue...

Post

pljones wrote:No, it's guaranteed crasher.

as much as I love that synth, you are absolutely right!!!!!!!!!

I emailed cakewalk about this, they told me to download the latest patches, I said I had them, and they blew me off...

HA

great synth wtf

constantly crashing abe l 6, and no change now that I have LIve 7

Post

ckatrun411 wrote:
pljones wrote:No, it's guaranteed crasher.

as much as I love that synth, you are absolutely right!!!!!!!!!

I emailed cakewalk about this, they told me to download the latest patches, I said I had them, and they blew me off...

HA

great synth wtf

constantly crashing abe l 6, and no change now that I have LIve 7
Hi,

Could you please email me a project that is causing Rapture to crash. Also include instructions on how to easily reproduce.

ChadBeckwith[at]Cakewalk[dot]com

We can address this issue for a future patch.

Best,
Chad

Post Reply

Return to “MuTools”