<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Yeah, I know... sigh! Might just have to compromise on bitrate to try to improve it :-/<div><br></div><div>—t3db0t</div><div><br><div><div>On Mar 29, 2011, at 11:58 AM, András Murányi wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Tue, Mar 29, 2011 at 17:20, Tedb0t <span dir="ltr"><<a href="mailto:lists@liminastudio.com">lists@liminastudio.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word"><div class="im"><blockquote type="cite">If i wanted to use Pd to generate sound for a web application, i'd have to keep an instance of Pd running on the server continuously, right? And keep all the patches i need open? Which means that if any patch crashes Pd there'll be no sounds anymore?<br>
</blockquote><br></div>Well, the question is how the audio is getting to the user. As you said, WebPd requires FF4's audio API. If you want the actual Pd running on a server then you need a way of hearing the output. In my own pd-on-the-web project, PuréeData, I'll be using an mp3 or ogg stream. Latency will be an issue, but hopefully not a tremendously bad one.<br>
<br>——t3db0t<div><div></div><div class="h5"><div><br></div><div></div></div></div></div></blockquote><div><br></div><div>Huh, if it really goes over the internet, not just on localhost, expect a latency of 1-10sec...</div>
<div><br></div><div>Andras</div></div>
_______________________________________________<br><a href="mailto:Pd-list@iem.at">Pd-list@iem.at</a> mailing list<br>UNSUBSCRIBE and account-management -> <a href="http://lists.puredata.info/listinfo/pd-list">http://lists.puredata.info/listinfo/pd-list</a><br></blockquote></div><br></div></body></html>