This is somewhat of a complete newb issue so I apologize up front for that.......
However, it seems that I cannot use pdextended and watch a youtube video at the same time (the youtube vid is a pd tutorial).
Here's what it's starting with:
pasuspender -- /usr/bin/pdextended -alsa %F
Is it absolutely necessary to start pd with 'pasuspender'?
When I don't (i.e. start it like this: '/usr/bin/pdextended -alsa' ), I get a bunch of 'device or resource busy' messages in the terminal and I don't get any audio when doing the whold testtone thing).
Is there any way around this?
It'd be nice to follow along with the tutorials in youtube (on the same computer).
Thanks!
-Aaron
On 2010-12-05 22:34, Aaron L. wrote:
This is somewhat of a complete newb issue so I apologize up front for that.......
However, it seems that I cannot use pdextended and watch a youtube video at the same time (the youtube vid is a pd tutorial).
Here's what it's starting with:
pasuspender -- /usr/bin/pdextended -alsa %F
Is it absolutely necessary to start pd with 'pasuspender'?
When I don't (i.e. start it like this: '/usr/bin/pdextended -alsa' ), I get a bunch of 'device or resource busy' messages in the terminal and I don't get any audio when doing the whold testtone thing).
Is there any way around this?
well, this is exactly the way how alsa is supposed to work:
pulseaudio is a way to circumvent this limitation. running Pd in pasuspender, effectively disables pulseaudio including all it's features.
luckily there are ways around that.
:-(; btw, pa is geared towards the ordinary consumer multimedia desktop where people would like to watch their youtube videos and at the same time listen to the latest p!nk smash hit; Pd is not really targeted towards that marketm, hence pa is not done yet)
several applications to send their audio output to the same hardware device (without the applications even knowing of it). i'm not 100% sure whether you can actually access this from within Pd....
allows to route the output of one process to the input of another process (or more); "process" can be both hardware (your soundcard) or software (Pd, your browser,...). there are also ways to make alsa-only applications (e.g. your browser) use a pseudo alsa device that really sends all audio to jack (thus the application need not be aware of jack at all)
madt IOhannes
Yep, when a software demands alsa (like pd does) it gets stuck. Jack is the way to go, but it actually works the same way, 'cause once jack gets a hold of alsa, everything else that is not communcating to jack and is demanding alsa will also be stuck. The trick is making/using programs that can talk to jack (i.e.: my audio player is mocp, video player is vlc, daw is ardour, etc... etc... they all can use jack as output).
Making flash plugin / browser going to jack has been coverd in many forums. example:
note: Last time I tried to put my chrome+flash_plugin working with jack it took a bit of long time and a lot of ubuntu studio forum reading!
best of luck, Pedro
On Mon, Dec 6, 2010 at 8:21 AM, IOhannes m zmoelnig zmoelnig@iem.at wrote:
On 2010-12-05 22:34, Aaron L. wrote:
This is somewhat of a complete newb issue so I apologize up front for that.......
However, it seems that I cannot use pdextended and watch a youtube video
at
the same time (the youtube vid is a pd tutorial).
Here's what it's starting with:
pasuspender -- /usr/bin/pdextended -alsa %F
Is it absolutely necessary to start pd with 'pasuspender'?
When I don't (i.e. start it like this: '/usr/bin/pdextended -alsa' ), I
get
a bunch of 'device or resource busy' messages in the terminal and I don't get any audio when doing the whold testtone thing).
Is there any way around this?
well, this is exactly the way how alsa is supposed to work:
- only one application can access a (hardware) device at any point
pulseaudio is a way to circumvent this limitation. running Pd in pasuspender, effectively disables pulseaudio including all it's features.
luckily there are ways around that.
- use pulseaudio (not a good option, as Pd currently doesn't support it
:-(; btw, pa is geared towards the ordinary consumer multimedia desktop where people would like to watch their youtube videos and at the same time listen to the latest p!nk smash hit; Pd is not really targeted towards that marketm, hence pa is not done yet)
- use alsa's "dmix" interface; "dmix" is a virtual device that allows
several applications to send their audio output to the same hardware device (without the applications even knowing of it). i'm not 100% sure whether you can actually access this from within Pd....
- use "jack". now you can think of jack as "pulseaudio for pros", it
allows to route the output of one process to the input of another process (or more); "process" can be both hardware (your soundcard) or software (Pd, your browser,...). there are also ways to make alsa-only applications (e.g. your browser) use a pseudo alsa device that really sends all audio to jack (thus the application need not be aware of jack at all)
madt IOhannes
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
IOhannes m zmoelnig zmoelnig@iem.at writes:
On 2010-12-05 22:34, Aaron L. wrote:
This is somewhat of a complete newb issue so I apologize up front for that.......
However, it seems that I cannot use pdextended and watch a youtube video at the same time (the youtube vid is a pd tutorial).
Here's what it's starting with:
pasuspender -- /usr/bin/pdextended -alsa %F
Is it absolutely necessary to start pd with 'pasuspender'?
When I don't (i.e. start it like this: '/usr/bin/pdextended -alsa' ), I get a bunch of 'device or resource busy' messages in the terminal and I don't get any audio when doing the whold testtone thing).
Is there any way around this?
well, this is exactly the way how alsa is supposed to work:
- only one application can access a (hardware) device at any point
pulseaudio is a way to circumvent this limitation. running Pd in pasuspender, effectively disables pulseaudio including all it's features.
luckily there are ways around that.
- use pulseaudio (not a good option, as Pd currently doesn't support it
:-(; btw, pa is geared towards the ordinary consumer multimedia desktop where people would like to watch their youtube videos and at the same time listen to the latest p!nk smash hit; Pd is not really targeted towards that marketm, hence pa is not done yet)
- use alsa's "dmix" interface; "dmix" is a virtual device that allows
several applications to send their audio output to the same hardware device (without the applications even knowing of it). i'm not 100% sure whether you can actually access this from within Pd....
- use "jack". now you can think of jack as "pulseaudio for pros", it
allows to route the output of one process to the input of another process (or more); "process" can be both hardware (your soundcard) or software (Pd, your browser,...). there are also ways to make alsa-only applications (e.g. your browser) use a pseudo alsa device that really sends all audio to jack (thus the application need not be aware of jack at all)
madt IOhannes
I'm new to Pd as well and ran into the ver same problem. After a bit of guesswork, I tried running Pd with the command:
pd -alsa -alsaadd dmix
which seems to add an unlabelled audio output in the Pd alsa configuration menu. When this output is selected, it solves the problem. I works well enough, but I haven't tried using jack. Can anyone who has used both dmix and jack offer offer an opinion on the pros and cons of each?
.Lewis
On Wed, Dec 8, 2010 at 4:29 PM, Lewis Pike phaselocker@gmail.com wrote:
IOhannes m zmoelnig zmoelnig@iem.at writes:
On 2010-12-05 22:34, Aaron L. wrote:
This is somewhat of a complete newb issue so I apologize up front for that.......
However, it seems that I cannot use pdextended and watch a youtube video
at
the same time (the youtube vid is a pd tutorial).
Here's what it's starting with:
pasuspender -- /usr/bin/pdextended -alsa %F
Is it absolutely necessary to start pd with 'pasuspender'?
When I don't (i.e. start it like this: '/usr/bin/pdextended -alsa' ), I
get
a bunch of 'device or resource busy' messages in the terminal and I
don't
get any audio when doing the whold testtone thing).
Is there any way around this?
well, this is exactly the way how alsa is supposed to work:
- only one application can access a (hardware) device at any point
pulseaudio is a way to circumvent this limitation. running Pd in pasuspender, effectively disables pulseaudio including all it's features.
luckily there are ways around that.
- use pulseaudio (not a good option, as Pd currently doesn't support it
:-(; btw, pa is geared towards the ordinary consumer multimedia desktop where people would like to watch their youtube videos and at the same time listen to the latest p!nk smash hit; Pd is not really targeted towards that marketm, hence pa is not done yet)
- use alsa's "dmix" interface; "dmix" is a virtual device that allows
several applications to send their audio output to the same hardware device (without the applications even knowing of it). i'm not 100% sure whether you can actually access this from within Pd....
- use "jack". now you can think of jack as "pulseaudio for pros", it
allows to route the output of one process to the input of another process (or more); "process" can be both hardware (your soundcard) or software (Pd, your browser,...). there are also ways to make alsa-only applications (e.g. your browser) use a pseudo alsa device that really sends all audio to jack (thus the application need not be aware of jack at all)
madt IOhannes
I'm new to Pd as well and ran into the ver same problem. After a bit of guesswork, I tried running Pd with the command:
pd -alsa -alsaadd dmix
which seems to add an unlabelled audio output in the Pd alsa configuration menu. When this output is selected, it solves the problem. I works well enough, but I haven't tried using jack. Can anyone who has used both dmix and jack offer offer an opinion on the pros and cons of each?
.Lewis
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
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.
Big bummer.