<html><body><div style="color:#000; background-color:#fff; font-family:arial, helvetica, sans-serif;font-size:10pt"><div><span>Well, I have the problem fixed (sort of). The new sound card seems to have been the culprit. For whatever reason, ChucK did not like my sound card. I did a fresh install of Linux while I was at it and had the same issues as I was having in Windows (never had a problem with ChucK in Linux before..I had purchased the sound card to try to resolve Windows issues!). All audio, aside from ChucK audio, was working fine. I took the sound card out and ChucK is working better than ever in both Windows and Linux. Go figure.<br></span></div><div><br></div> <div style="font-family: arial, helvetica, sans-serif; font-size: 10pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <font face="Arial" size="2"> <hr size="1"> <b><span
style="font-weight:bold;">From:</span></b> Spencer Salazar <spencer@ccrma.stanford.edu><br> <b><span style="font-weight: bold;">To:</span></b> ChucK Users Mailing List <chuck-users@lists.cs.princeton.edu> <br> <b><span style="font-weight: bold;">Sent:</span></b> Wednesday, April 25, 2012 3:20 PM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [chuck-users] Problems with running ChucK in terminal (Windows 7 64-bit): no sound!<br> </font> </div> <br>
<div id="yiv1681697564">Hey Chris,<div><br></div><div>Hmm, if miniAudicle works then conceivably chuck.exe should also work just as well; they both use the same code to access the underlying soundcard, but they use slightly different configuration logic by default. </div>
<div><br></div><div>To that end, can you post the output of chuck --probe, and the console output from miniAudicle after starting the virtual machine? </div><div><br></div><div>As far as a proper terminal, Console2 is pretty much the second thing I install on a new Windows system, after Chrome/Firefox. Highly recommended! </div>
<div><br></div><div>spencer</div><div><br><br><div class="yiv1681697564gmail_quote">On Wed, Apr 25, 2012 at 6:14 PM, Kassen <span dir="ltr"><<a rel="nofollow" ymailto="mailto:signal.automatique@gmail.com" target="_blank" href="mailto:signal.automatique@gmail.com">signal.automatique@gmail.com</a>></span> wrote:<br>
<blockquote class="yiv1681697564gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="yiv1681697564im">On Wed, Apr 25, 2012 at 07:02:05PM +0100, henrique matias wrote:<br>
> Long time i don't use windows too, but i do heard about a "chuck-asio" maybe it<br>
> might help you somehow.<br>
<br>
</div>It seemed to me that this issue is somehow related to communication<br>
between processes (particularly CLI windows). I can't imagine that<br>
that's no longer possible as it's quite important for a lot of stuff<br>
like server administration.<br>
<br>
Could it be a firewall issue? The communication between the VM and and<br>
the otf commands (like adding a shred) happens through ports on local-host<br>
a firewall might mistakenly assume that that is something it needs to<br>
stop?<br>
<br>
Just guessing,<br>
<div class="yiv1681697564HOEnZb"><div class="yiv1681697564h5">Kas.<br>
_______________________________________________<br>
chuck-users mailing list<br>
<a rel="nofollow" ymailto="mailto:chuck-users@lists.cs.princeton.edu" target="_blank" href="mailto:chuck-users@lists.cs.princeton.edu">chuck-users@lists.cs.princeton.edu</a><br>
<a rel="nofollow" target="_blank" href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users">https://lists.cs.princeton.edu/mailman/listinfo/chuck-users</a><br>
<br>
</div></div></blockquote></div><br></div>
</div><br>_______________________________________________<br>chuck-users mailing list<br><a ymailto="mailto:chuck-users@lists.cs.princeton.edu" href="mailto:chuck-users@lists.cs.princeton.edu">chuck-users@lists.cs.princeton.edu</a><br><a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-users</a><br><br><br> </div> </div> </div></body></html>