octave-maintainers
[Top][All Lists]
Advanced

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

Re: SOUND function and Macs


From: bpabbott
Subject: Re: SOUND function and Macs
Date: Thu, 29 Jul 2010 05:40:30 -0700 (PDT)

On 29 Jul, 2010,at 08:02 AM, volker böhm <address@hidden> wrote:


On 29.07.2010, at 13:39, Ben Abbott wrote:

> On Jul 29, 2010, at 7:31 AM, volker böhm wrote:
>
>> On 19.07.2010, at 00:23, Cary Martin wrote:
>>
>>> Hello - I'm attempting to do some basic exploration of sound waveform
>>> analysis and manipulation using Octave and the Audio package. I
>>> apologize for such a newbie/ignorant question but if someone could
>>> please provide some assistance in configuring Octave and whatever
>>> external utilities are required to play sound files from Octave under
>>> Mac OsX 10.6.4 I would be greatly appreciative. I'm somewhat well
>>> versed in many of the basics of Octave but it is completely unclear to
>>> me what a pipe is in this context and how I am to establish the links
>>> to the external utilities (and to which ones). Anyway, when attempting
>>> to output a waveform to the speakers using this command
>>>
>>> octave-3.2.2:10> sound(x,fs)
>>>
>>> This response is received:
>>>
>>> ssh: connect to host machine-mac-mini.local port 22: Connection refused
>>> warning: broken pipe -- some output may be lost
>>
>> i had the same problem as you. as i'm still pretty new to octave myself, i might miss the point here, but
>> what seems to be going wrong (at least on my machine, which runs 10.6.4) is that the check in sound.m,
>> if octave is run locally or not, fails.
>>
>> if i run
>> display=getenv("DISPLAY")
>> like in sound.m , i get
>> display = /tmp/launch-eHpt80/org.x:0
>> so, no hostname involved and the check fails.
>>
>
> Please set DISPLAY correctly,
>
> setenv ("DISPLAY", ":0.0")

ok, this fixes sound.m for me - thanks!

but i wonder what is causing this, as every time i launch octave, DISPLAY is set 'wrong'.
ok, i could probably 'fix' it, by putting setenv ("DISPLAY", ":0.0") in .octaverc.
but i'm still curious what's going wrong here, and if others maybe have the same problem.
volker.
 
SInce 10.5, MacOS X has been able to launch X11 on demand by using launchd. That's a nice feature, however it comes with the additional "feature" that the DISPLAY variable is now set by launchd and that its setting doesn't always agree with the expectation of various software developers.

For more info, take a look at ..

    http://stackoverflow.com/questions/610911/what-configuration-file-sets-display-in-leopard

    http://xquartz.macosforge.org/trac/wiki/X11-UsersFAQ

Ben
 



reply via email to

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