octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gsoc2013 octave audio system


From: Vytautas Jancauskas
Subject: Re: gsoc2013 octave audio system
Date: Thu, 18 Apr 2013 00:16:19 +0300

On Thu, Apr 18, 2013 at 12:11 AM, Jordi Gutiérrez Hermoso
<address@hidden> wrote:
> On 17 April 2013 16:52, Vytautas Jancauskas <address@hidden> wrote:
>> PulseAudio is one of "devices" that PortAudio presents as available.
>> You can set that device to any other and none of the code will have to
>> be rewritten.
>
> How does this work in general? How do you set devices at runtime
> without user interaction?
>

You cannot, obviously, do this without user interaction. But you can
set device at run-time with user interaction.

>> As far as abstraction this is as good as you are going to get. How
>> is any library to guess which audio infrastructure to use?
>
> Is it impossible for an audio library to query the operating system at
> runtime or build time to decide which audio infrastructure to use?
> Will no other library do this?
>

It is not possible. For example my system has jack, pulseaudio, alsa
and oss (I think) all working. Which one is the correct one? The
answer depends on the circumstances. You would use jack if you wrote,
say, a real-time effects processor in octave for example, you would
use pulseaudio if you just wanted to run a quick test without starting
the jack server.

> - Jordi G. H.



--
"Cheshire-Puss," she began, "would you tell me, please,
which way I ought to go from here?"
"That depends a good deal on where you want to get to," said the Cat.
"I don't care much where--" said Alice.
"Then it doesn't matter which way you go," said the Cat.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]