The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: RE: xPLMediaNet - Patch Update and First MVP Release


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

RE: xPLMediaNet: Limiting stream bandwidth per client


  • Subject: RE: xPLMediaNet: Limiting stream bandwidth per client
  • From: "Tony Tofts" <tony@xxxxxxxxxx>
  • Date: Fri, 16 Sep 2005 09:36:23 +0100

> However, due to the distinctly average upload bandwidth on my
> home connection, any tracks encoded at greater than 128Kb/s
> caused the stream to fragment :-(

I have the same issue, and will be working on it

> Is it possible to allow transcoding for a "remote" player
> (only) so that all music is encoded and streamed at a maximum
> of 128Kb/s (for example) while allowing any other "local"
> clients to play the full bandwidth streams?
> Apologies if this is already supported; I haven't found a way
> to make it work.

You can do it, but this would effect local hardware players too (as you
point out)...

I'm thinking I could include a bitrate in the software player url,
http://ip:port/playername/128,
including this would cause mp3's (.ogg, .flac
etc are already transcoded of course) to then be transcoded at the selected
bitrate (need to modify the transcoder to allow bitrate overrides too)

Currently you can't transcode a stream, which is what I really want as I
stream my local radio, and I can't say when this will be available as it's
a
tricky one!

BTW haven't done anything on xplmedianet this week, hectic week. This
weekend am going to fix the rio ogg etc issues found and will also make
this
change. MVP is so close to being ready, but looks like it won't be this
weekend

Regards
Tony




xPL Main Index | xPL Thread Index | xPL Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.