Re: Wanted: C++ Audio Programmer For Exciting Project Team
googlemike_at_hotpop.com
Date: 03/01/05
- Next message: googlemike_at_hotpop.com: "Re: Wanted: C++ Audio Programmer For Exciting Project Team"
- Previous message: David Schwartz: "Re: Wanted: C++ Audio Programmer For Exciting Project Team"
- Maybe in reply to: Otto Wyss: "Re: Wanted: C++ Audio Programmer For Exciting Project Team"
- Next in thread: John Hasler: "Re: Wanted: C++ Audio Programmer For Exciting Project Team"
- Reply: John Hasler: "Re: Wanted: C++ Audio Programmer For Exciting Project Team"
- Reply: Bruno Barberi Gnecco: "Re: Wanted: C++ Audio Programmer For Exciting Project Team"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 28 Feb 2005 15:55:24 -0800
Good thoughts, John. I'll try to make certain that Bruno Barberi Gnecco
sees this and can consider it. Do you want to join the project?
We're also still trying to come up with a name. Let me know if you have
an idea. I can secure the SourceForge space -- I've done this before
with my "pgst" project. Bruno can then drive as project manager and
some coding, but we're seeking another coder to do the audio work.
Bruno already has some of this work going already except for audio. For
me, I'm more an organizer, beta-tester, and tinkerer. I know C++ only
enough to read it and understand what's going on. (PHP, Bash, Python,
VB6 and anything database-related are my real forte.)
Also, if I'm a client that becomes a host for only one stream, isn't
that somewhat limiting? If my bandwidth can support a couple more
streams, why not take advantage of that?
The idea is that by default the command line app would throttle one's
bandwidth so that they could not only listen to the stream, but host it
for one or more other fans without hurting one's own stream or ability
to surf web or catch email. It would do this by short bandwidth tests
after one minute of cache time, I was thinking. Then, if the user's
bandwidth couldn't handle it, it would either throttle it back to
listen-only (such as for dial-up users) or host streams for less users.
Meanwhile, it would have a cap of about 8 outgoing streams so that the
thing doesn't take off to infinity. Last, if one wanted to force their
client software to opt out of being a broadcaster, they could use a
command line switch for that.
- Next message: googlemike_at_hotpop.com: "Re: Wanted: C++ Audio Programmer For Exciting Project Team"
- Previous message: David Schwartz: "Re: Wanted: C++ Audio Programmer For Exciting Project Team"
- Maybe in reply to: Otto Wyss: "Re: Wanted: C++ Audio Programmer For Exciting Project Team"
- Next in thread: John Hasler: "Re: Wanted: C++ Audio Programmer For Exciting Project Team"
- Reply: John Hasler: "Re: Wanted: C++ Audio Programmer For Exciting Project Team"
- Reply: Bruno Barberi Gnecco: "Re: Wanted: C++ Audio Programmer For Exciting Project Team"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|