[chuck-users] chuck + PulseAudio (was: Problem with multiple audion sources)
Joel Matthys
jwmatthys at yahoo.com
Thu Nov 14 19:46:14 EST 2013
I get a little bit of glitching for about the first second upon adding a
script, but hey, it's Pulse, what can you expect? As you point out, for
production environments you should be running Jack or at least Alsa, but
this is a nice alternative when you want to code while watching YouTube. ;)
Joel
On 11/14/2013 06:22 PM, Spencer Salazar wrote:
> Ah, my mistake. The tgz at that URL has been updated and should be
> good to go now.
>
> 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.).
>
> spencer
>
>
>
> On Thu, Nov 14, 2013 at 4:12 PM, Joel Matthys <jwmatthys at yahoo.com
> <mailto:jwmatthys at yahoo.com>> wrote:
>
> Hmm... there's no src folder in the ChucK link below.
>
> Joel
>
>
> On 11/14/2013 06:01 PM, Spencer Salazar wrote:
>> Hello ChucK linux users,
>>
>> 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.
>>
>> ChucK source (version 1.3.3.0-beta-3):
>> http://chuck.stanford.edu/release/files/beta/chuck-1.3.3.0-beta-3.tgz
>> miniAudicle source (version 1.3.1-beta-3):
>> http://chuck.stanford.edu/release/files/beta/miniAudicle-1.3.1-beta-3.tgz
>>
>> Thanks,
>> spencer
>>
>>
>>
>> On Wed, Nov 6, 2013 at 1:12 AM, Harald <hg42 at gmx.net
>> <mailto:hg42 at gmx.net>> wrote:
>>
>> 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.
>>
>> But musicians etc. / linux music distributions usually use jackd.
>>
>> Apart from that alsa allows to create virtual devices to be
>> routed through pulse or jack for those who know how to do it.
>> 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).
>>
>> 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.
>>
>> General rule: choose a good default for beginners and allow
>> advanced configuration for experts.
>>
>>
>> On Tue, Nov 5, 2013 at 11:51 PM, Morgan <morganiser at gmail.com
>> <mailto:morganiser at gmail.com>> wrote:
>>
>> My understanding is that chuck and or miniaudicle tries
>> to 'own' your
>> soundcard... it doesn't like to share.... but these
>> instructions tell
>> it to route through the mixer software
>>
>> I had similar issues (on Mint KDE which i believe has
>> alot in common
>> with KUbunutu), until I found and followed these
>> directions for
>> editing the audio config before compiling (from
>> https://class.coursera.org/chuck101-001/forum/thread?thread_id=130
>> )
>> -
>>
>>
>>
>> "We need to edit one of the files to allow audio mixing
>> through
>> PulseAudio, so that playing ChucK will not block other
>> audio sources
>> such as the sound in the course videos.
>>
>> Use a text-editor (preferably one that shows
>> line-numbers) to open the file:
>>
>> kate RtAudio/RtAudio.cpp
>>
>> Find line 5660:
>>
>> sprintf( name, "hw:%d,%d", card, subdevice );
>>
>> Revise this to read:
>>
>> //sprintf( name, "hw:%d,%d", card, subdevice ); //
>> commented out
>> sprintf( name, "pulse" );
>>
>> Find line 5699:
>>
>> int openMode = SND_PCM_ASYNC;
>>
>> Revise this to read:
>>
>> int openMode = SND_PCM_ASYNC;
>> printf( "pcm name %s\n", name ); // line inserted
>>
>> Save the file and close Kate (or whatever text-editor you
>> used)."
>>
>>
>> THEN compile etc
>>
>> I believe these directions should either be part of the
>> linux readme
>> or better still be scripted into the source...
>> ubuntu/mint being the
>> most popular distros thse days.
>>
>> Morgan
>>
>>
>> On 5 November 2013 15:49, <monon at att.net
>> <mailto:monon at att.net>> wrote:
>> > I am a new chuck user and have just installed
>> linux-alsa from source. All
>> > works well as long as there is no other audio source
>> active. If there is
>> > another active audio source active I get this message
>> when, for example, I
>> > type in chuck --loop:
>> >
>> > [chuck]: RtApiAlsa::getDeviceInfo: snd_pcm_open error
>> for device (hw:0,0),
>> > Device or resource busy.
>> >
>> > This seems to be a chuck issue as I can run multiple
>> audio sources as long
>> > as one of them is not chuck. My concern is that I
>> started a coursera course
>> > on chuck and would like to use chuck concurrently with
>> the course.
>> >
>> > My operating system is Kubuntu Linux 12.04.
>> >
>> > Does anyone have any ideas?
>> >
>> > Thank you,
>> > Monon
>> >
>> >
>> > _______________________________________________
>> > chuck-users mailing list
>> > chuck-users at lists.cs.princeton.edu
>> <mailto:chuck-users at lists.cs.princeton.edu>
>> > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
>> >
>> _______________________________________________
>> chuck-users mailing list
>> chuck-users at lists.cs.princeton.edu
>> <mailto:chuck-users at lists.cs.princeton.edu>
>> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
>>
>>
>>
>> _______________________________________________
>> chuck-users mailing list
>> chuck-users at lists.cs.princeton.edu
>> <mailto:chuck-users at lists.cs.princeton.edu>
>> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
>>
>>
>>
>>
>> _______________________________________________
>> chuck-users mailing list
>> chuck-users at lists.cs.princeton.edu <mailto:chuck-users at lists.cs.princeton.edu>
>> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
>
>
> _______________________________________________
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
> <mailto:chuck-users at lists.cs.princeton.edu>
> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
>
>
>
>
> _______________________________________________
> 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/20131114/cd9d6e8e/attachment.htm>
More information about the chuck-users
mailing list