M3 Tests

[liquidsound]

Please first connect at least 1 output of Reason in the MPA to the rest of the modular graph before double clicking 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.

Sorry Jo. I don't want this to turn into a tutorial but yes, now by following your latest instructions I get to load Reason but no matter how I connect the MPA Reason's Plugin outputs to any Rack (in the MPA) I get the audio coming out only from Rack A[1] while doing the exact thing in 2.7 I get each Synth in Reason to whatever Rack I want.
The exact same protocol. Something has changed in M3 regarding ReWire.

http://www.box.net/shared/ly0uzvf991

BTW the OVERLOAD must be from my borrowed D-HELL!! laptop I think.
My original workstation is down (security chip issue) and I have been doing all my tests at work on a server without audio!!!. That's the best I could do to help with M3. So never mind the OVERLOAD. I am pretty sure is my PC.

[MuTools]

Please first connect at least 1 output of Reason in the MPA to the rest of the modular graph before double clicking 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.

Sorry Jo. I don't want this to turn into a tutorial but yes, now by following your latest instructions I get to load Reason but no matter how I connect the MPA Reason's Plugin outputs to any Rack (in the MPA) I get the audio coming out only from Rack A[1] while doing the exact thing in 2.7 I get each Synth in Reason to whatever Rack I want.
The exact same protocol. Something has changed in M3 regarding ReWire.
http://www.box.net/shared/ly0uzvf991

Oh man i'm sorry

It's a limit of MU.LAB Free: Only mono output for ReWired devices.

BTW the OVERLOAD must be from my borrowed D-HELL!! laptop I think.
My original workstation is down (security chip issue) and I have been doing all my tests at work on a server without audio!!!. That's the best I could do to help with M3. So never mind the OVERLOAD. I am pretty sure is my PC.

Ok.

[liquidsound]

Oh man i'm sorry
It's a limit of MU.LAB Free: Only mono output for ReWired devices.

I'll wait for the Final Release.

(MONO...? What this has to do with sending everything to Rack A? Don't need to explain. I know you are busy but I'am getting trying to understand the inner works of MuLab. It's going to be my final DAW from now on.)

Thanks

[MuTools]

Oh man i'm sorry
It's a limit of MU.LAB Free: Only mono output for ReWired devices.

MONO...? What this has to do with sending everything to Rack A?

I'll try to explain better: In MU.LAB Free, all outputs of a ReWired device are mixed down to 1 single mono output. This is one of the MU.LAB Free limits.

[MuTools]

Regarding the MU.LAB Free mono rewire thing: Didn't you get that alert "MU.LAB Free only ReWires in MONO"?

Maybe the alert text is not good enough?

Is this better: "MU.LAB Free only rewires to 1 single mono output"?

[pquenin]

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.

Ok, i's not a big issue...

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?

Open a empty new session, zoom in to have the horizontal scrollbar, then go to the right : when you are around bar 32 the grid start to be not aligned with the ruler...

I have also encountered 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.

The way you draw controller curves in Mulab is not very good : when snap is ON, why not add a point each time a "snap point" is encountered (and the curve simply connect each point), so that we can modifiy only the bad points if we want to alter the curve. As it is now, we have to redraw the whole curve. Maybe you can download the demo of Andry Red Planet Temper : it's a VST host that seem to be abandoned, but it is filled with good ideas, and I like the way controller curves are handled...).

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?

I have encountered this only once, I've never reproduced this even with the GTG 44 S VSTi I was using...

[MuTools]

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?

Open a empty new session, zoom in to have the horizontal scrollbar, then go to the right : when you are around bar 32 the grid start to be not aligned with the ruler...

Indeed. Will be fixed. Thanks!

The way you draw controller curves in Mulab is not very good : when snap is ON, why not add a point each time a "snap point" is encountered (and the curve simply connect each point), so that we can modifiy only the bad points if we want to alter the curve. As it is now, we have to redraw the whole curve.

Huh? Why do you have to redraw the whole curve?

You can draw a line from-to where you want, and only redraw a part of the curve (from-to)

Maybe you can download the demo of Andry Red Planet Temper : it's a VST host that seem to be abandoned, but it is filled with good ideas, and I like the way controller curves are handled...).

I'll try to find time one day. I like to learn.

[MuTools]

Maybe you can download the demo of Andry Red Planet Temper : it's a VST host that seem to be abandoned, but it is filled with good ideas, and I like the way controller curves are handled...)

Ok, downloaded it, i see what you mean.

It's about breakpoint envelopes.

It's on the whishlist.

[pquenin]

Great !

Another thing : I don't see "Zoom selection" in the Shorcut functions : why ?

[MuTools]

Another thing : I don't see "Zoom selection" in the Shorcut functions : why ?

Will do!

[liquidsound]

Regarding the MU.LAB Free mono rewire thing: Didn't you get that alert "MU.LAB Free only ReWires in MONO"?

Maybe the alert text is not good enough?

Is this better: "MU.LAB Free only rewires to 1 single mono output"?

For a beginner or for less misunderstanding, "Mono" could also mean that it's just "Not Stereo" which is quite different than saying "everything on one Mono Output".

"MU.LAB Free only rewires to 1 single mono output"? = Yes. Much better.

[MuTools]

"MU.LAB Free only rewires to 1 single mono output"? = Yes. Much better.

Yes i think so too. Tuned in the next version!

[pquenin]

By default, the mouse wheel is mapped on the zoom. And shift + mouse wheel = scroll. Is it possible to inverse this ?

[liquidsound]

By default, the mouse wheel is mapped on the zoom. And shift + mouse wheel = scroll. Is it possible to inverse this ?

I tend to agree... Wheel scrolling is more natural

Wow, "Edit Shortcuts" has no Shortcut

[liquidsound]

It would be also useful to be able to Wheel Scroll while grabing a note or Part to overcome the lack of auto scroll window in the Composer and key editor.
It eliminates the double action to zoom out (and/or zoom in again) to position a Note/Part in the right place, mostly with small grid setting and long parts.

Or at least being able, while grabbing (holding a note/part,) to RightClick Scroll, as it is now implemented, to freely scroll where is needed.

<edited>

Maybe a "Zoom in" "Zoom Out" shortcuts while holding something (less elegant).