MU.LAB Beta C

[muzycian]

On the PC side, I've been having trouble loading some tunes created in Beta b2 into Beta 3. There's a message: "MU.LAB Free cannot load so many tracks".

Has this changed between versions? This tune has 7 tracks (2 of them muted) and 6 racks.

Yes, from beta C on, the Free version only allows 8 tracks.

The other limits, only 4 synths and 8 racks, have gone.

In the Free version, VST synths receive only on channel 1.

[Edit: The Mac side is fine. Are files between platforms compatible, apart from usual VST stuff?]

Yes, MuSession files are 100% platform independent (except for any missing vst plugins of course, like you say).

[pljones]

Hmm. Just noticed: "ADRS" envelope? Release before Sustain? A novel approach.

[Branis]

When you ctrl+select both the MuLab and the Racks windows (on the windows taskbar) and tile them horizontally, the racks go on top. Is it possible to make it the other way around?

NuSofting DK+ has an option to export the sequence from the integrated pattern sequencer by dragg&drop onto the arranger window. This doesn't work in MuLab, instead a midi file is saved in the MuLab folder.

[SonicBreeze]

Found a Midi Output and Session bug :

1. Start a New Session with Default Project Tempo 120 BPM.

2. Import Midi File (Song) it says 'This Session now has Two Compositions'. Fine... and It show 'No Target' at upper Routing tool bar.

3. Assign this Midi Sequence part a Midi Output Port ( In my case it was 'USB Audio Device' which is ESI Midimate connected to my Hardware Synth).

4. Play it. It plays fine with no problem at all.

5. Save this MuSession.

6. Close MU.LAB and restart it. It will ask to open the same session.

7. Open Session. Whew... Tempo is Changed to 146 BPM and Midi Sequence part/song is there and it show its roued to "Midi Output' instead od 'USB Audio Device'. Now there is no Sound coming from My Hardware Synth.

8. You can't even assign a Midi Output to this Midi file/Sequence part now because 'Midi Output' List option is Vanished.

[muzycian]

Hey Jo, Not sure if your aware... I am having massive vst plug in issues. Crash on creation of Elastik

Can't find a demo of Elastik.

no gui on rapture

Strange:

Here, on my system, Rapture works OK

On pljones' system, Rapture hiddenly crashes during scan, leaving a corrupt system

And on your system, Rapture scans OK, but no gui is seen.

Johnny, i'm sure Rapture does play fine in other hosts?

no sound of virsyn synths Tera + miniTera

miniTera plays fine here

no predator

Predator scans fine here, but i do get occasional crashes when plugging Predator in.

I've researched this, and i've sent email to Rob Papen with detailed info and a question. Hope they respond.

crash on Rm4

Scans and loads fine here

[muzycian]

Jo, I hate to tell you, but we are having serious crash and burn vst plug in issues over here... cam space, nomad fac, pluggo, mike norris... all these things just aint working, and causing crashes..

Camel space plays fine here

I'm sorry but this is very weird.

All these plugs not working on your system, but they do work here, i don't understand.

And all these plugs do work in other hosts on the same system???

Johnny, at what point do these plugs cause crashes:

when you scan them, or when you actually use them and send audio/midi to them?

[muzycian]

Jo, I hate to tell you, but we are having serious crash and burn vst plug in issues over here... cam space, nomad fac, pluggo, mike norris... all these things just aint working, and causing crashes..

Hi are you on PC or MAC?

I am having problems with Firebird+ V1.8
After i have tweaked some knobs on it it freezes and crash afterwards.
In Beta A and B2 it worked Fine.

My system is:
Windows XP Homeedition with Sp2 and all the latest updates.

I've downloaded Firebird and it does not want to load here.

I've checked with Dependency Walker and it seems that these files are missing:

DWMAPI.DLL
EFSADU.DLL

I remeber that a week or 2 ago, we had a similar issue with CM Vocoder.

But now the strange thing is that, as i wanted to doublecheck things, Dependency Walker tells this for almost any plugin here, but they do load fine. So it seems that these missing files is not the *very* reason for the failure.

I'm getting totally pissed by all these vst plugins problems.

At this moment i very much understand Propellerheads' strategy: no vst plugins...

[muzycian]

When you ctrl+select both the MuLab and the Racks windows (on the windows taskbar) and tile them horizontally, the racks go on top. Is it possible to make it the other way around?

Not supported, please arrange the windows by hand. And use F1-2-3 to switch between the various views.

NuSofting DK+ has an option to export the sequence from the integrated pattern sequencer by dragg&drop onto the arranger window. This doesn't work in MuLab, instead a midi file is saved in the MuLab folder.

External drag and drop is not yet supported.

[muzycian]

Found a Midi Output and Session bug :

1. Start a New Session with Default Project Tempo 120 BPM.

2. Import Midi File (Song) it says 'This Session now has Two Compositions'. Fine... and It show 'No Target' at upper Routing tool bar.

3. Assign this Midi Sequence part a Midi Output Port ( In my case it was 'USB Audio Device' which is ESI Midimate connected to my Hardware Synth).

4. Play it. It plays fine with no problem at all.

5. Save this MuSession.

