Displaying 3 results from an estimated 3 matches for "no_meta".
Did you mean:
node_meta
2005 Jul 28
2
icecast performance on many concurrentlow-bitrate streams
Hi Karl,
Thanks for your info. I have a standard Icecast-2.2 release with a few local patches. I'm a little apprehesive to apply my patches to the kh14 branch, so I'd rather patch my branch with the changes related to batched reads from the kh branch.
I've looked at your code to see if I could spot the changes related to batching reads. So far I have not been able to find where
2005 Jul 28
0
icecast performance on many concurrentlow-bitrate streams
...see if I could spot the changes related to batching reads. So far I have not been able to find where you've made this patch. Could you point me in the right direction?
The changes for batching part are really just isolated to the
format_mp3.[ch] files, within the 2 readers calls (filter_meta,
no_meta).
commit diff is listed on
http://lists.xiph.org/pipermail/commits/2005-June/007469.html
There have been various changes between 2.2 and the trunk/kh code so I'm
sure that just dropping those 2 files into the 2.2.0 tree will not work
right off. For one thing the response headers are treated...
2005 Jul 28
2
icecast performance on manyconcurrentlow-bitrate streams
...see if I could spot the changes related to
batching reads. So far I have not been able to find where you've made this
patch. Could you point me in the right direction?
The changes for batching part are really just isolated to the
format_mp3.[ch] files, within the 2 readers calls (filter_meta,
no_meta).
commit diff is listed on
http://lists.xiph.org/pipermail/commits/2005-June/007469.html
There have been various changes between 2.2 and the trunk/kh code so I'm
sure that just dropping those 2 files into the 2.2.0 tree will not work
right off. For one thing the response headers are treated d...