4 Nov
2011
4 Nov
'11
10:08 p.m.
On Fri, Nov 4, 2011 at 1:42 PM, Emanuel Rumpf <xbran(a)web.de> wrote:
2011/11/4 Iain Duncan
<iainduncanlists(a)gmail.com>om>:
Thanks for the opinion Emmanual, very helpful. Yeah, it may be better to
just start off in C++ for the engine side and bite the bullet there.
iain
On Fri, Nov 4, 2011 at 11:32 AM, Kjetil Matheussen
time
> Are you sure you need to use Python? There
are other high level
> languages
> letting you do this, which are much faster than Python.
> LuaAV for Lua is the most obvious since Lua is the same
> type of language as Python. Other alternatives I know of are Faust,
> Kronos (if it's available now) and Snd-RT.
> (Of those last three, you should look at Faust first.)
>
Well, I code in Python for a living, so as far as maximizing developer it makes sense! And there are a lot of nice
libraries out there for doing
things in Python ( gui, midi, osc interfaces, etc )
While I can understand your desire to code in Pyhton,
what you are trying to accomplish is not simple with Pyhton
(if possible at all), not even with C.
All your questions are just the beginning of a very huge problem ;)
I presume: by trying to use Python for this, dev-time will grow
exponentially ...
Do you have any experience in connecting python to C, "wrapping" ?
I would advice (if asked ;) to skip
Python for the real-time part.
Use any language that is capable.
(Apparently, most "Python Modules" are actually Wrapper-Classes for C
- would you call that a capable language ? ;)
You could still write the GUI in Python,
choosing any applicable protocol (OSC, D-Bus, ...) l in order to
connect to the non-rt part of the engine.