...and tweak buffers, on the client side too if possible - they are time-bottlenecks (is this the right expression? :o)
...going mono might help as well
...and i always liked realaudio's auto bitrate calibration based on network thruput - not that i'm recommending realaudio anyway

Andras


On Tue, Mar 29, 2011 at 18:01, Tedb0t <lists@liminastudio.com> wrote:
Yeah, I know... sigh!  Might just have to compromise on bitrate to try to improve it :-/

—t3db0t

On Mar 29, 2011, at 11:58 AM, András Murányi wrote:

On Tue, Mar 29, 2011 at 17:20, Tedb0t <lists@liminastudio.com> wrote:
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?

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.

——t3db0t


Huh, if it really goes over the internet, not just on localhost, expect a latency of 1-10sec...

Andras
_______________________________________________
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list


_______________________________________________
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list




--
Muranyi Andras