search for: enodings

...nfiguration is such that we have a low bitrate encoding on port 8000, and a high bitrate encoding on 889. I've been looking through the documentation but haven't found a good way to make this happen in Icecast. We're using Darkice to stream to the server, and that does the different enodings fine, but from the Icecast side I can't figure out how to set the same mount point ( / ), have different data on different ports. Is this possible? Or do I have to run separate Icecast instances? Thanks! .josh Josh Burley Computing Manager KUCI 88.9fm in Irvine

Hello. I found that anonymous structures does not work on gcc-2.95. If you guys want to support a bit older platforms I suggest fixing it. You can check out patch I created to fix this issue. I just added 2 extra structures to remove anonymous structs inside connection_status_t and node_status_t. Patch is here: ftp://borg.uu3.net/pub/unix/tinc/tinc.patch Attaching it as well. Regards, Borg

...uch that we have a low bitrate encoding on port 8000, > and a high bitrate encoding on 889. I've been looking through the > documentation but haven't found a good way to make this happen in > Icecast. We're using Darkice to stream to the server, and that does the > different enodings fine, but from the Icecast side I can't figure out > how to set the same mount point ( / ), have different data on different > ports. > > Is this possible? Or do I have to run separate Icecast instances? You can run your two streams on one icecast, configuring them as (for exa...

Hi, Sorry for the delay, it has taken some extra time as more than one bug showed up ☺ I continued to look into this with your viewpoint that a node that is conservatively allocatable should never be spilled. The first thing I did was therefore to add some extra code with an assert for this. I believe I then found three bugs and fixed the two: Bug 1: Incorrect transpositions in handleAddEdge()

- Re-sending to include llvm-dev. HI Jonas, This is great - thank you very much for your analysis! You're spot on about Bug 1 - the row/column checks are transposed there. I have fixed this in r227628. Regarding Bug 2, as discussed on the other thread I'm going to teach the register allocator to prune single-option vregs so that they never make it into the graph. I haven't had a

> A node should never be put into the conservatively allocatable list if there is a chance of it spilling. I can understand why the logic of NodeMetadata::isConservativelyAllocatable is necessary for the node to be allocatable, but I have not been able to convince myself this is sufficient, especially when the node degree > available registers. Cheers, Arnaud From:

Greetings all.. I'm sending this message out here because I suspect that some folks involved in the vorbis codec might be interested in the following (we'd certainly like to make vorbis work well with UCI, and welcome any help in this area). If this is not the case (or this is not an appropriate forum for this sort of thing) I apologize in advance.. <p> Project

(Second try to send this. I wonder if the first one gotten eaten by a spam filter; I'll link to patches instead of attaching them.) Here are the tincctl patches I've been working on. They apply to http://www.tinc-vpn.org/svn/tinc/branches/1.1@1545. I intend to commit them once the crypto stuff's fixed. Since they're basically done, I'm emailing them now for review and in case