rncbc / qmidinet Goto Github PK

Based on reveloxmidi, this systemd service file works for me:
file: qmidinet.service

[Unit]
After=local-fs.target network.target
Description=qmidinet MIDI UDP server network server
Documentation=man:qmidinet(1)

[Install]
WantedBy=multi-user.target

[Service]
User=root
Type=exec
#PIDFile=/run/qmidinet.pid
ExecStart=/usr/bin/qmidinet -a1 -n4 -g
Restart=on-failure
RestartSec=3

Perhaps spelling out long forms of the options, and offering some extra choices in commented-out lines would be helpful

checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking how to run the C++ preprocessor... g++ -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking whether gcc needs -traditional... no
checking for qmake-qt4... /usr/bin/qmake-qt4
checking for qmake... /usr/lib/x86_64-linux-gnu/qt4/bin/qmake
checking for Qt library version >= 4.4... yes
checking for moc... /usr/lib/x86_64-linux-gnu/qt4/bin/moc
checking for uic... /usr/lib/x86_64-linux-gnu/qt4/bin/uic
checking for lupdate... /usr/lib/x86_64-linux-gnu/qt4/bin/lupdate
checking for lrelease... /usr/lib/x86_64-linux-gnu/qt4/bin/lrelease
checking for main in -lm... yes
checking for main in -lX11... yes
checking for main in -lXext... yes
checking for main in -lasound... yes
checking for main in -ljack... no
configure: WARNING: *** JACK library not found.
checking for ANSI C header files... yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking sys/ioctl.h usability... yes
checking sys/ioctl.h presence... yes
checking for sys/ioctl.h... yes
checking for sys/stat.h... (cached) yes
checking for unistd.h... (cached) yes
checking signal.h usability... yes
checking signal.h presence... yes
checking for signal.h... yes
checking alsa/asoundlib.h usability... yes
checking alsa/asoundlib.h presence... yes
checking for alsa/asoundlib.h... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating qmidinet.spec
config.status: creating src/src.pri
config.status: creating src/qmidinet.desktop
config.status: error: cannot find input file: `src/config.h.in'

Hi here too Rui.

Any way of making this one translatable as well?

Would it be possible to add support for udp over unicast IP? I wanted to experiment with this over a Wireguard VPN connection (I know there'll be high latency but I still want to mess with it) but Wireguard does not support multicast and I'd rather avoid VXLAN if possible. I might attempt to write such a patch myself, but before I go through that effort (especially since I haven't touched C++ in a long time) I'd like to verify that there isn't a technical reason it's not doable.

It would be very useful for many use-cases having a headless mode, a "no-gui" flag.
Using "multimidicast" could be an option, but it lacks of jack-midi support. Also, it's not maintained anymore.

Thanks!

Hi, I have this error

Network Interface error - Qmidinet
The network interface cold not stablished

Pleas, make sure you hace an online network connection and try again

I don't know it means

Hi!
Trying to run qmidinet on windows to avoid usage of ipMIDI.
During creation of input sockets setsockopt(...) returns error code of:

"An unknown, invalid, or unsupported option or level was specified in a getsockopt or setsockopt call.\r\n"

I'm also not sure how the Interface choice affect the UdpDevice class