#231: jack with icecast (ogg) streaming causes hidden failures
-------------------------+--------------------------------------------------
Reporter: MiiJaySung | Owner: admin
Type: Bugs | Status: new
Priority: 5 | Milestone: NEAR FUTURE
Component: Liquidsoap | Version: 0.9.0+svn
Resolution: | Keywords: icecast jack disconnect
Mac: 1 | Linux: 1
Netbsd: 1 | Other: 1
Freebsd: 1 |
-------------------------+--------------------------------------------------
Comment (by MiiJaySung):
Not on the ML's, where's the sign up page to register to it? Would it not
be best to put in the SVN documentation?
After more fiddling between my last post and seeing your reply, I found
that this seems somewhat harder to recreate on my laptop (though with a
low frame size it still happen on JACK 0.116.x).
I've found the following things seem to help trigger this, they don't
always need to happen
* Low frame size
* JACK in LIQ ports need to be feed data (i.e. unconnected ports won't
trigger this)
* Server should be remote (i.e. small about of lag)
From the above it seems like due to some sort of data starvation is
triggering this. I've noticed on my laptop it's a lot harder to create,
which is odd as it's got a slowing CPU. The office machine is a top end 4
core Xeon. On the office box I've managed to have some success in reducing
the risk of this happening by the following:
Instead of having all of the streams + delayed versions in a single file,
have a script for each stream. This probably helps because each script is
on it's own core. This makes a big difference.
Setting JACK & Liquidsoap to have a nice value of about -5 seems to help.
The office PC won't accept a frame size under the 1024 mark, even with
soft mode.
I think the issue is liquidsoap related partly because I've found by using
a separate script for each stream (and it's delayed version) that
disconnections are local to the script instance, and when they do happen,
all streams disconnect for that script instance. The issue seems isolated
on a per a process basis which leads me to believe the issue is on the liq
side rather than JACK (and given the latest version of JACK doesn't stop
this on my laptop with a low frame size).
What irks me is the fact the the office machine is so sensitive. I can't
understand why. It's quite a critical issue though for me though as
disconnections need to be logged and reconnection should be attempted as
the only issues that will happen outside of my scope will be network ones
and these generally will only be temporary/recoverable glitches.
Hopefully next week I can provide you with some sort of access to the
troublesome machine for you to run tests on seeing it's proving to be not
as easy to trigger on my laptop. Both machines are running 64 bit Ubuntu,
have Intel CPU's, 4Gb RAM etc, so are similar specs, other than the lower
end laptop CPU.
--
Ticket URL: <http://savonet.rastageeks.org/ticket/231#comment:12>
Savonet <http://savonet.rastageeks.org/>
Let's program our stream !
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Savonet-trac mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-trac
