M4 Test

[MuTools]

Jo, there is something wrong with the Midi setup...

Especially, if you create a Midi Output module doubleclick it and quit the window with ok more than 1 times leads often into a crash here...

Can't immediately repeat that here.

Is there also a crash when you go (multiple times) to MULAB -> MIDI Setup and click OK there?

What crash happens? Red dialog box, Windows crash box? Hang?
Maybe post a screenshot if relevant?

Anyone else having a crash prob with MIDI setup?

[pljones]

In addition to not being able to get my note velocities back...

If I've got some notes along with a set of controller events, I can select all the notes with Ctrl-A... but this leaves all the controller events unselected, so if I pull the notes to the start of the sequence, the controller events no longer line up.

Is there a way to select all events in a sequence?


----

On the MIDI Setup crashing... well, no, didn't get a crash and it was probably something I was doing but I managed to get to needing to re-install MIDI Yoke... (I'd had Reaper and MULAB both running, got some expected complaints, stopped MIDI OX, Reaper and MULAB - and MIDI Yoke driver had crashed; rebooting didn't fix it... weird. I'd also just updated my AudioFire4 driver, so this is too messy to worry about!!!)

[MuTools]

Though when I saved a session, having set up my key, I got launched to the shop.

Oops only saw this now, was this added afterwards?

On topic: Well i guess this happened only once right?

[pljones]

Oops only saw this now, was this added afterwards?

Might have been... I'm a terror for quick edits...

On topic: Well i guess this happened only once right?

Yes, this was on closing MULAB; next time it opened with the key in place and it hasn't done it again.

[MuTools]

In addition to not being able to get my note velocities back...

Oops, i don't know what's this about. Did you post something about this?

If I've got some notes along with a set of controller events, I can select all the notes with Ctrl-A... but this leaves all the controller events unselected, so if I pull the notes to the start of the sequence, the controller events no longer line up.

Is there a way to select all events in a sequence?

Method 1: Select all in the note editor + select all in the controller editor.
When using a key shortcut, the focus defines which editor section does the Select All. This method is only interesting if there is only one controller used.

Method 2: Logical Selector with no criteria.

Method 3: List Editor -> Select All.

[pljones]

Actually... the "Buy now/Maybe later" prompt could have an "Enter key" option, if you've already got a key...

[pljones]

In addition to not being able to get my note velocities back...

Oops, i don't know what's this about. Did you post something about this?

Easily overlooked - I had trouble finding it:
http://www.kvraudio.com/forum/viewtopic ... 43#4812243

[Trancit]

Can't immediately repeat that here.

Is there also a crash when you go (multiple times) to MULAB -> MIDI Setup and click OK there?

What crash happens? Red dialog box, Windows crash box? Hang?
Maybe post a screenshot if relevant?

Anyone else having a crash prob with MIDI setup?

I could narrow it down a little bit...

It happens to me as soon as I set up the same Midi driver in the Input port 2 and Output Port 2...

I was able to get one red crash box on closing of MuLab after I opened the normal Midi setup window a few times (but this only happened once)...

But with the midi output module I get the crash (Windows own crash box: MuLab.exe doesn't work anymore ...with the option to close the app) everytime...

I tested it with my virtual Midi driver (Maple) and with my normal midi driver from my EMU soundcard...both crash after open the midi setup 2-4 times from the Midi Output module...everytime
But it does not happen with the Automap Midi port from my Novation Nocturn...

Perhaps it is related to my system...dunno, I first thought about midi feedback problems, but this should not happen with the EMU drivers...

[pljones]

(unwrecked...)

Method 1: Select all in the note editor + select all in the controller editor.
When using a key shortcut, the focus defines which editor section does the Select All. This method is only interesting if there is only one controller used.

Method 2: Logical Selector with no criteria.

Method 3: List Editor -> Select All.

4. Right-click, Select All in either area of the sequence editor.

With any of these, however, when I try to use the hand tool on a note, the controller events aren't picked up.

I managed to do what I was after using right-click, cut then right-click, paste. But it'd be nice if drag'n'drop worked (i.e. the click-drag action didn't unselect anything).

[pljones]

In addition to not being able to get my note velocities back...

Oops, i don't know what's this about. Did you post something about this?

Easily overlooked - I had trouble finding it:
http://www.kvraudio.com/forum/viewtopic ... 43#4812243

Ah, found it.

Track->Set MIDI Channel: Part
Part->Set MIDI Channel: Event

That then let me select the right events

[Nielzie]

Tranciiiiiiiiiiit

Ok, I've just checked again...forget about the doubleclick on the Midi Out module in the session modular area...but if you hover the mouse over the inputs of the Midi Out module, it shows, which connector reflects each output you have set up before...

Here is a little guide with pictures:

Hey many thanks Trancit, I got it working now, but only with an Arp plugin, like in your tutorial

When I try the same with a step (multi)sequencer, then it goes all weird and crash prone (red crash boxes). But I'm sure that when MuLab get's an event recorder that also will work fine eventually.

[MuTools]

Ah, found it.

Track->Set MIDI Channel: Part
Part->Set MIDI Channel: Event

That then let me select the right events

Yes indeed.

I assume you imported single track multi channel midi file, right?
In that case MuLab should auto set track to "per part" and the part to "per event". Tuned in the next version. (in case the midi file is imported as a new composition; the other case has a note on the WL)

[pljones]

I managed to do what I was after using right-click, cut then right-click, paste. But it'd be nice if drag'n'drop worked (i.e. the click-drag action didn't unselect anything).

The editing functions are also very useful, for when the visual approach isn't so easy. One of the bits I was editing had an pick-up beat phrase before the main part came in... and I could not get it lined up nicely by cut'n'paste... but simply subtracting two bars got it to where I wanted it.

[Nielzie]

Anyone else having a crash prob with MIDI setup?

Just investigated this and indeed when opening MIDI setup by double clicking the Midi Output module in the Session Modular Area it crashes very often (after 2-4 times usually).

I didn't notice before because I used to open the Midi Setup via the MuLab knob menu all the time. The crashes do not happen then.

Also using a same (virtual) MIDI port for MIDI in and MIDI out in the setup (but not the same one as Trancit does). I get just a Windows application crash window, not the MuLab red box window.

What might also be interesting to know is that when I open the Session Modular Area before I have opened the Midi Setup, then there is no MIDI Output module in the displayed in the Modular Area.

I have to open the MIDI Setup first (without changing anything, the right ports are already set) and click Cancel or Done and then the MIDI Output module pops into the Modular Area window.

[MuTools]

Can't immediately repeat that here.

Is there also a crash when you go (multiple times) to MULAB -> MIDI Setup and click OK there?

What crash happens? Red dialog box, Windows crash box? Hang?
Maybe post a screenshot if relevant?

Anyone else having a crash prob with MIDI setup?

I could narrow it down a little bit...

It happens to me as soon as I set up the same Midi driver in the Input port 2 and Output Port 2...

I was able to get one red crash box on closing of MuLab after I opened the normal Midi setup window a few times (but this only happened once)...

But with the midi output module I get the crash (Windows own crash box: MuLab.exe doesn't work anymore ...with the option to close the app) everytime...

I tested it with my virtual Midi driver (Maple) and with my normal midi driver from my EMU soundcard...both crash after open the midi setup 2-4 times from the Midi Output module...everytime
But it does not happen with the Automap Midi port from my Novation Nocturn...

Perhaps it is related to my system...dunno, I first thought about midi feedback problems, but this should not happen with the EMU drivers...

At the moment i assume it's a system specific issue.
It should be the same in MuLab 3 then, using the same setup. Right?