Jump to: navigation, search

Difference between revisions of "Ogre3D:Puredata"

(Created page with "Researches and notes about a communication between Ogre3D and puredata. == Development == Communication via internal network messages. * [netsend] and [netreceive] - http:/...")
 
(Development)
Line 7: Line 7:
 
* [netsend] and [netreceive] - http://en.flossmanuals.net/pure-data/network-data/send-and-receive/
 
* [netsend] and [netreceive] - http://en.flossmanuals.net/pure-data/network-data/send-and-receive/
 
* FUDI - https://en.wikipedia.org/wiki/FUDI
 
* FUDI - https://en.wikipedia.org/wiki/FUDI
 +
  
 
To be efficient, it requires a specialised patch (or a custom c/c++ object) to parse message '''sent by''' Ogre and another one to prepare message to '''send to''' Ogre.
 
To be efficient, it requires a specialised patch (or a custom c/c++ object) to parse message '''sent by''' Ogre and another one to prepare message to '''send to''' Ogre.
Line 12: Line 13:
 
* [ogre in] with preprocessed messages routing
 
* [ogre in] with preprocessed messages routing
 
* [ogre out] with one inlet type message
 
* [ogre out] with one inlet type message
 
  
 
== Release ==
 
== Release ==
  
 
Based on [[https://github.com/danomatika/ofxPd ofxPd]], prepare a binding to unable the communication with libPD.
 
Based on [[https://github.com/danomatika/ofxPd ofxPd]], prepare a binding to unable the communication with libPD.

Revision as of 11:44, 1 June 2016

Researches and notes about a communication between Ogre3D and puredata.

Development

Communication via internal network messages.


To be efficient, it requires a specialised patch (or a custom c/c++ object) to parse message sent by Ogre and another one to prepare message to send to Ogre.

  • [ogre in] with preprocessed messages routing
  • [ogre out] with one inlet type message

Release

Based on [ofxPd], prepare a binding to unable the communication with libPD.