Comments on: Realm of the Practical http://codehop.com/realm-of-the-practical/ #code #art #music Wed, 14 Dec 2011 17:08:46 +0000 hourly 1 https://wordpress.org/?v=4.2.38 By: Andres Cabrera http://codehop.com/realm-of-the-practical/#comment-38 Sun, 30 May 2010 08:30:52 +0000 http://slipmat.noisepages.com/?p=178#comment-38 Do you mean that python iterators will be wrong for the graph because they are too slow?
 
Cheers,
Andrés

]]> By: Jacob Joaquin http://codehop.com/realm-of-the-practical/#comment-37 Thu, 27 May 2010 18:53:00 +0000 http://slipmat.noisepages.com/?p=178#comment-37 In Python 3, map() returns an iterator, as opposed to python 2 where map() returns a list. So let’s say you have this expression:

foo = map(lambda x, y: x + y, [1, 2, 3], [4, 5, 6])

Printing foo in Python 2 returns [5, 7, 9]. Printing foo in Python 3 returns <map object at 0xd5f190>.

The * operator in the statement “print(*f00)” prints each value that is yielded by the map iterator object, outputting: 5 7 9

That said, iterators/generators are completely inadequate for DSP graphs, though they did come in handy for developing a quick prototype.

I think what might happen is that a graph on the Python side of Slipmat will merely be a description of how unit generators are connected. Perhaps done with XML? Once a graph description is passed to the C/C++ engine, the graph description is parsed, and an actual graph is created. This really isn’t too different to how the Python Csound API works, or how Supercollider creates byte code that is passed to the server.

And hopefully I answered your question.

]]> By: Andrés http://codehop.com/realm-of-the-practical/#comment-36 Thu, 27 May 2010 17:15:10 +0000 http://slipmat.noisepages.com/?p=178#comment-36 Hi,
I’ve just checked this, and even though they are called generators, they seem to be evaluated when they are created. I’m using python 2.6, so they * operator doesn’t work… What is it for? (Is this the trick?)
 
Cheers,
Andrés
 

]]>