MuTools

pquenin · Post by **pquenin** » Sat Jan 16, 2010 5:59 pm

I don't see the composition name in the title bar : is it normal ?

liquidsound · Post by **liquidsound** » Sat Jan 16, 2010 6:00 pm

mutools wrote:And the Part Property Panel is back in the game <-> Part Targets.

Home sweet Home

The Rewire error from the MPA still there...

mutools wrote:Look at the mouse cursor info box at the bottom right of the editor.
Based on the position info there, it's easy to know when snapping is on of off.

Yes, simplicity as usual. Neat!

Jo, the whole thing it's so good. It feels great.

TheGuysanIdiot · Post by **TheGuysanIdiot** » Sat Jan 16, 2010 6:37 pm

Hi pquenin,

Save the session first with a name.

Then you will see MU.LAB : "session name" : "composition name" in the title bar.

Hopefully.

OZ

MuTools · Post by **MuTools** » Sat Jan 16, 2010 7:01 pm

pquenin wrote:maybe a bug in 3.0.8 : when I change the tempo above the counter (the small one), the time position is not changed accordingly...

Could you please post/email a screenshot as i don't know what you mean, sorry.

MuTools · Post by **MuTools** » Sat Jan 16, 2010 7:02 pm

pquenin wrote:I don't see the composition name in the title bar : is it normal ?

I'll finetune this.

Also noticed that when renaming a composition, the main window title bar is not updated. Will be fixed.

MuTools · Post by **MuTools** » Sat Jan 16, 2010 7:04 pm

liquidsound wrote:The Rewire error from the MPA still there...

Please read my previous post about this.

In short: first connect the ReWired device!

mutools wrote:Look at the mouse cursor info box at the bottom right of the editor.
Based on the position info there, it's easy to know when snapping is on of off.
Yes, simplicity as usual. Neat!

Jo, the whole thing it's so good. It feels great.

Bugs please!!

(euh, thanks! Thanks to you all!)

Nielzie · Post by **Nielzie** » Sat Jan 16, 2010 7:13 pm

mutools wrote:No, MU.LAB is distributed in a zip package, lean and mean.

Ok, but remember that no installer could scare of people who are new to DAWS, music software, etc. especially when they go comparing with other DAWS.

I personally don't have any problems with not having an installer and most of us "tweakers" at KVR don't and shouldn't either, but it also may look less professional and more "obscure" to others that a user does have to unzip, copy, make shortcuts by himself. Especially for someone who is not so bright with computers.

If you want to market MULAB as an easy-for-beginners (less bells and whistles, etc.) DAW, then an installer could be more appropriate. But then again, I don't know how you want to market this fine program. and what kind of (and how large) userbase you are aiming at

Just my 2 cents & no offense meant

pquenin · Post by **pquenin** » Sat Jan 16, 2010 9:34 pm

If I set the tempo to 60 bpm, the time position must change to 2 04, but you have to go to another location and come back to the same song position to have the correct value.

You can also see that if I scroll to the right, the ruler and the grid are not aligned !

I have also encounterded 2 bugs, but I cant reproduce them :
- in the Event Graph Editor, after a while, the pen tool has no effect : impossible to draw something,
- with the VST editor panel opened, I send program change to the VSTi, the sound change, but the patch name doesn't change.[/url]

liquidsound · Post by **liquidsound** » Sat Jan 16, 2010 9:41 pm

Bugs...OK

Open New Session
Rack A > Choose Plug-In > Rewire > Reason [Reason Loads]

In Reason
> New Mixer + New Thor

In MuLab
> Track/Rack B > Choose Target > Rack A > Reason
> Track/Rack B > Choose MIDI Channel > Open Drop-Down Channel Menu = OVERLOAD
> Quit Reason > Quit MuLab > Task Manager = Mulab.exe running > End Process > OK

I know I do not need to quit I can just click once in the OVERLOAD box but at least you know what's going on.

liquidsound · Post by **liquidsound** » Sun Jan 17, 2010 5:31 am

mutools wrote:
liquidsound wrote:The Rewire error from the MPA still there...
Please read my previous post about this.

In short: first connect the ReWired device!

Let me explain.

If "In short: first connect the ReWired device", all I get is 1 Rack to control all the devices audio output from Reason. No mixing except in Reason mixer.

BUT...

if I load Reason in the MPA first and then Edit/Load Reason from there THEN I am able to have each track sending to Reason's individual devices and for each Audio return from Reason I have a dedicated Rack so I can do all the mixing in MuLAb.

And (and this is Unique to MuLab!!!) I can have Parts targeting Reason's Devices. It's a Dream!:wheee:

This is what I was saying in regards to "The Other Way".

Reason becomes just a rack full of independent Plug-ins, like a VST folder.

Unless there is another way to do this, that ERROR is a problem.
This is how I was doing it in 2.7.

Please: Fix It

MuTools · Post by **MuTools** » Sun Jan 17, 2010 12:47 pm

Nielzie wrote:
mutools wrote:No, MU.LAB is distributed in a zip package, lean and mean.
Ok, but remember that no installer could scare of people who are new to DAWS, music software, etc. especially when they go comparing with other DAWS.
...

You make a point.

I think it's more a point on Windows than on OSX as on OSX the zip file is automatically extracted on the desktop, and so it's very ready to use.

Anyway, will reflect on this some more in the future.

Thanks.

bpblog · Post by **bpblog** » Sun Jan 17, 2010 1:13 pm

i'm also loving the zip and despise installers. still, having a zip/exe choice when downloading mulab wouldn't hurt anyone, plus installers are certainly more popular with people who don't mess with their computers too much.

MuTools · Post by **MuTools** » Sun Jan 17, 2010 3:05 pm

pquenin wrote:

If I set the tempo to 60 bpm, the time position must change to 2 04, but you have to go to another location and come back to the same song position to have the correct value.

When playing an audio file, and then changing the tempo on the fly, the audio also keeps on playing without recueing. If you want a recue, reset the position. I'll leave these aspects as they are now.

You can also see that if I scroll to the right, the ruler and the grid are not aligned!

Hey that's strange. Do you know how i can repeat this?

I have also encounterded 2 bugs, but I cant reproduce them :
- in the Event Graph Editor, after a while, the pen tool has no effect : impossible to draw something,

Lets keep an eye on it! Hopefully we can narrow down this issue.

with the VST editor panel opened, I send program change to the VSTi, the sound change, but the patch name doesn't change.

Strange, i tried this with AlphaCM and it all worked fine.

Which VST did you use? Can you repeat that issue with other VSTs?

MuTools · Post by **MuTools** » Sun Jan 17, 2010 3:09 pm

liquidsound wrote:Bugs...OK

Open New Session
Rack A > Choose Plug-In > Rewire > Reason [Reason Loads]

In Reason
> New Mixer + New Thor

In MuLab
> Track/Rack B > Choose Target > Rack A > Reason
> Track/Rack B > Choose MIDI Channel > Open Drop-Down Channel Menu = OVERLOAD

Do you have any idea why you get a CPU overload?

Are you indeed loading/mixing cpu-heavy songs?

MuTools · Post by **MuTools** » Sun Jan 17, 2010 3:13 pm

liquidsound wrote:Unless there is another way to do this, that ERROR is a problem. This is how I was doing it in 2.7.

Please: Fix It

Please first connect at least 1 output of Reason in the MPA to the rest of the modular graph before doubleclicking the Reason plug box.

In the MPA, plugins that are not connected are not processed. I think this is correct and good.

But Reason needs processing in order to work fine. So you have to connect Reason! Hope i explain well.

MuTools

KVR Audio

M3 Tests