Launching pdlork on OSX - says "Pd started." but user needs to still wait 15-20 seconds (mid-2009 MBP) before the app works
When I first moved from PD Vanilla to PDlork/PurrData, the first thing I had was, I'd boot up pdlork and immediately load up a patch. And nothing would happen.
I then realized that even though pdlork says "Pd started.", I gotta wait 15-20 seconds before it is actually ready to be used. It then outputs this stuff:
incoming connection to GUI canvasinfo: v0.1 stable canvasinfo methods: args dir dirty editmode vis pdinfo: v.0.1 stable pdinfo methods: dir dsp version classinfo: v.0.1 stable classinfo methods: size objectinfo: v.0.1 stable objectinfo methods: class [import] $Revision: 1.2 $ [import] is still in development, the interface could change! compiled against Pd-l2ork version 20170122 libdir loader 1.9 compiled on Jan 22 2017 at 20:09:36 compiled against Pd version 0.42.7.20170122 Gem: can't load library libdir_loader: added 'cyclone' to the global objectclass path libdir_loader: added 'zexy' to the global objectclass path libdir_loader: added 'creb' to the global objectclass path libdir_loader: added 'cxc' to the global objectclass path libdir_loader: added 'iemlib' to the global objectclass path libdir_loader: added 'list-abs' to the global objectclass path libdir_loader: added 'mapping' to the global objectclass path libdir_loader: added 'markex' to the global objectclass path libdir_loader: added 'maxlib' to the global objectclass path libdir_loader: added 'memento' to the global objectclass path libdir_loader: added 'mjlib' to the global objectclass path libdir_loader: added 'motex' to the global objectclass path libdir_loader: added 'oscx' to the global objectclass path libdir_loader: added 'pddp' to the global objectclass path libdir_loader: added 'pdogg' to the global objectclass path libdir_loader: added 'pixeltango' to the global objectclass path libdir_loader: added 'rradical' to the global objectclass path libdir_loader: added 'sigpack' to the global objectclass path libdir_loader: added 'smlib' to the global objectclass path libdir_loader: added 'unauthorized' to the global objectclass path vbap - v1.1 - 14 Aug. 2014 - (c) Ville Pulkki 1999-2006 (Pd port by HCS) libdir_loader: added 'pan' to the global objectclass path libdir_loader: added 'hcs' to the global objectclass path libdir_loader: added 'jmmmp' to the global objectclass path libdir_loader: added 'ext13' to the global objectclass path libdir_loader: added 'ggee' to the global objectclass path libdir_loader: added 'ekext' to the global objectclass path PDP: pure data packet version 0.12.7 libdir_loader: added 'disis' to the global objectclass path libdir_loader: added 'lyonpotpourri' to the global objectclass path
and THEN it's ready to be used. Could there be some sort of warning of this long haul of preparation being, well, in preparation - before Pd is actually started? Like some sort of "loading extra libraries" or something. I'm perfectly fine (no I'm not!) waiting 15-20 seconds for pdlork/purrdata to get it's default extensions (don't know what they're called?) loaded, but it would be nice to know that something extra is being done.