

I looked up the instrument packages actually available on this release: "timidity -iAD -B2,8 -Os1l -s 44100 -x'soundfont /usr/share/midi/sf2/mypatches.sf2 order=1' " Thought readers of my latest submission would like to see where Until that is fixed in timidity, this is a work-around.

Restarting it, and then giving it a problem command makes timidity get the default right the second time. Apparently timidity fails to set client 128 correctly during boot start-up. There is no directory "/usr/share/midi/sf2/mypatches.sf2" Timidity sets the client 128:0 to use soundfonts defined in /usr/share/midi/sf2/mypatches.sf2 Gksudo opens a window for sudo password and then runs timidity restart as sudo You now have an icon on the desktop that:Īconnect makes the midi input device from your keyboard (etc) connect to wine's default midi input Save this to your desktop as Studio4-Wine-Shell.shĬommand line: "chmod 775 Studio4-Wine-Shell.sh" Timidity -iAD -B2,8 -Os1l -s 44100 -x'soundfont /usr/share/midi/sf2/mypatches.sf2 order=1' Using kate or gedit or any convenient text editor:Īconnect 24:0 14:0 #Connects the MIDI port to the input of wine This solution should be used exactly once per boot-up: The sound problem with Studio 4 has another solution that does not require using Cadence as I described previously. If someone can write a script to do this automatically, I am sure we would all like to see it. This last item connects your MIDI device. Look for a Green device describing your MIDI interface from your keyboard (or whatever)Īfter this, everything except the Patchage connection should start on login.

These are the links that you just set up running Cadence. Several groups of physical and logical devices will appear with links among them: Start Wine-> Programs -> MidiSoft Studio 4 On "PulseAudio" section under "JACK Bridges" On "ALSA MIDI" section under "JACK Bridges" On "ALSA Audio" section under "JACK Bridges"įor Bridge Type, select "ALSA -> Loop -> JACK Output Device: Select from drop-down window Digital version of Device/InterfaceĬheck "Duplex Mode" and "Hardware Aliases" (leave others blank)Ĭheck "Auto-start Jack/LADISH at start-up" Input Device: Select from drop-down window Digital version of Device/Interface (This is to reset if all does not run as desired)ĭriver list should show highlight of ALSAĭevice/Interface grayed out (in my PC it is hw:Intel,0 WRITE DOWN (or capture and print) CONFIGURATION AS YOU FIND IT On the first tab (System) Jack Status "configure" On the first tab (System) Jack Status "stop" KXStudio, latest version (note that this establishes numerous audio tools, JACK being the most important) First, I will describe the Linux I am using: I now have a solution that works repeatedly for running MIDISOFT Studio. I have had this problem for some time now.
