-
When using alsa and the first audio device is busy, the client fails to start.
(To be done: Make the client try other available devices. Make it possible to select a device in the config file.)
2008-11-23 23:19:16 UTC in Linux-Wildo!
-
scorpyn committed revision 312 to the Linux-Wildo! SVN repository, changing 1 files.
2007-11-25 21:45:26 UTC in Linux-Wildo!
-
Re-opening due to a miscommunication, it was not supposed to be removed. Nobody is currently assigned to it, but I'll get to it after sorting out the documentation for the project a bit.
2007-11-22 18:54:50 UTC in Linux-Wildo!
-
I'm temporarily unassigning myself from this since I will focus on the documentation for a bit first.
2007-11-22 18:29:35 UTC in Linux-Wildo!
-
blah blah portability blah blah have spoken to ds about it on irc a while ago etc.
2007-11-06 12:31:18 UTC in Linux-Wildo!
-
We've decided to skip fixing this (at least for now), and instead add support for OpenAL.
2007-11-06 12:17:38 UTC in Linux-Wildo!
-
>>When closing the client, the dataserver gets a flood of the following 2
>>lines :
>>[>NetworkErrorException: Unknown packet identifier received.
>
>rev 308 should fix this. Please test (I tested here and works)
Fix confirmed, it appears to be working properly here too.
2007-09-24 19:39:50 UTC in Linux-Wildo!
-
tested rev. 307
When closing the client, the dataserver gets a flood of the following 2 lines :
[
2007-09-22 16:22:14 UTC in Linux-Wildo!
-
The scenario :
Controlserver on lwc.foo.com
Dataserver on lwd.foo.com
(the addresses are just examples)
The client tries to create a room on lw.foo.com (which doesn't have a dataserver running).
Now, what should happen :
The controlserver tries to contact the dataserver, fails, and the room won't be visible when the client requests a room list.
What really happens :
The...
2007-06-27 18:16:04 UTC in Linux-Wildo!
-
A workaround that appears to be working every time :
1. Connect to the controlservers internal ip
2. Create a new room on the dataserver, but with the internal ip instead of the external one. (This is actually possible, I assume that the control server doesn't know about every interface the dataserver has.)
3. Set the codec to the same as the external version of the room, then continue as...
2007-06-23 14:26:21 UTC in Linux-Wildo!