Not playing the right track

[ftnwo2012]

On this multi track project, I can't play any track except the first one.
As shown in the attached screenshot (real time playing mode), I select and try to play the second track (or any other) but MuLab plays only the 1st one.
I tried to open a new project with several track and there, I can play any track.
This only happens on this project. But why ?
Where's the bug ?
I use the same keyboard with the same settings.
Moreover, on the plugins presenting a virtual keyboard, if I "play" it with the mouse, the notes come out.
But if I try with the real keyboard, it doesn't work while it works on any other project.

[MuTools]

Are you using VSTs?
If yes then replace the VSTs by internal sounds, just for test.
Then is does the issue still there?
If yes then zip + share/send that pure MuLab project.

[ftnwo2012]

So, with more explications:
I tried to delete all the tracks then open a new track with basic synth and no effects (on the same project).
It doesn't work.
If I click on the virtual keyboard of MuLab (so without playing the real keyboard), same thing, only the 1st track plays.
The real keyboard is recognized in midi setup and if I close this project and open a new one without any other changes, I can play normally any track but only on this project, I can't play any other tracks except the 1st one.
Yes, I use VSTs and if I play in audio mode (external instrument), here it works and I can play with the keyboard on this project.
I can play any VST on another project but not on this one.
And if i press play, the song "progresses" and all the vu-meters light up, all the tracks works.
But I can't add anything other than with the mouse.

[MuTools]

But I can't add anything other than with the mouse.

What do you mean with this?

And about event signals: Please doublecheck the event signal flow using Event Monitor modules.

[ftnwo2012]

I mean if i add some notes with mouse, it works. But if I add notes with keyboard, it doesn't work.
And nethertheless, without changing anything in settings, if I open a new project, I will be able to add any note, bend or acting with MW on any track with the keyboard.
I must admit that I have an ultra basic need for a DAW. I play, record, make some adjustments and I'm happy.
So I'm not sure what exactly you mean by "Event Monitor modules". Is that it ?

[MuTools]

The Event Monitor allows you to see how events flow.
It's in the "Event Processors" group.

[robert_p]

I mean if i add some notes with mouse, it works. But if I add notes with keyboard, it doesn't work.

I see on your screenshot that there is nothing connected to the "Event Input" pin - this might be the case

[ftnwo2012]

I tried the "event monitor" but as i don't know where to put it, I placed it on the "master" track.
It shows absolutely nothing and stays desperately black.
However, it cuts out the sound completely. The meters are agitated but I have no return.
Concerning the "event input pin", there is nothing but if I open a new project with the "basic synth", the "event input pin" is not connected to anything either.

[MuTools]

Also check Project menu -> MIDI Input Channel Targets.
For info see https://www.mutools.com/info/M9/docs/mu ... uting.html

Also check Project menu -> Monitor MIDI Input Notes.
That's a diagnostic tool to see which events MuLab receives at its very MIDI input.
From there on the events are dispatched using the MIDI Input Channel Targets setup (see above) and then the events further stream via the modular modules and connections.

If you don't know how to use the Event Monitor or why an Event Monitor doesn't bypasses audio signals, it feels like you need to learn more about MuLab's modular aspects like signal types, see https://www.mutools.com/info/M9/docs/mu ... ditor.html

[ftnwo2012]

With the "MIDI Input Channel Targets" there is a bit of a change. By assigning each track, where only the 1st played whichever one was chosen, now the 2nd plays too.
Problem: 1st continues to play at the same time and the others still do not respond present.
Concerning the "event monitor", I don't have an "event input" or "event output" connected but as I said, if I open a new empty project (except for the basic synth which appears automatically) , there is also no "in" or "or" plugged in and yet it works.
On all my other projects, there is also no "in" or "out" plugged in and it still works.
If I erase all tracks, the project is empty. I add a new and unique track without changing the project, without effect. That doesn't work.
(See 1)
I open a new basic project, it works even though I haven't made any changes.
(see 2)
No "input/output" and no "midi input channel target" in the 2 cases. The 1st doesn't work, the 2nd works.

[MuTools]

I have difficulties understanding your explanation.
Please distillate the most simple project, without VSTs, that demonstrates the issue you have questions about, zip it and share it here.

[pljones]

Also, in case you've not noticed, in the MIDI Input Channel Targets:

MIDI Input Channel Targets.png

, note that you have chosen to have your hardware inputs follow whatever you last focussed in MuLab.

[ftnwo2012]

On any of my projects, I've never bothered with "MIDI Input Channel Targets" (I just found out they exist) and it has always worked.
"note that you have chosen to have your hardware inputs follow whatever you last focused in MuLab"
I don't understand what you mean. I didn't do anything in particular.
As I said before, I use a very basic DAW. I place a VST or audio, I play, I record, I mix a little and voila!
I don't use at least 80% of MuLab.
I admit that I don't understand half of it, too technical for me.
I just want to be able to play bug-free, record with some automation if needed and that's it.
Even that is difficult.
I'm beginning to understand why more and more musicians are turning to hardware rather than wrestling with software.

[MuTools]

"note that you have chosen to have your hardware inputs follow whatever you last focused in MuLab"
I don't understand what you mean. I didn't do anything in particular.

Did you read the doc pages i linked too?

I just want to be able to play bug-free, record with some automation if needed and that's it.
Even that is difficult.

Not at all. Just hit record and there you go.

Thanks for sending the project.
I see that in the Project menu you have chosen to uncheck "Automatic MIDI Input Focus".
So you're telling MuLab you do not want that clicking a track / rack sets that as the MIDI Input target = play it from MIDI.
Could it be that you have unselected that by accident?

Please do read the doc pages i linked to, they explain how MIDI input is used.
MuLab has flexible options to use MIDI input.
Out of the box it's very easy to use, but it also offers options to use it in other ways.

[ftnwo2012]

Thank you very much for the help.
Indeed, while looking for the cause of the problem, I had to click on "Automatic MIDI Input Focus" and unintentionally deselecting it. I had never noticed that he actually was selected.
I apologize if I seemed a little annoyed, but although I spent time reading the pages and advices kindly provided by the forum (which I thank very much), I only came up with questions about functions which I was not even aware of and which I have never used.
It didn't help me and I was quite unable to explain correctly and simply a simple problem that I didn't understand.
Especially since, as you say, all I had to do before was click on record and...go!
Like everyone I imagine, between the 50,000 apps and windows, not a day goes by without problems and you end up spending 3/4 of your time untangling knots instead of making music.
As we say in France, I'll go to bed less stupid tonight.
Anyway, thank you again to all and I apologize again for an unjustified annoyance although human.
Have a good day