<div dir="ltr">Ah, my mistake. The tgz at that URL has been updated and should be good to go now. <div><br></div><div>Also, quick note, the pulse build is used when you run 'make linux-pulse'. In addition to the usual development libraries that chuck uses, you need 'libpulse-dev' installed (PulseAudio development headers/etc.). </div>
<div><br></div><div>spencer</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Nov 14, 2013 at 4:12 PM, Joel Matthys <span dir="ltr"><<a href="mailto:jwmatthys@yahoo.com" target="_blank">jwmatthys@yahoo.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Hmm... there's no src folder in the
ChucK link below.<span class="HOEnZb"><font color="#888888"><br>
<br>
Joel</font></span><div><div class="h5"><br>
<br>
On 11/14/2013 06:01 PM, Spencer Salazar wrote:<br>
</div></div></div><div><div class="h5">
<blockquote type="cite">
<div dir="ltr">Hello ChucK linux users,
<div><br>
</div>
<div>We are excited to have a beta version of chuck that
features PulseAudio support! While PulseAudio is not always
ideal for professional audio usage, we absolutely recognize
that its a popular choice for general-purpose Linux
installations. We would love it if Linux + Pulse users could
try out the beta and report any feedback, issues, etc. </div>
<div><br>
</div>
<div>
<div>ChucK source (version 1.3.3.0-beta-3):</div>
<div><a href="http://chuck.stanford.edu/release/files/beta/chuck-1.3.3.0-beta-3.tgz" target="_blank">http://chuck.stanford.edu/release/files/beta/chuck-1.3.3.0-beta-3.tgz</a></div>
</div>
<div>
<div>miniAudicle source (version 1.3.1-beta-3):</div>
<div><a href="http://chuck.stanford.edu/release/files/beta/miniAudicle-1.3.1-beta-3.tgz" target="_blank">http://chuck.stanford.edu/release/files/beta/miniAudicle-1.3.1-beta-3.tgz</a></div>
</div>
<div><br>
</div>
<div>Thanks,</div>
<div>spencer</div>
<div><br>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Wed, Nov 6, 2013 at 1:12 AM,
Harald <span dir="ltr"><<a href="mailto:hg42@gmx.net" target="_blank">hg42@gmx.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">
<div>
<div>
<div>pulseaudio should usually work out of the box
because most linux desktop distributions have
this installed and configured, so it should be
nice for beginners.<br>
<br>
But musicians etc. / linux music distributions
usually use jackd.<br>
</div>
<br>
</div>
<div>Apart from that alsa allows to create virtual
devices to be routed through pulse or jack for
those who know how to do it.<br>
So alsa would be a good choice for all, but
unfortunately desktop distributions don't come
with alsa on top of pulse (from what I remember).<br>
<br>
</div>
So there should be a choice between all these
systems, probably with default to pulse and a BIG
comment at a prominent place saying latency etc. may
be bad and using jackd would be better. Users who
can install jackd should also be able to choose a
sound device in chuck.<br>
</div>
<br>
General rule: choose a good default for beginners and
allow advanced configuration for experts.<br>
</div>
<div>
<div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Tue, Nov 5, 2013 at
11:51 PM, Morgan <span dir="ltr"><<a href="mailto:morganiser@gmail.com" target="_blank">morganiser@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">My
understanding is that chuck and or miniaudicle
tries to 'own' your<br>
soundcard... it doesn't like to share.... but
these instructions tell<br>
it to route through the mixer software<br>
<br>
I had similar issues (on Mint KDE which i
believe has alot in common<br>
with KUbunutu), until I found and followed
these directions for<br>
editing the audio config before compiling
(from<br>
<a href="https://class.coursera.org/chuck101-001/forum/thread?thread_id=130" target="_blank">https://class.coursera.org/chuck101-001/forum/thread?thread_id=130</a>
)<br>
-<br>
<br>
<br>
<br>
"We need to edit one of the files to allow
audio mixing through<br>
PulseAudio, so that playing ChucK will not
block other audio sources<br>
such as the sound in the course videos.<br>
<br>
Use a text-editor (preferably one that shows
line-numbers) to open the file:<br>
<br>
kate RtAudio/RtAudio.cpp<br>
<br>
Find line 5660:<br>
<br>
sprintf( name, "hw:%d,%d", card, subdevice );<br>
<br>
Revise this to read:<br>
<br>
//sprintf( name, "hw:%d,%d", card, subdevice
); // commented out<br>
sprintf( name, "pulse" );<br>
<br>
Find line 5699:<br>
<br>
int openMode = SND_PCM_ASYNC;<br>
<br>
Revise this to read:<br>
<br>
int openMode = SND_PCM_ASYNC;<br>
printf( "pcm name %s\n", name ); // line
inserted<br>
<br>
Save the file and close Kate (or whatever
text-editor you used)."<br>
<br>
<br>
THEN compile etc<br>
<br>
I believe these directions should either be
part of the linux readme<br>
or better still be scripted into the source...
ubuntu/mint being the<br>
most popular distros thse days.<br>
<br>
Morgan<br>
<div>
<div><br>
<br>
On 5 November 2013 15:49, <<a href="mailto:monon@att.net" target="_blank">monon@att.net</a>>
wrote:<br>
> I am a new chuck user and have just
installed linux-alsa from source. All<br>
> works well as long as there is no
other audio source active. If there is<br>
> another active audio source active I
get this message when, for example, I<br>
> type in chuck --loop:<br>
><br>
> [chuck]: RtApiAlsa::getDeviceInfo:
snd_pcm_open error for device (hw:0,0),<br>
> Device or resource busy.<br>
><br>
> This seems to be a chuck issue as I
can run multiple audio sources as long<br>
> as one of them is not chuck. My
concern is that I started a coursera
course<br>
> on chuck and would like to use chuck
concurrently with the course.<br>
><br>
> My operating system is Kubuntu Linux
12.04.<br>
><br>
> Does anyone have any ideas?<br>
><br>
> Thank you,<br>
> Monon<br>
><br>
><br>
</div>
</div>
>
_______________________________________________<br>
> chuck-users mailing list<br>
> <a href="mailto:chuck-users@lists.cs.princeton.edu" target="_blank">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>
chuck-users mailing list<br>
<a href="mailto:chuck-users@lists.cs.princeton.edu" target="_blank">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>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
chuck-users mailing list<br>
<a href="mailto:chuck-users@lists.cs.princeton.edu" target="_blank">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>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
chuck-users mailing list
<a href="mailto:chuck-users@lists.cs.princeton.edu" target="_blank">chuck-users@lists.cs.princeton.edu</a>
<a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-users</a>
</pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
chuck-users mailing list<br>
<a 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></blockquote></div><br></div>