<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
I've once made a project like this, and found out that it's better to not send interpolated data through FUDI,<br>
interpolation can be done on client's end, it saves a lot of bandwidth.<br>
<br></blockquote><div>yes, my idea as well, is the only send message data across, with all the heavy lifting done in the "signal" patch on the client end. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Just an idea,<br>
<br>
for sequencing events there are ways to reduce a lot the dataflow by using protocols different from MIDI sequencing.<br>
MIDI needs a very tight timecode, the amount of data is increasing with bpm and controller values.<br>
I've found one different way that is about sending a packet containing all the pattern informations<br>
that would be triggered with a simple beat clock. There is a backup of this work there:<br>
<br>
<a href="http://megalego.free.fr/pd/patko/list-sequence/" target="_blank">http://megalego.free.fr/pd/patko/list-sequence/</a></blockquote><div><br></div><div>would this work properly on high speed realtime data? my goal is to create a connection that can handle many streams of real time data, very fast. it may be a moot point later this week as i just ordered an i7 based quadcore laptop which i think will deal with all of this without blinking but I would like to find the most efficient route for elegance sake.</div>
<div><br></div><div>thanks for the feedback. i will investigate those patches thoroughly.</div><div><br></div><div>onyx</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
<br>
This might be suited for transmitting sequential events through network,<br>
but I haven't experimented this yet,<br>
the main idea was about interpreting tabla language:<br>
<br>
<a href="http://megalego.free.fr/pd/patko/tablas/" target="_blank">http://megalego.free.fr/pd/patko/tablas/</a><br>
<br>
<br>
There you have my two cents, good luck in your project.<br>
<br>
<br>
Colet Patrice<br>
<br>
----- Mail original -----<br>
> De: "<a href="mailto:onyx@onyx-ashanti.com">onyx@onyx-ashanti.com</a>" <<a href="mailto:onyxashanti@gmail.com">onyxashanti@gmail.com</a>><br>
> À: <a href="mailto:Pd-list@iem.at">Pd-list@iem.at</a><br>
> Envoyé: Jeudi 8 Décembre 2011 19:19:55<br>
> Objet: [PD] Networking patches to utilize multiple cores<br>
<div><div class="h5">><br>
> Greets.<br>
><br>
> Is there a proper or preferred method for using any of the networking<br>
> objects in pd-extended to allow for realtime bi-directional<br>
> communication<br>
> between patches on the same computer, so as to utilize 2 or more cpu<br>
> cores?<br>
> I am currently trying to discover the best way to handle this.<br>
><br>
> i started with netsend/netrecieve and used [route] to send<br>
> approximately 40<br>
> or so streams as messages, and it worked, somewhat, but I think i may<br>
> have<br>
> been squeezing too much data through that one netsend as it was a bit<br>
> sluggish (running on a dual core thinkpad 1.83ghz, 3gb ram). I am<br>
> working<br>
> with 2-5ms latencies so sluggish can screw me up in performance,<br>
> especially<br>
> since i havent even added 60% of the data that will be streaming from<br>
> my<br>
> "messages" patch to my "signals" patch. I am looking at<br>
> netserver/netclient and contemplating breaking the streams up into 2<br>
> or<br>
> more clients but i wanted to see if anyone had any advice in this<br>
> regard.<br>
><br>
> the goal is to have a "messages" patch that would interpret all the<br>
> incoming sensor and performance data, send it to subpatches for GEM<br>
> visualizations, interpretive synth controls and looping system<br>
> parameters,<br>
> THEN, send that data to a separate patch that would house around 15<br>
> signal<br>
> object based subpatches for synthesis, looping and effects. any<br>
> status<br>
> feedback i need from the signal objects would need to be sent back to<br>
> the<br>
> messages patch for processing and display, so a realtime,<br>
> bi-directional<br>
> solution is very important.<br>
><br>
> insight?<br>
><br>
> Onyx<br>
><br>
> --<br>
> <a href="http://www.onyx-ashanti.com" target="_blank">www.onyx-ashanti.com</a><br>
><br>
</div></div>> _______________________________________________<br>
> <a href="mailto:Pd-list@iem.at">Pd-list@iem.at</a> mailing list<br>
> UNSUBSCRIBE and account-management -><br>
> <a href="http://lists.puredata.info/listinfo/pd-list" target="_blank">http://lists.puredata.info/listinfo/pd-list</a><br>
><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div><div><a href="http://www.onyx-ashanti.com" target="_blank">www.onyx-ashanti.com</a></div><br></div><a title="phone number" style="color:rgb(0,0,63);background-color:rgb(255,255,191)"><br>
</a><br>