Hi Anthony.
first welcome aboard.
Thanks for reminding of this issue. I did know about it, and was going
to put a warning on the website, so that for users with controllers, we
recommend using the loopmidi software instead of loopbe1, as controllers
do send a lot of bulk similar midi data (such as the volume slider),
which can cause loopbe1 to think it is receiving the same midi data and
make it mute itself.
It doesn't seem to effect many users that are using the keyboard,
perhaps the occasional mute, but switching quickly back to the mallmuzik
speech software and pressing 'M' will bring up the loopbe1 setting panel
to uncheck the mute checkbox.
The reason the mallMuzik software freezes is because if the midi port is
muted, it will never receive the disconnect midi command from virtual
DJ, and will sit waiting for this midi command.
It looks like loopbe1 only analyses the first few bytes of the midi
header data, to detect feedback, and this is what might be the issue, I
will try to contact the developer about it, although it has not been
updated since about 2016.
I do have some workarounds in mind, which I will have a play with.
The reason I still have loopbe1 as an option, is that it seems more
responsive than loopmidi, (Probably because like I previously mentioned,
it probably only checks the first part of the midi header, instead of
the whole midi message, for feedback protection), but i'm only guessing
here lol.
Just a side note, you say you are coming from a Mac, have you tried the
Speech software with Virtual DJ on MacOs?.
All the best, and sorry for the headache you got, for me not putting
this information up sooner, and thank you for reminding me.
Pete