Hi,
Can anyone explain to me why I am getting multiple instances of midi connections to my two external midi keyboards?
Regards,
Soren
First, you can delete the unneeded ones 
Second, you probably selected to hardware instead of the existing port ([portname] in Connections) and every time a new port has been added.
Third: there is a tiny bug since v1 ( @musicullum or @Spork if you will have a minute to check&fix this, reported once, but not pushed it later ): regardless clicking “Cancel” on that dialog
The new port will be created under “Connections” regardless of clicking CANCEL.
Repro: Go to any in/out port selector for any kind of track/layer and select one option from the dropdown that is != existing-proxy-I/O
Thank you for a very speedy reply - I’ll look into your suggestion
I have now tried to clean up the connections. However, two inputs keep comming back despite repeatedly deleting them. One is a launchPad which is not a part of any songs in the project anymore. The other is MIDI IN1 which is not part of the project either. ???
That is by intention. If you don’t name a port, it will take the hardware ports’ name instead.
I mean if I click CANCEL to create a new (example making a mistake on selection) the new port will be created ….
Why then asking me? Do you get my point of view?
And that result at the end of the day, new and new ports are created despite if my repeated intention “CANCEL” as user I’m asking by pressing cancel “dont do this VL”
For example in rush, sometimes selecting non-existing I/O , question popping up, CANCEL, but port has been made regardless….. (regardless I dont need at all, the hall thing is coming from a “bad” choice where the CANCEL/OK would make sense)
askin for you to type a name. Will remove Cancel button but that will delay “ghost frame” from VD Monitor
Before removing CANCEL, please think about the situation I described above. We need both cancel and ok buttons, with a fix that cancel is terminating the dialog. Please consider it 
of course can live with since v1, but that new thread brought it up
Yes, Cancel means cancel. I cannot cancel payment and go out of shop taking goods with me.
If someone needs that connection and don’t want to name it other than given in the input field, he will hit OK. It’s the logic in any software, like cancel means cancel at any position of workflow.
Another comparison - Save As - if you hit Cancel, the file won’t be saved and it would be strange if it was saved with given name… (unfortunately VST Live no longer offers the name of an existing project in the “Save As” dialog… 
)
tried to change it and immediately confused because it behaves differently and does not create a port anymore which it used to to since ever. So “Cancel” should be “Use Hardware name” but changing the Cancel button in a generic Input dialog is a major task so we need to push it down the list again, sorry.
Ooohh, I see now it’s nature. Sure, all we can live with for now of course, no worries
Personally - if that would be my “child”, I would approach some merge like:
- dialog filled with default hardware port name
- user have option to rewrite name [string]
- “OK btn” initiating port creation with [string content of dialog]
- Cancel is terminating dialog
Input dialog is generic. Of course you can do anything, but it requires a re-write of all input dialogs etc.
Don’t worry, time spent on this conversation already exceeds that
I am sorry but the confusion about midi connection continues.
I tried to set up a completely new project as a test. Nothing is connected to the computer.
I set up two midi inputs and two midi outputs named Nord Stage 3 and Nord Piano 5 with nc as connection (no keyboards was connected)
I saved the project, closed the program and re-opened the program.
Now on the front page the two midi inputs are named Nord 5 and Nord 3 both with Core Midi: iAC-driver Bus 1 as connection.
Opening the new project and going to connections I find three new Midi inputs - two of which are names from previous projects.
It seems to me like there are previous connection saved “under the hood” and that the program has unwanted level of authornomy in its behaviour
Those two MIDI Inputs that also appear in the Hub get assigned input(s) if none set, because new users won’t hear anything when playing their keyboards otherwise. That is by design.
@Soren_Ziebe, just don’t use nc as an input device. NC means not only “not connected”, but also “no chance”. I’m almost sure no one can record anything using this default device. You see, even Mr. Hub tries to avoid such relationships. But, don’t worry, nc also can be “nothing criminal”. So, do you dream about CC from nc? 
More seriously:
You set up project, set up connections, load virtual instruments, create songs, go on stage and fire up devices and only then run VST Live so the Hub see that you have everything set up and can load your project for 100% as it was in you bedroom, sorry, studio. See? There is no room for nc. Everything works if you do everything right.