6. Close MU.LAB and restart it. It will ask to open the same session.

7. Open Session. Whew... Tempo is Changed to 146 BPM

Indeed a bug: the tempo field is not updated on tempo changes. Will be fixed.

and Midi Sequence part/song is there and it show its roued to "Midi Output' instead od 'USB Audio Device'. Now there is no Sound coming from My Hardware Synth.

8. You can't even assign a Midi Output to this Midi file/Sequence part now because 'Midi Output' List option is Vanished.

Indeed, bugs too

Thanks for reporting this. Will be fixed asap!

[muzycian]

I'm getting totally pissed by all these vst plugins problems.

At this moment i very much understand Propellerheads' strategy: no vst plugins...

I wonder wether it is related with the Windows Xp <-> Vista <-> Explorer 7 changes.

I get the impression they're messing around a bit at ms.

Not only saying this in this context, but it's meant more general.

It's not normal that a major update of an OS is rejected so hard, right?

[D-Fusion]

Jo, I hate to tell you, but we are having serious crash and burn vst plug in issues over here... cam space, nomad fac, pluggo, mike norris... all these things just aint working, and causing crashes..

Hi are you on PC or MAC?

I am having problems with Firebird+ V1.8
After i have tweaked some knobs on it it freezes and crash afterwards.
In Beta A and B2 it worked Fine.

My system is:
Windows XP Homeedition with Sp2 and all the latest updates.

I've downloaded Firebird and it does not want to load here.

I've checked with Dependency Walker and it seems that these files are missing:

DWMAPI.DLL
EFSADU.DLL

I remeber that a week or 2 ago, we had a similar issue with CM Vocoder.

But now the strange thing is that, as i wanted to doublecheck things, Dependency Walker tells this for almost any plugin here, but they do load fine. So it seems that these missing files is not the *very* reason for the failure.

I'm getting totally pissed by all these vst plugins problems.

At this moment i very much understand Propellerheads' strategy: no vst plugins...

He-he. i understand your frustration M8
I also think about it sometimes when i buy a vst and it does'nt work.

The weird thing is that i have the fullversion of CM Vocoder from image line and it is working fine here.

[D-Fusion]

DWMAPI.DLL
EFSADU.DLL

Those Dlls should'nt be needed from a vst.

The DWMAPI.DLL is a Vista only Dll and the EFSADU.DLL is tied to the EFS File encryption, so if you don't have the EFS enabled the EFSADU.DLL will be missing

You can find more information about those two dll's from here.
http://www.msfn.org/board/Missing_DWMAP ... 93950.html

[muzycian]

Hmm. Just noticed: "ADRS" envelope? Release before Sustain? A novel approach.

Will be fixed, thanks.

[libero]

Hi,
wow, the modular area is great. and the synth... amazing stuff!
I have a couple of questions:
muverb seems to ask a lot of cpu here, 30% at least.
Is it normal?

I'm on a powerbook g4 1Ghz with 1 GB of ram.
system is mac os 10.4.10

Also, sometimes the cpu indicator number doesn't show. I have to quit and reopen MU.LAB to get it working again.

Best regards,

Libero

[oldguy]

Hi Jo, Here's my feedback on MuLab C as a beta tester:

Bugs (duplicated more than once on my computer. - Athlon XP 2000+, XP, Presonus Firebox.)

#1: Created New Rack. Attempted to add new Synth. Selected "VST." MuLab Crashed. (Note that I had not yet added any VST in the VST Manager.) Adding VST's to the VST Manager fixes the problem, but program needs to have trap for this user error.

#2: Set external audio to Wavosaur. Stop play transport. Clicked on audiopart file. Rightclick, select 'Edit in External Audio Editor.' Wave file opens in Wavosaur. Simply quit Wavosaur, close file.
Start play transport - Other midi and audio parts play fine, but 'edited' Audio part quits playing in MuLab. It sometime plays a quick snip but then stops. Shows OK in editors.

Can reopen and see/play silent part in Wavosaur from MuLab, but it won't play in MuLab.

Restart MuLab. Part plays great again.

This used to work fine in Luna...

Documentation

#1: Need to update the user (introduction page) documentation to reflect the new feature set of MuLab free - unlimited synths and racks, but limited tracks. (BTW - I think this is the right way to go.)

Update some pages to show new skin and change Luna to MuLab.

Ease of Use

#1:
Open Luna 8.4 session file with waves and midi. Three instrument racks are all routed to 'output' rack where monitoring VST runs and final sound processing takes place.

Delete the output rack.

Add new main output rack. Assign outs from other three racks.

The 1st rack stopped playing (1st rack is fed from wav files and processes them through Anwinda Soft DX Reverb Light). Investigation shows that the 1st rack audio output is not assigned to go to the output rack, but the midi output instead. The output from the other two racks was assigned properly as Audio.

Come to find out that I'd been right clicking and changing the output assign mode to Event - aka, midi. It was not obvious that I was assigning the Midi output instead of the audio. Suggest changing the Speaker symbol to a Note symbol when the Event output is selected on a rack? Add another output just for Midi at the bottom?

Keep up the great work. More later.

-Oldguy.