<br><br><div class="gmail_quote">On Wed, Dec 8, 2010 at 4:29 PM, Lewis Pike <span dir="ltr"><<a href="mailto:phaselocker@gmail.com" target="_blank">phaselocker@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div><div>IOhannes m zmoelnig <<a href="mailto:zmoelnig@iem.at" target="_blank">zmoelnig@iem.at</a>> writes:<br>
<br>
> On 2010-12-05 22:34, Aaron L. wrote:<br>
>> This is somewhat of a complete newb issue so I apologize up front for<br>
>> that.......<br>
>><br>
>> However, it seems that I cannot use pdextended and watch a youtube video at<br>
>> the same time (the youtube vid is a pd tutorial).<br>
>><br>
>> Here's what it's starting with:<br>
>><br>
>> pasuspender -- /usr/bin/pdextended -alsa %F<br>
>><br>
>> Is it absolutely necessary to start pd with 'pasuspender'?<br>
>><br>
>> When I don't (i.e. start it like this: '/usr/bin/pdextended -alsa' ), I get<br>
>> a bunch of 'device or resource busy' messages in the terminal and I don't<br>
>> get any audio when doing the whold testtone thing).<br>
>><br>
>> Is there any way around this?<br>
><br>
><br>
> well, this is exactly the way how alsa is supposed to work:<br>
> - only one application can access a (hardware) device at any point<br>
><br>
> pulseaudio is a way to circumvent this limitation.<br>
> running Pd in pasuspender, effectively disables pulseaudio including all<br>
> it's features.<br>
><br>
><br>
> luckily there are ways around that.<br>
><br>
> - use pulseaudio (not a good option, as Pd currently doesn't support it<br>
> :-(; btw, pa is geared towards the ordinary consumer multimedia desktop<br>
> where people would like to watch their youtube videos and at the same<br>
> time listen to the latest p!nk smash hit; Pd is not really targeted<br>
> towards that marketm, hence pa is not done yet)<br>
><br>
> - use alsa's "dmix" interface; "dmix" is a virtual device that allows<br>
> several applications to send their audio output to the same hardware<br>
> device (without the applications even knowing of it). i'm not 100% sure<br>
> whether you can actually access this from within Pd....<br>
><br>
> - use "jack". now you can think of jack as "pulseaudio for pros", it<br>
> allows to route the output of one process to the input of another<br>
> process (or more); "process" can be both hardware (your soundcard) or<br>
> software (Pd, your browser,...).<br>
> there are also ways to make alsa-only applications (e.g. your browser)<br>
> use a pseudo alsa device that really sends all audio to jack (thus the<br>
> application need not be aware of jack at all)<br>
><br>
><br>
> madt<br>
> IOhannes<br>
<br>
</div></div>I'm new to Pd as well and ran into the ver same problem. After a bit of<br>
guesswork, I tried running Pd with the command:<br>
<br>
pd -alsa -alsaadd dmix<br>
<br>
which seems to add an unlabelled audio output in the Pd alsa<br>
configuration menu. When this output is selected, it solves the<br>
problem. I works well enough, but I haven't tried using jack. Can<br>
anyone who has used both dmix and jack offer offer an opinion on the<br>
pros and cons of each?<br>
<font color="#888888"><br>
.Lewis<br>
</font><div><div></div><div><br>
_______________________________________________<br>
<a href="mailto:Pd-list@iem.at" target="_blank">Pd-list@iem.at</a> mailing list<br>
UNSUBSCRIBE and account-management -> <a href="http://lists.puredata.info/listinfo/pd-list" target="_blank">http://lists.puredata.info/listinfo/pd-list</a><br></div></div></blockquote><div><br><br>Interestingly enough, I ran into another bug when using Jack and PD. Basically ends up with Jack going non-responsive and any attempt to rid the system of any Jack processes don't really work. All Jack processes simply return a 'defunct' when you look at "top". Makes Jack unusable since it will neither start nor stop. The more research I did revealed that this is a bug in the 8.04 Hardy Heron kernel.<br>
<br>Big bummer. <br></div></div><br>