hi. first of all please check your local networking setup:
a. make sure no firewall is in charge for your local network segment;
b. make sure the multicast IP address and port must be ALL the same on ALL the apps (qmidinet, qmidictl: address 225.0.0.37 and port 21928 are the default, as this are kept for original ipMIDI compatibility...);
c. if you have more than one activated on any of your machines, always use the interface name (eg. "eth0", "wlan0") that connects to your local network, explicitly (ie. don't use the default "(Any)"); this applies most especially if you have for instance a VPN tunnel through the internet or even a network bridge adapter for running intrough VM guests (QEMU/KVM, VirtualBox, etc.).
d. I'm not really sure what MIDI port you should connect qmidinet to Ardour precisely but it sounds kinda weird it's the "MTC In"... on Qtractor you can make it to any MIDI input port *iif* you don't have the special dedicated "Control" ones, for which it should be just those and none other.
hi. first of all please check your local networking setup:
a. make sure no firewall is in charge for your local network segment;
b. make sure the multicast IP address and port must be ALL the same on ALL the apps (qmidinet, qmidictl: address 225.0.0.37 and port 21928 are the default, as this are kept for original ipMIDI compatibility...);
c. if you have more than one activated on any of your machines, always use the interface name (eg. "eth0", "wlan0") that connects to your local network, explicitly (ie. don't use the default "(Any)"); this applies most especially if you have for instance a VPN tunnel through the internet or even a network bridge adapter for running intrough VM guests (QEMU/KVM, VirtualBox, etc.).
d. I'm not really sure what MIDI port you should connect qmidinet to Ardour precisely but it sounds kinda weird it's the "MTC In"... on Qtractor you can make it to any MIDI input port *iif* you don't have the special dedicated "Control" ones, for which it should be just those and none other.
hth.
cheers