You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am a linux noob. After purchasing a SteamDeck and in an attempt to achieve outcomes from first principles I am trying to get MUNT to work with Dosbox 0.74-3 from the flathub repo (??). I successfully grabbed the DosBox flatpak from the Discover Store and successfully downloaded, compiled and installed MUNT using terminal commands. I know that there are Dosbox versions with built in MT-32 support, which I have installed (eg. Dosbox Staging) but in order to understand Linux a bit better am challenging myself to code from first principles. After running the mt32emu-qt command from the terminal and then running: aconnect -o
I am expecting to see client 128: 'Munt MT-32' [type=user] 0 'Standard'
The issue is the line regarding client 128 is blank. MUNT launches, I have the ROMs installed and have tested midi files through MUNT and get sound, but when trying to point midiconfig=128:0
in the dosbox config file, it is not working.
Here are the steps I took to install MUNT, there were dependencies I needed to install and initialise features on SteamOS that are normally not used in vanilla SteamOS builds: sudo steamos-readonly disable sudo pacman-key --init sudo pacman-key --populate archlinux sudo pacman-key --populate holo sudo pacman -Syu sudo pacman -S qt5-multimedia sudo pacman -S qt6-multimedia git clone http://www.github.com/munt/munt sudo pacman -S install build-essential sudo pacman -S libgl cmake -DCMAKE_BUILD_TYPE:STRING=Release make sudo make install mt32emu-qt
I then added the '/usr/local/lib' path to /etc/ld.so.conf.d to ensure MUNT picked up the local library and then ran sudo ldconfig
Please assist in trying to understand why the MUNT client is not showing up?
Thanks
Please can I ask you to review this issue posted on the Munt Repo to see if you can advise on how to resolve the issue. The progress on troubleshooting is indicated by the discussion on the Munt issue channel.
Thanks.
The text was updated successfully, but these errors were encountered:
kingjoma
changed the title
Hi All
SteamOS 3.5 - Client 128: 'Munt MT-32' Misssing
Jan 26, 2024
Hi All
I am a linux noob. After purchasing a SteamDeck and in an attempt to achieve outcomes from first principles I am trying to get MUNT to work with Dosbox 0.74-3 from the flathub repo (??). I successfully grabbed the DosBox flatpak from the Discover Store and successfully downloaded, compiled and installed MUNT using terminal commands. I know that there are Dosbox versions with built in MT-32 support, which I have installed (eg. Dosbox Staging) but in order to understand Linux a bit better am challenging myself to code from first principles. After running the mt32emu-qt command from the terminal and then running:
aconnect -o
I am expecting to see
client 128: 'Munt MT-32' [type=user] 0 'Standard'
The issue is the line regarding client 128 is blank. MUNT launches, I have the ROMs installed and have tested midi files through MUNT and get sound, but when trying to point
midiconfig=128:0
in the dosbox config file, it is not working.
Here are the steps I took to install MUNT, there were dependencies I needed to install and initialise features on SteamOS that are normally not used in vanilla SteamOS builds:
sudo steamos-readonly disable
sudo pacman-key --init
sudo pacman-key --populate archlinux
sudo pacman-key --populate holo
sudo pacman -Syu
sudo pacman -S qt5-multimedia
sudo pacman -S qt6-multimedia
git clone http://www.github.com/munt/munt
sudo pacman -S install build-essential
sudo pacman -S libgl
cmake -DCMAKE_BUILD_TYPE:STRING=Release
make
sudo make install
mt32emu-qt
I then added the '/usr/local/lib' path to /etc/ld.so.conf.d to ensure MUNT picked up the local library and then ran
sudo ldconfig
Please assist in trying to understand why the MUNT client is not showing up?
Thanks
Originally posted by @kingjoma in munt/munt#116
Please can I ask you to review this issue posted on the Munt Repo to see if you can advise on how to resolve the issue. The progress on troubleshooting is indicated by the discussion on the Munt issue channel.
Thanks.
The text was updated successfully, but these errors were encountered: