How to do the four things people ask about.

Nothing on your side has to be switched off, and the two of you can play the same instrument together. Their side is the one with the problem: Windows hands a MIDI keyboard to the first program that opens it and to nobody after that, so while their own DAW is holding their keyboard, FL Connect cannot read a single note from it.

Nothing is forwarded until they name the keyboard, and the list lives on their machine because that is where it is plugged in.

This is the switch on your side that lets their notes into your DAW at all. It is normally already on, so this is a check rather than a step.

The Bridge is the piece that catches their notes and hands them to your DAW. Without it in the project there is nothing to hand the notes to. The line under the name is the one to read: green and it found FL Connect, orange and it is still looking.

The Bridge does not make any sound by itself. It only carries the notes, so it needs something to carry them to. Any VST synth works, and so does your DAW's own.

This is the one people get wrong. The two numbers are set in your DAW's plugin wrapper, not inside FL Connect, and they have to match: whatever number leaves the Bridge is the number the synth has to be listening on. The other field on each side stays empty.

If it stays silent, check the two numbers match before you change anything else. That is the problem nine times out of ten. After that, check step 1 actually happened on their side.

Their microphone is off until they say so. That is deliberate: nobody joins a session and is live without knowing it. Yours stays out of this, so if you want to talk back you can, but it is not part of the recording.

Windows often picks a webcam microphone or a monitor over the one they actually sing into. If they sound far away and thin, this is why, and no amount of mixing will fix it afterwards.

The first two steps were theirs, this one is yours, and it is the same plugin as the one in the first tutorial. It does the second half of the job: what comes out of it is their microphone. To your DAW that is an instrument making sound, so it lands on a mixer track like anything else.

Record the track, not the master, or you record your own playback with it. Set the Volume on the plugin before the take rather than fixing it after, since that is the level going onto the disk.

You can only invite people who are on your friends list. There is no open room to walk into, which is the point.

Green means they are at their computer. You cannot invite somebody who is offline, so if the invite button does nothing, look at this first.

It is the second of the two small buttons on their row. The first one is chat. Hover it and it turns blue.

They get a notification. Nothing happens on your side until they say yes.

This is the step people miss. Accepting the invite puts them in the session, but it does not open your screen. They have to go and ask for it.

Now they see your screen, and they can click in your DAW as if they were sitting there. If the picture stays black for a second or two that is normal, it is waiting for a full frame.

Otherwise a guest could click around in your browser, your files or anything else you have open. So the moment your DAW is not the window you are on, everybody else is held.

This is what stops the cursor being yanked out of your hand mid-drag. You move, they wait. You stop, a short countdown runs, and then they have it back.

Turning it off means you and your guests share the cursor with no priority at all. That is genuinely nicer with somebody you trust, and genuinely annoying with somebody who does not stop moving. Your call, and you can change it mid-session.

Cooldown trigger decides what counts as you being busy: your mouse, your keyboard, or both. Mouse only is the usual answer, because typing in a DAW is not the same as reaching for something.