newbie accomodation

[MuTools]

It happened to me that I disconnected USB MIDI device while running MULAB when I wanted to free an USB port. Everything looked fine until I visited MIDI Setup dialog, just for curiosity, but it didn't even appear - the whole application just freezed and had to kill it manually.

That's not a supported operation in MU.LAB.

I can imagine MU.LAB will not be the only application suffering from such operation. The problems may even be starting on driver level.

Also, horizontal bar slider of piano roll should be reworked - it is extremly sensitive. Move it just one pixel to the right and it travels from bar #1 to bar #246712, an another pixel and the current bar is #493422 when it is moved further to the right a large amount of number is exceeded and an application freezes. To reproduce, simply import this MIDI sequence and open it in roll piano:

http://www.live-styler.de/kksound/LS-8BtHiString.mid

This is very related with an earlier reported MIDI file issue.

Please retry importing this special MIDI file into MU.LAB Test F which will be released tomorrow. Test F has more robust handling of more special MIDI files.

Note already that this MIDI file contains a trigger note, i.e. a note that never ends.

Another freeze I experienced after importing the following MIDI file and trying to open any of its tracks for editing (the piano roll did not even showed up):

http://www.live-styler.de/kksound/1DOOM.MID

Same answer as above.

Besides, I can't find a way to use MIDI OUT ports in MULAB. I select several ports in MIDI setup dialog but when I want to use any of them as sequence target there are no MIDI outputs listed ("No MIDI Output"). I tried to find something in documentation but with no luck. What do I do wrong?

MU.LAB differentiates between a MIDI port (MIDI Setup) and a MIDI Output (MPA).

In order to use MIDI Output there are 2 things to check:

-> Check Edit menu -> MIDI Setup -> Choose at least 1 MIDI output port
-> In the MPA, double-click the MIDI Output box (create one if not yet there) and choose one of the MIDI ports that you have activated in the previous step.

By default, when you do 'New' MU.LAB automatically creates a MIDI Output for each activated MIDI output port.

Hope you see the picture.

Now, there are severe problems with recording overwrite mode (seems like it is still under development).
These are following:
- record some MIDI messages once and tell the program to put them into sequencer by overwritting data
- record again and tell it the same - the messages will be recorded in incorrect place, and the sequence will be artificially expanded. Now when I try moving transport after ending point (look at the image below) a message is generated:

Tried repeating it here, but couldn't find a problem.

Is this repeatable? If yes, could you please list step by step how to repeat the problem. Thanks.

Btw. a question - is there poly pressure support planned? I know it is rare as a hardware controller but quite common in sequencers.

MU.LAB's Event List Editor does support Poly Pressure.

Test F has some more finetunings regarding poly pressure, but it should already work fine in Test E too

[KrzysiekK]

Note already that this MIDI file contains a trigger note, i.e. a note that never ends.

Now I get it, I wasn't aware of that.

-> In the MPA, double-click the MIDI Output box (create one if not yet there) and choose one of the MIDI ports that you have activated in the previous step.

I am sorry for bothering but, although I've already chosen MIDI Out port in MIDI Setup dialog, in MPA grid there is one unconnected "No MIDI Output"-titled port box visible. When I doubleclick it there is "nothing to edit" message. However, still in MPA, after I choose Add Plugin->Input Output->Event Output, a box appears with the name of the first MIDI Out port selected in MIDI I/O Settings. So this is probably what I need, but now I can see no way to choose other MIDI Out port if there are more then one activated in MIDI I/O settings because when I doubleclick the "event output" box I just created , same "nothing to edit" message popups.

By default, when you do 'New' MU.LAB automatically creates a MIDI Output for each activated MIDI output port.

Yes, I confirm this.

Tried repeating it here, but couldn't find a problem.

Is this repeatable? If yes, could you please list step by step how to repeat the problem. Thanks.

I will make a video and write a description.

Best regards,
Krzysiek

[MuTools]

I am sorry for bothering but, although I've already chosen MIDI Out port in MIDI Setup dialog, in MPA grid there is one unconnected "No MIDI Output"-titled port box visible. When I doubleclick it there is "nothing to edit" message.

Oops, right, there's a bug. Will be fixed in Test F, which will be released tomorrow (normally). Test F is only fixes and tunings.

[MuTools]

Tried repeating it here, but couldn't find a problem.

Is this repeatable? If yes, could you please list step by step how to repeat the problem. Thanks.

I will make a video and write a description.

Ok, thanks.

[KrzysiekK]

Unfortunately I did not reproduced the crash and I realized that the recording is being performed in correct way - this is because I didn't realize that each time I record something within a sequence using overwrite function, there is a loop of this recording created and it is repeated within the length of whole sequence (assuming the recording is shorter than the sequence) or the sequence is expanded (assuming the recording is longer than the sequence). However I think there is something wrong with displaying in roll piano view hence I've perceived the actual recording as incorrect.

According to this video : http://www.live-styler.de/kksound/overwrite.avi

1. in roll piano view when I record something longer than the loop (white area - see from 8s of recording), the transport is cycling within this loop section. I think it should pass into greyed area to show where the events are actually recorded. In fact this is apparent only after I do the recording (12s).

2. in roll piano view when I record something shorter than the loop (13s of the video and later), an actual position of the transport is proceeding according to the big bar display on top of the screen, while the cursor visible in roll piano jumps back to the beginning each time I am ready with recording. I think it shouldn't

Best regards,
Krzysiek

[MuTools]

Unfortunately I did not reproduced the crash and I realized that the recording is being performed in correct way

Anyway, from your previous screenshot there seems to be a bug somewhere, as the 'red alert' popped up. Could it have been a vst plugin?

If it would come back, please let me know preferrably together with a description of your very last actions.

However I think there is something wrong with displaying in roll piano view hence I've perceived the actual recording as incorrect.

According to this video : http://www.live-styler.de/kksound/overwrite.avi

1. in roll piano view when I record something longer than the loop (white area - see from 8s of recording), the transport is cycling within this loop section. I think it should pass into greyed area to show where the events are actually recorded. In fact this is apparent only after I do the recording (12s).

New recorded events are only put into the resulting sequence once recording has been stopped. So at the time of recording it's not yet known where the events will come. And so in fact the display is correct as it shows the situation as it is now.

2. in roll piano view when I record something shorter than the loop (13s of the video and later), an actual position of the transport is proceeding according to the big bar display on top of the screen, while the cursor visible in roll piano jumps back to the beginning each time I am ready with recording. I think it shouldn't

In fact this is correct too.

Because once you decide to put the new recorded events into that sequence using 'Overwrite' option, the new recorded events are put in that sequence and MU.LAB will automatically set a default Start-Loop-End for these events, based on their recorded times.

And so just after finishing that recording, the sequence position line will jump to its start again because it's just beyond its new end point and it's immediately looping.

I hope i explain this well, it seems a bit bizar at first sight, but in fact it's normal.

Of course, you can easily change the default loop points for the new recording if you want by dragging the Start-Loop-End flags around in the sequence editor.

[Bonteburg]

BTW, Jo. Remember the "quantized parts drop the first note" bug a few months ago? It appears to have disappeared

[MuTools]

Wasn't that resolved already?

I remember the topic, but forgot the details...

(it's in some thread here, but which one..?)