MuLab 10.0.85

[MuTools]

Got another minor bug -- it looks like when I create a Note Key Mapper, whilst it does the work and carries on working, if I go in to edit it, the display has reset (C4 is selected and nothing else).

Can't repeat it:
I opened the Note Key Mapper, selected F4, mapped a chord to it, closed the editor, opened the editor again, F4 was still selected, chord was still there.

Please elaborate or make a screen video of the issue you encounter. Maybe best to use a standard screen recorder as the previous videos had issues.

[pljones]

OK, weird. Now it's not saved it at all. I'll try again from scratch...
1. In Reaper, add MuLab Plugin Effect on a MIDI All input track
2. Strip the project back to VST MIDI In, VST MIDI Out
3. Add Event Monitor and make that the Main module for the project, link this to VST MIDI Out; add a second Event Monitor and link this to VST MIDI In
4. Link an Note Key Mapper between VST MIDI In and the main Event Monitor (connected to the Out)
5. Switch from Octave to Full range and do "Clear All"
6. Map C#3 to C#-1 (main Event Monitor shows All Notes Off)
7. Use the Reaper keyboard (Alt-B) to check that's working
8. Save MuLab project, save the Reaper project
9. Close and reopen Reaper for the saved project and use the onscreen keyboard to check the patch still works
10. Open up the modular area, double click the Note Mapper and ..... C4 is selected as Input and nothing as Output, despite it working...

It's the same if I open temp.MuProject back in MuLab App -- C4 is selected as Input and nothing as Output (I can't get the MuLab onscreen keyboard to focus on anything, though)

Reaper project: http://peter.drealm.info/media/saved.rpp
MuLab project: http://peter.drealm.info/media/temp.MuProject

[MuTools]

Which input key is highlighted is not saved.
So if you save the project with G4 highlighted, then reopen the project, the default C4 will be highlighted.
But which input key is highlighted only is an editor aspect and does not have any impact on the processing.
So on reopening the project everything still sounds exactly the same.

Does this match/clarify what you are reporting?
Or do you mean something else?

NB: I can't open your URLs as they're blocked by security.

[pljones]

It means it's not a usable editor -- if I can't see the current settings, how can I know what they are? If I've created three (or a dozen...) mappings for three separate keys and I want to change one of them, I need to know which is which without messing around disconnecting each in turn until I work it out the hard way. The display should match what the control is doing.

[Teksonik]

Is there a demo version of 10.0.46 ? I'd like to try MuLab but would like to try the latest version.

[MuTools]

It means it's not a usable editor -- if I can't see the current settings, how can I know what they are? If I've created three (or a dozen...) mappings for three separate keys and I want to change one of them, I need to know which is which without messing around disconnecting each in turn until I work it out the hard way. The display should match what the control is doing.

I've spent another decent amount of time trying to understand what you mean, but i don't understand, sorry. Please make a screen video clearly explaining what you mean.
(best using a standard screen recorder)

[MuTools]

Is there a demo version of 10.0.46 ? I'd like to try MuLab but would like to try the latest version.

Sure: https://www.mutools.com/mulab-app-downloads.html

[Teksonik]

Ok thanks, downloaded. I can't seem to figure out how to make MuLab go full screen. I'm sure it's something simple but I'm missing it so far.....

[pljones]

It means it's not a usable editor -- if I can't see the current settings, how can I know what they are? If I've created three (or a dozen...) mappings for three separate keys and I want to change one of them, I need to know which is which without messing around disconnecting each in turn until I work it out the hard way. The display should match what the control is doing.

I've spent another decent amount of time trying to understand what you mean, but i don't understand, sorry. Please make a screen video clearly explaining what you mean.
(best using a standard screen recorder)

Which input key is highlighted is not saved.
So if you save the project with G4 highlighted, then reopen the project, the default C4 will be highlighted.
But which input key is highlighted only is an editor aspect and does not have any impact on the processing.
So on reopening the project everything still sounds exactly the same.

