<div dir="ltr">After reinstalling the older package version of chucK (Dracula)<div>/usr/bin/chuck <a href="http://gomidi2.ck">gomidi2.ck</a></div><div>gives me the 'um, couldn't open' message, and exits.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Oct 22, 2019 at 2:20 PM Forrest Curo <<a href="mailto:treegestalt@gmail.com">treegestalt@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr">Recently I downloaded (Ubuntu 19.04) Chuck 1.4.0.0 and had to do Awful Things to my Jack packages in order to provide libjack.h so it would compile.<div><br></div><div>So now chucK is running fine, except that it can't give me a midi port (either alsa or jack) for my keyboards to connect to.</div><div><br></div><div>running the <a href="http://gomidi.ck" target="_blank">gomidi.ck</a> examples I get (after one to several 'SUCCESS' messages):<br></div><div><br></div><div>"(JACK) the JACK server is shutting down this client."</div><div><br></div><div>At that point chucK has not quit, but its audio is stifled until I start it again.</div><div><br></div><div>Aconnectgui can't find a chucK port to connect anything else to until I open a 'MidiIn', which is exactly what upsets JACK.</div><div><br></div><div>Help?!</div><div><br></div><div>Forrest Curo</div><div>San Diego</div></div>
</blockquote></div>