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:10:41 +0300

On Thu, Apr 18, 2013 at 12:07 AM, Jordi Gutiérrez Hermoso
<address@hidden> wrote:
> On 17 April 2013 16:52, John Swensen <address@hidden> wrote:
>> Give the guy a break. He has barely started getting interested in
>> Octave and tries to whip up a quick test along the lines of what he
>> thinks the best solution is and gets blasted by you for using the
>> toolchain he is most comfortable with and for an incomplete
>> solution. He has been working on this for all of one day, you can't
>> expect a full solution.
>
> I don't think the problem is his solution being incomplete, but
> completely in the wrong direction from the beginning. This can't be a
> solution for Octave if it's already getting tied to pulseaudio. This
> may be a limitation of portaudio, not of Vyatauta's implementation, in
> which case, we might want to consider a different audio library.
>
>> To be frank, Jordi, your treatment of others on this list has been
>> putting me off a bit lately also.
>
> I apologise for that. Do you have a particular incident in mind where
> I have mistreated others?
>
> - Jordi G. H.

I will repeat this for the 3rd time. My code is not tied to
pulseaudio. Portaudio provides a list of devices and each is used
identically to any other with no code changed, all you need to do is
change the id of the device. I set this to pulseaudio for simplicity
but it is in no way tied to it. Picking an audio system to use can be
left to octave user for example.


reply via email to

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