disable the "socket in separate thread" code again since it does not perform the way it was intended to
This commit is contained in:
parent
f85115d548
commit
e8b65b6c0d
1 changed files with 6 additions and 2 deletions
|
@ -74,8 +74,12 @@ LED bar: lbr
|
||||||
// be put in the jitter buffer with highest priority).
|
// be put in the jitter buffer with highest priority).
|
||||||
// Since the new code is still in "experimental state", we introduced this macro
|
// Since the new code is still in "experimental state", we introduced this macro
|
||||||
// to enable/disable the new code.
|
// to enable/disable the new code.
|
||||||
#define ENABLE_RECEIVE_SOCKET_IN_SEPARATE_THREAD
|
//
|
||||||
//#undef ENABLE_RECEIVE_SOCKET_IN_SEPARATE_THREAD
|
// I disabled the new code again since it seems not to improve the situation
|
||||||
|
// much. Maybe things must be tweaked for it to work correctly...
|
||||||
|
//
|
||||||
|
//#define ENABLE_RECEIVE_SOCKET_IN_SEPARATE_THREAD
|
||||||
|
#undef ENABLE_RECEIVE_SOCKET_IN_SEPARATE_THREAD
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue