Okay,

The wxController.py example that comes with csound runs on my machine. I
understand it pretty much. This is progress, & my basis for moving forward.

I have 3 immediate questions.

1) if i want to (for example) write values to an ftable in csound using a
wxSlider interface, assumedly there is another way to pass the value from
the slider to csound than via a score statement using InputMessage() & have
an instrument interpret the pfields to rewrite the ftable? 

2) kind of the reverse. Lets say i have a list in Python, & I want to record
note on times / kdata1 & kdata2 recieved using the midiin opcode to that
list. How is this achieved?

assumedly then chnget & chnset opcodes come into all of this as the
alternative to pfield messages?? (& obviously i cant send "pfield messages"
back to python after all!)

Victor's cb.py & cb.csd in the examples directory seem to offer some inroads
- why would i / should i use chnexport as opposed to chnget / chnset? does
GetChannel() & SetChannel() work identically for chnget & chnset?

Im afraid the other python_callback.py example leaves me a little
bemused....

3) does anyone have anything further / new to add in trying to get an
overview of the Python Csound API?

David W, if you are reading this, wasn't there some beginner info about
"pydocs" on your website somewhere? I couldn't find it when i had a quickish
look this morning... & if i get answers to 1) & 2) perhaps you can
incorporate them as examples on your site.

Oeyvind - i've looked a bit at the documentation you have created /
generated for Barebones, & i'm wondering could something similar not be done
for the Python API itself? (or at least the "grass roots functionality" of
establishing links & input from one to the other...). 

& I remain contually confused about csound versus cppsound in all this...
(again terms i'm familiar with vis a vis the API, but don't fully
understand.)

The actual refman.pdf i still feel is of limited to zero application to
someone like myself who simply wants to cobble together some more meaningful
relationships based on what he knows of csound / python.

I guess the "problem" here is the "python" API is actually just a wrap of
C++ code? So that explains why everything about the API (such as rory's
brief introduction) is based on C or C++...

It's just very frustrating from my point of view to be perpetually locked
out of this process. 

The API dinner's on the python plate, but still there's no knife & fork...

I have an EU passport. if someone wants to consider offering me special
dispensation to enrol in an appropriate semester length course to learn this
stuff & i can find a job on campus flipping burgers to avoid starvation i'm
all ears.

-----
*******************
www.phasetransitions.net
hermetic music * python * csound * possibly mindless ranting
various werk in perpetual delusions of progress....

-- 
View this message in context: http://www.nabble.com/Python-API---chnget-ing---chnset-ing-%28mainly%29-tp16930283p16930283.html
Sent from the Csound - General mailing list archive at Nabble.com.