2005-01-16, 22:56
i've been playing with the new live tv interface, which is pretty darn cool, but i've noticed a few problems with it.
firstly, i'm running a backend recording dvb-t streams, and xbmc doesn't like streaming from a nuv with one of these mpeg-2 streams unless there's about 5 seconds of data available already. i've hacked in a dialog between the request to the backend and the call to play in the scripts so i can wait a few seconds before proceeding, but it's not really ideal. if i get in too quickly the resulting stream often crashes xbmc. i've reduced the smb cache sizes right down which helps a little, but it doesn't fix the problem.
the other catch is that the scripts assume the stream is coming from tuner 1, my backend is set up to use "tuner 13", hence the scripts can't find the right .nuv ringbuffer. maybe the tuner number comes back in the response from the server or something, i dunno, but it might be worth looking into for completeness (i haven't had a chance to look myself yet).
dooze
firstly, i'm running a backend recording dvb-t streams, and xbmc doesn't like streaming from a nuv with one of these mpeg-2 streams unless there's about 5 seconds of data available already. i've hacked in a dialog between the request to the backend and the call to play in the scripts so i can wait a few seconds before proceeding, but it's not really ideal. if i get in too quickly the resulting stream often crashes xbmc. i've reduced the smb cache sizes right down which helps a little, but it doesn't fix the problem.
the other catch is that the scripts assume the stream is coming from tuner 1, my backend is set up to use "tuner 13", hence the scripts can't find the right .nuv ringbuffer. maybe the tuner number comes back in the response from the server or something, i dunno, but it might be worth looking into for completeness (i haven't had a chance to look myself yet).
dooze