Does this match/clarify what you are reporting?
Or do you mean something else?

NB: I can't open your URLs as they're blocked by security.

You said it yourself -- you don't save the current settings. That means the "editor" isn't an editor, it doesn't show anything useful. It means if you make a mistake and come back to change something, you have to check where the mistake is, not by looking at the settings, but by pulling the wires out until you find the one that's wrong.

[MuTools]

Ok, so i understand that you're answering 'yes' to my question whether the issue you're encountering is that the highlighed key is not preserved in the project file data.

Note that it is preserved within a project session though, so the issue you're focusing on only happens after you reopened a project, not within a project session.

You wrote earlier you have mapped several keys. Now you also wrote

It means if you make a mistake and come back to change something, you have to check where the mistake is, not by looking at the settings, but by pulling the wires out until you find the one that's wrong.

First of all: I really don't understand what you mean with having to pull wires out. Please explain. Why not simply click the input keyboard to see the mapping of an input key?

Also this: Lets assume the highlighted input key would be saved in the project file data, but the edit you need to make is not on the highlighted key, then the whole issue you're focusing on still remains the same, right?

I still think a screen video demonstrating the workflow issue you're encountering would be more easy and efficient than these many text messages as we're having a difficult time to understand each other by text.

[MuTools]

Ok thanks, downloaded. I can't seem to figure out how to make MuLab go full screen. I'm sure it's something simple but I'm missing it so far.....

MuLab starts full screen by default, that is taking your system preferences about the task bar into account. So as you ask the question i assume you have a non hiding taskbar and you want MuLab to go really full screen overwriting the task bar, right?

[pljones]

OK, I learned one thing I didn't know - you can set up multiple maps in the mapper: I thought it was single input to one or more outputs, not many inputs to many outputs. That helps a lot anyway (and greatly reduces the problem I'm working on immediately!!). Given that there are multiple inputs, I now see why it makes no sense to display any particular input key. That was what I was missing. Sorry!

(I tried recording and thought I said "no" to "only main window" - but it only recorded the main window, so it doesn't show anything useful.)

Edit: it might be nice to shade or highlight somehow those keys already mapped, though - it doesn't matter what's selected or shown first but being able to see what you've done already it still useful.

Edit2: Also having MuNoteMapper.Backup files would be nice... (I just overwrote one -- no undo for save)

[Teksonik]

Ok thanks, downloaded. I can't seem to figure out how to make MuLab go full screen. I'm sure it's something simple but I'm missing it so far.....

MuLab starts full screen by default, that is taking your system preferences about the task bar into account. So as you ask the question i assume you have a non hiding taskbar and you want MuLab to go really full screen overwriting the task bar, right?

Yes I'd like MuLab to go over the bottom taskbar without having to use the Windows auto hide function.

[MuTools]

Yes I'd like MuLab to go over the bottom taskbar without having to use the Windows auto hide function.

The next MuLab 10.0.47 update will have such option. In the current MuLab 10.0.46 there already are some other options and if you're on a 1920x1080 screen you can already use "Size FHD 1920x1080". But the next M10.0.47 will have an explicit "Full Screen" option too.

[MuTools]

OK, I learned one thing I didn't know - you can set up multiple maps in the mapper: I thought it was single input to one or more outputs, not many inputs to many outputs. That helps a lot anyway (and greatly reduces the problem I'm working on immediately!!). Given that there are multiple inputs, I now see why it makes no sense to display any particular input key. That was what I was missing.

To also respond some of your other feedback points:
The next M10.0.47 update will also memorize the view position of the input and output keyboards, and the highlighted key and both these view positions will be saved data.

(I tried recording and thought I said "no" to "only main window" - but it only recorded the main window, so it doesn't show anything useful.)

If you chose "no" on that question then the screen rectangle of the project window is recorded.
If that Note Mapper window is not inside the project window screen rectangle then it won't be visible in the video. Does that clarify it?