is that the classic messed up /private/etc/hosts file? Desperately installing the Adobe crack on OS X and in the process of hindering it of calling home deleting the localhost line?
ping localhost
On 2017년 07월 21일 16:01, me.grimm wrote:
same stuff going on here... what to be done?
test3 $ /Volumes/U/Pd.app/Contents/Resources/bin/pd -verbose input channels = 2, output channels = 2 Pd-0.48.0 ("test3") compiled 07:55:09 Jul 21 2017 port 5400 "/Volumes/U/Pd.app/Contents/Resources/../MacOS/Pd" 5400 Waiting for connection request... WARNING: connect to pd failed, retrying port localhost:5400. WARNING: connect to pd failed, retrying port localhost:5400. WARNING: connect to pd failed, retrying port localhost:5400. WARNING: connect to pd failed, retrying port localhost:5400. WARNING: connect to pd failed, retrying port localhost:5400. WARNING: connect to pd failed, retrying port localhost:5400. WARNING: connect to pd failed, retrying port localhost:5400. WARNING: connect to pd failed, retrying port localhost:5400. ^CPd: signal 2 gui socket 0 - closing audio... closing MIDI... ... done.
from this morn git pull $ /Volumes/U/Pd-0.48-0test3.app/Contents/Resources/bin/pd -verbose input channels = 2, output channels = 2 Pd-0.48.0 ("test3") compiled 22:16:32 Jul 19 2017 port 5400 "/Volumes/U/Pd-0.48-0test3.app/Contents/Resources/../MacOS/Pd" 5400 Waiting for connection request... WARNING: connect to pd failed, retrying port localhost:5400. WARNING: connect to pd failed, retrying port localhost:5400. WARNING: connect to pd failed, retrying port localhost:5400. WARNING: connect to pd failed, retrying port localhost:5400. WARNING: connect to pd failed, retrying port localhost:5400. WARNING: connect to pd failed, retrying port localhost:5400. WARNING: connect to pd failed, retrying port localhost:5400. WARNING: connect to pd failed, retrying port localhost:5400. WARNING: connect to pd failed, retrying port localhost:5400. ^CPd: signal 2 gui socket 0 - closing audio... closing MIDI... ... done. $
On Thu, Jul 20, 2017 at 11:37 AM, Miller Puckette <msp@ucsd.edu mailto:msp@ucsd.edu> wrote:
Thanks.. and how does "test3" behave? It's compiled with 8.5-gen Tcl/TK - should behave like "test1" ded, except with better text spacing. M On Thu, Jul 20, 2017 at 11:08:30AM -0400, me.grimm wrote: > ok... got a chance to test this morn. > > miller test02 (pd icon just bounces in the dock) > > $ /Volumes/U/Pd-0.48-0test2.app/Contents/Resources/bin/pd -verbose > input channels = 2, output channels = 2 > Pd-0.48.0 ("test2") compiled 08:40:39 Jul 19 2017 > port 5400 > "/Volumes/U/Pd-0.48-0test2.app/Contents/Resources/../MacOS/Pd" 5400 > Waiting for connection request... > WARNING: connect to pd failed, retrying port localhost:5400. > WARNING: connect to pd failed, retrying port localhost:5400. > WARNING: connect to pd failed, retrying port localhost:5400. > ^CPd: signal 2 > gui socket 0 - closing audio... > closing MIDI... > ... done. > $ > > > my compile with tk 8.6.6 (tk "feather" icon just bounces in the dock > > $ /Volumes/U/Pd.app/Contents/Resources/bin/pd -verbose > input channels = 2, output channels = 2 > Pd-0.48.0 ("test1") compiled 16:38:24 Jul 19 2017 > port 5400 > "/Volumes/U/Pd.app/Contents/Resources/../MacOS/Pd" 5400 > Waiting for connection request... > WARNING: connect to pd failed, retrying port localhost:5400. > WARNING: connect to pd failed, retrying port localhost:5400. > WARNING: connect to pd failed, retrying port localhost:5400. > WARNING: connect to pd failed, retrying port localhost:5400. > WARNING: connect to pd failed, retrying port localhost:5400. > WARNING: connect to pd failed, retrying port localhost:5400. > WARNING: connect to pd failed, retrying port localhost:5400. > WARNING: connect to pd failed, retrying port localhost:5400. > WARNING: connect to pd failed, retrying port localhost:5400. > WARNING: connect to pd failed, retrying port localhost:5400. > WARNING: connect to pd failed, retrying port localhost:5400. > WARNING: connect to pd failed, retrying port localhost:5400. > WARNING: connect to pd failed, retrying port localhost:5400. > WARNING: connect to pd failed, retrying port localhost:5400. > WARNING: connect to pd failed, retrying port localhost:5400. > WARNING: connect to pd failed, retrying port localhost:5400. > WARNING: connect to pd failed, retrying port localhost:5400. > ^CPd: signal 2 > gui socket 0 - closing audio... > closing MIDI... > ... done. > $ > > > tell me what to try and i will since i have access to student computer next > couple weeks.... > > cheers > m > > > On Wed, Jul 19, 2017 at 1:32 PM, Miller Puckette <msp@ucsd.edu <mailto:msp@ucsd.edu>> wrote: > > > Can you try with "test2"? (on my site, just now uploaded it). > > > > thanks > > Miller > > > > On Wed, Jul 19, 2017 at 06:00:36PM +0200, Dan Wilcox wrote: > > > The error indicates the pd core has crashed or is not running. Sometimes > > this also happens if the pd proves has hung in the background. Open > > Activity Monitor and make sure there is no "pd" processing running, if so > > then kill it. > > > > > > As a test, try running the pd core from the command line in Terminal: > > > > > > /Applications/Pd-VERSION.app/Contents/Resources/bin/pd > > > > > > You can at least see some info. You can also run it with the -verbose > > flag to see even more info. > > > > > > > On Jul 18, 2017, at 11:21 PM, pd-list-request@lists.iem.at <mailto:pd-list-request@lists.iem.at> wrote: > > > > > > > > Subject: Re: [PD] Macbook Air Errors with 0.48 Test 1 > > > > Date: July 18, 2017 at 10:16:13 PM GMT+2 > > > > To: Miller Puckette <msp@ucsd.edu <mailto:msp@ucsd.edu> <mailto:msp@ucsd.edu <mailto:msp@ucsd.edu>>> > > > > Cc: "pd-list@lists.iem.at <mailto:pd-list@lists.iem.at> <mailto:pd-list@lists.iem.at <mailto:pd-list@lists.iem.at>>" < > > pd-list@lists.iem.at <mailto:pd-list@lists.iem.at> <mailto:pd-list@lists.iem.at <mailto:pd-list@lists.iem.at>>> > > > > > > > > > > > > sierra indicates > > > > > > > > 10.12 > > > > > > > > https://en.wikipedia.org/wiki/MacOS_Sierra <https://en.wikipedia.org/wiki/MacOS_Sierra> <https://en.wikipedia.org/ > > wiki/MacOS_Sierra> > > > > > > > > > > > >> On 18 Jul 2017, at 21:55, Miller Puckette <msp@ucsd.edu <mailto:msp@ucsd.edu> <mailto: > > msp@ucsd.edu <mailto:msp@ucsd.edu>>> wrote: > > > >> > > > >> Really 10.2.5? Not 10.5? > > > >> > > > >> I've tested on 10.6. I ues I'd better try an earlier one :) > > > >> > > > >> M > > > >> > > > >> On Tue, Jul 18, 2017 at 02:39:06PM -0400, me.grimm wrote: > > > >>> Hello, > > > >>> > > > >>> So I have a student with a Macbook Air. Pd 0.47.1 that she > > downloaded hangs > > > >>> and quits as detailed here: > > > >>> https://lists.puredata.info/pipermail/pd-list/2016-12/117154.html <https://lists.puredata.info/pipermail/pd-list/2016-12/117154.html> < > > https://lists.puredata.info/pipermail/pd-list/2016-12/117154.html <https://lists.puredata.info/pipermail/pd-list/2016-12/117154.html>> > > > >>> > > > >>> then miller said he maybe fixed? > > > >>> https://lists.puredata.info/pipermail/pd-list/2016-12/117157.html <https://lists.puredata.info/pipermail/pd-list/2016-12/117157.html> < > > https://lists.puredata.info/pipermail/pd-list/2016-12/117157.html <https://lists.puredata.info/pipermail/pd-list/2016-12/117157.html>> > > > >>> > > > >>> So I just tried the version (recent test) i recently compiled and > > that > > > >>> opens (sort of) but I get now Pd window. I did get error: > > > >>> > > > >>> Not connected to 'pd' process > > > >>> Not connected to 'pd' process > > > >>> while executing > > > >>> "error "Not connected to 'pd' process"" > > > >>> (procedure "pdsend" line 6) > > > >>> invoked from within > > > >>> "pdsend "pd audio-properties"" > > > >>> (procedure "::tk::mac::ShowPreferences" line 3) > > > >>> invoked from within > > > >>> "::tk::mac::ShowPreferences" > > > >>> > > > >>> shes on macbook air 10.2.5 (sierra) 13" early 2015 > > > >>> > > > >>> I know there has been trouble running Pd on Macbook Airs in the past > > and > > > >>> would like to nail whats wrong. let me know what to do to test while > > I have > > > >>> access to this machine for the next couple weeks. > > > >>> > > > >>> thanks!