[chuck-users] Problems with running ChucK in terminal (Windows 7 64-bit): no sound!

[Spencer Salazar]

Hey Chris,

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.

To that end, can you post the output of chuck --probe, and the console
output from miniAudicle after starting the virtual machine?

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!

spencer


On Wed, Apr 25, 2012 at 6:14 PM, Kassen <signal.automatique at gmail.com>wrote:

> On Wed, Apr 25, 2012 at 07:02:05PM +0100, henrique matias wrote:
> > Long time i don't use windows too, but i do heard about a "chuck-asio"
> maybe it
> > might help you somehow.
>
> It seemed to me that this issue is somehow related to communication
> between processes (particularly CLI windows). I can't imagine that
> that's no longer possible as it's quite important for a lot of stuff
> like server administration.
>
> Could it be a firewall issue? The communication between the VM and and
> the otf commands (like adding a shred) happens through ports on local-host
> a firewall might mistakenly assume that that is something it needs to
> stop?
>
> Just guessing,
> Kas.
> _______________________________________________
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cs.princeton.edu/pipermail/chuck-users/attachments/20120425/00e3563a/attachment-0001.html>