| Perhaps because your MacPython is PPC as well,
and Apple's Python is Intel.
>
> Well, but the task
>
> import csnd
>
> is ok in MacPython 2.3 (IDLE 1.0). The csnd module is
> found and can be loaded correctly.
>
> But when I go to the terminal and try the same in
> /usr/bin/python2.3 I get:
>
> Python 2.3.5 (#1, Jan 13 2006, 20:13:11)
> [GCC 4.0.1 (Apple Computer, Inc. build 5250)] on darwin
> Type "help", "copyright", "credits" or "license" for more
> information.
> >>> import csnd
> Traceback (most recent call last):
> File "", line 1, in ?
> File
> "/System/Library/Frameworks/Python.framework/Versions/2.3/
> lib/ python2.3/csnd.py", line 7, in ?
> import _csnd
> ImportError:
> dlopen(/System/Library/Frameworks/Python.framework/
> Versions/2.3/lib/python2.3/_csnd.so, 2): no suitable image
> found. Did find:
>
> /System/Library/Frameworks/Python.framework/Versions/2.3/l
> ib/ python2.3/_csnd.so: mach-o, but wrong architecture
>
> Is this because of the PPC version (being on an IntelMac)?
> Why no problem with MacPython/ IDLE?
>
> joachim
>
>
> Am 09.11.2007 um 22:14 schrieb Oeyvind Brandtsegg:
>
> > I think one should not run any halfway complex stuff in
> > IDLE. I do not remember the exact reason why, neither
> > the exact implications, but it has to with IDLE itself
> > being written in Python. This means we get one Python
> > app running on top of another and it does sometimes lead
> > to unexpected results and strange error messages. Repeat
> , do not run stuff in IDLE. >
> > best
> > Oeyvind
> >
> >
> > 2007/11/9, Victor Lazzarini :
> >> The code is correct. The -1 answer means that
> >> probably the CSD was not found or that other
> >> problem happened during the compilation.
> >>
> >> -1 actually means an error. Also in OSX maybe
> >> the csound messages have been printed to the
> >> console (see it in utilities), not the terminal.
> >>
> >> (On Windows, if I run it from Idle, I also do
> >> not get any Csound messages)
> >>
> >> Victor
> >>>
> >>> Hi David -
> >>>
> >>> I find it very useful. But your example "Playing an
> >>> existing csd file" doesn't work on my system
> (MacPython >>> 2.3, Csound PPC 5.07). No error messages,
> but it returns >>> -1:
> >>>
> >>>>>> import csnd
> >>>>>> cs = csnd.Csound()
> >>>>>> fname =
> >>>
> "/Users/jh/Documents/Csound/PythonInCsound/pythontest.csd"
> >>>>>> cs.Perform(fname) >>> -1
> >>>
> >>> When I first run main.py from Oeyvinds
> >>> PartikkelCloudDesigner (it stops at a certain point,
> but >>> after loading all the csnd stuff), it's ok
> (returns 0) >>> and "test.aif" is written in the directory
> of the >>> PartikkelCloudDesigner. So maybe there has to
> be one or >>> more other tasks before cs.Perform(fname)?
> >>>
> >>> Best -
> >>>
> >>> joachim
> >>>
> >>>
> >>>
> >>> Am 09.11.2007 um 13:33 schrieb David Worrall:
> >>>
> >>>> Hi All,
> >>>> I've been finding my way around the python wrappers
> for >>>> csnd. In my search I've come across quite a few
> people >>>> who have found the process just too hard. So
> , bearing >>>> in mind thathis process is likely to
> attract new users >>>> , I thought it would be good to
> begin to put a >>> graduated introduction together. >
> >>>> I've just scratched out a temporary beginning, for
> the >>>> moment at http://www.avatar.com.au/sonify/csnd/
> >>>>
> >>>> A couple of things suggest themselves.
> >>>>
> >>>> Reference material
> >>>> -------------------------
> >>>> Apart from some simple examples, it would be good to
> >>>> merge the output from help(csnd) with the info in
> the >>>> header files, particularly csound.h
> >>>> Has anyone written such a script? It wouldn't be too
> >>>> hard a hack and then each version or compile
> options >>>> change, a reference could be computed by
> the user >>> particular to their own system. >
> >>>> Examples
> >>>> --------------
> >>>> From what I can see, the only example from the
> examples >>>> directory in the sources that runs on the
> default OSX >>>> .dmg install of v5.7 without being
> modified is >>>> Victor's vu.py (It relies on TclSTk being
> installed.) >>>> tFair enough - It is a "way in" I could
> put up a hacked >>> down version (no graphics), just to
> illustrate the use of >>>> CsoundPerformanceThread and
> SetChannel and proceed >>> that way ... >
> >>>> I'm not sure if people would find these type of
> things >>>> useful. Perhaps you have other ideas.
> Feedback? >>>>
> >>>> ciao,
> >>>>
> >>>> David
> >>>>
> >>>>
> >>>>
> >>>> _________________________________________________
> >>>> experimental polymedia: www.avatar.com.au
> >>>> Sonic Communications Research Group,
> >>>> University of Canberra:
> >>> creative.canberra.edu.au/scrg/ >
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >
>
>
|